October 4, 201015 yr I just upgraded my box to 5.0 beta 2, I added a supermicro AOC-SASLP_MV8, and two 2TB WD WD20EARS Drives (one as parity). I removed my old parity (it was dead), i precleared both drives, I added the first drive as a storage drive, then formatted it. Then added the other drive as parity and started the array + parity sync. I am getting a parity sync speed report as follows: Total size: 2 TB Current position: 138.66 GB (6.9%) Estimated speed: 3.67 MB/sec Estimated finish: 8448.4 minutes Does 3 MB/sec sound correct, I remember doing a full parity sync to a 1TB drive and it took me about 15hours, this one has been going for over 10 and is still going to take me like 140 more hours. Should I stop it and reboot the machine, then try again? Any help is greatly appreciated, I have attached the current syslog, Thanks. syslog_10_04_2010_part1.txt
October 4, 201015 yr Looks like Disk4 (ata3) is having issues... I'd start with swapping the SATA cable, and making sure the power and SATA cable are connected tightly.
October 4, 201015 yr You should be getting 40 to 80 MB/sec. Definitely something wrong. Don't wait for this to try to finish.
October 5, 201015 yr The second half of the syslog shows a lot of errors. I think ata3 is /dev/sdd (the parity disk) [pre]Oct 2 15:28:25 oxnet kernel: ata3.00: exception Emask 0x52 SAct 0x7 SErr 0x1400c01 action 0x6 frozen Oct 2 15:28:25 oxnet kernel: ata3.00: irq_stat 0x08000000, interface fatal error Oct 2 15:28:25 oxnet kernel: ata3: SError: { RecovData Proto HostInt Handshk TrStaTrns } Oct 2 15:28:25 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:28:25 oxnet kernel: ata3.00: cmd 60/00:00:c8:68:47/01:00:00:00:00/40 tag 0 ncq 131072 in Oct 2 15:28:25 oxnet kernel: res 40/00:04:c8:68:47/00:00:00:00:00/40 Emask 0x52 (ATA bus error) Oct 2 15:28:25 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:28:25 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:28:25 oxnet kernel: ata3.00: cmd 60/00:08:90:4b:35/02:00:09:00:00/40 tag 1 ncq 262144 in Oct 2 15:28:25 oxnet kernel: res 40/00:04:c8:68:47/00:00:00:00:00/40 Emask 0x52 (ATA bus error) Oct 2 15:28:25 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:28:25 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:28:25 oxnet kernel: ata3.00: cmd 60/00:10:c8:69:47/01:00:00:00:00/40 tag 2 ncq 131072 in Oct 2 15:28:25 oxnet kernel: res 40/00:04:c8:68:47/00:00:00:00:00/40 Emask 0x52 (ATA bus error) Oct 2 15:28:25 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:28:25 oxnet kernel: ata3: hard resetting link Oct 2 15:28:26 oxnet kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 2 15:28:26 oxnet kernel: ata3.00: configured for UDMA/133 Oct 2 15:28:26 oxnet kernel: ata3: EH complete Oct 2 15:28:27 oxnet kernel: ata3.00: exception Emask 0x10 SAct 0x7 SErr 0xc00001 action 0x6 frozen Oct 2 15:28:27 oxnet kernel: ata3.00: irq_stat 0x08000008, interface fatal error Oct 2 15:28:27 oxnet kernel: ata3: SError: { RecovData Handshk LinkSeq } Oct 2 15:28:27 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:28:27 oxnet kernel: ata3.00: cmd 60/00:00:c8:b9:49/01:00:00:00:00/40 tag 0 ncq 131072 in Oct 2 15:28:27 oxnet kernel: res 40/00:04:c8:b9:49/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 2 15:28:27 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:28:27 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:28:27 oxnet kernel: ata3.00: cmd 60/00:08:90:5f:35/02:00:09:00:00/40 tag 1 ncq 262144 in Oct 2 15:28:27 oxnet kernel: res 40/00:04:c8:b9:49/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 2 15:28:27 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:28:27 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:28:27 oxnet kernel: ata3.00: cmd 60/00:10:c8:ba:49/01:00:00:00:00/40 tag 2 ncq 131072 in Oct 2 15:28:27 oxnet kernel: res 40/00:04:c8:b9:49/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 2 15:28:27 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:28:27 oxnet kernel: ata3: hard resetting link Oct 2 15:28:27 oxnet kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 2 15:28:27 oxnet kernel: ata3.00: configured for UDMA/133 Oct 2 15:28:27 oxnet kernel: ata3: EH complete Oct 2 15:29:10 oxnet kernel: ata3.00: exception Emask 0x52 SAct 0x3 SErr 0x1400c01 action 0x6 frozen Oct 2 15:29:10 oxnet kernel: ata3.00: irq_stat 0x08000000, interface fatal error Oct 2 15:29:10 oxnet kernel: ata3: SError: { RecovData Proto HostInt Handshk TrStaTrns } Oct 2 15:29:10 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:29:10 oxnet kernel: ata3.00: cmd 60/00:00:58:55:d6/01:00:00:00:00/40 tag 0 ncq 131072 in Oct 2 15:29:10 oxnet kernel: res 40/00:04:58:55:d6/00:00:00:00:00/40 Emask 0x52 (ATA bus error) Oct 2 15:29:10 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:29:10 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:29:10 oxnet kernel: ata3.00: cmd 60/00:08:58:56:d6/01:00:00:00:00/40 tag 1 ncq 131072 in Oct 2 15:29:10 oxnet kernel: res 40/00:04:58:55:d6/00:00:00:00:00/40 Emask 0x52 (ATA bus error) Oct 2 15:29:10 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:29:10 oxnet kernel: ata3: hard resetting link Oct 2 15:29:10 oxnet kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 2 15:29:10 oxnet kernel: ata3.00: configured for UDMA/133 Oct 2 15:29:10 oxnet kernel: ata3: EH complete Oct 2 15:29:29 oxnet kernel: ata3: limiting SATA link speed to 1.5 Gbps Oct 2 15:29:29 oxnet kernel: ata3.00: exception Emask 0x10 SAct 0x3 SErr 0xc00001 action 0x6 frozen Oct 2 15:29:29 oxnet kernel: ata3.00: irq_stat 0x08000008, interface fatal error Oct 2 15:29:29 oxnet kernel: ata3: SError: { RecovData Handshk LinkSeq } Oct 2 15:29:29 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:29:29 oxnet kernel: ata3.00: cmd 60/00:00:e8:3f:14/01:00:01:00:00/40 tag 0 ncq 131072 in Oct 2 15:29:29 oxnet kernel: res 40/00:0c:e8:3e:14/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Oct 2 15:29:29 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:29:29 oxnet kernel: ata3.00: failed command: READ FPDMA QUEUED Oct 2 15:29:29 oxnet kernel: ata3.00: cmd 60/00:08:e8:3e:14/01:00:01:00:00/40 tag 1 ncq 131072 in Oct 2 15:29:29 oxnet kernel: res 40/00:0c:e8:3e:14/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Oct 2 15:29:29 oxnet kernel: ata3.00: status: { DRDY } Oct 2 15:29:29 oxnet kernel: ata3: hard resetting link Oct 2 15:29:29 oxnet kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 2 15:29:29 oxnet kernel: ata3.00: configured for UDMA/133 Oct 2 15:29:29 oxnet kernel: ata3: EH complete Oct 2 15:30:52 oxnet emhttp: disk_temperature: ATTR_Temperature_Celsius not found Oct 2 16:05:21 oxnet emhttp: disk_temperature: ATTR_Temperature_Celsius not found Oct 2 16:05:27 oxnet emhttp: disk_temperature: ATTR_Temperature_Celsius not found Oct 2 16:25:19 oxnet kernel: mdcmd (420): spindown 6 Oct 2 16:51:32 oxnet kernel: mdcmd (572): spindown 4 Oct 2 16:55:16 oxnet kernel: mdcmd (594): spindown 3 Oct 2 17:02:10 oxnet kernel: mdcmd (634): spindown 1 Oct 2 17:25:56 oxnet kernel: mdcmd (773): spindown 2 Oct 2 18:18:00 oxnet kernel: mdcmd (1086): spindown 5 Oct 2 23:09:16 oxnet kernel: ata3.00: exception Emask 0x10 SAct 0xffffff SErr 0x400100 action 0x6 frozen Oct 2 23:09:16 oxnet kernel: ata3.00: irq_stat 0x08000000, interface fatal error Oct 2 23:09:16 oxnet kernel: ata3: SError: { UnrecovData Handshk } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/00:00:a8:25:53/04:00:31:00:00/40 tag 0 ncq 524288 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) Oct 2 23:09:16 oxnet kernel: ata3.00: status: { DRDY } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/00:08:a8:29:53/04:00:31:00:00/40 tag 1 ncq 524288 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) Oct 2 23:09:16 oxnet kernel: ata3.00: status: { DRDY } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/00:10:a8:2d:53/04:00:31:00:00/40 tag 2 ncq 524288 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) Oct 2 23:09:16 oxnet kernel: ata3.00: status: { DRDY } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/08:18:a8:31:53/00:00:31:00:00/40 tag 3 ncq 4096 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) Oct 2 23:09:16 oxnet kernel: ata3.00: status: { DRDY } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/00:20:b8:3d:53/04:00:31:00:00/40 tag 4 ncq 524288 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) Oct 2 23:09:16 oxnet kernel: ata3.00: status: { DRDY } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/00:28:a8:45:53/04:00:31:00:00/40 tag 5 ncq 524288 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) Oct 2 23:09:16 oxnet kernel: ata3.00: status: { DRDY } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/00:30:a8:49:53/04:00:31:00:00/40 tag 6 ncq 524288 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) Oct 2 23:09:16 oxnet kernel: ata3.00: status: { DRDY } Oct 2 23:09:16 oxnet kernel: ata3.00: failed command: WRITE FPDMA QUEUED Oct 2 23:09:16 oxnet kernel: ata3.00: cmd 61/00:38:a8:4d:53/04:00:31:00:00/40 tag 7 ncq 524288 out Oct 2 23:09:16 oxnet kernel: res 40/00:bc:b8:41:53/00:00:31:00:00/40 Emask 0x10 (ATA bus error) [/pre]
October 5, 201015 yr Author Ok i pulled the parity drive from the bottom icydock (motherboard SATA) and moved it to the top ICYDock (supermicro sata). I am still averaging 3-4mb per sec, see the attached log, I am not seeing the same errors though. Also to note, when I moved this, the old sdb changed to sdc, and this drive which was sdd is now the new sdb. SDB -> SDC *empty 2TB drive* SDD -> SDB *parity* Any other advice aside from just like it take 140hours to finish? syslog_replace.txt
October 5, 201015 yr Did you add the jumper on the EARS drives? That might be your issue. See here: http://lime-technology.com/forum/index.php?topic=5384.0
October 5, 201015 yr Author After adding the jumper to the parity WDC WD20EARS drive, It is found in unRaid, but it will not allow the array to start. If I pull it out of the array and try to preclear it, I do not get any drive information, and I get the following error when I force it: =========================================================================== = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1 = Disk Pre-Read in progress: % complete = ( bytes of read ) = = = = = = = = = = Elapsed Time: 0:00:00 ./preclear_disk.sh: line 550: 1+( 1973925108)%() : syntax error: operand expected (error token is ") ") ============================================================================ == == Disk /dev/sdb has been successfully precleared == ============================================================================ I have not removed the jump and retried yet, is there something else I can do first? Thanks,
October 5, 201015 yr Author root@oxnet:/boot# hdparm /dev/sdb /dev/sdb: IO_support = 1 (32-bit) HDIO_GET_UNMASKINTR failed: Inappropriate ioctl for device HDIO_GET_DMA failed: Inappropriate ioctl for device HDIO_GET_KEEPSETTINGS failed: Inappropriate ioctl for device readonly = 0 (off) readahead = 256 (on) geometry = 46593/255/63, sectors = 3907029168, start = 0 Same as sdc root@oxnet:/boot# smartctl -d ata -A /dev/sdb smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. root@oxnet:/boot# smartctl -d ata -A -T permissive /dev/sdb smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
October 8, 201015 yr Author Anyone else have any other advice? If I take the jumper off, I can preclear my drive (at 110ish speed), but my parity sync is 3MB a sec If I put the jumper on 7-8, I cannot pre-clear, and my array will not start if the drive is assigned Any help would be greatly appreciated. Thanks.
October 8, 201015 yr Try formatting the drive with the jumper on in Windows or MacOS. Then try running preclear on it again.
October 8, 201015 yr Try formatting the drive with the jumper on in Windows or MacOS. Then try running preclear on it again. Ditto that. I had to do the same thing when I was messing around with the jumpers on the EARS drives. Once I partitioned the drives in Windows first, I could get back to business with UnRAID and the preclear script. Somewhat confusingly (to me anyway) is that I only put jumpers on 2 of my 3 EARS drives... and I have noticed no great difference in transfer rates or parity sync times.
October 8, 201015 yr Somewhat confusingly (to me anyway) is that I only put jumpers on 2 of my 3 EARS drives... and I have noticed no great difference in transfer rates or parity sync times. Other users have reported the same thing. The performance decrease associated with not using the jumper seems to be hit or miss. Even fewer users have reported corrupted data and other data-loss problems. That's the part that I find scary. Even if the risk is minimal, why risk it when a 2 cent jumper fixes it?
October 9, 201015 yr Author I'm just worried there is a bigger problems, people are reporting full parity sync speeds of 50-80m, and I am getting 3. Will the jumpers really make that big of a difference, or is there somewhere else I should be looking.
October 12, 201015 yr That definitely isn't normal. The jumper should not make that big of a difference (I think the performance hit is supposed to be around 30%). Run SMART on the drive and start a thread in the 'hardware' forum with the SMART results. At a glance it sounds like you just have a bad drive.
December 15, 201015 yr =========================================================================== = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1 = Disk Pre-Read in progress: % complete = ( bytes of read ) = = = = = = = = = = Elapsed Time: 0:00:00 ./preclear_disk.sh: line 550: 1+( 1973925108)%() : syntax error: operand expected (error token is ") ") ============================================================================ == == Disk /dev/sdb has been successfully precleared == ============================================================================ I have a similar problem... I have just added two 2TB WDEARS drives - both jumpered. One preclears okay - the other one is stuck on a similar message to what you have above. And so I cannot preclear it now. Did you find an answer to your issue..? Is this a bad drive and should I RMA it...? I'm pretty new to this so all thoughts welcome...
December 15, 201015 yr the disk has stopped responding. This is because after changing the jumper the pre-clear script attempts to access its geometry and gets it wrong. (Others discovered it was possible to get it to wake up and respond again by power cycling it) To proceed you can do this: Stop the server. Power down the server Power back up Run this command to clear the initial few sectors on the disk. dd if=/dev/zero of=/dev/sdb count=8 Then you should be able to run the pre-clear script on it. (These same symptoms have shown up before if a drive was used first without a jumper and then a jumper added.) Now, it is possible the drive has an actual problem, but these steps will get you past the geometry issue and the lock-up issue others have seen.
December 15, 201015 yr Thanks for the swift response. Everything I've read before about the speed of you guys is true ! I will try that - I'm currently in a parity check after powering down and restarting everything, so I'll retry after that's done. Many thanks
February 3, 201115 yr Author I am sorry to resurrect my own dead post,but i have been living with my unRaid with no parity awhile now. So I looked back on all the forums, found all the updates to support AF drives (specifically in preclear). So I took my drive out and formatted it in windows as suggested, then pushed it back to my unRaid box. I was not able to preclear until I removed the jumper. Once I did so, the drive was pre-clearable, so i started the process. Step 1 and 2 ran at about 100MB/s here was the output: ================================================================== 1.2 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Step 10 of 10 - Verifying the clear has been successful. = Disk Post-Clear-Read completed DONE Disk Temperature: 32C, Elapsed Time: 27:27:48 ============================================================================ == == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ./preclear_disk.sh: line 724: [: : integer expression expected ./preclear_disk.sh: line 753: [: : integer expression expected No SMART attributes are FAILING_NOW 1 sector is pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I then added my drive to the array in the parity slot, started the array and the sync and presto!! Total size: 2 TB Current position: 1.12 GB (0.0%) Estimated speed: 3.47 MB/sec Estimated finish: 9588.3 minutes I need to find out the issue here, what can i provide to help figure this out, still only 3MB a sec, and only 150 hours left till completion???
Archived
This topic is now archived and is closed to further replies.