heppy

error output attached. Was working perfectly up until yesterday and I've not changed anything

Do the following: Stop the container Delete the "logs" folder and every *.tar.gz file you see from the main directory from Radarr which lives usually in your appdata directory Star the container This will reinstall the latest version. I just tried it and the latest version just works fine over here. Will this also fix NZBGet which has broken for me this morning?

So....the weirdest thing is happening. I hate gigabit fibre (Sky Fibre Ireland) to the home and download speeds are up there at 800 Mb/s and uploads has always been around 70-90 Mb/s which is great. Suddenly, overnight, the upload speeds have dropped to 10 and downloads have remained the same, however, using the SpeedTest tracker on my UnRaid Server, the speeds are consistently 75Mb/s but nothing else in the house is whether it's wired or wireless. The ISP says, well the connection to the house is obviously fine if one device is working. I've tried different cables, used the UnRaid cat5e cable on the Mac, moved all the ethernet ports around, turned off wi-fi, hard reset the router and nothing makes any difference. Does anyone have any idea what could be going on and how to fix it?

To close this out, I turned off Plex’s DLNA option and the problem hasn’t reoccurred so the issue must be with Plex.

will do, and thanks for the help.

I think this may be the cause of some other issues. The steps were, I was going to reassign one of my cache pool drives, stopped array, decided not to and then restarted the array and Fix Common Problems caught OOM error. Diagnostics attached, please help! tower-diagnostics-20240209-1143.zip

Hi there, I had this problem exactly a week ago and I ended up having to power off by the button and restarting and checking parity. Thought everything was fine but like I said, it happened again at almost the exact same time whilst doing something similar (browsing in sonarr). Anyway, same thing happened, couldn't log into the UI, docker image containers would load but incredibly slowly. I managed to shut one down and then a couple of minutes later all came back as normal. I have the syslog server on this time and nothing looks too untoward to me but then, I don't really know what I'm looking at This happened about an hour before the crash but the actual crash happened somewhere between these two moments and nothing was logged then there's this which looks like it may be relevant? full syslog and diagnostics attached. Would be great if someone could shed some light on the issue and possibly present a solution? Thanks all. tower-diagnostics-20240205-1122.zip syslog-192.168.1.200.log

help! It happened again, and weirdly at the same time as last week on a Monday. Given that I've not put in a shutdown script can anyone explain what might have happened?

Hi there, Not sure what happened here, last week finally upgraded from 6.11.5 to 6.12.6 which seemed to go smoothly. Changed docker network type from macvlan to ipvlan. Also upgraded cache drive to zfs all of which went well and no issues. This morning, made a change to Sonarr and suddenly everything slowed down to a crawl, couldn't log in via the GUI and just about managed to get in via terminal (again, very slow) and get the diagnostics (attached). Docker was still running as I could sporadically open them but then they'd stop working again. Went and plugged in a monitor and a forced shutdown had been started (not by me). Stupidly didn't have syslog server activated. Must be a new issue as previous uptime was over a year. Wonder if anyone can help decode the issue. tower-diagnostics-20240131-1048.zip

I meant to replace that drive anyway, but I’m always terrified of shutting the server down as last time it went into hang on shutdown and I had to force shutdown which was a whole other nightmare!

Perfect, will run another test and thanks for the reply. I should have a mentioned that one of my drives has a broken piece of plastic on the connection which i had to bodge fix with some hot glue so i wonder if that’s the fail point even though the server hasn’t moved in over a year. Will run another extended text.

Here’s the downloaded report tower-smart-20240123-0833.zip

I have no idea what this means but I’m presuming replaced the disk immediately?

yup, as I said in the original post, am doing that already and will post what it comes back with. Thanks

Saw this in the syslog after a warning came up Jan 10 01:09:38 Tower kernel: I/O error, dev sdh, sector 4648311824 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311760 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311768 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311776 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311784 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311792 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311800 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311808 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311816 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311824 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311832 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311840 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311848 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311856 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311864 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311872 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311880 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311888 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311896 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311904 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311912 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311920 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311928 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311936 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311944 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311952 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311960 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311968 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311976 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311984 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648311992 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648312000 Jan 10 01:09:38 Tower kernel: md: disk5 read error, sector=4648312008 Dashboard reports an error, Smart Self Test is reporting OK (am now running an extended test) Diagnostics attached....and if it's somehow ok, can I clear the error TIA, Simon tower-diagnostics-20240115-1045.zip