Came home after work today and found my server making a bit more noice than normally. When looking at my dashboard I've noticed that disk 9 was disabled and that the contents were being emulated as well that I should spin down my disk 9.

 

Before doing anything, I prefer to have your input about what I should do next.toschestation-diagnostics-20250318-2158.ziptoschestation-smart-20250318-1356.zip

Disk dropped offline, so there, so SMART, power down, check/replace cables and post new diags after array start.

Thanks for the reply. Tried several cables but no luck. Everytime when I restart disk 9 mentions "no device". Will probably order some new cables as I've had no luck with the ones I have.

See if the disk is being detected din the BIOS, if not, it may be dead.

BIOS doesn't detect it so probably a dead disk.

As it has been a while that I've added a new drive, is this still the correct way to replace the failed disk?

1. Stop the array

2. Unassign the old drive if still assigned (to unassign, set it to No Device)

3. Power down

-> These steps have already been done as I've shutdown the system.

 

4. [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing)

5. Install the new drive

6. Power on

7. Assign the new drive in the slot of the old drive

8. Go to the Main → Array Operation section

9. Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button

10. The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives

https://docs.unraid.net/unraid-os/manual/storage-management/#normal-replacement

Not related to rebuild.

 

Many of your disks are too full, and your user shares have no Minimum Free set. Expect to have out-of-space errors.

Server is running again. Will have a look at the "minimum free" set

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#minimum-free-space