1 drive is faulty. Red X. Can I remove it from array, pre-clear it once again, and re-assign to array?

[jang430]

Ok, will see if I can get all cables replaced at the same time, then upgrade unraid, correct?  Then do a diagnostic while the drive is not on array?

[trurl]

Upgrading is lower priority. Get your array healthy first.

[jang430]

Hi.  Replaced all the SATA cables for all drives.  Attaching new diagnostics.

diagnostics-20180902-1032.zip

smart-20180901-2018.zip

[trurl]

Disk looks OK. And there is no need to post SMART with Diagnostics since Diagnostics already contains SMART for all disks.

 

Your syslog is flooded with these, which makes it difficult to read:

Sep  1 19:55:59 chu root: error: plugins/preclear.disk/Preclear.php: wrong csrf_token

See here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?page=2&tab=comments#comment-545988 for cause.

 

Still some problems communicating with disks.

 

ata5 is cache, ata3 is disk1.

 

I don't know if this would interfere with rebuild attempt or not.

 

Sep  1 13:27:08 chu kernel: ata5.00: ATA-10: WDC WD30EFRX-68N32N0,      WD-WCC7K3LLVJKC, 82.00A82, max UDMA/133
...
Sep  1 13:27:08 chu kernel: ata3.00: ATA-9: WDC WD30EFRX-68EUZN0,      WD-WCC4N5UZ0HCC, 82.00A82, max UDMA/133
...
Sep  1 16:34:47 chu kernel: ata5.00: exception Emask 0x0 SAct 0x1fe SErr 0x0 action 0x0
Sep  1 16:34:47 chu kernel: ata5.00: irq_stat 0x40000008
Sep  1 16:34:47 chu kernel: ata5.00: failed command: WRITE FPDMA QUEUED
Sep  1 16:34:47 chu kernel: ata5.00: cmd 61/08:08:40:a3:30/00:00:00:00:00/40 tag 1 ncq dma 4096 out
Sep  1 16:34:47 chu kernel:         res 41/10:00:40:a3:30/00:00:00:00:00/00 Emask 0x481 (invalid argument) <F>
Sep  1 16:34:47 chu kernel: ata5.00: status: { DRDY ERR }
Sep  1 16:34:47 chu kernel: ata5.00: error: { IDNF }
Sep  1 16:34:47 chu kernel: ata5.00: configured for UDMA/133
Sep  1 16:34:47 chu kernel: ata5: EH complete
...
Sep  1 22:30:57 chu kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep  1 22:30:57 chu kernel: ata3.00: failed command: IDENTIFY DEVICE
Sep  1 22:30:57 chu kernel: ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 13 pio 512 in
Sep  1 22:30:57 chu kernel:         res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep  1 22:30:57 chu kernel: ata3.00: status: { DRDY }
Sep  1 22:30:57 chu kernel: ata3: hard resetting link
Sep  1 22:30:57 chu kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep  1 22:30:57 chu kernel: ata3.00: configured for UDMA/133
Sep  1 22:30:57 chu kernel: ata3: EH complete

 

[jang430]

Hi.  If you say it looks good, should be able to rebuild successfully right?  Any other thing I can do to ensure it's success?

[trurl]

Fix this before trying rebuild so your next diagnostics will be cleaner:

 

32 minutes ago, trurl said:

Your syslog is flooded with these, which makes it difficult to read:

Sep  1 19:55:59 chu root: error: plugins/preclear.disk/Preclear.php: wrong csrf_token

See here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?page=2&tab=comments#comment-545988 for cause.

 

 

[jang430]

ok.  Will do it before rebuild.  

[jang430]

After successfully rebuilding the Disk1, I now see "Unmountable Disk Present" . It's my cache drive now.  I'm given the option to format.  What do I do?

[trurl]

7 hours ago, jang430 said:

What do I do?

Post diagnostics of course

[jang430]

Hi trurl, 

 

See attached.  Thanks

diagnostics-20180903-0752.zip

 

**Just a note.  When I initially cannot get my Disk1 working, I replaced all SATA cables, and it still failed.  I went back to check all the power cables.  For isolation purposes, I switched the power cable of Disk1 with another Disk that I didn't take note of.  The rebuild finished successfully, as I shared above.  Now, I'm thinking whether it's the power cable that is originally connected at Disk1 that is the power cable that I connected to the cache drive hence the cache drive is acting up.  Please take a look at logs.  If nothing else, I'll go back onsite and pullout the unit to test the power cable connected.

[trurl]

Syslog shows still having the same problems communicating with that disk as I mentioned above (ata5). Of course formatting will lose all data on that disk. It is also showing "unsupported partition" which we have been seeing in some other threads.

 

I'll tag @johnnie.black and see if he has some ideas.

[jang430]

Thanks.  Added some info to my last post.  Don't want to be reformatting.  I'll pull out the unit to test locally, specially the power cable issue. 

[JorgeB]

The unsupported partition issue is almost certainly related to the ATA errors, disk itself looks fine so first replace both cables and connect it to a different SATA port, you still have 2 free, to rule everything else out, if there are still issues it's likely the disk.

[jang430]

Hi @trurl, @johnnie.black, thanks.  Solved this problem by changing my power supply cable.  When I changed it from disk1 to cache, the cache went berserk.  I finally replaced it, working already!