Currently, my server has been up for 3mos 26d and 23min:

it was most likely rebooted the last time I did updates.

 

Early Saturday morning (2024-04-06) I updated all docker apps, and plugins, basically anything that needed to be updated. Everything seemed to go fine, and I was away from home the rest of the day.

 

Early Sunday morning (Sunday is when the Parity Drive gets checked), I received an error notice from NetData, and upon checking the server, I have MANY errors and issues now.

 

My Shares have disappeared:

 

 

From my file manager:

 

I work mainly from this server, so I have no access to my files from my computers at this point.

 

One of the files that I had open in my text editor, states that it couldn't open/find the file, which is expected since the shares are no longer there:

but also, I cannot find the file via the UNRAID file manger, which suggests that I may have lost some data also.

 

My Parity Drive seems to have failed, and is still running some kind of check with no end time estimated:

 

Only 3 docker containers are running:

however, when I try to access the WebUI for PieHole, I get an "500 Internal Server Error"

 

MiniDLNA seems to be working as I can access from my TV's but no data. In the docker logs, it shows that it also cannot find the media share:

2024-04-06 06:01:55,518 DEBG 'start' stdout output:
[2024/04/06 06:01:55] minidlna.c:669: error: Media directory "/media" not accessible [No such file or directory]

 

and NetData is working, which shows the following errors:

NOTE: I do not remember setting anything up using BTRFS, I assume that may be what UNRAID uses for the parity drive???
All other drives are XFS.

 

 

When I attempt to start any of the other docker containers, I just get the following execution error:

 

I'm not sure what to do at this point. as I pretty much "set-it-and-forget-it", I really don't fiddle too much once everything is up and running.

 

Any advice appreciated.

base-diagnostics-20240408-0905.zip

Errors with all array disks at the same time, possibly a controller issue, or power, you will need to reboot to recover the server.

UPDATE: Sorry, it seems that the SSD cache drives are formatted under BTRFS.

2 minutes ago, JorgeB said:

Errors with all array disks at the same time, possibly a controller issue, or power, you will need to reboot to recover the server.

Since there is still an ongoing task, will rebooting cause any further issues?

Nothing can be read/written to the array ATM, if you have something using the pool it may still work, but try to reboot as soon as you can.

I rebooted and all the shares are back, but show that they are unprotected:

 

Which, I assume is due to the Parity issue:

 

Docker containers seems to be functioning again.

 

What's the best way to check whether there is actually issues with that disk?

12 hours ago, AgentEccks said:

but show that they are unprotected:

That's normal since parity is disabled, post new diagnostics.

Here's the updated Diagnostics.

base-diagnostics-20240409-2351.zip

Diags are not opening, post new ones.

Here's update. I tested on my end, it opened. I'll test again after I post this.

base-diagnostics-20240410-1120.zip

Yes, it opened on my end after posting.

SMART for parity looks OK, just re-sync parity:

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

Thanks for the info., I'll get that going.

 

Do you think the updates I did caused all of this? If not, definitely a strange coincidence!

 

I think at one point I rebooted in safe mode, disconnected the parity drive and rebooted again, and under the `Unassigned Devices` plugin, the parity drive did show as an XFS drive so not sure why I got the NetData Errors regarding BTRFS and then the parity went wonky:

 

 

 

any insights regarding the BTRFS errors?

 

As it seems now, aside from the parity drive needing to be synced, there is nothing else wrong and maybe, if I rebooted the server after doing the updates, that would have prevented this whole incident?

There aren't any btrfs errors in the previous diags, post new ones.

I was simply referring to the errors noted initially by NetData when everything went sideways.

 

As of now the Parity check completed and shows that the "Parity is valid".

 

Everything seems back to normal, just trying to understand why it glitched in the first place.

 

Attaching new diags.

base-diagnostics-20240412-0240.zip

I've never used Netdata, but they are likely from the previous issues, there aren't any errors now, so it's OK, just acknowledge/clear them.

Once everything was back to normal, the NetData Errors  went away also.

 

Also, the server has now gone through the scheduled weekly Parity Check without further issues, so everything seems good now.

 

Thanks for the assistance/guidance!