TechnicallySaved

Yea no dice... 2.0 still boots to Tower rather than name I gave it... Flash drive is usb 3.2 usb micro center but passed all tests. However the server is the same, except for name which is ODD... Like I said it had a bad ram which may have caused some improper shutdowns to occur. That ram is removed, correct name didnt return but server is same except for name. I was messing around with testing running unraid on an old laptop and allowed the server to boot onto the net with the tower name, so im not sure if somehow that confused the system to think that its name but literally my server name is the only thing different. Everything else works fine under tower.... I even logged in with my root/ and correct pw

Hi All new here! So I was experiencing some odd shutdown issues, I believed mostly related to plex. Last time it shutdown I was unable to boot into web gui but screen said it had an IP. Eventually I checked that IP and found its Valid but the Server name had changed back to Tower. I had the USB out and I didn't have any scan disk issues, also I saw all the typical files I believe so it seems like it was functioning fine. I didn't run a formal test on it although I could do a HD sentinal. What I did do was run a Memtest and I pulled out a bad stick of RAM. Thinking this would have solved the issue. I tried to boot again but with no luck. Still loads OS just My Server name is gone but I can login to Tower at the IP. The address is no longer working at https: but rather http: How should I proceed. I plan on backing up my .key and maybe the whole flash unless im told some information is not needed. Id love to not have to reconfigure the whole server... Is my server there just with a different name from the corrupt ram issue? If I Login to 'tower' will it all be there and maybe fix itself?? I have a back up I believe on the flash I can probably grab too. Maybe even a recent diag somewhere, but it seems the logs were hitting issues with plex and the ram? Not Sure... Thanks ALL if you need more information let me know... I spent a while trolling the forums to fix eventually fixing ram errors thinking that was issue, obviously not... I know enough to be dangerous and I guess that's what happened here LMAO.