Freighter

Okay after a little experimenting it seems like simply pasting '/etc/rc.d/rc.0' into the user script has the intended result and it runs the shutdown script the same as pressing the shutdown button does.

So since I actually only use my server during the evening, I would like it to only be on during certain times. I was able to use the BIOS setting to set the server to turn on every day at 15:30. However I also want Unraid to shut down every evening at 03:00. I found that you can do this using User Scripts however I can't find the correct command to do it gracefully. I found the command 'shutdown now' but that doesn't quite seem to work. With the monitor attached I do see it's trying to shut down (it says 'Waiting up to 60 seconds for a graceful shutdown'), then it says it's Waiting for all processes to exit, then it says going to single user mode, and then it's back to the command line saying 'server login: _'. The computer doesn't actually turn off though - but also unraid will be inaccessible over the network. Whatever it's doing, it's not shutting it down but it's also not remaining accessible either. In other posts I found the 'powerdown' command but that doesn't work at all for me, it does nothing. I tried checking what UnRaid does when you click the shutdown button through the gui, and it says 'running shutdown script /etc/rc.d/rc.0:'. I assume that's what I need user scripts to schedule, but I'm not sure how to do it. Could anybody advice me?

Yes, I did! The cache drive got unassigned for some reason. I reassigned it. Afterwards the Radar and Sonar databases were corrupted. However I managed to restore these by using the radar.db and config.xml files from the backup folder (and removing the log files, since someone on another post mentioned that a corrupted log file could also cause issues). Everything is back up and running now, thank you so much!

I haven't since I noticed it, but it probably happened at an earlier point, since I connected the server to a mouse and keyboard downstairs - confirmed it was accessible again, and then returned it to it's original location. Not sure if the logs are still useful in that case. I also included a log from the radarr docker, since it has some lines about "Migrating data source" which I thought might be relevant? Thank you so far! alphabox-diagnostics-20220115-2039.zip radarr_log.rtf

Hi all, So my UnRaid server used to be on the 192.168.1.x subnet. Now I've received a new router from my ISP and the subnet is now 192.168.2.x. I tried changing it back on the router, but that option is blocked off. My server became inaccessible because of that, so I took out the USB stick and changed network.cfg and changed the IP address of my server to correspond with the new subnet. After that I rebooted the server. UnRaid itself is now accessible again and seems to be working normally, however, my dockers Plex/Radarr and Sonarr seem to have completely reset. They don't have any data anymore and also the settings are all back to defaults. It's as if they're starting for the first time. I just can't figure out why this happened or how to fix it. I don't understand how changing the UnRaid IP affects the databases of the dockers. Especially since they use port mapping to begin with (Sonarr for instance is 172.17.0.3:8989 and maps to the 192.168.2.x:8989 subnet range). Does anybody have an idea of what might be going on and how to fix it? Thanks!