Hello,

 

I logged into my NAS a few days ago and one of my 10TB WD Red Pro drives had 31 write errors on it and showed up as disabled and that my content was being emulated. I immediately stopped my array to prevent data loss and ran an extended SMART test which passed (see attached zip). Is it safe to re-enable the disk? If so, how do I do so?

 

I've also attached a whole diagnostics report. Any help would be greatly appreciated!

 

Thanks,

Chris

nas-diagnostics-20200804-2157.zip nas-smart-20200804-2151.zip

Diags are after rebooting so we can't see what happened but the disk looks fine, recommend replacing/swapping cables to rule them out and then rebuild on top (assuming the emulated disk is mounting correctly and contents look OK).

 

P.S. you should update to latest beta.

Thanks for the response! I was actually logging into my NAS to update to the latest beta when I found my disks disabled and figured it was safest to get my array healthy again before doing the upgrade.

 

I swapped the cable on the disabled disk and remounted it in the hot-swap bay to be safe. How do I go about rebuilding that disk? Should I follow the steps outlined here? https://wiki.unraid.net/UnRAID_Manual_-_FAQ

 

Thanks!

Chris

Edited August 5, 20205 yr by Christopher Haws

No need to remove the disk, you can follow this.

I unassigned the drive, started the array and then tried stopping the array, but for some reason it is stuck in the "stopping" state.

 

At the bottom of the screen it shows:  Array Stopping•Retry unmounting disk share(s)...

 

And the syslogs show the following (repeated many times):

Aug  5 11:30:39 nas emhttpd: shcmd (265902): umount /mnt/disk1
Aug  5 11:30:39 nas root: umount: /mnt/disk1: target is busy.
Aug  5 11:30:39 nas emhttpd: shcmd (265902): exit status: 32
Aug  5 11:30:39 nas emhttpd: Retry unmounting disk share(s)..

 

Running fuser on the mount point shows that "mount" is the only thing accessing it:

root@nas:~# fuser -vm /mnt/disk1
                     USER        PID ACCESS COMMAND
/mnt/disk1:          root     kernel mount /mnt/disk1

 

Edited August 5, 20205 yr by Christopher Haws

@johnnie.black, Thanks for your help. I ended up finding killing the docker process manually to allow my array to stop. I finished the process in the link you provided and everything is back up and running!

 

Thanks!

Chris