Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

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

Featured Replies

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

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.

  • Author

Both cache devices are connected on its own M2 connector.

I'll swap the two devices, and see which one is showing.

Thanks!

Edited by wblondel

Missed the M.2 part, so it's the one on socket M.2_1 non responding:

 

Quote

When a device in SATA mode is installed on the M.2_1 socket, SATA_1 port cannot be used.

 

  • Author

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

6 minutes ago, wblondel said:

I believe the drive died... just with a reboot?

It's pretty common when there's a problem with an SSDs for it die after a reboot/power cycle, i.e., it keeps working until a re-initialization is needed.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.