daemuth

@JonathanM Hey, just checking back in: I'm happy to report that after resetting the root creds everything reverted to normal pretty much immediately - nothing else seems to have gotten corrupted, which is surprising but also a relief. Everything works as expected. Thanks for the assist!

Thanks you for this post, it was reassuring to read. Apologies for the late reply, I kinda blocked this out of my head because didn't want to deal with the stress of it while away. I'll do a diff between what I can salvage from the usb drive and the latest backup - unfortunately the last backup was late last year, but it is the case you describe, that should help me with restoring the ident config file. Marked your answer as solution for now. Thanks for the assist!

I see, that's a valid point. In that scenario, assuming I get access to the faulty USB drive, what steps do I need to take to restore it in working order? Everything else apart from the OS config seems to be in working order. I have a backup from the beginning of the year and I haven't modified much in OS since then. It would be nice if I wouldn't have to delete WG / docker configs etc

Hi all, Our Unraid server has experienced a power outage. After rebooting the machine it appears that the device's name has been reverted to the default "Tower", and I cannot log into the root account with the previous user/password combination. Unfortunately I do not have physical access to the server for the foreseeable future, which is why I cannot follow the steps laid out in the password recovery section. What I don't understand is the following: I can connect without problems to the WireGuard server that runs on the machine. Some docker containers also seem to have been restarted as the Twingate connector docker container is also online (I could verify it from Twingate's website). Things that work: - I have access to the file shares (non-root user) - WireGuard server - Twingate docker container running on the OS Things that don't work: - Unraid is running on the wrong port (previously remapped to 8080 due to using NPM, now running on 80 again) - SSH seems to be disabled on an OS level - Root account password seems to have been reset Questions as follows: - Is there any way to reset the password remotely in this scenario without having physical access to the computer? - How does a server end up in such a weird mix of half working / half not working state? Thank you!