Beijergard

Thank you! That power cycle actually seems to fix it. Now it has ben up and running for quite a while. Could this be an indication of a failing m2 drive or something else? Here is a smart report for the m2 drive. The drive is about 5 years old by now.

Hi there. My Unraid have been a bit problematic for a while now with different errors and this seems to be the most irritating one. All my dockers went offline today and I got Execution Error 403 when I tried to start them. After a reboot, which took a lot longer than usual, my cache drive is now gone.. It is a single Kingston A1000 480GB, and now I wonder what is the smartest next step? My mobo only has one M.2 slot, but some avalible SATA ports. I will remove the drive and try using it in a USB case to see if I can connect to it. And if all data is gone, I actually don't know what is lost. I haven't done any writes to the shares recently so there should not be any data loss there. But all appdata from Plex and Jellyfin might be gone I suppose. plexworm-diagnostics-20240114-2200.zip

Thank you, I just read the update notes for 6.12.6 and saw this tip. I will try it.

So just now the server has crashed again. Here is the diag file. Please help me plexworm-diagnostics-20231220-1808.zip

Okay, thank you, I set it up the wasy way, and hope to have more information if it crashes igain.

Hi. I have had my server for a few years with no major issues but today the server was not detected on the network, so I hauled out a 10m hdmi and connected it to my tv but there was no signal. I saw no other option but to power it off manually and then start it again. At that point I got a video signal to my tv, all the unix code flashed by but then the video signal was lost. At that point I could connect to the GUI again and download a diagnostic. Does anyone know the cause of this? plexworm-diagnostics-20231215-1904.zip

I discussed it with a friend who knows Unraid and Unix a whole lot more than me, and we tried this. I only have two dockers, some plugins but no VMs, so I think I will put the 128 nvme back in and start using it again. Just have to figure out how to put the appdata and dockers on the ssd.. Edit, I just freed up a 480GB Nvme from my gaming PC, I will put it in the Unraid server tomorrow, then I can use the disk as a cache aswell, 128GB isnt quite enough I believe.

Ok, now the second Parity Check is done with corrections unchecked and this time with zero errors. Attaching diagnostics if you want to take a look. Does this mean that all is good now? plexworm-diagnostics-20220211-2215.zip

I had issue with the cache being full and mover doing nothing, scheduled or manually. I have a 128gb nvme, which I initially wanted to use only for dockers, but when I starter using it as cache it got full and never emptied, had to move files with midnight commander and might have messed something up. I also have a 250gb sata ssd, but I dont want to take up any more sata and power cables. So yeah I can but the 128gb back for the dockers.

Okay, now after reboot the docker service is unable to start. Dont know if it has something to do with me removing the cache drive about one week ago..? Edit, I removed the vDisk for the dockers and reinstalled them again plexworm-diagnostics-20220210-1521.zip

Yes i unchecked the corrections in scheduler, and then I unchecked "write corrections to parity" under main and pressed Check. I don't know how else to run it manually, and it seems strange that it ran corrections even though I unchecked the box?

Ok, so now the parity check is done. I unchecked the box for corrections. Is there anything I should or not should do now? plexworm-diagnostics-20220209-0811.zip

Okay, I should have attached the photos from the start. I havent turned of the parity correction but I will do it now and run a check and see what the results are. I am truly greatful for your respectful answers and your help!

I never saw the disk as disabled. The lost and found just contained 17 files named with a lot of numbers, and filesize from 20-100kB, so I guess nothing too important. I might have used wrong words(if so, im sorry), the Parity check said Disk 1 has read errors, see jpg.

Ok, the disk is now visible and the array is back online. Here is the diagnostics. plexworm-diagnostics-20220207-1740.zip