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.

Both Cache drives disappeared after adding new disk

Featured Replies

Hi,

yesterday both cache disks disapperead and are now only shown as "Historical Devices" the cache setting does not say "missing". Here is what I have done before:

 

  • Connected a new drive via case usb port
  • Ran two preclear cycles
  • Stopped the array; increased array slots by one and selected the new diskt
  • Then the dropdown menu for the first of my two cache ssd's became blank and I could not select anything
  • Unraid listed the disk as "Historcal Device"; fdisk -l did not show the disk anymore;
  • I rebooted the server
  • Now both cache drives are "Historical" and not selectable nor recognized by fdisk.
  • I tried removing the newly added disk from the parity but it did not help

 

What would be my next step? Could the motherboard have a limit on how many drives it can detect? Any pointers are appreciated.

 

 

Here are some specs
 

Unraid Version: Version: 6.8.3
MB: ASRock H110M-DVS R3.0; American Megatrends Inc., Version P1.20
CPU: Intel Pentium G4560 @ 3.5RAM: 2* 4GB
Array: 1 Parity Disk; 6 Data Disks between 4 and 8 TB (including the new one)
Cache: 2* 240GB San Disk SSD Plus
Diagnostics: attached

server02-diagnostics-20201228-0155-anonymized.zip

Edited by Lerrrtaste
typo

  • Community Expert

Both are failing to initialize:

Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: limiting SATA link speed to 3.0 Gbps
Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata4: limiting SATA link speed to 3.0 Gbps
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: reset failed, giving up

 

Try different cables, you can then just check if they are detected in the board BIOS, if they aren't they also won't be detected by Unraid.

  • Author
2 minutes ago, JorgeB said:

Both are failing to initialize:


Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0)
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: limiting SATA link speed to 3.0 Gbps
Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata4: limiting SATA link speed to 3.0 Gbps
Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16)
Dec 28 01:18:08 Server02 kernel: ata1: reset failed, giving up

 

Try different cables, you can then just check if they are detected in the board BIOS, if they aren't they also won't be detected by Unraid.

Thanks for looking into it, I will try new cables and report back.

  • Author

I tried a different cable and then removed them from my server completely and tried connecting it to my PC with a SATA to USB adapter: Not showing up anyhwere...

 

Could they possibly died simulatinously? One of them is rather new.

 

No idea what else I could try :/

  • Community Expert

If they are not detected in different computer they are likely dead, not much else you can do.

  • Author
19 minutes ago, JorgeB said:

If they are not detected in different computer they are likely dead, not much else you can do.

Ok, thanks a lot for your help. To the backups it is then...

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.