Date: Thu, 07 Apr 2011 21:43:56 -0700 From: David Newman <dnewman@networktest.com> To: freebsd-fs@freebsd.org Subject: Re: new ZFS install Message-ID: <4D9E928C.5020109@networktest.com> In-Reply-To: <201104061815.p36IFDUd024758@higson.cam.lispworks.com> References: <4C51ECAA.2070707@networktest.com> <4C51FE41.8030906@FreeBSD.org> <4D941BFF.6050807@networktest.com> <AANLkTikt%2BG_1Mbm5G3qbdQvkr-rho7LR0sTSM9nJOSEA@mail.gmail.com> <4D973400.9060404@networktest.com> <201104041138.p34BckHS029801@higson.cam.lispworks.com> <4D9B6713.4050107@networktest.com> <201104061815.p36IFDUd024758@higson.cam.lispworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/6/11 11:15 AM, Martin Simmons wrote: >>>>>> On Tue, 05 Apr 2011 12:01:39 -0700, David Newman said: >> >> On 4/4/11 4:38 AM, Martin Simmons wrote: >>>>>>>> On Sat, 02 Apr 2011 07:34:40 -0700, David Newman said: >>>> >>>> I've tried booting from 8.1 and 8.2 mfsBSD ISOs but both hang at >>>> loader.conf. >>> >>> Have you tried the regular FreeBSD installation ISO? That doesn't know about >>> ZFS by default, but you can enter Fixit mode with "Use the live filesystem >>> CDROM/DVD" and load the modules using >>> >>> kldload /dist/boot/kernel/opensolaris.ko >>> kldload /dist/boot/kernel/zfs.ko >> >> Thanks, that did the trick, along with repairing the boot records on >> each disk. > > Good -- though it is strange the mfsBSD hung. Does it still hang, now that > you have repaired the system? > > >> This server is showing some evidence of flaky hardware, and I'm looking >> to move its data onto a new server running FreeBSD 8.2 and ZFS in all >> partitions. > > Maybe that is the cause of mfsBSD hanging too? > > >> I understand the guide I used to build the old server has been >> deprecated. What's the recommended setup these days? > > I don't know -- AFAIK http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 is > still accurate. Thanks. Yes, bum hardware was the culprit. That guide has worked well for me in the past. The only gotcha is that upgrading between versions using freebsd-update clobbers the boot records on each disk, and requires repair. Not a big deal but I have to remember this issue each time a new release comes out. dn > > __Martin > _______________________________________________ > 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?4D9E928C.5020109>