Date: Fri, 11 Nov 2011 23:10:18 +0400 From: Darren Baginski <kickbsd@yandex.ru> To: Peter Maloney <peter.maloney@brockmann-consult.de> Cc: freebsd-fs@freebsd.org Subject: Re: Unable to boot from zfsroot 9.0-RC2 (while 9.0-RC1 boots fine) Message-ID: <67971321038618@web140.yandex.ru> In-Reply-To: <4EBD6AAF.5020401@brockmann-consult.de> References: <598941321021900@web148.yandex.ru> <4EBD6AAF.5020401@brockmann-consult.de>
next in thread | previous in thread | raw e-mail | index | archive | help
I did 'mfs' install years back . Please note, I'm not talking about *clean* install, but rather setup which worked for 8.0, 8.1, 8.2, 9.0-beta1, 9.0-beta2, 9.0-beta3, 9.0-RC1 up to November 8 (I csup-ing frequently on that box). But suddenly, today's 9.0-RC2 kernel from won't boot. I'm considering that as a regression, if something worked for so long time and stopped. Was there any changes related to subject in kernel ? 11.11.2011, 22:34, "Peter Maloney" <peter.maloney@brockmann-consult.de>: > Darren, > > Did you try the normal procedure, or is it something specific to version 9? > > *normal procedure:* > From a boot cd, do something like this: > > import, and if it fails, go ahead and use -f > # zpool import -o altroot=/z -o cachefile=/tmp/zpool.cache zroot > > # zfs set mountpoint=/ zroot > > # cp /tmp/zpool.cache /z/boot/zfs/zpool.cache > > Optionally here you set mountpoint back to legacy (which is what you > showed in your message). > # zfs umount -a zroot > # zfs set mountpoint=legacy zroot > > (As you can see I have not exported the pool, which is mandatory [I > think it is considered a bug and was supposed to be fixed in 9]. > Also note I left the mount point as "/" rather than "legacy", which is > optional. > At this point, I rebooted and removed the original to test.) > > Here is a reference to a very similar solution... scroll down to mm's > post, or search for the text "Therefore I suggest" > > http://freebsd.1045724.n5.nabble.com/Difficulties-to-use-ZFS-root-ROOT-MOUNT-ERROR-td4771828.html > > *and also another note*, you need to make sure your first zfs slice on > the disk is the root one. > > eg. This will definitely not boot if the log and cache are for another > pool. I think they also might not boot if they are log and cache for zroot: > > # gpart show -l > => 34 500118125 da5 GPT (238G) > 34 2014 - free - (1M) > 2048 128 1 (null) (64k) > 2176 1920 - free - (960k) > 4096 1048576 2 swap0 (512M) > 168824832 8388608 3 log0 (4.0G) > 177213440 322904064 4 cache0 (154G) > 1052672 167772160 5 root0 (80G) > 500117504 655 - free - (327k) > (note I edited the above... the numbers don't make sense, just the order) > > Peter > > Am 11.11.2011 15:31, schrieb Darren Baginski: > >> Hi! >> >> I'm having troubles booting today's 9.0-RC2 from zfsroot, I'm getting 'unknown filesystem' error. >> But 9.0-RC1 from Tue Nov 8 2011 boots fine. >> >> Here is output with 9.0-RC1 kernel: >> >> # zpool list >> NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT >> zroot 5.97G 2.85G 3.11G 47% 1.00x ONLINE - >> >> # zfs list >> NAME USED AVAIL REFER MOUNTPOINT >> zroot 2.85G 3.02G 2.85G legacy >> >> # cat /boot/loader.conf >> zfs_load="YES" >> vfs.root.mountfrom="zfs:zroot" >> >> Originally that box with installed with FreeBSD 8.x, but continuously updated up to today's version, so : >> >> VER FILESYSTEM >> --- ------------ >> 4 zroot >> >> VER POOL >> --- ------------ >> 15 zroot >> >> Any suggestions ? What could be the problem? >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67971321038618>