Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2355720.1
Update Date:2018-02-05
Keywords:

Solution Type  Technical Instruction Sure

Solution  2355720.1 :   How to Check if the USB is Corrupt on a BDA Server  


Related Items
  • Big Data Appliance X5-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>BDA>Big Data Appliance>DB: BDA_EST
  •  




In this Document
Goal
Solution
References


Applies to:

Big Data Appliance X5-2 Hardware - Version All Versions and later
Linux x86-64

Goal

How to check if a USB is corrupt after following "Rebooting a BDA Server Leads to a Black Screen with Blinking Cursor Instead of the Grub Menu (Doc ID 2142573.1)?"

Solution

To verify if the USB is corrupt on a server do the following as 'root' user on that server.

Note: None of the checks below are disruptive and no downtime is needed.

1. First run bdacheckhw:

# bdacheckhw

Successful output with regards to the USB looks like:

...
SUCCESS: Correct internal USB device identified (sdm) : 1
SUCCESS: Sufficient internal USB size (>=4000): 8011
SUCCESS: Sufficient internal USB size (<=17000): 8011
...

2. Run bdachecksw:

# bdachecksw

Output showing that the USB is healthy looks like:

...
SUCCESS: Correct internal USB device (sdm) : 1
SUCCESS: Correct internal USB partitions : 1 ext4 primary
SUCCESS: Correct internal USB ext3 partition check : clean
... 

3. If neither bdacheckhw nor bdachecksw report errors with regards to the USB, the USB drive should be healthy.  However the recommendation is to continue with the following checks to confirm USB health.

Compare the output on the node experiencing issues with one which is not.

If the following checks do not indicate a problem with the USB then no further action is needed to confirm the USB health.

a) Run the following parted command where /dev/sdm is the USB location.  Verify that the output of the parted command is the same on as on a server where the USB disk has no detectable issues.

# parted /dev/sdm p

Example output is like:

# parted /dev/sdm p
Model: ORACLE SSM (scsi)
Disk /dev/sdm: 8011MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 8010MB 8009MB ext4 primary

b) Run e2fsck:

# e2fsck /dev/sdm1

Example output: 

# e2fsck /dev/sdm1
  
e2fsck 1.43-WIP (20-Jun-2013)
BDAUSB: clean, 126277/489600 files, 1013943/1955328 blocks

c) Mount /usbdisk and check the space.  Then un-mount it.

# mount /usbdisk
# df -h /usbdisk  
# umount /usbdisk

Example output:

 # mount /usbdisk
  
# df -h /usbdisk
  
Filesystem Size Used Avail Use% Mounted on
/dev/sdm1 7.3G 3.7G 3.3G 54% /usbdisk
# umount /usbdisk 

  

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback