[Solved] Disk red balled

[wgstarks]

Not sure of the best way to handle this.

 

Here's the relevant log entries from unmenu-

Jun 26 17:17:03 Brunnhilde kernel: ata1: SATA max UDMA/133 abar m2048@0xf7332000 port 0xf7332100 irq 50 (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: scsi1 : mvsas (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: scsi 1:0:4:0: Direct-Access     ATA      ST3000DM001-9YN1 CC46 PQ: 0 ANSI: 5 (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] 4096-byte physical blocks (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] Write Protect is off (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] Mode Sense: 00 3a 00 00 (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Jun 26 17:17:03 Brunnhilde kernel:  sdk: sdk1 (Drive related)
Jun 26 17:17:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] Attached SCSI disk (Drive related)
Jun 26 17:17:05 Brunnhilde emhttp: ST3000DM001-9YN166_W1F03MN3 (sdk) 2930266584 (Drive related)
Jun 26 17:17:05 Brunnhilde kernel: md: import disk7: [8,160] (sdk) ST3000DM001-9YN166_W1F03MN3 size: 2930266532 (Drive related)
Jun 26 17:17:06 Brunnhilde emhttp: shcmd (17): /usr/local/sbin/set_ncq sdk 1 $stuff$> /dev/null (Drive related)
Jun 26 17:17:06 Brunnhilde kernel: md7: running, size: 2930266532 blocks (Drive related)
Jun 26 17:17:08 Brunnhilde emhttp: shcmd (37): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md7 /mnt/disk7 |$stuff$ logger (Other emhttp)
Jul  5 07:46:14 Brunnhilde unmenu[1372]: WARNING: GPT (GUID Partition Table) detected on '/dev/sdk'! The util fdisk doesn't support GPT. Use GNU Parted. (Minor Issues)
Jul  5 07:51:51 Brunnhilde unmenu[1372]: WARNING: GPT (GUID Partition Table) detected on '/dev/sdk'! The util fdisk doesn't support GPT. Use GNU Parted. (Minor Issues)
Jul  5 07:55:00 Brunnhilde unmenu[1372]: WARNING: GPT (GUID Partition Table) detected on '/dev/sdk'! The util fdisk doesn't support GPT. Use GNU Parted. (Minor Issues)
Aug 24 04:42:32 Brunnhilde kernel: sd 1:0:4:0: [sdk] command e5454000 timed out (Drive related)
Aug 24 04:59:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] Unhandled error code (Errors)
Aug 24 04:59:03 Brunnhilde kernel: sd 1:0:4:0: [sdk]   (Drive related)
Aug 24 04:59:03 Brunnhilde kernel: sd 1:0:4:0: [sdk] CDB:  (Drive related)
Aug 24 04:59:03 Brunnhilde kernel: end_request: I/O error, dev sdk, sector 4041344 (Errors)
Aug 24 04:59:03 Brunnhilde kernel: md: disk7 read error, sector=4041280 (Errors)
Aug 24 04:59:18 Brunnhilde kernel: sd 1:0:4:0: [sdk] Unhandled error code (Errors)
Aug 24 04:59:18 Brunnhilde kernel: sd 1:0:4:0: [sdk]   (Drive related)
Aug 24 04:59:18 Brunnhilde kernel: sd 1:0:4:0: [sdk] CDB:  (Drive related)
Aug 24 04:59:18 Brunnhilde kernel: end_request: I/O error, dev sdk, sector 4041344 (Errors)
Aug 24 04:59:18 Brunnhilde kernel: end_request: I/O error, dev sdk, sector 4041344 (Errors)
Aug 24 04:59:18 Brunnhilde kernel: md: disk7 write error, sector=4041280 (Errors)


Total Lines: 31

 

Would welcome any advice.

[dgaschk]

http://lime-technology.com/wiki/index.php/Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F

[wgstarks]

Thanks for the link. I went through the different troubleshooting steps without much luck. Didn't find any loose connectors. Couldn't re-add the drive or get a smart report. I've transferred all the data to another drive and done a new config. Parity is running now. Tried installing the drive in another spare slot while I had the array stopped, but I'm still not seeing it. Would I have to re-boot the enclosure to see the drive again or is it just toast? Wouldn't surprise me. I bought 4 of these 3TB Seagate drives at the same time and this is the third one I've lost in the past 6 months or so.

[itimpi]

I would suggest plugging the drive into a PC and running the Seagate tests (Seatools) against it to see what they say.

[dgaschk]

Drives will aften start responding after a power cycle.

[wgstarks]

I would suggest plugging the drive into a PC and running the Seagate tests (Seatools) against it to see what they say.

Thanks but I don't own a PC and Seagate hasn't seen fit to write a Mac version of Seatools. Might take a shot with Disk Utility though.

 

 

Drives will aften start responding after a power cycle.

Thanks. The other 2 of these Seagate drives that failed did it in exactly the same manor. Constant I/O failures. I'm sure there a lots of possible causes but I'm using latching cables so I don't think they're loose. My experience with Seagate drives hasn't been great. This one may come back to life after a power cycle but I think I'll save myself some headaches and go ahead and replace it now (next time the 4TB WD Reds go on sale anyway).

[itimpi]

I have had some Seagate 3TB disks that caused problems.  One indication was that the reallocated sector count in SMART reports was a high value (3000+).  On a new drive one expects this to be 0, or at least a very low value.  You also should not have any Pending sectors.

[wgstarks]

I have had some Seagate 3TB disks that caused problems.  One indication was that the reallocated sector count in SMART reports was a high value (3000+).  On a new drive one expects this to be 0, or at least a very low value.  You also should not have any Pending sectors.

The new parity has finished. I may try rebooting the enclosure this evening to see if I can get the drive to spinup so I can get a smart report.

[wgstarks]

Tried rebooting. No joy. I'm guessing the drive is toast, I don't think it's even spinning up. Definitely no I/O anyway. Tried the drive in different slots but that didn't make any difference. Not worth too much trouble anyway, because there's no way I would trust it back in the array now even if it did come back.

 

Thanks to everyone for your help.