January 24, 201016 yr Hi, I know that clearing a new hard drive can be long but... As I say in my title I have a brand new 750gb samsung spinpoint hard drive and after 24hres only 15% clearing done. Should I let it go( my array will be down for a week!!!) or should I try to stop it?
January 24, 201016 yr my array will be down for a week!!! It's a good idea to use the preclear_disk tool before adding new disks to your array. That way your array won't be down at all. See this post: http://lime-technology.com/forum/index.php?topic=2817.0
January 24, 201016 yr Hi, I know that clearing a new hard drive can be long but... As I say in my title I have a brand new 750gb samsung spinpoint hard drive and after 24hres only 15% clearing done. Should I let it go( my array will be down for a week!!!) or should I try to stop it? Please post a syslog... Odds are high your disk is encountering errors and reducing its data rate to intolerable levels trying to adapt, but you will not know for sure until you analyze the log. If you are using a recent version of unRAID you can simply browse to //tower/log/syslog and then save the file to your PC. Zip it up, and then attach it to your next post. For older versions of unRAAID you can capture the syslog as described in the wiki under troubleshooting. A 750Gig drive should take a few hours to clear... As already mentioned, next time, if you use the preclear_disk.sh script, the clearing will take place while your array is on-line. Then, when you add the disk to your array, the downtime will only be a few minutes. Joe L.
January 24, 201016 yr Author Ok something really wrong!!! Try to make log but end up with almost a 1gb files(stop because no more place on the flash drive) I took a look at the array and the drive are down except the one clearing. So I think I will hit the power button to shut it down and disconnect the drive and reboot and see if everything and ok. If everything ok I will reconnect the drive and try to preclear it. What do you think... sounds good?
January 24, 201016 yr Ok something really wrong!!! Try to make log but end up with almost a 1gb files(stop because no more place on the flash drive) I took a look at the array and the drive are down except the one clearing. So I think I will hit the power button to shut it down and disconnect the drive and reboot and see if everything and ok. If everything ok I will reconnect the drive and try to preclear it. What do you think... sounds good? If you can get to a command prompt via a telnet command, type sed 10000q /var/log/syslog Then paste from the telnet window into notepad, then proceed to zip it and attach it. It will at least give us an idea of what is happening now. Then reboot.
January 24, 201016 yr Author Ok thanks, here is the log: -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4: EH complete -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 > Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:f7:48:d7/00:00:00:00:00/e2 tag 0 dma 86016 out > Jan 23 21:29:32 tower kernel: res 61/04:a8:f7:48:d7/84:00:02:00:00/e2 Emask 0x1 (device error) > Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } > Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } > Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 > Jan 23 21:29:32 tower kernel: ata4: EH complete > Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 > Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:f7:48:d7/00:00:00:00:00/e2 tag 0 dma 86016 out > Jan 23 21:29:32 tower kernel: res 61/04:a8:f7:48:d7/84:00:02:00:00/e2 Emask 0x1 (device error) > Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } > Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } > Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 > Jan 23 21:29:32 tower kernel: ata4: EH complete > Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] 1465149168 512-byte hardware sectors (750156 MB) > Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 > Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:f7:48:d7/00:00:00:00:00/e2 tag 0 dma 86016 out > Jan 23 21:29:32 tower kernel: res 61/04:a8:f7:48:d7/84:00:02:00:00/e2 Emask 0x1 (device error) > Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } > Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } > Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 > Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 > Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Sense Key : 0xb [current] [descriptor] > Jan 23 21:29:32 tower kernel: Descriptor sense data with sense descriptors (in hex): > Jan 23 21:29:32 tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 > Jan 23 21:29:32 tower kernel: 02 d7 48 f7 > Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] ASC=0x0 ASCQ=0x0 > Jan 23 21:29:32 tower kernel: end_request: I/O error, dev sdc, sector 47663351 Jan 23 21:29:32 tower kernel: ata4: EH complete> Jan 23 21:29:32 tower kernel: ata4: EH complete > Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Write Protect is off > Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 > Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 > Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out > Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) > Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } > Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } > Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 > Jan 23 21:29:32 tower kernel: ata4: EH complete > Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 > Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 > Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out > Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) > Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } > Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } > Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 > Jan 23 21:29:32 tower kernel: ata4: EH complete > Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001-bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 -bash: Jan: command not found Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) -bash: syntax error near unexpected token `(' root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } Jan 23 21:29:32 tower kernel: ata4: EH complete-bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 -bash: Jan: command not found Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out root@tower:~# Jan 23 21:29:32 tower kernel: ata4: EH complete -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 -bash: Jan: command not found Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out -bash: Jan: command not found Jan 23 21:29:32 tower kernel: ata4: EH complete root@tower:~# Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) -bash: syntax error near unexpected token `(' root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4: EH complete -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] 1465149168 512-byte hardware sectors (750156 MB) -bash: syntax error near unexpected token `(' root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out -bash: Jan: command not found Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) root@tower:~# Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) -bash: syntax error near unexpected token `(' root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } -bash: Jan: command not found Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT }root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4: EH complete -bash: Jan: command not found Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 root@tower:~# Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Write Protect is off Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00 -bash: Jan: command not found Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: irq_stat 0x40000001 -bash: Jan: command not found Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: cmd ca/00:a8:9f:49:d7/00:00:00:00:00/e2 tag 0 dma 86016 out -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: res 61/04:a8:9f:49:d7/84:00:02:00:00/e2 Emask 0x1 (device error) Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Sense Key : 0xb [current] [descriptor] -bash: syntax error near unexpected token `(' root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: status: { DRDY DF ERR } Jan 23 21:29:32 tower kernel: Descriptor sense data with sense descriptors (in hex): -bash: Jan: command not found Jan 23 21:29:32 tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: error: { ABRT } Jan 23 21:29:32 tower kernel: 02 d7 49 9f-bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4.00: configured for UDMA/133 -bash: Jan: command not found Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] ASC=0x0 ASCQ=0x0root@tower:~# Jax00 driverbyte=0x08 kernel: sd 4:0:0:0: [sdc] Result: hostbyte=0 Jan 23 21:29:32 tower kernel: end_request: I/O error, dev sdc, sector 47663519 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] Sense Key : 0xb [current] [descriptor] -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: Descriptor sense data with sense descriptors (in hex): -bash: syntax error near unexpected token `(' root@tower:~# Jan 23 21:29:32 tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: 02 d7 49 9f -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: sd 4:0:0:0: [sdc] ASC=0x0 ASCQ=0x0 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: end_request: I/O error, dev sdc, sector 47663519 -bash: Jan: command not found root@tower:~# Jan 23 21:29:32 tower kernel: ata4: EH complete -bash: Jan: command not found
January 24, 201016 yr As you might expect, the errors are not normal. When you reboot, you might consider powering down and checking the cables to the drive you are adding. (I am assuming it is /dev/sdc as that is the device that is failing. ) The power or data cable might be loose, or it might be the drive itself has failed. We won't know until you reboot and can get a SMART report on the drive by running: smartctl -a -d ata /dev/sdc Joe L.
January 24, 201016 yr Author Thank you for the help. End up that the new hard drive was a bad one. THanks Yan
Archived
This topic is now archived and is closed to further replies.