TryRebooting.Tech Unraid

Thanks JorgeB! That does indeed seem to have fixed the issue. Putting mover stop in my wheelhouse in case I ever need it again. Cheers!!!

Interesting find, btw: When I go to enable mover logging, it tells me the mover is running. However, the mover button is currently clickable and does not seem to think the mover is running, so they are in disagreement with one another. Either way, enabled mover logging, hit mover button, here are the results.unraid-diagnostics-20241018-1337.zip

So, my mover stopped working awhile back, and it turned out to be an easy fix that time, it was a mover plugin that was breaking things. That ticket was here: After removing the plugin, all was well and it worked fine. I've made no changes to the share or the mover since then, and today I find that I'm in the same situation as before. Here's the situation: I have a share called data. Primary storage is Large_SSD and secondary storage is Array. Mover action is Large_SSD->Array. My Large_SSD is is at 2.77 TB used, 944 GB free. When I look at the contents of the drive, much of that space being taken up is from items in the data share. When I hit the button to manually start the mover, it immediately seems to be done. I did notice last night that the mover was running, as I just happened to see the button was grayed out. Attached are the diagnostics. Thanks for any help you can provide! unraid-diagnostics-20241018-1246.zip

Turns out there was nothing wrong with my Unraid installation at all, all of the points of failure were on my Desktop. I found I could access everything via my phone. So I tried from my desktop again on another browser, but it still failed. Then I removed the Tailscale software running on my desktop and it worked again.

I'm not sure I understand, so would I be starting with a brand new install of Unraid on my drive and then bring these items over? Also I had to get "permission" to use this drive, as I was out of UIDs, will I run into that again? I notice there's been no opening of the .zip file I have with diagnostics, is there some chance a less chaotic fix might be discovered in there? I'm not super keen on the idea of redoing my whole boot drive. I'm on chemo this week and I'd like to keep further distasters to a minimum while I recover :).

Tried safe mode, and no dice: I can get to services I have that use a domain (emby.mydomain.com, requests.mydomain.com) but I still cannot get to anything by internal IP. So using safe mode hasn't changed anything for me.

Thank you, I'll try that sometime early next week (server is heavily used on weekends) and get back to the forum with those results!

Ooooh boy, I don't know what I did. I had Tailscale plugin running before, but I wanted to start fresh and get some things working. I had advertised subnet routes before, and when doing the command tailscale up --advertise-routes=192.168.50.0/24, I had a feeling that maybe there were old settings in there that were competing and maybe needed to be cleared out. I tried tailscale down, and removing/readding the plugin. And somewhere in the process, I found that I couldn't get my docker containers to open by their IP address. In the process of trying a few things, I lost my ability to remote into Unraid at all. I restarted the server in GUI mode so I could see what I was doing. I was able to restore my ability to remote into the server via the IP address login page, so that's progress. But still no access via my custom docker network (every container has it's own IP address in my regular network scheme, so like 192.168.50.100 is Unraid, .101 might be Sonarr, .102 Radarr, etc. I figured that meant my whole system is down, but on a whim tried emby.myserver.com and PRESTO, the thing is working that way. So, being a Friday, and with a new kitten on the way tomorrow and plans tonight, I figured okay, stop touching things right now, leave it alone, the front end is working even if I torched the backend. lol If someone could help me figure out what I did, or better yet what to undo, I'd be greatful. I'm not really familiar with the command line, so I shouldn't have randomly tried various tailscale commands. But when in a hole, stop digging lol. So I'm not trying more until I have a better idea what to do. Attached are my diagnostics and my deepest thanks unraid-diagnostics-20240927-1435.zip

itimpi, that seems to be spot on!!!!!!!!! I removed it, hit mover, and now it's staying grayed out like it's actually working on it. Is this some sort of known issue? And thank you so much, that was very helpful!

I'm trying to use mover to move my "data" share. I am out of space on my "Large_SSD" pool device, which is 4TB. When I invoke Mover, it immediately seems to complete and stops running (from what I can tell on the UI, as the Mover button is available to be pressed again after running a second before). The primary storage for data is Large_SSD, the secondary storage is Array. Mover action is set for Large_SSD->Array. I'm not sure when this stopped working but it has worked before, I've had Unraid for years now and this was set up correctly before (meaning, the mover did what was expected). I'm on Unraid 7.0.0 beta 2 now, but I am pretty sure this was an issue before I moved to the beta. Not 100% sure, but like 99% sure. Diagnostics included in the post. unraid-diagnostics-20240816-1534.zip

