Hi all, just out of interest what would you say major issue with this drive is?  I got the red x, drive is disabled, contents emulated etc.....

 

Going to try a restart but...

 

Thankfully it's under warranty

 

Screenshot and logs attached (pre reboot).

 

obi-wan-diagnostics-20190518-0556.zip

SMART looks fine, and since there are several timeout errors with different drives before that one getting disable it suggest the disk isn't the problem, e.g:

 

May 18 14:17:13 Obi-Wan kernel: sd 11:0:4:0: attempting task abort! scmd(0000000053efd4d5)
May 18 14:17:13 Obi-Wan kernel: sd 11:0:4:0: [sdl] tag#0 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00
May 18 14:17:13 Obi-Wan kernel: scsi target11:0:4: handle(0x000d), sas_address(0x4433221106000000), phy(6)
May 18 14:17:13 Obi-Wan kernel: scsi target11:0:4: enclosure logical id(0x590b11c03824d600), slot(5)
May 18 14:17:13 Obi-Wan kernel: sd 11:0:4:0: task abort: SUCCESS scmd(0000000053efd4d5)
May 18 14:17:22 Obi-Wan kernel: sd 11:0:2:0: attempting task abort! scmd(0000000053efd4d5)
May 18 14:17:22 Obi-Wan kernel: sd 11:0:2:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00
May 18 14:17:22 Obi-Wan kernel: scsi target11:0:2: handle(0x000b), sas_address(0x4433221104000000), phy(4)
May 18 14:17:22 Obi-Wan kernel: scsi target11:0:2: enclosure logical id(0x590b11c03824d600), slot(7)
May 18 14:17:25 Obi-Wan kernel: sd 11:0:2:0: task abort: SUCCESS scmd(0000000053efd4d5)
May 18 14:21:20 Obi-Wan kernel: sd 11:0:2:0: Power-on or device reset occurred
May 18 14:21:20 Obi-Wan kernel: sd 11:0:4:0: Power-on or device reset occurred

First thing would be to see if these disks plus disk2 share anything in common, like a power splitter, miniSAS cable, etc.

 

It's hard to overlook coincidences, but I can't see why it would happen at exactly the same time I stopped the docker service lol.

 

After the reboot those errors have not come back from the log.  I have backups so, I've just deleted the partition from the disk and re added to the array.  It's running in emulated mode anyway, so may as well give it a go and in the mean while figure out if all those disks are on the same perc cable or what. I did get a new cable about a month ago (have a Dell Perc 310 running in IT mode).  The new thread ripper board took me down to only 6 onboard SATA ports so was quite grateful for it!

 

Thanks for the help.

 

 

4 hours ago, Marshalleq said:

I've just deleted the partition from the disk and re added to the array.

Why did you delete the partition? If you follow the FAQ for re-enabling a disk, the whole disk will be recreated from parity, emulated filesystem and all.

As an aside, where I'm from, "to pork" is an activity synonymous with, "to copulate" so I must confess to nearly choking on my coffee when I read the title.

 

I notice you're a Kiwi, so it's a bit like "to root" to you guys I guess.

 

Edited May 18, 20197 yr by CHBMB

@CHBMBLOL - I knew it would stand out a bit but didn't think I'd get someone choking - perhaps we could rebrand HDD docks to HDD porkers lol.

 

@jonathanm I didn't do a lot of reading - the one thread I read seemed to say you couldn't re-enable - I guess that's what happens when you're tired.  Though I'm guessing you meant to say 'the whole disk won't be recreated from parity, filesystem and all?  Because by deleting the partition I am now getting the whole disk recreated from parity, filesystem and all.

 

I figured doing it that way rather than finding a way to just re-add it would likely find any bad sectors / issues better.

 

1 hour ago, Marshalleq said:

'the whole disk won't be recreated from parity, filesystem and all?  Because by deleting the partition I am now getting the whole disk recreated from parity, filesystem and all.

 

Rebuilds always rebuild the entire drive.