I'm having some issues getting the array working again with unraid.

 

Version: 6.2.4

 

I was doing an update to a plex docker container and the system hung. It never finished updating the container and the server became completely unresponsive. I came home a while later and rebooted the server, as it wasn't responding. It brings up the web ui just fine now, but whenever I start the Arrays using the WebUI it hangs and never starts. I'm still able to ssh to the device, so I was able to grab a syslog.

 

I've also attached a picture of my drives. 

 

Around line 3165 of the syslog I see:

Nov 14 19:36:32 Tower emhttp: err: shcmd: shcmd (205): exit status: -119
Nov 14 19:36:32 Tower emhttp: mount error: No file system (-119)
Nov 14 19:36:32 Tower emhttp: shcmd (206): umount /mnt/disk6 |& logger
Nov 14 19:36:32 Tower root: umount: /mnt/disk6: not mounted

 

Which seems like drive 6 is failing? But why wouldn't the array just start with that drive in a 'failed' state?

 

Edit: Smart seems to report no errors with disk6. I attached the smart test report.

syslog.txt

smart-drive6.zip

here are the drives.

I am at the same point, I was deleting a Docker app it didn't finished, now I can't start Array .

Don't know what to try next.

You need to check filesystem on disk6.

Thank you! Using @johnnie.black's suggestion I was able to repair my drive. For @BullDog656 or anyone else having this issue here's how I solved it.

 

There's a great article in the wiki talking about repairing filesystems. https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems

 

I started the array in maintenance mode, and ran a test filesystem check using the gui. You can see the results of that in filesystem-check.txt attached.

The highlight of that file was:

Metadata corruption detected at xfs_agf block 0x1ffffffe1/0x200

flfirst 118 in agf 4 too large (max = 118)

 

I then continued the guide and ran this command via SSH: xfs_repair -v /dev/md6

which didn't work and gave me the error:

The filesystem has valuable metadata changes in a log which needs to be replayed.  Mount the filesystem to replay the log, and unmount it before re-running xfs_repair.

 

This same error was addressed in another forum topic https://lime-technology.com/forum/index.php?topic=52644.0, but the gist of it was to run to run xfs_repair with -L, hoping there wouldn't be any data loss.

You can see the results of xfs_repair -vL /dev/md6 in filesystem-repair.txt, but it ran successfully.

 

I was then able to get the array up and running and I haven't noticed any data loss.

 

Thanks for your help and the great wiki!

filesystem-check.txt

filesystem-repair.txt

That was Awesome bashNinja!

 

I had a problem with my Disk 3 and I did the same fix.

Finally I was able to  start my array !

 

Thanks to everyone that helped with this problem.