Re: ZFS not usable on FreeBSD-8.1
Dear Sir/Madam, Your email was unable reach the intended person that you were sending it to. For more information on our business please click on the following link: [1]Click here for our website We look forward to your continued business in the future. Regards, Webmaster References 1. http://www.downwind.com.au/avdir/rd.php?id=7564 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
Dear Sir/Madam, Your email was unable reach the intended person that you were sending it to. For more information on our business please click on the following link: [1]Click here for our website We look forward to your continued business in the future. Regards, Webmaster References 1. http://www.downwind.com.au/avdir/rd.php?id=7564 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
On 16-8-2010 20:14, Roland Smith wrote: It could be that newfs is overwriting the partition table. Can you post the output of 'gpart showdevice' and 'bsdlabeldevices1'? westmark# gpart show ad8 = 63 976773105 ad8 MBR (466G) 63 9767731051 freebsd [active] (466G) westmark# bsdlabel ad8s1 # /dev/ad8s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 209715204.2BSD0 0 0 b: 12582912 2097152 swap c: 9767731050unused0 0 # raw part, don't edit d: 16777216 146800644.2BSD0 0 0 e: 41943040 314572804.2BSD0 0 0 f: 903372785 734003204.2BSD0 0 0 westmark# I dumped/restored the system to ad8 yesterday and booted from it. The system *did* boot but (alas) the /dev/ads1a(f) slices were mounted. So, the system loaded the *old* root partitions (from the first drive). After googling and reading I think I need *boot0cfg* but I'm a bit scary to ruin my new boot (ad8) drive. So, what is the exact syntax to make my system not only boot from ad8, but also mount the /deb/ad8s1 slice as root slice? After that I can remove my old ata drive and hopefully my zfs errors are gone too then. ;-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
Dick Hoogendijk schrieb: On 16-8-2010 20:14, Roland Smith wrote: It could be that newfs is overwriting the partition table. Can you post the output of 'gpart showdevice' and 'bsdlabeldevices1'? westmark# gpart show ad8 = 63 976773105 ad8 MBR (466G) 63 9767731051 freebsd [active] (466G) westmark# bsdlabel ad8s1 # /dev/ad8s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 209715204.2BSD0 0 0 b: 12582912 2097152 swap c: 9767731050unused0 0 # raw part, don't edit d: 16777216 146800644.2BSD0 0 0 e: 41943040 314572804.2BSD0 0 0 f: 903372785 734003204.2BSD0 0 0 westmark# I dumped/restored the system to ad8 yesterday and booted from it. The system *did* boot but (alas) the /dev/ads1a(f) slices were mounted. So, the system loaded the *old* root partitions (from the first drive). After googling and reading I think I need *boot0cfg* but I'm a bit scary to ruin my new boot (ad8) drive. So, what is the exact syntax to make my system not only boot from ad8, but also mount the /deb/ad8s1 slice as root slice? After that I can remove my old ata drive and hopefully my zfs errors are gone too then. ;-) Did you adjust /etc/fstab on ad8s1? Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
On Tue, Aug 17, 2010 at 11:06:12AM +0200, Dick Hoogendijk wrote: On 16-8-2010 20:14, Roland Smith wrote: It could be that newfs is overwriting the partition table. Can you post the output of 'gpart showdevice' and 'bsdlabeldevices1'? westmark# gpart show ad8 = 63 976773105 ad8 MBR (466G) 63 9767731051 freebsd [active] (466G) westmark# bsdlabel ad8s1 # /dev/ad8s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 209715204.2BSD0 0 0 b: 12582912 2097152 swap c: 9767731050unused0 0 # raw part, don't edit d: 16777216 146800644.2BSD0 0 0 e: 41943040 314572804.2BSD0 0 0 f: 903372785 734003204.2BSD0 0 0 westmark# Ok. That looks good. I dumped/restored the system to ad8 yesterday and booted from it. The system *did* boot but (alas) the /dev/ads1a(f) slices were mounted. So, the system loaded the *old* root partitions (from the first drive). After googling and reading I think I need *boot0cfg* but I'm a bit scary to ruin my new boot (ad8) drive. :-) You can use either boot0cfg or fdisk. The first option gives you the splash screen with the menu choice between normal booting, single user etc. You can install this with 'boot0cfg -B ad8'. The boot block installed by 'fdisk -B ad8' does not give you the menu, but gives you a boot prompt which defaults to normal booting after a couple of seconds. You can still boot into single mode with the boot prompt. Both methods only affect the boot block, they do not change the slice table. So, what is the exact syntax to make my system not only boot from ad8, but also mount the /deb/ad8s1 slice as root slice? * Install one of the boot blocks, as mentioned above. * Check with 'fdisk ad8' if the first slice is active. If not, run 'fdisk -a ad8'. * You'll need to change /etc/fstab on ad8s1a! Best do this before rebooting. It's easier. :-) * Make sure that /boot/ is there and populated on ad8s1a! Then you can re-boot, and make ad8 the first device to boot from in the BIOS. From that point on, according to boot(8), it should work. Good luck! Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp3cBXA7UKiV.pgp Description: PGP signature
Re: ZFS not usable on FreeBSD-8.1
On Mon, Aug 16, 2010 04:49 AM, Adam Vande More amvandem...@gmail.com wrote: On Sun, Aug 15, 2010 at 1:45 PM, Dick Hoogendijk d...@nagual.nl wrote: My 500Gb drives won't however. they keep on giving cg); bad magic number. Sysinstall won't newfs the drives. newfs -U /dev/gm1a (created with the script mentioned before does not work OK either. Always this unexplained message (cg0: bad magic number). I have NO CLUE whatsoever what can be the cause of this. Both drives can be formatted by Windows, Linux and lots of other utilities. They can not be formatted UFS2 for / by FreeBSD-8.1/amd64 You can try to get your system up and running using something like http://mfsbsd.vx.sk/ or pcbsd. If that works, then I guess the possible cause is you. :-) Good idea. I will give it a shot, although I'm pretty sure I'm not the cause. I have four years experience as a (Open)Solaris system administrator and before that I used FreeBSD heavely. From the 4.10 series up to the 6.x series. So I do know something about the matter. But, we'll see... Keep you posted. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
On Mon, Aug 16, 2010 at 10:35:58AM +0200, Dick Hoogendijk wrote: On Mon, Aug 16, 2010 04:49 AM, Adam Vande More amvandem...@gmail.com wrote: On Sun, Aug 15, 2010 at 1:45 PM, Dick Hoogendijk d...@nagual.nl wrote: My 500Gb drives won't however. they keep on giving cg); bad magic number. Sysinstall won't newfs the drives. newfs -U /dev/gm1a (created with the script mentioned before does not work OK either. Always this unexplained message (cg0: bad magic number). I have NO CLUE whatsoever what can be the cause of this. Both drives can be formatted by Windows, Linux and lots of other utilities. They can not be formatted UFS2 for / by FreeBSD-8.1/amd64 You can try to get your system up and running using something like http://mfsbsd.vx.sk/ or pcbsd. If that works, then I guess the possible cause is you. :-) Good idea. I will give it a shot, although I'm pretty sure I'm not the cause. I have four years experience as a (Open)Solaris system administrator and before that I used FreeBSD heavely. From the 4.10 series up to the 6.x series. So I do know something about the matter. But, we'll see... Keep you posted. It could be that newfs is overwriting the partition table. Can you post the output of 'gpart show device' and 'bsdlabel devices1'? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpqkiHe8r5as.pgp Description: PGP signature
Re: ZFS not usable on FreeBSD-8.1
On 16-8-2010 20:14, Roland Smith wrote: On Mon, Aug 16, 2010 at 10:35:58AM +0200, Dick Hoogendijk wrote: On Mon, Aug 16, 2010 04:49 AM, Adam Vande Moreamvandem...@gmail.com wrote: On Sun, Aug 15, 2010 at 1:45 PM, Dick Hoogendijkd...@nagual.nl wrote: My 500Gb drives won't however. they keep on giving cg); bad magic number. Sysinstall won't newfs the drives. newfs -U /dev/gm1a (created with the script mentioned before does not work OK either. Always this unexplained message (cg0: bad magic number). I have NO CLUE whatsoever what can be the cause of this. Both drives can be formatted by Windows, Linux and lots of other utilities. They can not be formatted UFS2 for / by FreeBSD-8.1/amd64 You can try to get your system up and running using something like http://mfsbsd.vx.sk/ or pcbsd. If that works, then I guess the possible cause is you. :-) Good idea. I will give it a shot, although I'm pretty sure I'm not the cause. I have four years experience as a (Open)Solaris system administrator and before that I used FreeBSD heavely. From the 4.10 series up to the 6.x series. So I do know something about the matter. But, we'll see... Keep you posted. It could be that newfs is overwriting the partition table. Can you post the output of 'gpart showdevice' and 'bsdlabeldevices1'? I have found the cause of my troubles. Using FixIt I was able today to use my ad8 with gpart and newfs it without errors. I also found out that zpool scrub pool was waiting for an uninterruptible disk wait. That made me remember I used to have troubles before in this hardware setting. The problem lies in a flaw in my MB. I have one ATA disk attached as master and an ATAPI dvd drive (slave) on ATA channel 0 plus four SATA2 drives (ATA channel 4,5,6,7 master). Somehow this does not work OK. Without the ATA drive on channel 0 (an older model) my four SATA2 drives work perfectly. I suspect some kind of interrupt issue. Problem: FreeBSD is installed on my ATA drive on channel 0. I tried to do a minimal install on drive ad8 today to dump/restore the system over and get rid of that lousy ATA drive. Bad luck. Sysinstall can't find /dev/ad8s1b so it can't complete the creation of the filesystems. And thus I can't do a minimal install on this SATA2 drive. Any ideas how I can overcome this issue? westmark# atacontrol list ATA channel 0: Master: ad0 ST3160021A/8.01 ATA/ATAPI revision 6 Slave: acd0 PLEXTOR DVDR PX-755A/1.08 ATA/ATAPI revision 6 ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: ad8 Hitachi HDP725050GLA360/GM4OA5CA SATA revision 2.x Slave: no device present ATA channel 5: Master: ad10 Hitachi HDP725050GLA360/GM4OA50E SATA revision 2.x Slave: no device present ATA channel 6: Master: ad12 Hitachi HDT721010SLA360/ST6OA31B SATA revision 2.x Slave: no device present ATA channel 7: Master: ad14 Hitachi HDS721010CLA332/JP4OA39C SATA revision 2.x Slave: no device present ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ZFS not usable on FreeBSD-8.1
-Original Message- From: Dick Hoogendijk [mailto:d...@nagual.nl] Sent: 16 August 2010 21:49 To: Roland Smith Cc: freebsd-questions@freebsd.org Subject: Re: ZFS not usable on FreeBSD-8.1 On 16-8-2010 20:14, Roland Smith wrote: On Mon, Aug 16, 2010 at 10:35:58AM +0200, Dick Hoogendijk wrote: On Mon, Aug 16, 2010 04:49 AM, Adam Vande Moreamvandem...@gmail.com wrote: On Sun, Aug 15, 2010 at 1:45 PM, Dick Hoogendijkd...@nagual.nl wrote: My 500Gb drives won't however. they keep on giving cg); bad magic number. Sysinstall won't newfs the drives. newfs -U /dev/gm1a (created with the script mentioned before does not work OK either. Always this unexplained message (cg0: bad magic number). I have NO CLUE whatsoever what can be the cause of this. Both drives can be formatted by Windows, Linux and lots of other utilities. They can not be formatted UFS2 for / by FreeBSD-8.1/amd64 You can try to get your system up and running using something like http://mfsbsd.vx.sk/ or pcbsd. If that works, then I guess the possible cause is you. :-) Good idea. I will give it a shot, although I'm pretty sure I'm not the cause. I have four years experience as a (Open)Solaris system administrator and before that I used FreeBSD heavely. From the 4.10 series up to the 6.x series. So I do know something about the matter. But, we'll see... Keep you posted. It could be that newfs is overwriting the partition table. Can you post the output of 'gpart showdevice' and 'bsdlabeldevices1'? I have found the cause of my troubles. Using FixIt I was able today to use my ad8 with gpart and newfs it without errors. I also found out that zpool scrub pool was waiting for an uninterruptible disk wait. That made me remember I used to have troubles before in this hardware setting. The problem lies in a flaw in my MB. I have one ATA disk attached as master and an ATAPI dvd drive (slave) on ATA channel 0 plus four SATA2 drives (ATA channel 4,5,6,7 master). Somehow this does not work OK. Without the ATA drive on channel 0 (an older model) my four SATA2 drives work perfectly. I suspect some kind of interrupt issue. Problem: FreeBSD is installed on my ATA drive on channel 0. I tried to do a minimal install on drive ad8 today to dump/restore the system over and get rid of that lousy ATA drive. Bad luck. Sysinstall can't find /dev/ad8s1b so it can't complete the creation of the filesystems. And thus I can't do a minimal install on this SATA2 drive. Any ideas how I can overcome this issue? westmark# atacontrol list ATA channel 0: Master: ad0 ST3160021A/8.01 ATA/ATAPI revision 6 Slave: acd0 PLEXTOR DVDR PX-755A/1.08 ATA/ATAPI revision 6 ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: ad8 Hitachi HDP725050GLA360/GM4OA5CA SATA revision 2.x Slave: no device present ATA channel 5: Master: ad10 Hitachi HDP725050GLA360/GM4OA50E SATA revision 2.x Slave: no device present ATA channel 6: Master: ad12 Hitachi HDT721010SLA360/ST6OA31B SATA revision 2.x Slave: no device present ATA channel 7: Master: ad14 Hitachi HDS721010CLA332/JP4OA39C SATA revision 2.x Slave: no device present ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Bit of a long shot, but have you tried enabling AHCI mode for the sata drives in the bios and setting ahci_load=YES in /boot/loader.conf assuming your the board supports it. Regards Graeme ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
On 16-8-2010 23:13, Graeme Dargie wrote: Bit of a long shot, but have you tried enabling AHCI mode for the sata drives in the bios and setting ahci_load=YES in /boot/loader.conf assuming your the board supports it. I will certainly check this one out. Wouldn't know if my MB supports it. Hope so, for I get the feeling most problems will be over then. and if not, I'm removing the older ATA drive. The system is now being transfered to the first sata2 drive. We'll see if it will boot tomorrow. It should. The drive is prepard for it with gpart. ;-) Thanks for the pointer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
On 15-8-2010 3:10, George Hartzell wrote:
Dick Hoogendijk writes:
And how do I make the partition precisely one block smaller than the
slic it lives in?
How do I know what the blocksize is?
Are you using explicit device names to add the disks to your pool? If
so you'll gain robustness by using labels, either glabels as described
here:
http://submesa.com/data/bsd/zfs
or if you're in the gpt world then gpt labels as described in the
gpart commands illustrated here:
http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror
I tried both methods. I had the disks as GPT labeld ones and slices by
sysinstall. None worked.
So it may be the one block difference. Please tell me how to do that.
Just to be clear, I'm not refering to using GPT vs. MBR. I'm
suggesting that you when you use GPT you also label the partition with
something like 'disk1' and then do something like (s/mirror/raidz/ as
appropriate)
zpool create mirror foo /dev/gpt/disk1 /dev/gpt/disk2
and *not*
zpool create mirror foo /dev/ad1p1 /dev/ad2p1
If that's true you probably have something else going on.
Tried this today (again). Watched every step but zpool scrub ruined my
zpool agian with the vdev.bad_label warning. It simply does not work. My
1Tb drives do not waork with ZFS either, but at least these work with
gmirror.
http://people.freebsd.org/~rse/mirror/
The first script, just after the comment that starts:
place a PC MBR...
uses fdisk to set up a slice that's one block smaller than the disk
device (I was in{accurate,correct} in my description of the issue
earlier when I attributed it to slice/partition interference). You
can see where it subtracts 1 from the size
I learned a lot from the scripts. ;-) The drives work wonderful as a
gmirror now.
My 500Gb drives won't however. they keep on giving cg); bad magic number.
Sysinstall won't newfs the drives. newfs -U /dev/gm1a (created with the
script mentioned before does not work OK either. Always this unexplained
message (cg0: bad magic number). I have NO CLUE whatsoever what can be
the cause of this. Both drives can be formatted by Windows, Linux and
lots of other utilities. They can not be formatted UFS2 for / by
FreeBSD-8.1/amd64
I would love to get some feedback about possible causes and/or
solutions. right now those two 500Gb drives are useless. Spining around
for no good. ;-)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
On Sun, Aug 15, 2010 at 1:45 PM, Dick Hoogendijk d...@nagual.nl wrote: I learned a lot from the scripts. ;-) The drives work wonderful as a gmirror now. My 500Gb drives won't however. they keep on giving cg); bad magic number. Sysinstall won't newfs the drives. newfs -U /dev/gm1a (created with the script mentioned before does not work OK either. Always this unexplained message (cg0: bad magic number). I have NO CLUE whatsoever what can be the cause of this. Both drives can be formatted by Windows, Linux and lots of other utilities. They can not be formatted UFS2 for / by FreeBSD-8.1/amd64 I would love to get some feedback about possible causes and/or solutions. right now those two 500Gb drives are useless. Spining around for no good. ;-) You can try to get your system up and running using something like http://mfsbsd.vx.sk/ or pcbsd. If that works, then I guess the possible cause is you. :-) -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
Dick Hoogendijk writes: I run FreeBSD-8.1/amd64. I have used ZFS for four years on (Open)Solaris, so I have some experience with it. It always served me very very well. However, I cannot get it to work on my SATA2 drives. At first I thought they'de suffer from something from there OpenSolaris ZFS mirroring. So, I wiped out the drives completely by writing zero's to them. Then I created a ZFS zpool on one drive, destroyed it and created a mirrored zpool on my 2 Tb drives. It seemed OK; files could be written and removed to/from it. A new zfs filesystem worked OK too. *HOWEVER*, the moment I *do* something to the zpool like zpool scrub pool I get a vdev failure (type=vdev.bad_label) and the pool is ruined. It can't be destroyed or exported anymore. It's just a waste. I tested this behaviour on 10 different drives. Four of them brandnew. It happened everytime again. It is not the drives! Booting into OpenSolaris b134 I am perfectly able to create workable ZFS mirrors out of the drives. I can also scrub them ;-) ;-) or whatever io related thing I want to do. This leads me to the conclusion that something is definitely wrong with ZFS in FreeBSD-8.1/amd64. For the moment I created some gmirrors on a couple of drives, but man, how I'd liked to have zpools. They work zo much sweater/easier. Am I alone in these matters? Are there any known issues regarding ZFS. I know there are some in FreeBSD-9 (at least I saw some reports on vdev.bad_label messages) on nabble.com You haven't provided enough information for me to make a concrete suggestion, but this kind of thing often seems to boil down to something getting confused over slices and partitions when they both have the same extent (start-end) on disk. This used to bite me in the gmirror world until I learned to make the partition one block smaller than the slice it lived in. Are you using explicit device names to add the disks to your pool? If so you'll gain robustness by using labels, either glabels as described here: http://submesa.com/data/bsd/zfs or if you're in the gpt world then gpt labels as described in the gpart commands illustrated here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror g. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS not usable on FreeBSD-8.1
On 14-8-2010 21:24, George Hartzell wrote: You haven't provided enough information for me to make a concrete suggestion, but this kind of thing often seems to boil down to something getting confused over slices and partitions when they both have the same extent (start-end) on disk. This used to bite me in the gmirror world until I learned to make the partition one block smaller than the slice it lived in. And how do I make the partition precisely one block smaller than the slic it lives in? How do I know what the blocksize is? Are you using explicit device names to add the disks to your pool? If so you'll gain robustness by using labels, either glabels as described here: http://submesa.com/data/bsd/zfs or if you're in the gpt world then gpt labels as described in the gpart commands illustrated here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror I tried both methods. I had the disks as GPT labeld ones and slices by sysinstall. None worked. So it may be the one block difference. Please tell me how to do that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
