Charles Menser
2009-Sep-23 12:35 UTC
[zfs-discuss] [indiana-discuss] Boot failure with snv_122 and snv_123
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: ide at 0, ata0
ata0 is /pci at 0,0/pci-ide at 14,1/ide at 0
PCI Express-device: pci1002,597a at 4, pcieb1
pcieb1 is /pci at 0,0/pci1002,597a at 4
PCI Express-device: pci1002,597d at 7
pcieb3 is /pci at 0,0/pci1002,597d at 7
UltraDMA mode 4 selected
sd4 at ata0: target 0 lun 0
sd4 is /pci at 0,0/pci-ide at 14,1/ide at 0/sd at 0,0
NOTICE: Can not read the pool label from ''/pci at 0,0/pci1043,8231 at
12/disk at 0,0:a''
NOTICE: spa_import_rootpool: error 5
Cannot mount root on /pci at 0,0/pci1043,8231 at 12/disk at 0,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc2efe0: vfs_mountroot: cannot mount root
fffffffffbc50ce0 genunix:vfs_mountroot+350 ()
fffffffffbc50d10 genunix:main+e7 ()
fffffffffbc50d20 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(fffffffffb934340)
panicsys+0x41c(fffffffffbb89070, fffffffffbc50c70, fffffffffbc58e80, 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: ide at 0, ata0
> > ata0 is /pci at 0,0/pci-ide at 14,1/ide at 0
> > PCI Express-device: pci1002,597a at 4, pcieb1
> > pcieb1 is /pci at 0,0/pci1002,597a at 4
> > PCI Express-device: pci1002,597d at 7
> > pcieb3 is /pci at 0,0/pci1002,597d at 7
> > UltraDMA mode 4 selected
> > sd4 at ata0: target 0 lun 0
> > sd4 is /pci at 0,0/pci-ide at 14,1/ide at 0/sd at 0,0
> > NOTICE: Can not read the pool label from
> ''/pci at 0,0/pci1043,8231 at 12/disk at 0,0:a''
> > NOTICE: spa_import_rootpool: error 5
> > Cannot mount root on
> /pci at 0,0/pci1043,8231 at 12/disk at 0,0:a fstype zfs
> >
> > panic[cpu0]/thread=fffffffffbc2efe0: vfs_mountroot:
> cannot mount root
> >
> > fffffffffbc50ce0 genunix:vfs_mountroot+350 ()
> > fffffffffbc50d10 genunix:main+e7 ()
> > fffffffffbc50d20 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(fffffffffb934340)
> > panicsys+0x41c(fffffffffbb89070, fffffffffbc50c70,
> fffffffffbc58e80, 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:
> >
> > charles at 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 done, the
> pool will no longer be accessible on older
> software versions.
> scrub: none requested
> config:
> >
> > NAME STATE READ WRITE CKSUM
> > rpool ONLINE 0 0 0
> > mirror ONLINE 0 0 0
> > c7t0d0s0 ONLINE 0 0 0
> > c7t1d0s0 ONLINE 0 0 0
> > c7t3d0s0 ONLINE 0 0 0
> >
> > errors: No known data errors
> >
> > charles at carbon-box:~$ zpool upgrade
> > This system is currently running ZFS pool version
> 18.
> >
> > The following pools are out of date, and can be
> upgraded. After being
> > upgraded, these pools will no longer be accessible
> by older software versions.
> >
> > VER POOL
> > --- ------------
> > 14 rpool
> >
> > Use ''zpool upgrade -v'' for a list of available
> versions and their associated
> > features.
> >
> > charles at carbon-box:~$ zfs upgrade
> > This system is currently running ZFS filesystem
> version 4.
> >
> > The following filesystems are out of date, and can
> be upgraded. After being
> > upgraded, these filesystems (and any ''zfs send''
> streams generated from
> > subsequent snapshots) will no longer be accessible
> by older software versions.
> >
> >
> > VER FILESYSTEM
> > --- ------------
> > 3 rpool
> > 3 rpool/ROOT
> > 3 rpool/ROOT/opensolaris
> > 3 rpool/ROOT/opensolaris-1
> > 3 rpool/ROOT/opensolaris-2
> > 3 rpool/ROOT/opensolaris-3
> > 3 rpool/ROOT/opensolaris-4
> > 3 rpool/export
> > 3 rpool/export/home
> > 3 rpool/export/home/charles
> > 3 rpool/export/home/charles/vm
> > 3 rpool/export/home/charles/vm/centos
> > 3 rpool/export/home/charles/vm/debian
> > 3 rpool/export/home/charles/vm/openbsd
> > 3 rpool/export/home/charles/vm/opensolaris
> > 3 rpool/export/home/charles/vm/solaris-10
> > 3
> rpool/export/home/charles/vm/ubuntu-9.04-desktop
> 3 rpool/export/home/charles/vm/ubuntu-9.10-desktop
> 3 rpool/export/home/charles/vm/windows-7
> 3 rpool/export/home/charles/vm/xp-base
> 3 rpool/tftp
> >
> > charles at carbon-box:~$ zfs get all rpool
> > NAME PROPERTY VALUE
> SOURCE
> filesystem -
> on Sun Aug 9 13:58 2009
> -
> sed 63.0G
> -
> 394G -
> nced 82K
> -
> 1.42x -
> ted yes
> -
> none default
> rvation none
> default
> 128K default
> point /rpool
> default
> off
> default
> on default
> ression on
> local
> on default
> ices on
> default
> on default
> uid on
> default
> off default
> ed off
> default
> hidden default
> ode groupmask
> default
> restricted
> default
> on
> default
> off default
> tr on
> default
> 1 default
> sion 3
> -
> off -
> rmalization none
> -
> sensitive -
> off
> default
> off default
> esmb off
> default
> none default
> eservation none
> default
> all default
> darycache all
> default
> 0 -
> bydataset 82K
> -
> 63.0G -
> byrefreservation 0
> -
> n:install ready local
> >
> > What next?
> >
> > Thanks,
> > Charles
> >
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-d
> iscuss
--
This message posted from opensolaris.org