Unraid has been working really well for me for the past few months.  I am not good with linux so I was a little hesitant to use unraid but it has exceeded all my expectations.  That is until this past week or so.  Every 2-3 days I notice erratic behavior.  Some shares become inaccessible.  Docker apps start malfunctioning.  Then I log in to the webgui only to see that the dash board shows none of my drives.  Not only that I can't even do a reboot with out going into command line and forcing a reboot.  When I go to the shares tab it says array offline. A whole host of problems. When I try to download the diagnostics it gives me a 404 error.  Has anyone experienced this before?  Heres a picture of my webgui.

 

Thanks

 

 

First guess would be that you have a misconfigured docker or something that is writing directly to RAM instead of a disk location. Any host path that doesn't include /mnt or /boot is writing to RAM, and if you make a typo in what comes after the /mnt you could also be writing to RAM.

Have you applied the drive monitor script fix? Not have the drive db monitor script fixed seems to be causing issues and hanging systems. I cant recall the exact thread, but there is a sed command to place into your go file that will replace the http:// address with https:// in the appropriate monitor script.

Have you applied the drive monitor script fix? Not have the drive db monitor script fixed seems to be causing issues and hanging systems. I cant recall the exact thread, but there is a sed command to place into your go file that will replace the http:// address with https:// in the appropriate monitor script.

 

Here's the sed command:

https://lime-technology.com/forum/index.php?topic=47386.0

I think I may have found the culprit.  Found this line in the syslog regarding my cache:

 

Apr  5 09:12:29 battleserver kernel: XFS (sdd1): Metadata CRC error detected at __read_verify+0xaf/0xbc, block 0xb966f88

Apr  5 09:12:29 battleserver kernel: XFS (sdd1): Unmount and run xfs_repair

Apr  5 09:12:29 battleserver kernel: XFS (sdd1): First 64 bytes of corrupted metadata buffer:

 

A few weeks ago I had my cache drive develop what seemed to be a some filesystem errors which I attributed to the fact it was btrfs so I switched xfs and thought my problems were behind me.  I think I need a new cache drive.

 

I also applied the fix above so we'll see if the issue returns.

 

Thanks.