Instructions to Re-provision Oracle Big Data Appliance USB Partition upon Corruption or Replacement

Asset ID:	1-71-1900993.1
Update Date:	2017-12-21
Keywords:

Solution Type Technical Instruction Sure

Solution 1900993.1 : Instructions to Re-provision Oracle Big Data Appliance USB Partition upon Corruption or Replacement

Applies to:

Big Data Appliance Hardware - Version All Versions and later
Big Data Appliance Integrated Software - Version 2.2.1 and later
Linux x86-64

Goal

This document provides instructions to re-provision the internal USB drive on a Oracle Big Data Appliance (BDA) server in case it is corrupted or has been replaced.

Solution

When USB partition is corrupted below errors may be noticed while re-imaging the cluster or during mammoth installations or while executing bdachecksw/bdacheckcluster. Similar errors may be seen when USB is replaced as well.

SUCCESS: Correct internal USB device (sdm) : 1
WARNING: Wrong internal USB partitions :
INFO: Expected internal USB partitions : 1 primary ext3 or 1 ext4 primary
...............
WARNING: Big Data Appliance warnings during software validation checks

Trying to mount the USB partition also results in below error

# mount /usbdisk
mount: special device LABEL=BDAUSB does not exist

Commands to display USB partition table results in below error

# parted /dev/sdm -s print
Error: /dev/sdm: unrecognised disk label

# parted /dev/sdm1 -s print
Error: /dev/sdm1: unrecognised disk label

Use the bdaredousb script to re-provision a new internal USB drive or corrupted internal USB drive. The bdaredousb script will prompt to confirm that the internal USB drive will be completely wiped and then proceed to completely wipe and re-provision the internal USB drive.

On BDA versions less than 3.x and lower use the attached is bdaredousb script.

On BDA versions 4.x and higher use the bdaredousb script that is shipped with the BDA.

Below steps need to be performed as root user on the node where the USB partition is corrupted or replaced

1) Copy the bdaredousb script into /tmp directory. Ensure execute privileges are correctly set for root/owner.

# ls -l /tmp/bdaredousb
-rwxr--r-- 1 root root 7310 Jun 25 08:18 /tmp/bdaredousb

2) Pick node in the same BDA cluster so USB contents from that node will be used to format the USB on the current node . Pass that node as an argument to bdaredousb script.

# /tmp/bdaredousb <Node in the same BDA cluster with Functional usb>

Say for example mybda10.us.oracle.com is in the same cluster as the node with corrupted/replaced USB then command to execute bdaredousb would be

# /tmp/bdaredousb mybda10.us.oracle.com

Sample Output from BDA 3.0.*

Internal USB will be formatted and its contents will be replaced.
Do you want to continue with this operation? (y/n): y
mke2fs 1.41.12 (17-May-2010)
Filesystem label=BDAUSB
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
244800 inodes, 978432 blocks
48921 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1002438656
30 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.12 (17-May-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds

Copying content from <Functional-BDA-Node>... this will take some time
7831552+0 records in
7831552+0 records out
4009754624 bytes (4.0 GB) copied, 341.012 s, 11.8 MB/s
0+148886 records in
0+148886 records out
4009754624 bytes (4.0 GB) copied, 348.247 s, 11.5 MB/s
Finished copying USB contents from <Functional-BDA-Node>
Mounting USB
Patching network files for USB
BdaAdmNwSetup: Start time                = Tue Jun 24 20:09:10 PDT 2014
BdaAdmNwSetup: Using local files         = false
/dev/sdm1 on /usbdisk type ext4 (rw)
BdaAdmNwSetup: Apply nws settings on uds = true
BdaAdmNwSetup: Apply dns settings        = true
BdaAdmNwSetup: Apply ntp settings        = true
BdaAdmNwSetup: Apply ssh settings        = true
BdaAdmNwSetup: Apply bondib0 settings    = false
BdaAdmNwSetup: Apply eth0 settings       = true
BdaAdmNwSetup: Apply ilom settings       = false
BdaAdmNwSetup: Apply /etc/hosts settings = false
BdaAdmNwSetup: Set timezone              = true
BdaAdmNwSetup: Set host name             = false
BdaAdmNwSetup: Creating                  = /usbdisk/etc/sysconfig/network-scripts/ifcfg-eth0
BdaAdmNwSetup: Creating                  = /usbdisk/etc/sysconfig/network
BdaAdmNwSetup: Append to                 = /usbdisk/etc/ntp.conf
bdasettime: restarting ntp service
bdasettime: find working ntp server in list 10.***.40.1 10.***.56.1 10.***.128.1
server 10.***.40.1, stratum 3, offset -0.000033, delay 0.02600
24 Jun 20:09:13 ntpdate[1845]: adjust time server 10.133.40.1 offset -0.000033 sec
bdasettime: using ntp server 10.***.40.1
Shutting down ntpd:                                        [ OK ]
24 Jun 20:09:13 ntpdate[1860]: step time server 10.***.40.1 offset -0.000027 sec
Starting ntpd:                                             [ OK ]
BdaAdmNwSetup: Append to                 = /usbdisk/etc/resolv.conf
BdaAdmNwSetup: Append to                 = /usbdisk/etc/ssh/sshd.conf
BdaAdmNwSetup: Reset                     = /usbdisk/etc/clock
BdaAdmNwSetup: Reset                     = /usbdisk/etc/localtime link
Unmounting USB

Note:- Support to 'Patching network files for USB' is added starting with BDA 3.0.* release

Sample Output from BDA 2.*

Attachments

This solution has no attachment