Re: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
On 11/29/10 19:32, James R. Van Artsdalen wrote: O. Hartmann wrote: Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Please send the output of camcontrol devlist and zpool status on FreeBSD-8.1. Then export the pool in FreeBSD-8.1, boot FreeBSD-9 with verbose booting and send the output of camcontrol devlist, zpool import BACKUP and the part of /var/log/messages that shows FreeeBSD searching for the pool during the import. Appended, you'll find some of the requested data. There is no valuable dmesg/message output, due to the simple fact, that after yesterday's make world and another import try the BACKUP00 pool was imported. The only thing to report is, that while importing the BACKUP00 pool, which is on devise ada3, I got an message on console like: Nov 29 21:13:36 0.2 thor kernel: ZFS WARNING: Unable to attach to ada1. This strange message always came up when importing the BACKUP00 pool (BACKUP is a typo, sorry for the inconvenience) and when it was about to fail. It might be useful to know what disk controller is being used. = 34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) It is not related to your problem, but how did that unused space wind up before partition 1? Well, my fault. I initiated the partitions with the -b 4096 option set for the first partition. It was so nice and at ease playing around with gpart ... And here comes the data requested: #FreeBSD 8.2-PRE/amd64 -- camcontrol devlist WDC WD5001AALS-00L3B2 01.03B01 at scbus4 target 0 lun 0 (pass0,ada0) WDC WD1001FALS-00J7B0 05.00K05 at scbus5 target 0 lun 0 (pass1,ada1) WDC WD1001FALS-00J7B0 05.00K05 at scbus6 target 0 lun 0 (pass2,ada2) WDC WD20EURS-63Z9B1 80.00A80 at scbus7 target 0 lun 0 (pass3,ada3) HL-DT-ST DVDRAM GH22LS50 TL03at scbus9 target 0 lun 0 (cd0,pass4) #FreeBSD 9.0-CURRENT/amd64 -- camcontrol devlist WDC WD6402AAEX-00Y9A0 01.01V01 at scbus4 target 0 lun 0 (pass0,ada0) WDC WD1001FALS-00J7B0 05.00K05 at scbus5 target 0 lun 0 (pass1,ada1) WDC WD1001FALS-00J7B0 05.00K05 at scbus6 target 0 lun 0 (pass2,ada2) WDC WD20EURS-63Z9B1 80.00A80 at scbus7 target 0 lun 0 (pass3,ada3) WDC WD5001AALS-00L3B2 01.03B01 at scbus8 target 0 lun 0 (pass4,ada4) HL-DT-ST DVDRAM GH22LS50 TL03at scbus9 target 0 lun 0 (cd0,pass5) (needed to swap 1st and 5th drive since FBSD 8 was installed with MBR and no labels and needed device special file for mounting partitions while on FreeBSD 9 I used the first time GPT partitioning scheme with labeling for mounting via /etc/fstab) #FreeBSD 8 zpool status: pool: BACKUP00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM BACKUP00ONLINE 0 0 0 ada3p1ONLINE 0 0 0 errors: No known data errors pool: THOR00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM THOR00 ONLINE 0 0 0 ada1p1ONLINE 0 0 0 ada2p1ONLINE 0 0 0 errors: No known data errors #FreeBSD 8 pciconf -lcv (for the requested controller) ah...@pci0:0:31:2: class=0x010601 card=0x82d41043 chip=0x3a228086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '6 port SATA AHCI Controller' class = mass storage subclass = SATA cap 05[80] = MSI supports 16 messages enabled with 1 message cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair cap 09[b0] = vendor (length 6) Intel cap 2 version 0 In kernel config, I use AHCI driver modell, not the atapi one, but I guess this is obvious due to 'adaXX' ... And by the way, the 2 TB drive in question is sold as a 'PVR/VCR video special device, I mistakenly ordered this one since it promissed low power, high sustain-reliability (it is used for backups), but some web sites claim that the controller of this specific, expensive 2 TB hdd deals different with errornous blocks read or written out - I can not verify this, since I have no technical paper nor do I understand much of HDD electrical engineering ... Regards, Oliver ___ 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: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
On 12/1/2010 5:36 PM, O. Hartmann wrote: There is no valuable dmesg/message output, due to the simple fact, that after yesterday's make world and another import try the BACKUP00 pool was imported. The only thing to report is, that while importing the BACKUP00 pool, which is on devise ada3, I got an message on console like: Nov 29 21:13:36 0.2 thor kernel: ZFS WARNING: Unable to attach to ada1. Unfortunately until the problem reproduces there's no way to dig into it further. boot-verbose will show what ZFS finds when it scans ada3p1 both for the pool and for the vdev (by GUID). ZFS can't claim ada1 since that's GPT-partitioned. ___ 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: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
On 29.11.2010 11:52, O. Hartmann wrote: Exporting both volumes in FreeBSD 8 works. But importing them in FreeBSD 9.0-CURRENT/amd64 as with the most recent make world of today fails on the 2TB HDD (ZFS pool/volume BACKUP00). Issuing zpool import BACKUP00 results in cannot import 'BACKUP': no such pool available and on console I receive message It seems strange, why the pool name in error message is 'BACKUP' but not 'BACKUP00'? Surprisingly, the GPT partition of the pool BACKUP00 isn't shown in FreeBSD 9, while I see ada3p1 in FreeBSD 8.2. gpart show ada3 lists this: =34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) Do you have something related to GPT in log files? Can you show full output of `gpart show` from FreeBSD-8 and FreeBSD-9? -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
O. Hartmann ohart...@zedat.fu-berlin.de writes: I'm running a newly setup FreeBSD 9.0-CURRENT/amd64 SMP box. The former OS was FreeBSD 8.1-PRE/amd64. Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Two 1TB HDD are spanning a volume with 2 TB capacity which is quite fast due to parallel access through ZFS. The underlying layout is, as mentioned, GPT, bot devices are named /dev/ada1p1 and /dev/ada2p1. The thir drive is a WD Caviar Green 2TB HDD acting as a compressed ZFS backup media, also based on a GPT partitioning scheme and known as device /dev/ada3p1. In FreeBSD 8.2-PRE/amd64 I can use the JBOD volume resembled from two 1TB HDD without problems, mounting is all right, dismounting, also with the 2TB HDD, labeld as BACKUP00 volume in ZFS. Doing a zpool export on both ZFS volumes works fine in FBSD 8, importing is also no problem. The system's log does not show any kind of irregularities, errors or something else indicating soemthing weird with one of the three devices. Exporting both volumes in FreeBSD 8 works. But importing them in FreeBSD 9.0-CURRENT/amd64 as with the most recent make world of today fails on the 2TB HDD (ZFS pool/volume BACKUP00). Issuing zpool import BACKUP00 results in cannot import 'BACKUP': no such pool available and on console I receive message ZFS WARNING: Unable to attach to ada1 But the drive is and was ada3! Looking with zpool status, I get the follwoing picture: pool: BACKUP00 state: FAULTED status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-5E scrub: none requested config: NAMESTATE READ WRITE CKSUM BACKUP00FAULTED 0 0 0 corrupted data ada3 UNAVAIL 0 0 0 corrupted data pool: THOR00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM THOR00 ONLINE 0 0 0 ada1p1ONLINE 0 0 0 ada2p1ONLINE 0 0 0 errors: No known data errors This picture differs from what I see i FreeBSD 8.2-PRE/amd issuing the same command! I did a full zpool scrub on both pools - no effect. Surprisingly, the GPT partition of the pool BACKUP00 isn't shown in FreeBSD 9, while I see ada3p1 in FreeBSD 8.2. gpart show ada3 lists this: =34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) The drive in question is a WesternDigital Caviar Green WD (WDC WD20EURS-63Z9B1 80.00A80 at scbus7 target 0 lun 0 (pass3,ada3)). Can someone explain what#s going on? The drive in question is one of the new 4k sized physical block devices. Why is FreeBSD 8 dealing with the HDD, FreeBSD 9 not? Any help at this point? Hope the volume is not lost. Thanks in advance, Oliver Hi Oliver, just a wild guess and maybe completely wrong: are the ZFS version numbers and zpool version numbers the same across 8.1 and 9-CURRENT ? Best Regards, Leonidas ___ 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: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
On 29 November 2010 16:41, Leonidas Tsampros ltsamp...@upnet.gr wrote: O. Hartmann ohart...@zedat.fu-berlin.de writes: I'm running a newly setup FreeBSD 9.0-CURRENT/amd64 SMP box. The former OS was FreeBSD 8.1-PRE/amd64. Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Two 1TB HDD are spanning a volume with 2 TB capacity which is quite fast due to parallel access through ZFS. The underlying layout is, as mentioned, GPT, bot devices are named /dev/ada1p1 and /dev/ada2p1. The thir drive is a WD Caviar Green 2TB HDD acting as a compressed ZFS backup media, also based on a GPT partitioning scheme and known as device /dev/ada3p1. In FreeBSD 8.2-PRE/amd64 I can use the JBOD volume resembled from two 1TB HDD without problems, mounting is all right, dismounting, also with the 2TB HDD, labeld as BACKUP00 volume in ZFS. Doing a zpool export on both ZFS volumes works fine in FBSD 8, importing is also no problem. The system's log does not show any kind of irregularities, errors or something else indicating soemthing weird with one of the three devices. Exporting both volumes in FreeBSD 8 works. But importing them in FreeBSD 9.0-CURRENT/amd64 as with the most recent make world of today fails on the 2TB HDD (ZFS pool/volume BACKUP00). Issuing zpool import BACKUP00 results in cannot import 'BACKUP': no such pool available and on console I receive message ZFS WARNING: Unable to attach to ada1 But the drive is and was ada3! Looking with zpool status, I get the follwoing picture: pool: BACKUP00 state: FAULTED status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-5E scrub: none requested config: NAMESTATE READ WRITE CKSUM BACKUP00FAULTED 0 0 0 corrupted data ada3 UNAVAIL 0 0 0 corrupted data pool: THOR00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM THOR00 ONLINE 0 0 0 ada1p1ONLINE 0 0 0 ada2p1ONLINE 0 0 0 errors: No known data errors This picture differs from what I see i FreeBSD 8.2-PRE/amd issuing the same command! I did a full zpool scrub on both pools - no effect. Surprisingly, the GPT partition of the pool BACKUP00 isn't shown in FreeBSD 9, while I see ada3p1 in FreeBSD 8.2. gpart show ada3 lists this: =34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) The drive in question is a WesternDigital Caviar Green WD (WDC WD20EURS-63Z9B1 80.00A80 at scbus7 target 0 lun 0 (pass3,ada3)). Can someone explain what#s going on? The drive in question is one of the new 4k sized physical block devices. Why is FreeBSD 8 dealing with the HDD, FreeBSD 9 not? Any help at this point? Hope the volume is not lost. Thanks in advance, Oliver Hi Oliver, just a wild guess and maybe completely wrong: are the ZFS version numbers and zpool version numbers the same across 8.1 and 9-CURRENT ? Best Regards, Leonidas ___ 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 i think both are on version 15, however a v22 patch is in testing and will probably hit head fairly soon ___ 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: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
O. Hartmann wrote: Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Please send the output of camcontrol devlist and zpool status on FreeBSD-8.1. Then export the pool in FreeBSD-8.1, boot FreeBSD-9 with verbose booting and send the output of camcontrol devlist, zpool import BACKUP and the part of /var/log/messages that shows FreeeBSD searching for the pool during the import. It might be useful to know what disk controller is being used. =34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) It is not related to your problem, but how did that unused space wind up before partition 1? ___ 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: CURRENT: Issue with ZFS and 2TB WD HDD (WDC WD20EURS-63Z9B1 80.00A80)
On 11/29/10 17:41, Leonidas Tsampros wrote: O. Hartmannohart...@zedat.fu-berlin.de writes: I'm running a newly setup FreeBSD 9.0-CURRENT/amd64 SMP box. The former OS was FreeBSD 8.1-PRE/amd64. Attached to the system are three WD harddrives with ZFS as filesystem on GPT partitioning scheme. Two 1TB HDD are spanning a volume with 2 TB capacity which is quite fast due to parallel access through ZFS. The underlying layout is, as mentioned, GPT, bot devices are named /dev/ada1p1 and /dev/ada2p1. The thir drive is a WD Caviar Green 2TB HDD acting as a compressed ZFS backup media, also based on a GPT partitioning scheme and known as device /dev/ada3p1. In FreeBSD 8.2-PRE/amd64 I can use the JBOD volume resembled from two 1TB HDD without problems, mounting is all right, dismounting, also with the 2TB HDD, labeld as BACKUP00 volume in ZFS. Doing a zpool export on both ZFS volumes works fine in FBSD 8, importing is also no problem. The system's log does not show any kind of irregularities, errors or something else indicating soemthing weird with one of the three devices. Exporting both volumes in FreeBSD 8 works. But importing them in FreeBSD 9.0-CURRENT/amd64 as with the most recent make world of today fails on the 2TB HDD (ZFS pool/volume BACKUP00). Issuing zpool import BACKUP00 results in cannot import 'BACKUP': no such pool available and on console I receive message ZFS WARNING: Unable to attach to ada1 But the drive is and was ada3! Looking with zpool status, I get the follwoing picture: pool: BACKUP00 state: FAULTED status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-5E scrub: none requested config: NAMESTATE READ WRITE CKSUM BACKUP00FAULTED 0 0 0 corrupted data ada3 UNAVAIL 0 0 0 corrupted data pool: THOR00 state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM THOR00 ONLINE 0 0 0 ada1p1ONLINE 0 0 0 ada2p1ONLINE 0 0 0 errors: No known data errors This picture differs from what I see i FreeBSD 8.2-PRE/amd issuing the same command! I did a full zpool scrub on both pools - no effect. Surprisingly, the GPT partition of the pool BACKUP00 isn't shown in FreeBSD 9, while I see ada3p1 in FreeBSD 8.2. gpart show ada3 lists this: = 34 3907029101 ada3 GPT (1.8T) 344062- free - (2.0M) 4096 3907025039 1 freebsd-zfs (1.8T) The drive in question is a WesternDigital Caviar Green WD (WDC WD20EURS-63Z9B1 80.00A80 at scbus7 target 0 lun 0 (pass3,ada3)). Can someone explain what#s going on? The drive in question is one of the new 4k sized physical block devices. Why is FreeBSD 8 dealing with the HDD, FreeBSD 9 not? Any help at this point? Hope the volume is not lost. Thanks in advance, Oliver Hi Oliver, just a wild guess and maybe completely wrong: are the ZFS version numbers and zpool version numbers the same across 8.1 and 9-CURRENT ? Best Regards, Leonidas Hello Leonidas, both pools are versioned '15', that is the most recent version in 9.0-CURRENT and 8.2-PRE. One of the both pools, that one spanned over two 1 TB hard drives, works perfectly. The backup pool on the 2TB hdd does not. It seems that the partitioning information got lost in FreeBSD 9. The hdd in question is one of that new 2TB drives of WD with 4k blocks ... maybe I made a mistake when initiatet the GPT layout ... (started the partition at block 4096 with the '-b'-option of 'gpart add'). Greetings, Oliver ___ 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
