This morning I received a notification my unraid server (v6.9.2) that Disk 6 was disabled and 'in error state'. I've be very lucky and have not had to deal with any drive failures in many many years, I've replaced drives over the last few years due to age usually around 4-5 years rather then failures as they were not NAS drives. I prefer the proactive approach but probably due to paranoia more then anything LOL

 

I was going to run a File System Check, following the instructions in the Manual, Drive_shows_as_unmountable. Steps I've followed so far:

- Ran Diagnostic Tool

- Stopped the Array

- Powered Down Server

- Checked cables in Drive Trays and to LSI Card

- Powered Server back on, I have auto mount set as off

 

I was going to start in 'Maintenance Mode' but the Disk now shows as 'Unassigned' and the drive is no longer listed, I assume because it is not longer considered to be a valid drive for assignment? I have not started the array in maintenance mode or otherwise. Looking for some direction before I do anything further.

 

Do I leave the disk as 'Unassigned' and start the array in maintenance mode and do the File System Check, and repair the File System if needed?

 

Or should I just replace the drive and start the rebuild?

 

The drive is question was next to be replaced, so I already have a replacement drive pre-cleared and ready.

 

First thing I did was run the diagnostic tool, results attached. Maybe if someone could take a look? I've also attached the post-reboot syslog in case it might be helpful.

 

I appreciate any help and advice!

mrnas-diagnostics-20220813-1149.zip mrnas-syslog-20220813-1349.zip

Diagnostics shows array started in normal mode, disabled/emulated disk6 mounted but I don't see its SMART report. There is a different unassigned disk in smart.

 

Post screenshots of Array Devices and Unassigned Devices.

 

Thanks trurl!

 

I noticed that the SMART report for disk6 was missing and just thought that that it was missing because it was disabled and couldn't be accessed by unraid. 

 

Here's the screenshot of Unassigned Devices, it's a precleared drive.

 

 

 

Here's the screenshot of the Array Devices, the only drive available in the dropdown list for drive6 is the same drive in the unassigned disks.

 

Those screenshots don't have the same sdX as your diagnostics. Did you reboot before getting them?

I rebooted after getting the diagnostics. So the Diagnostics are pre-reboot and the screenshots are post-reboot.

 

 

Shutdown, check connections, both ends, SATA and power, including splitters. Reboot and post new diagnostics

Powered down, checked all connections and here's a new diagnostics.

 

 

mrnas-diagnostics-20220813-1636.zip

Still not seeing SMART for disk6, and since you didn't start the array can't tell if emulated disk6 mounts.

 

Can you see disk6 in the webUI anywhere? Can you see it in BIOS?

I don't see the disk listed anywhere in the WebUI, I also checked System Devices under Tools as well. The drive is connected to a LSI SAS card so I didn't expect that it would show in the BIOS.

 

I physically swapped the 'Unassigned Device' drive and drive that was disk6 to rule out bad cable or bad connector and the 'Unassigned Device' drive was detected but the drive that was assigned to disk6 was still not detected. 

 

Should/Can I start the array with the disk missing? I wasn't sure if that would unassign the slot, making a drive rebuild impossible.

 

The Array Operations shows 'Stopped. Configuration valid.'

 

 

Array Devices, shows the disk 'Device is missing (Disabled), contents Emulated'.

 

Here's a new diagnostics just incase it's useful. 

 

mrnas-diagnostics-20220813-1744.zip

12 hours ago, Seonac said:

Should/Can I start the array with the disk missing?

You can, and check that the emulated disk mounts, you should then replace the missing disk ASAP.

Thank you!

 

I started the array and was able to browse the emulated contents of disk6. I stopped the array and replaced disk6 with a new precleared drive already in the server and started the rebuild process.