viethan Posted April 25, 2020 Share Posted April 25, 2020 Hi All, I ran Fix Common problems last night and advised me to post the diagnostics and of course I didn't cause of my hubris. This leads me to my next query for help. I'm wondering how I can restart my unRaid without holding down the power button. I started parity yesterday afternoon and left it over night. This morning I cannot access it - I think there is something wrong with the onboard NIC. The Intel NIC stopped working Thursday afternoon so I started using the second one (Realtek) and seemed to have worked fine I was able to finish transferring all the files prior to running parity. It might be possible the Reatek NIC is also dying maybe that is why I was getting MCELOG errors? Its a ASUS P8P67 Deluxe mobo. Anyway, I can't access it - I connected a monitor/keyboard but there is no signal its like its asleep. I tried to SSH into it with Putty but since there is no IP I can't login. I tried unplugging/plugging the cable, switching cables and still can't get an IP. Its connected to a unmanaged switch which is connected to my router. The onboard NIC is lighting up with the greed light and orange blinking. Other than hard reboot is there another way to gracefully reboot it? I'm worried about creating errors in case it hasn't completed parity. When I went to sleep ~1am EST parity still had about 7 more hours ~9am as of this posting. It might be finished but I'd like to be sure. I hope I'm not missing anything. Sorry for the long post. fortress-smart-20200413-1928.zip Quote Link to comment
Squid Posted April 25, 2020 Share Posted April 25, 2020 8 minutes ago, viethan said: Other than hard reboot is there another way to gracefully reboot it Since you can't login to the UI or via SSH or at the local console, then no. 8 minutes ago, viethan said: It might be possible the Reatek NIC is also dying maybe that is why I was getting MCELOG errors? unlikely. You should post the diagnostics showing the MCE errors Quote Link to comment
viethan Posted April 25, 2020 Author Share Posted April 25, 2020 (edited) Thanks squid I guess the attached diagnostics didn't have the meclog errors? my bad I uploaded the wrong file What could be expected if I do a hard reboot? Edited April 25, 2020 by viethan Quote Link to comment
Squid Posted April 25, 2020 Share Posted April 25, 2020 3 minutes ago, viethan said: What could be expected if I do a hard reboot? Most times nothing adverse will happen, but we don't know if the server crashed, or just stopped responding. IE: I wouldn't be surprised if parity is NOT completed building. Quote Link to comment
itimpi Posted April 25, 2020 Share Posted April 25, 2020 If the server has not crashed (as appears likely) then a short press on the power button will trigger a shutdown. Quote Link to comment
viethan Posted April 25, 2020 Author Share Posted April 25, 2020 I did a hard reboot, there was a kernal panic but I i didn't get a pic of it, something to do with a CPU sync. I grabbed the diagnostics but I don't see the mcelog - I checked that its installed via nerdpack. fortress-diagnostics-20200425-0932.zip Quote Link to comment
viethan Posted April 25, 2020 Author Share Posted April 25, 2020 (edited) 13 minutes ago, itimpi said: If the server has not crashed (as appears likely) then a short press on the power button will trigger a shutdown. I tired earlier but there was no response. Doing the hard reboot worked, parity didn't finish and it started again. But as I write this this popped up - is that what I think it means - need to replace the CPU? Edited April 25, 2020 by viethan resized photo Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.