Second Cache Device disappeared after updating to 6.8 - not recognized AT ALL


wblondel

Recommended Posts

Hi,

 

Since I updated to Unraid 6.8 and rebooted my system, one of my two Cache Devices completely disappeared from my system.

It doesn't show in the Cache Devices list, it doesn't show on the Unassigned Devices list, and I can't see it with a fdisk -l.

I rebooted multiple times to make sure.

 

Both Cache Devices are SSD WESTERN DIGITAL Green 120 Go M.2 2280 and they were working fine before the update/reboot.

 

Is it possible that one of two died ?

 

tower-diagnostics-20191216-1143.zip

Link to comment

Assuming it's connected to onboard SATA port1 it's not responding:

Dec 16 11:24:47 Tower kernel: ata1: COMRESET failed (errno=-16)
Dec 16 11:24:47 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 16 11:24:47 Tower kernel: ata1: COMRESET failed (errno=-16)
Dec 16 11:24:47 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 16 11:24:47 Tower kernel: ata1: COMRESET failed (errno=-16)
Dec 16 11:24:47 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps
Dec 16 11:24:47 Tower kernel: ata1: COMRESET failed (errno=-16)
Dec 16 11:24:47 Tower kernel: ata1: reset failed, giving up

 

Try replacing cables, or swap with another device.

Link to comment

I removed the recognized drive, and moved the unrecognized drive from the M.2_1 socket to the M.2_2 socket, it is still not recognized.

 

Dec 16 12:39:45 Tower kernel: ata6: COMRESET failed (errno=-16)
Dec 16 12:39:45 Tower kernel: ata6: link is slow to respond, please be patient (ready=0)
Dec 16 12:39:45 Tower kernel: ata6: COMRESET failed (errno=-16)
Dec 16 12:39:45 Tower kernel: ata6: link is slow to respond, please be patient (ready=0)
Dec 16 12:39:45 Tower kernel: ata6: COMRESET failed (errno=-16)
Dec 16 12:39:45 Tower kernel: ata6: limiting SATA link speed to 3.0 Gbps
Dec 16 12:39:45 Tower kernel: ata6: COMRESET failed (errno=-16)
Dec 16 12:39:45 Tower kernel: ata6: reset failed, giving up

It's not a socket problem, good.

I believe the drive died... just with a reboot? Well, that was a cheap drive anyway. It lived less than a year though. I'll contact Western Digital.

 

Thank you for your help!

Edited by wblondel
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.