Difference between revisions of "Nokia boot failed due to raid mirror"
From cpwiki.net
(→activate raid volume) |
(→relabel volume metadata (ipso 6.x)) |
||
| (8 intermediate revisions by one user not shown) | |||
| Line 3: | Line 3: | ||
Nokia firewall fails to boot off a RAID pair of drives moved from another chassis. This is because the volume is deactivated when moved between systems. | Nokia firewall fails to boot off a RAID pair of drives moved from another chassis. This is because the volume is deactivated when moved between systems. | ||
| − | + | '''Errors:''' | |
Boot manager loaded. | Boot manager loaded. | ||
Entering autoboot mode. | Entering autoboot mode. | ||
Type any character to enter command mode. | Type any character to enter command mode. | ||
Error: /image on /dev/mirror/gmroots1f | Error: /image on /dev/mirror/gmroots1f | ||
| − | + | does not exist or is not a file | |
umount: /mnt: not a file system root directory | umount: /mnt: not a file system root directory | ||
boot failed | boot failed | ||
| Line 78: | Line 78: | ||
<br> | <br> | ||
Volume 0 is Bus 0 Target 0, Type IM (Integrated Mirroring) | Volume 0 is Bus 0 Target 0, Type IM (Integrated Mirroring) | ||
| − | Volume State: degraded, enabled, resync in progress | + | Volume State: '''degraded, enabled, resync in progress''' |
Volume Settings: write caching enabled, auto configure | Volume Settings: write caching enabled, auto configure | ||
Volume draws from Hot Spare Pools: 0 | Volume draws from Hot Spare Pools: 0 | ||
| Line 113: | Line 113: | ||
Type 'boot <enter>' to continue boot process .. | Type 'boot <enter>' to continue boot process .. | ||
| − | If the device O.S. is ipso 4.x, then you are done and it should be ready to boot. If ipso 6.x, continue... | + | If the device O.S. is ipso 4.x, then you are done and it should be ready to boot. The raid will likely show degraded and resync in progress, but it is usable during the resync. |
| + | |||
| + | If ipso 6.x, continue... | ||
=== relabel volume metadata (ipso 6.x)=== | === relabel volume metadata (ipso 6.x)=== | ||
'''check macbase data for mismatch''' | '''check macbase data for mismatch''' | ||
| + | |||
| + | A mismatch in the mirror metadata for the macbase will cause the mounting of the root file system to fail. This will be the case when trying to boot off a drive pair from another device. | ||
| + | |||
| + | 1) Determine the name of the disk device. This varies by platform. | ||
| + | |||
| + | BOOTMGR[2]> '''sysinfo''' | ||
| + | CPU 0: 2793 MHz Intel(R) Xeon(TM) CPU 2.80GHz | ||
| + | Memory: 2100350976 (2004M bytes) | ||
| + | Disk Devices: | ||
| + | IO port 0x1f0 adc0: unit 0 (ad0): <STI Flash 8.0.0> | ||
| + | 1024MB (2001888 sectors), 1986 cyls, 16 heads, 63 S/T | ||
| + | IO port 0x6088 adc2: unit 0 ('''ad4'''): <FUJITSU MHY2080BS> | ||
| + | 80026MB (156301488 sectors), 16383 cyls, 16 heads, 63 S/T | ||
| + | |||
| + | |||
| + | 2) Enter maintenance shell | ||
| + | |||
| + | BOOTMGR[5]> '''sh''' | ||
| + | |||
| + | This command should result in a new # prompt. | ||
| + | |||
| + | 3) Check mac address in the raid label | ||
| + | |||
| + | # '''gmirror dump da0s1''' | ||
| + | Metadata on da0: | ||
| + | magic: GEOM::MIRROR | ||
| + | version: 4 | ||
| + | name: gmroots1 | ||
| + | mid: 2548360505 | ||
| + | did: 1949224550 | ||
| + | all: 1 | ||
| + | genid: 0 | ||
| + | syncid: 1 | ||
| + | priority: 0 | ||
| + | slice: 4096 | ||
| + | balance: round-robin | ||
| + | mediasize: 79857450496 | ||
| + | sectorsize: 512 | ||
| + | syncoffset: 0 | ||
| + | mflags: NOAUTOSYNC | ||
| + | dflags: NONE | ||
| + | hcprovider: | ||
| + | provsize: 79857451008 | ||
| + | macbase: 0 a0 8e c1 97 10 | ||
| + | MD5 hash: 7f666d5c5c279faa7fb7a1d42b43555d | ||
| + | |||
| + | 4) Check hardware mac address | ||
| + | |||
| + | # '''ipsctl -a hw:eeprom:mac_addr_base''' | ||
| + | hw:eeprom:mac_addr_base = 0:a0:8e:be:aa:50 | ||
| + | |||
| + | 5) compare the mac_addr_base to the macbase above. if mis-matched, then relabel... | ||
| + | |||
| + | |||
| + | '''relabel volume metadata''' | ||
| + | |||
| + | # '''gmirror deactivate gmroots1 ad4s1''' (It’s OK if this command returns an error) | ||
| + | # '''gmirror clear ad4s1''' | ||
| + | # '''gmirror label –v –n –b round-robin gmroots1 ad4s1''' | ||
| + | |||
| + | system should now boot! | ||
| + | |||
| + | == links == | ||
| + | taken from [http://dl3.checkpoint.com/paid/43/RAID.pdf?HashKey=1411187746_b3e9208e053682b1d5b208df8b23cf82&xtn=.pdf raid.doc] | ||
| + | |||
| + | [[category:nokia]] | ||
Latest revision as of 20:39, 7 January 2015
Contents |
Problem
Nokia firewall fails to boot off a RAID pair of drives moved from another chassis. This is because the volume is deactivated when moved between systems.
Errors:
Boot manager loaded. Entering autoboot mode. Type any character to enter command mode. Error: /image on /dev/mirror/gmroots1f does not exist or is not a file umount: /mnt: not a file system root directory boot failed
Solution
activate raid volume
BOOTMGR[1]> raid -------------------------------------------------------- IPSO LSI Logic Configuration Utility version : Version 0.5, June 8, 2007 -------------------------------------------------------- Adapter Type ............. 3 (SAS Adapter) PCI Device ID ............ 0x0056 Hardware Revision ID ..... 0x0004 Devices in Volume ........ 0 FW Version ............... (01.18.00.00) decimal MPI Version of FW ........ MPI Version 1.5.13.0 -------------------------------------------------------- 1) Raid Options Sub-Menu 2) Firmware operations q) EXIT -------------------------------------------------------- Choose an option: 1 ------------------- RAID MENU -------------------------- 1) Show volume(s) 2) Show physical disk(s) 3) Get Volume Status
Options below available from boot manager ----------------------------------------- 10) Disable volume 11) Enable volume 12) Deactivate volume 13) Activate volume 30) Create RAID Volume 31) Delete RAID Volume q) Main Menu -------------------------------------------------------- Choose an option: 13 Volume: [0-1 or RETURN to quit] 0
Volume 0 is being activated
Changes made, doing a camcontrol rescan Re-scan of bus 0 was successful Re-scan of bus 0 was successful Waiting 5 seconds for SCSI devices to settle ...... done ------------------- RAID MENU -------------------------- 1) Show volume(s) 2) Show physical disk(s) 3) Get Volume Status
Options below available from boot manager ----------------------------------------- 10) Disable volume 11) Enable volume 12) Deactivate volume 13) Activate volume 30) Create RAID Volume 31) Delete RAID Volume q) Main Menu --------------------------------------------------------
Choose an option: 1 ------------------ Show Volumes ------------------------ 1 volume is active, 2 physical disks are active
Volume 0 is Bus 0 Target 0, Type IM (Integrated Mirroring) Volume State: degraded, enabled, resync in progress Volume Settings: write caching enabled, auto configure Volume draws from Hot Spare Pools: 0 Volume Size 76158 MB, Stripe Size 0 KB, 2 Members Primary is PhysDisk 0 (Bus 0 Target 4) Secondary is PhysDisk 1 (Bus 0 Target 1)
------------------- RAID MENU -------------------------- 1) Show volume(s) 2) Show physical disk(s) 3) Get Volume Status
Options below available from boot manager ----------------------------------------- 10) Disable volume 11) Enable volume 12) Deactivate volume 13) Activate volume 30) Create RAID Volume 31) Delete RAID Volume q) Main Menu -------------------------------------------------------- Choose an option: q -------------------------------------------------------- 1) Raid Options Sub-Menu 2) Firmware operations q) EXIT --------------------------------------------------------
Choose an option: q Re-scan of bus 0 was successful Re-scan of bus 0 was successful Waiting 5 seconds for SCSI devices to settle .. Type 'boot <enter>' to continue boot process ..
If the device O.S. is ipso 4.x, then you are done and it should be ready to boot. The raid will likely show degraded and resync in progress, but it is usable during the resync.
If ipso 6.x, continue...
relabel volume metadata (ipso 6.x)
check macbase data for mismatch
A mismatch in the mirror metadata for the macbase will cause the mounting of the root file system to fail. This will be the case when trying to boot off a drive pair from another device.
1) Determine the name of the disk device. This varies by platform.
BOOTMGR[2]> sysinfo
CPU 0: 2793 MHz Intel(R) Xeon(TM) CPU 2.80GHz
Memory: 2100350976 (2004M bytes)
Disk Devices:
IO port 0x1f0 adc0: unit 0 (ad0): <STI Flash 8.0.0>
1024MB (2001888 sectors), 1986 cyls, 16 heads, 63 S/T
IO port 0x6088 adc2: unit 0 (ad4): <FUJITSU MHY2080BS>
80026MB (156301488 sectors), 16383 cyls, 16 heads, 63 S/T
2) Enter maintenance shell
BOOTMGR[5]> sh
This command should result in a new # prompt.
3) Check mac address in the raid label
# gmirror dump da0s1
Metadata on da0:
magic: GEOM::MIRROR
version: 4
name: gmroots1
mid: 2548360505
did: 1949224550
all: 1
genid: 0
syncid: 1
priority: 0
slice: 4096
balance: round-robin
mediasize: 79857450496
sectorsize: 512
syncoffset: 0
mflags: NOAUTOSYNC
dflags: NONE
hcprovider:
provsize: 79857451008
macbase: 0 a0 8e c1 97 10
MD5 hash: 7f666d5c5c279faa7fb7a1d42b43555d
4) Check hardware mac address
# ipsctl -a hw:eeprom:mac_addr_base hw:eeprom:mac_addr_base = 0:a0:8e:be:aa:50
5) compare the mac_addr_base to the macbase above. if mis-matched, then relabel...
relabel volume metadata
# gmirror deactivate gmroots1 ad4s1 (It’s OK if this command returns an error) # gmirror clear ad4s1 # gmirror label –v –n –b round-robin gmroots1 ad4s1
system should now boot!
links
taken from raid.doc
