5.5 HP StorageWorks X9720 Network Storage System Administrator Guide (AW549-96026, March 2011)

1. Log on to the server.
2. Start hp-ilo:
# service hp-ilo start
3. Flash the power PIC:
# /opt/hp/mxso/firmware/power_pic_scexe
4. Reboot the server.
ibrix_fs -c failed with "Bad magic number in super-block"
If a file system creation command fails with an error like the following, it could be because the segment
creation command failed to preformat the LUN.
[root@eirosone1 configd]# ibrix_fs -c -f fs1 -s seg1_4
Calculated owner for seg1_4 : glory22
failed command (/usr/local/ibrix/bin/tuneibfs -F
3e2a9657-fc8b-46b2-96b0-1dc27e8002f3 -H glory2 -G 1 -N 1 -S fs1 -R 1
/dev/vg1_4/seg1_4 2>&1) status (1) output: (/usr/local/ibrix/bin/tuneibfs: Bad
magic number in super-block while trying to open /dev/vg1_4/seg1_4 Couldn't
find valid filesystem superblock. /usr/local/ibrix/bin/tuneibfs 5.3.461 Rpc
Version:5 Rpc Ports base=IBRIX_PORTS_BASE (Using EXT2FS Library version 1.32.1)
[ipfs1_open] reading superblock from blk 1 )
Iad error on host glory2
To workaround the problem re-create the segment on the failing LUN. For example to identify the
correct LUN associated with the failure above, run a command similar to the following on the first
server in the system. In the following example, server glory2 is the name of a file serving node:
# ibrix_pv -l -h glory2
PV_NAME SIZE(MB) VG_NAME DEVICE RAIDTYPE RAIDHOST RAIDDEVICE
------- -------- ------- --------------- -------- -------- ----------
d1 131070 vg1_1 /dev/mxso/dev4a
d2 131070 vg1_2 /dev/mxso/dev5a
d3 131070 vg1_3 /dev/mxso/dev6a
d5 23551 vg1_5 /dev/mxso/dev8a
d6 131070 vg1_4 /dev/mxso/dev7a
The Device column identifies the LUN number. The volume group vg1_4 is created from LUN 7.
Re-create the segment according to the instructions in the HP StorageWorks X9000 File Serving
Software User Guide.
After this command completes, rerun the file system creation command.
LUN status is failed
A LUN status of failed indicates that the logical drive has failed. This is usually the result of failure of
three or more disk drives. This can also happen if you remove the wrong disk drive when replacing
a failed disk drive.
If this situation occurs, take the following steps:
1. Carefully record any recent disk removal or reinsertion actions. Make sure you track the array,
box, and bay numbers and know which disk drive was removed or inserted.
X9720 Network Storage System Administrator Guide 125