Difference between revisions of "Nokia boot failed due to raid mirror"
From cpwiki.net
(→Problem) |
(→Problem) |
||
| 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. | ||
Revision as of 04:30, 20 September 2014
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. 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.
# ipsctl -a hw:eeprom:mac_addr_base hw:eeprom:mac_addr_base = 0:a0:8e:be:aa:50
# gmirror list Geom name: gmroots1 State: COMPLETE Components: 1 Balance: round-robin Slice: 4096 Flags: NOAUTOSYNC GenID: 0 SyncID: 1 ID: 2548360505 Providers: 1. Name: mirror/gmroots1 Mediasize: 79857450496 (74G) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: da0s1 <<<<<<<<<<<<<<<<<<<<< root device Mediasize: 79857451008 (74G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: NONE GenID: 0 SyncID: 1 ID: 1949224550
# 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 <<<<<<<<<<<<<<<< compare to macbase above, if mis-matched, then relabel...
MD5 hash: 7f666d5c5c279faa7fb7a1d42b43555d
relabel volume metadata
# gmirror deactivate gmroots1 da0s1 (It’s OK if this command returns an error) # gmirror clear da0s1 # gmirror label –v –n –b round-robin gmroots1 da0s1
