Re: [zfs-discuss] [indiana-discuss] Boot failure with snv_122 and snv_123

2009-11-14 Thread peter brouwer
Has this issue been solved yet? I see the same issue when trying to upgrade 
from 112 to 126.
-- 
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] [indiana-discuss] Boot failure with snv_122 and snv_123

2009-09-23 Thread Charles Menser
Cross-posted to ZFS-Discuss per Vikram's suggestion.

Summary: I upgraded to snv_123 and the system hangs on boot. snv_121, and 
earlier are working fine.

Booting with -kv, the system still hung, but after a few minutes, the system 
continued, spit out more text (referring to disks, but I could not capture the 
text). Here is what was left on the screen once the debugger kicked in:

PCI Express-device: i...@0, ata0
ata0 is /p...@0,0/pci-...@14,1/i...@0
PCI Express-device: pci1002,5...@4, pcieb1
pcieb1 is /p...@0,0/pci1002,5...@4
PCI Express-device: pci1002,5...@7
pcieb3 is /p...@0,0/pci1002,5...@7
UltraDMA mode 4 selected
sd4 at ata0: target 0 lun 0
sd4 is /p...@0,0/pci-...@14,1/i...@0/s...@0,0
NOTICE: Can not read the pool label from '/p...@0,0/pci1043,8...@12/d...@0,0:a'
NOTICE: spa_import_rootpool: error 5
Cannot mount root on /p...@0,0/pci1043,8...@12/d...@0,0:a fstype zfs

panic[cpu0]/thread=fbc2efe0: vfs_mountroot: cannot mount root

fbc50ce0 genunix:vfs_mountroot+350 ()
fbc50d10 genunix:main+e7 ()
fbc50d20 unix:_locore_start+92 ()

panic: entering debugger (do dump device, continue to reboot)

Then I ran ::stack and ::status:

[0]> ::stack
kmdb_enter+0xb()
debug_enter+0x38(fb934340)
panicsys+0x41c(fbb89070, fbc50c70, fbc58e80, 1)
vpanic+0x15c()
panic+0x94()
vfs_mountroot+0x350()
main+0xe7()
_locore_start+0x92()

[0]> ::status
debugging live kernel (64-bit) on (not set)
operating system: 5.11 snv_123 (i86pc)
CPU-specific support: AMD
DTrace state: inactive
stopped on: debugger entry trap


To clarify, when build 122 was announced, I tried upgrading. The new BE would 
not boot, hanging in the same way that snv_123 does. I later deleted the 
snv_122 BE.

Also, I checked my grub config, and nothing seems out of line there (though I 
have edited the boot entries to remove the splashimage, foreground, background, 
and console=graphics).

Thanks,
Charles


> Hi,
> 
> A problem with your root pool - something went wrong
> when you upgraded 
> which explains why snv_122 no longer works as well.
> One of the ZFS 
> experts on this list could help you - I suspect
> others may have run into 
> similar issues before.
> 
> Vikram
> 
> Charles Menser wrote:
> > Vikram,
> >
> > Thank you for the prompt reply!
> >
> > I have made no BIOS changes. The last time I
> changed the BIOS was before reinstalling OpenSolaris
> 2009.06 after changing my SATA controller to AHCI
> mode. This was some time ago, and I have been using
> the /dev repo and installed several development
> builds since then (the latest that worked was
> snv_121).
> >
> > I switched to a USB keyboard and mdb was happy. I
> am curious why a PS/AUX keyboard works with the
> system normally, but not MDB.
> >
> > Here is what I have from MDB so far:
> >
> > I rebooted with -kv, and after a few minutes, the
> system continued, spit out more text (referring to
> disks, but I could not capture the text). Here is
> what was left on the screen once the debugger kicked
> in:
> >
> > PCI Express-device: i...@0, ata0
> > ata0 is /p...@0,0/pci-...@14,1/i...@0
> > PCI Express-device: pci1002,5...@4, pcieb1
> > pcieb1 is /p...@0,0/pci1002,5...@4
> > PCI Express-device: pci1002,5...@7
> > pcieb3 is /p...@0,0/pci1002,5...@7
> > UltraDMA mode 4 selected
> > sd4 at ata0: target 0 lun 0
> > sd4 is /p...@0,0/pci-...@14,1/i...@0/s...@0,0
> > NOTICE: Can not read the pool label from
> '/p...@0,0/pci1043,8...@12/d...@0,0:a'
> > NOTICE: spa_import_rootpool: error 5
> > Cannot mount root on
> /p...@0,0/pci1043,8...@12/d...@0,0:a fstype zfs
> >
> > panic[cpu0]/thread=fbc2efe0: vfs_mountroot:
> cannot mount root
> >
> > fbc50ce0 genunix:vfs_mountroot+350 ()
> > fbc50d10 genunix:main+e7 ()
> > fbc50d20 unix:_locore_start+92 ()
> >
> > panic: entering debugger (do dump device, continue
> to reboot)
> >
> > [again, the above is hand transcribed, and may
> contain typos]
> >
> > Then I ran ::stack and ::status:
> >
> > [0]> ::stack
> > kmdb_enter+0xb()
> > debug_enter+0x38(fb934340)
> > panicsys+0x41c(fbb89070, fbc50c70,
> fbc58e80, 1)
> > vpanic+0x15c()
> > panic+0x94()
> > vfs_mountroot+0x350()
> > main+0xe7()
> > _locore_start+0x92()
> >
> > [0]> ::status
> > debugging live kernel (64-bit) on (not set)
> > operating system: 5.11 snv_123 (i86pc)
> > CPU-specific support: AMD
> > DTrace state: inactive
> > stopped on: debugger entry trap
> >
> > The motherboard is an ASUS M3A32-MVP, with BIOS Rev
> 1705.
> >
> > There are four 500G SATA drives connected to the
> on-board SATA controller.
> >
> > There is only one pool (rpool), setup as a
> three-way mirror:
> >
> > char...@carbon-box:~$ zpool status
> >   pool: rpool
> >  state: ONLINE
> > status: The pool is formatted using an older
> on-disk format.  The pool can
> > still be used, but some features are
> unavailable.
> > action: Upgrade the pool using 'zpool upgrade'.
>  Once this is