Both Cache drives disappeared after adding new disk


Recommended Posts

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
Link to comment

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.

Link to comment
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.

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.