Riktronics

I got a syslog server set up Friday morning and started the logging. It crashed again a little while ago. I took a look at the logs and nothing is jumping out at me. I see I need to reset my mail password and that the cable to my ups is unplugged. Maybe I am missing something or don't have the logging level set correctly. Plexnas

I've been having an issue with my server. Every 1 to 3 days the server will become unresponsive, I usually notice in when I go to watch something on Plex and it won't load. When I check the server the fans are running full blast like it is under a heavy load. Most of the times when I try to login to the web interface it won't load, this morning it actually let me log in but I was unable to get any of the pages to load. I am attaching the diagnostics, I don't know if they will do any good since I haven't been able to grab diagnostics when the server is actually acting up. plexnas-diagnostics-20250501-0737.zip

Just an update, I enabled the drive and ran another parity check, it finished we zero errors. I've got a monthly check that runs on the first, Just for fun at let it run (even though the last one had finished 2 days before) and it ran with zero errors as well. I will chalk it up as a glitch and if it happens again I will take a look at moving the controller to a different slot or replacing it. Thanks!

Thanks for taking a look. And oh boy, I hadn't even thought about the controller. I have rebooted and am attaching the diagnostics. l33tnas-diagnostics-20240727-0817.zip

I ran a parity check on my server because of an issue I had that is most likely unrelated. It got 81.9% done with 65 errors and then a disk went disabled. I was hoping someone might be able to look at the logs and see if it looks like the disk has failed or if it is a cabling issue. The server has been up for 26 days before I rebooted and ran the parity check and was not having any issues, the idea of a working cable going bad when it is in a sever untouched seems far fetched to me but stranger things have happened. It won't give me any SMART reports or any information about the disk because it is disabled. I'm sure I could reboot and start it in maintence mode and attach the disk and get the reports (which I will need if the drive is indeed bad and I need to start a warranty claim on it) but I didn't want to touch anything until I had some guidance. I've learned that lesson! The probably unrelated issue is this: The server was running along happily and the power blinked. The UPS kept everything online (except my main switch, oversite when I replaced it which has been fixed) When I got back on my other machine after the blink I noticed that several torrents that were running had gone red and said the files were missing. Sure enough, they were gone. I found them in the recycle bin. I wasn't anywhere near the files and I know I didn't deleted them and I wouldn't think that even if it was in use the program using it losing connection with server wouldn't cause it to get deleted, but who knows. Thank you! Diags attached. l33tnas-diagnostics-20240726-1251.zip

I disabled docker again and ran mover (logging was already on). I think I have found the problem: May 9 07:01:56 PlexNAS move: file: /mnt/disk1/system/libvirt/libvirt.img May 9 07:01:56 PlexNAS move: move_object: /mnt/disk1/system/libvirt/libvirt.img File exists May 9 07:01:56 PlexNAS move: file: /mnt/disk3/system/docker/docker.img May 9 07:01:56 PlexNAS move: move_object: /mnt/disk3/system/docker/docker.img File exists May 9 07:01:56 PlexNAS move: mover: finished The docker.img on disk 3 is dated 2023-10-17, the one on cache is dated today. I *assume* I can just delete the one on disk3, but I wanted to ask someone that knows what they are doing before I do anything silly. The libvirt.img is the same situation, the one on disk one is dated 2023-11-17 (the day I was clearly hacking at things instead of asking first and messed something up). The one in cache has yesterday's day, which makes sense, I never turned the VMs back on since I haven't used a VM so far. Is it safe to manually delete the two old copies that are still on the array?

Thank you for the quick reply and great instructions! I ran the memtest and found that one stick of my memory was bad and I removed it leaving me with 8GB instead of 16. I then adjusted the settings for the shares and ran mover. It moved everything to cache as expected, however it left 22.57 GB on the array. I'm not sure why that is, I double and triple checked all the settings and didn't see anythign wrong, and there is 725 GB free on the cache drive. I also double checked that docker was shut down. After that was completed I attempted to gather the diagnostics but it kept crashing my browser. It would scroll through for 20 to 30 minutes and then the browser would give me an error page. I tried in both Chrome and Firefox. I rebooted the server and ran diagnostics again which I am attaching. There is good news. It seems to be the munin server that is corrupted and not my Plex. I don't even use munin so I can just delete it and leave it stopped. Thanks again, let me know how the new diagnostics look. plexnas-diagnostics-20240508-2013.zip

My server has started getting the above error on the console screen 6 times (3 are for the same logical number, the other 3 are 3 different ones. ) Everything seems to be running fine, it ran a parity check on the 1st and it didn't find any errors. I had a drive with SMART errors, I swapped that out, but it didn't make any difference. I am attaching my diag. Any ideas? plexnas-diagnostics-20240508-1010.zip