Nils

Members
  • Posts

    19
  • Joined

  • Last visited

Everything posted by Nils

  1. have you found the cause yet?
  2. I added the /dev/dri as a device in the Plex docker but this makes the docker error
  3. In the meantime I was keeping an eye on the server's console and I think withnessed the error that has been making the server freeze after sometime running (i've never managed to keep it running for 24h). It says: Kernel panic - not syncing: Attempted to kill the idle task! Shutting down cpus with NMI Kernel Offset: disabled I've uploaded a pic of the console. Now that this showed up the webgui is unavailable (it was running fine just before that). Searching for this line I found Camaropilot's thread. Apparently he solved this by replacing the motherboard and cpu. Since I run intel on my main pc I'll try boot unraid from there and see what I can figure out
  4. I have set a DHCP reservation on my router for the server and now it seems to be more reliable. I'm certain of it, though it's not the only problem i think. From my understanding, since I only have one ethernet port on my server I don't have much choice. That said, I'll go on my network settings on my server and router to see if it's all right now.
  5. I was browsing the webgui when the common problems plugin suggested I have a hardware issue and that I should download mcelog through nerdtools but the command doesn't work and prompts me to edac_mce_amd instead. Only problem, apparently this edac_mce_amd isn't available. Since I have already swapped out the ram, it can't be that that is malfunctioning. That leaves the mobo and the cpu. going through the system log I found this May 28 10:51:52 Tower kernel: mce: [Hardware Error]: Machine check events logged May 28 10:51:52 Tower kernel: mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 5: bea0000000000108 May 28 10:51:52 Tower kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8105436c MISC d012000100000000 SYND 4d000000 IPID 500b000000000 May 28 10:51:52 Tower kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1590688294 SOCKET 0 APIC 6 microcode 8001138
  6. Lucky you I have the same error but swapping the memory didn't change anything. So there is no edac_mce_amd?
  7. I left it running for 1 and a half hours and as I expected the screen was blank. Not really black, but something alike and the webgui didn't respond.
  8. So, I booted with both the old and the newly flashed usb. As before, I could login with this adress. The login didn't require any password. Checking the trial status it prompted me to adjust the network settings and so I set the static IPv4 to 192.168.1.100 Now the trial shows the days remaining and the servers seems to let me do everything I could do before, only I don't know if it's going to occasionally stop like it also was doing before. Now the webgui is accessable through the ip I set. Rebooting the system again and the ip I set before times out the page. The only way to access it is through this 169.254.200.22 ip. Again, the trial " Cannot connect to key-server! ". I went to the network setting to change the IPv4 again (this time to 192.168.1.99). just like before it "works" I'm starting to guess it's a problem with my usb device... Just to be sure I attached the diagnostics and system log files if it's in any case helpful. friariello-syslog-20200528-1441.zip friariello-diagnostics-20200528-1641.zip
  9. additionally, before letting it boot I went into the bios to set the boot drive to be the usb I was using before, to check again if I missed something but it simply "skipped" it and booted from the new drive
  10. unfortunately not. my server's ip is set to static: 192.168.1.6 I checked and at least my main pc and the unraid rig are on the same subnet. I tried booting my server from a different usb stick and I'm not quite sure if what happened was all right. It bootet normally, just slower. On the console the server name was Tower and the ip 169.254.200.22. I double checked it on my router and even could access the webgui. The trial didn't show (as one would expect), but everything was as I had configured (also the name was Friariello and not tower). What really stranged me out was the fact that in the network settings it all was configured to be static on this ip 192.168.1.6.
  11. i also can't access it from file explorer
  12. Hi, I wanted to thank you for the post. I was just getting mentally prepared to do all of this but now, again, i can't manage to access the webgui. So now i'm back to the original title of these posts... Is it possible to install unraid on a different usb and start from scratch? If so, would it be a viable option? Would I lose all of my data?
  13. I tried doing it with unRaid from the boot menu but every time it just restarted. I tried re-inserting the memory just to be sure there is no false contact and also swapped it out for some other modules from my main pc but still, just restarted over and over again every time I tried. Anyway, I did the test on my main pc with my server's module and got 0 errors
  14. Still doesn't work with https://friariello Every now and then it also just stops responding completely. Not even the power button works... Could this be a hardware issue? friariello-diagnostics-20200524-1623.zip
  15. Here it is In the meantime I installed the Fix Common Problems plugin. I read on some other thread it could help me figure out the problem but I could get much information. pussydestroyer-diagnostics-20200524-1145.zip
  16. I put it into a different usb2 but nothing much changed. I've managed to access the webgui by setting the servers IP adress to static. Now i can access using the ip andress and the trial doesn't show to be expired anymore, though the https://tower still doesn't work, so I don't think I've adressed the right problem. Eventually it will also shut down the array but I haven't had time to look into it. Maybe it's some setting I'm missing?
  17. So, I've tried re-flashing the drive and saving the config files. I've managed to access the webgui but only through the IPv4 adress and for a short time. I saw my trial (which started yesterday but doesn't matter) expired but before I could do anything else it timed me out of the page. Accessing the tower through its name still doesn't work. I thought I should maybe configure it for the ip to be static, but I don't know how to configure DNS.
  18. I've set a password, yet it doesn't let me do much. When I try to type in the password it doesn't write anything. Honestly I don't know if that's the problem. When i first got it running it did the same thing but I could access it through the webgui and the file explorer. Now either of them work
  19. Help! I just started with unraid. Everything went smooth up until now. I was trying to get plex media server running and now I can't reach the webgui. I've tried restarting the tower but it didn't work. I don't know what to do. I tried logging in by connecting a monitor to my server but it just says the login informations are wrong. Please help