Hi! I have installed svn_62 a few days ago and thought to give zfs boot a try. I followed the manual instructions and was able to get everything up and running with a zfs boot/root environment. After some tweaking (adding 2. Disk to the rootpool, moving some files from some old zfs fs to the rootpool etc ) I''ve tried a reboot to see if everything comes up again, I got boot loop. The error message isn''t detectable, but I suppose it is a kernel panic since he does not find his root fs System is a Intel PiV based NN system with 2 PATA Disks @ 250GB on c0d0 and c0d1 and 2 SATA Disks @80 GB on c2d0 and c3d0. The root pool is on mirror c0d0s0 and c0d1s0 and I am able to boot into the failsafe mode and import the rootpool there. Any hints how I can tell the boot process to find it''s root fs? cheerio Steve This message posted from opensolaris.org
Matthew B Sweeney - Sun Microsystems Inc.
2007-May-11 19:17 UTC
[zfs-discuss] Lost in boot loop..
Hey Steve, Not that I can help you out but I''m in the same boat. I''m using nv63 with the zfsbootkit. I''ve build a DVD after patching the netinstall. The instructions work fine, but I get the boot loop you describe. I haven''t been able to catch the error yet, even with a boot -allthezfsstuff -avr. I can see it reads the disk and it loads the ata driver and then something goes by very quickly and I get into the loop. I''m running nv B63 n a Toshiba tecra M3. Previously I had a windoze partition in addition to the Solaris partition. I'' tried with the whole disk to see if that improves the situation,but alas, I''m still looping. Matt Steffen Weinreich wrote:> Hi! > > I have installed svn_62 a few days ago and thought to give zfs boot a try. I followed the manual instructions and was able to get everything up and running with a zfs boot/root environment. > > After some tweaking (adding 2. Disk to the rootpool, moving some files from some old zfs fs to the rootpool etc ) I''ve tried a reboot to see if everything comes up again, I got boot loop. The error message isn''t detectable, but I suppose it is a kernel panic since he does not find his root fs > System is a Intel PiV based NN system with 2 PATA Disks @ 250GB on c0d0 and c0d1 and 2 SATA Disks @80 GB on c2d0 and c3d0. The root pool is on mirror c0d0s0 and c0d1s0 and I am able to boot into the failsafe mode and import the rootpool there. > > Any hints how I can tell the boot process to find it''s root fs? > > cheerio > Steve > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
zfs boot should work on b62, but does not work on b63 (see bug 6553537). This bug is supposed to be fixed in b65 (I''m testing the most recent nevada bits today to verify the fix). I''m not sure what''s up with the build 62 problem that Steffen is having. Steffen, if you''ll send me more information I''ll try to help figure it out. Lori Matthew B Sweeney - Sun Microsystems Inc. wrote:> Hey Steve, > > Not that I can help you out but I''m in the same boat. I''m using nv63 > with the zfsbootkit. I''ve build a DVD after patching the netinstall. > The instructions work fine, but I get the boot loop you describe. I > haven''t been able to catch the error yet, even with a boot > -allthezfsstuff -avr. I can see it reads the disk and it loads the > ata driver and then something goes by very quickly and I get into the > loop. > > I''m running nv B63 n a Toshiba tecra M3. Previously I had a windoze > partition in addition to the Solaris partition. I'' tried with the > whole disk to see if that improves the situation,but alas, I''m still > looping. > Matt > > > > Steffen Weinreich wrote: >> Hi! >> >> I have installed svn_62 a few days ago and thought to give zfs boot a >> try. I followed the manual instructions and was able to get >> everything up and running with a zfs boot/root environment. >> After some tweaking (adding 2. Disk to the rootpool, moving some >> files from some old zfs fs to the rootpool etc ) I''ve tried a reboot >> to see if everything comes up again, I got boot loop. The error >> message isn''t detectable, but I suppose it is a kernel panic since he >> does not find his root fs System is a Intel PiV based NN system with >> 2 PATA Disks @ 250GB on c0d0 and c0d1 and 2 SATA Disks @80 GB on >> c2d0 and c3d0. The root pool is on mirror c0d0s0 and c0d1s0 and I am >> able to boot into the failsafe mode and import the rootpool there. >> Any hints how I can tell the boot process to find it''s root fs? >> >> cheerio >> Steve >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Hi Lori et al, I am not 100% sure that it breaks in zfs. I have managed to attach a serial console to the machine and I see the following in the boot process after booting into the kernel debugger: Welcome to kmdb kmdb: unable to determine terminal type: assuming `vt100'' Loaded modules: [ unix krtld genunix ] [0]> :c WARNING: cannot open system file: etc/system SunOS Release 5.11 Version snv_62 32-bit Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. panic[cpu0]/thread=fec217e0: read_binding_file: /etc/name_to_major file not found fec3a874 genunix:read_binding_file+278 (fec51df3, fec8bef0,) fec3a898 genunix:mod_setup+1c (fe84006e, 3, fec3a8) fec3a8a8 unix:startup_modules+35 (fec3a8c4, fe912222,) fec3a8b0 unix:startup+2b (fe800010, fec36680,) fec3a8c4 genunix:main+1e () panic: entering debugger (no dump device, continue to reboot) kmdb: target stopped at: kmdb_enter+0xa: pushl %eax [0]> I have checked the boot_archive by booting into the failsave mode importing the zfs pool and running # ./sbin/bootadm list-archive -R /tmp/root/b [..] etc/system etc/name_to_major etc/driver_aliases [..] etc/zfs/zpool.cache # now I somehow lost in space ;-) cheerio Steve This message posted from opensolaris.org
A few of us used the same b62 boot images, with some having the boot loop problems and some not. It seems it may have been related to the specific profile used. Could you post the contents of your pfinstall profile? Thanks, Malachi On 5/14/07, Steffen Weinreich <steve at weinreich.org> wrote:> > Hi Lori et al, > > I am not 100% sure that it breaks in zfs. I have managed to attach a > serial console to the machine and I see the following in the boot process > after booting into the kernel debugger: > > > > Welcome to kmdb > kmdb: unable to determine terminal type: assuming `vt100'' > Loaded modules: [ unix krtld genunix ] > [0]> :c > WARNING: cannot open system file: etc/system > SunOS Release 5.11 Version snv_62 32-bit > Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved. > Use is subject to license terms. > > panic[cpu0]/thread=fec217e0: read_binding_file: /etc/name_to_major file > not found > fec3a874 genunix:read_binding_file+278 (fec51df3, fec8bef0,) > fec3a898 genunix:mod_setup+1c (fe84006e, 3, fec3a8) > fec3a8a8 unix:startup_modules+35 (fec3a8c4, fe912222,) > fec3a8b0 unix:startup+2b (fe800010, fec36680,) > fec3a8c4 genunix:main+1e () > > panic: entering debugger (no dump device, continue to reboot) > kmdb: target stopped at: > kmdb_enter+0xa: pushl %eax > [0]> > > I have checked the boot_archive by booting into the failsave mode > importing the zfs pool and running > > # ./sbin/bootadm list-archive -R /tmp/root/b > [..] > etc/system > etc/name_to_major > etc/driver_aliases > [..] > etc/zfs/zpool.cache > # > > now I somehow lost in space ;-) > > cheerio > Steve > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070514/eb65942a/attachment.html>