JorgeB you beautiful person! That seems to have done it. And just like you said, it seems "off". In docker I see a ton of these: Warning: mkdir(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 351 Warning: file_put_contents(/var/lib/docker/unraid/images/ai-chat-app-icon.png): failed to open stream: Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 93 Warning: mkdir(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 351 Warning: file_put_contents(/var/lib/docker/unraid/images/binhex-sabnzbd-icon.png): failed to open stream: Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 93 Warning: mkdir(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 351 But just the same, I can browse to that drive and I believe I can copy files out of there. If I can, I'll save the files to my local machine, then I'll move the shares to a different drive. If that works out I'll mark this as solved, otherwise If I hit any snags I'll come back for advice. Thanks so much!!!!

Hi all, Today I noticed that while I could get into my dockers via their local IP address, my https websites were down. I rebooted, thinking it might well come back up without further issue with a simple reboot. When my computer booted back up, the docker service failed to start. It said the path wasn't valid. And sure enough, I have what seems to be a totally new issue than the reason I had rebooted: my 1TB SSD says it's unmountable. Also, this drive isn't in the parity drives, since it's the drive I run docker containers. So if I really have lost it, I don't think I can rebuild it automatically. Attached are the diagnostics, any help you can offer would be awesome. unraid-diagnostics-20230309-0927.zip

I think that's it. CPU cooler died (hopefully) or power to the cooler is jacked. Fan spins for a bit, stops, spins, stops, spins, stops. Then I shut it down.

The plot thickens. Okay, so the cables all seemed fine. I unplugged USB and booted. I went back into the room to see how the machine was doing. I noticed it seemed to be mid turn-off right when I was in there looking. I think the CPU fan might have died. Doesn't seem to be spinning, and the CPU heatsink is screaming hot. Might be the cooler died. I'm going to let it cool down, then boot it back up to briefly test if that fan spins. Would explain why it's powering down faster now, since there is more residual heat. If you see anything in the diagnostic that supports this I'd be all ears. Thanks for your help either way, nice to have someone to talk to about this.

I could pull the Unraid USB to test but I run it headless so I wouldn't be able to tell what the boot was doing. But I would be able to tell if it was still on or not. I can try that next. I was able to get it to boot again and I ran the diagnostic. Hopefully this can get us some specific info. I'm going to give a visual inspection to the power cords, see if anything is loose or whatnot. unraid-diagnostics-20230111-2010.zip

Sounds good. I'll try to run that, although I just found my server is off again. So the shutdowns are still happening and appear to be more frequent. I'll try to boot and run that. Thanks!

Before I moved the machine to a different outlet and bypass the UPS, I found it was powered off again. Here is a copy of that log file in case it is helpful. Meanwhile, the machine is moved to a different power outlet and without the UPS. If it's going to power off again I suspect it'll happen in 2ish hours or so. syslog (1)

Thanks for the reply. I have a UPS but it's not connected via USB, just something it's plugged into. When I come into the room it's totally powered off, or at least it appears that way. Fans not spinning. RGB lightings from the motherboard is off. I'm not losing power to the server that I know of, no breakers tripped or anything. No one messing with the server either, 100%. I can move the plug to a different outlet and see what happens. Can you tell me/show me what in the log you're looking at? I have to admit I get the gist of the lines but not the bulk of it.

My server has kept turning itself off over the last several days. I recently replaced a drive that was going bad, and it's been stable for a handful of days with the new drive while it did the data rebuild. I closed up the machine and within a day or two it started to power off randomly. After hitting the power button, the machine comes back up, boots properly, and works as expected. Attached are my log files. I'm seeing this line but not finding anything specifically after a Google search: Jan 11 16:34:15 Unraid kernel: ACPI Warning: \_PR.C003._PSS: SubPackage[0,1] - suspicious power dissipation values (20220331/nsrepair2-684) syslog

Thank you very much!!!!

Hoping to bounce this back into the hearts and minds of the mod team, now that the holidays are done. Thank you!

No rush, and happy NYE to everyone!

Could I please change "Looking Glass Unraid" to "TryRebooting.Tech Unraid"? Please and thank you!

Did a little search and found this post. VERY helpful, thank you. This also works on an NVIDIA Quadro p2200.