Fatman vs ZFS – Who will win

Fatman said:
Thanks, that solved that problem but I hit another road block:

Code:
Fixit# gpart bootcode -b /mnt2/boot/pmbr -p /mnt2/boot/gptzfsboot -i 1 ad0

outputs: "ad0 has bootcode". Is that ok?

I'm going to say yes, but I can tell you for sure in about 3 minutes when I reboot.


Edit: Works great. :h
 
So far so good, i have a quick question:

Should I be running my make install from the i386 folder. I'm currently running on 64bit platform.

Code:
Fixit# echo 'LOADER_ZFS_SUPPORT=YES' > /etc/src.conf
Fixit# mount -t devfs devfs /dev
Fixit# export DESTDIR=""
Fixit# cd /usr/src/sys/boot/
Fixit# make obj
Fixit# make depend
Fixit# make
Fixit# cd i386/loader
Fixit# make install
 
Fatman said:
So far so good, i have a quick question:

Should I be running my make install from the i386 folder. I'm currently running on 64bit platform.

Yes, there is no amd64 specific bootloader that I'm aware of.
 
Thanks, the install went through smoothly. How ever i was not able to unmount /dev.

Code:
Fixit# umount /dev
cannot unmount '/dev': device busy

I kept going and now seeing the same message with:

Code:
Fixit# zfs unmount -a
cannot unmount '/zroot': device busy

Any ideas?
 
Make sure you're trying to unmount the devfs that is mounted in the chroot, and make sure you're not in /zroot while trying to unmount it (# cd / first). # pwd will tell you where you are.
 
Sorry Voltar,

I don't understand. I exited chroot and I still get the same message. I even made sure i'm in /.
 
Run # mount. Do you have something like ...

Code:
devfs on /zroot/dev (devfs, local, multilabel)

If so, try # umount /zroot/dev
 
Glad you got back to me, I was going to attempt to force it with the -f option. :e

mount shows me the following:
Code:
devfs on /dev (devfs, label multilabel)
zroot on /zroot (zfs, local)

I get the following message when attempting to umount /zroot/dev:
Code:
umount: /zroot/dev: not a file system root directory
 
Haha, there's no stupid question.. just idiots like me that can't follow clear instructions. I was sure that i exited but I must of not have. I exited all the way out and re-entered fix-it. I was then able to run umount /zroot.

zfs umount -a went through as expected now.

Thanks again Voltar...
 
I have a dumb question for you. I'm use to doing installs via the standard option that you can select after boot up of the FreeBSD OS DVD.

In point 5:
Exit Fixit mode, and then sysinstall. Remove the FreeBSD install CD and the system will boot using the ZFS root.

I'm not sure what I need to sysinstall. Can I just reboot and run postsnap, freebsdupdate and start using my box? I'm a little confused.

Thanks again for all your help.
 
Voltar, I haven't tried importing my old zpools but the following messages worries me from dmesg:
Code:
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
            to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version 13
ZFS storage pool version 13
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 480Mbps High Speed USB v2.0
ad0: 38204MB <SAMSUNG SP0411N TW100-11> at ata0-master UDMA100
ugen0.1: <nVidia> at usbus0
uhub0: <nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <nVidia> at usbus1
uhub1: <nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
acd0: DVDROM <HL-DT-STDVD-ROM GDR8164B/0L06> at ata0-slave UDMA33
ad4: 953869MB <WDC WD10EADS-00L5B1 01.01A01> at ata2-master SATA300
ad6: 953869MB <WDC WD10EADS-00L5B1 01.01A01> at ata3-master SATA300
ad8: 953869MB <WDC WD10EADS-00L5B1 01.01A01> at ata4-master SATA300
ad10: 953869MB <WDC WD10EADS-00L5B1 01.01A01> at ata5-master SATA300
GEOM: ad4: corrupt or invalid GPT detected.
GEOM: ad4: GPT rejected -- may not be recoverable.
ad12: 953869MB <WDC WD10EADS-00L5B1 01.01A01> at ata6-master SATA300
GEOM: ad6: corrupt or invalid GPT detected.
GEOM: ad6: GPT rejected -- may not be recoverable.
GEOM: ad8: corrupt or invalid GPT detected.
GEOM: ad8: GPT rejected -- may not be recoverable.
GEOM: ad10: corrupt or invalid GPT detected.
GEOM: ad10: GPT rejected -- may not be recoverable.
uhub0: 10 ports with 10 removable, self powered
ad14: 953869MB <WDC WD10EADS-00L5B1 01.01A01> at ata7-master SATA300
GEOM: ad12: corrupt or invalid GPT detected.
GEOM: ad12: GPT rejected -- may not be recoverable.
SMP: AP CPU #1 Launched!
GEOM: ad14: corrupt or invalid GPT detected.
GEOM: ad14: GPT rejected -- may not be recoverable.

A sides from that, everything booted up and I can actually shutdown my system! :p

The import was unsuccessful. When I run
Code:
zpool import
to attempt to view any available zpools, it comes up blank. According the ZFS chapter in OpenSolaris, this should return the pools available. Or maybe, I've missed something. I'm going to re-read the chapter, do I need to define a pool and attach the drives?

Code:
mrnas# zpool list
NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
zroot  33.2G   730M  32.5G     2%  ONLINE  -
 
Did you partition the ZFS disks in OpenSolaris, or did you use the entire disk in the pool?

Try running # zdb -l drive/partition and see if you have labels on any of the drives.
 
I put all 6x 1TB drive in a Raidz2 zpool called zstorage. From there I created multiple sub-folders with my pictures, videos, work stuff. I'm pretty sure I have nothing to worry about right now since I tested formatting the 40gig IDE drive and reinstalling OpenSolaris which detected my zpool without any issues in the past.

The only thing that I can think of is that I might of changed the positions of the sata connections on the motherboard. However I thought that was the great thing about zfs, the drives are hot swappable...

The command you asked me to run provides me the following output:
Code:
mrnas# zdb zstorage
zdb: can't open zstorage: No such file or directory
mrnas# zdb ad6
zdb: can't open ad6: No such file or directory
mrnas# zdb -l ad6
cannot open 'ad6': No such file or directory
mrnas# zdb -l zstorage
cannot open 'zstorage': No such file or directory

I found the following link however it does not look good:
http://forums.freebsd.org/showthread.php?t=2139

I can blow away the data if I really have too but I rather not. There's a lot of stuff on there that I didn't back up.
 
Code:
mrnas# zdb -l /dev/ad4
--------------------------------------------
LABEL 0
--------------------------------------------
failed to unpack label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to unpack label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to unpack label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to unpack label 3

Code:
mrnas# zdb -l /dev/ad6
--------------------------------------------
LABEL 0
--------------------------------------------
failed to unpack label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to unpack label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to unpack label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to unpack label 3

Code:
mrnas# zdb -l /dev/ad8
--------------------------------------------
LABEL 0
--------------------------------------------
failed to unpack label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to unpack label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to unpack label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to unpack label 3
Code:
mrnas# zdb -l /dev/ad10
--------------------------------------------
LABEL 0
--------------------------------------------
failed to unpack label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to unpack label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to unpack label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to unpack label 3
Code:
mrnas# zdb -l /dev/ad12
--------------------------------------------
LABEL 0
--------------------------------------------
failed to unpack label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to unpack label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to unpack label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to unpack label 3
Code:
mrnas# zdb -l /dev/ad14
--------------------------------------------
LABEL 0
--------------------------------------------
failed to unpack label 0
--------------------------------------------
LABEL 1
--------------------------------------------
failed to unpack label 1
--------------------------------------------
LABEL 2
--------------------------------------------
failed to unpack label 2
--------------------------------------------
LABEL 3
--------------------------------------------
failed to unpack label 3
 
Code:
mrnas# ls /dev/ | grep ad4
ad4

mrnas# ls /dev/ | grep ad
ad0
ad0p1
ad0p2
ad0p3
ad10
ad12
ad14
ad4
ad6
ad8
mrnas#

This posting is very interesting:
http://groups.google.com/group/mail...ad/5b6ff6729353f6a9/fef81f4daae88fdc?lnk=raot

On Tue, Nov 17, 2009 at 12:12 PM, Robert Noland <rnol...@freebsd.org> wrote:

This should be fixed in -CURRENT. The issue seems to be that solaris claims that the GPT header is 512 bytes, where we expected it to always be 92 bytes. The fixes are slated to merge to 7/8 stable within a few days, however they won't make it into 8.0.

robert.

Code:
mrnas# uname -a
FreeBSD mrnas.citywidenetworks.com 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009     [email]root@mason.cse.buffalo.edu[/email]:/usr/obj/usr/src/sys/GENERIC  amd64
 
I was about to post the same link, and happened to refresh to see that you already found it. (I was starting to run out of ideas)

Perhaps try updating to 8-STABLE and see if it works.
 
I remember someone telling me a long time ago that it's always better to re-install then to upgrade to a different branch/release. Do you recommend that I download the ISO for the stable branch and repeat the same steps that I took to complete this install?
 
I've never had issues with upgrading. Personally I would csup the 8-STABLE sources and compile/install per the handbook.
 
Looks like I don't have a choice! :p I can't download the stable branch from the website. I'll work on this tomorrow and let you know of the results.

Haha.. Just my luck, nothing ever runs smoothly and works the first time. I don't know why I complicate my life so much. All this effort because I want to be able to shutdown a server that I really never shutdown....

I'm calling it a night. Thanks for all your help, it's very much appreciated.

Fatman
 
Back
Top