• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Kirizan

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Interesting, the UPS is a brand new CyberPower OR1500PFCRT2U. According to Unraid, it's only 25-30% loaded. I have noticed Unraid looses connection to the UPS occasionally, but I thought it was due to the USB cable being loose. The cable is as far as it can be and still be connected. I'm getting a server rack to put the UPS and the Unraid server in pretty soon. I don't think power at my place is unstable, my old NAS ran fine for years on a pretty cheap UPS without every crashing. As far as the networking concerns JorgeB pointed out, while I have the same type of configuration (some
  2. I discovered a small bug. If you remove a container without removing it from the folder, it still shows up as in the folder count, but there is no way to remove it. As seen here: It says there are 1/2 containers started, but there is only 1 container left in the folder. In the folder.json file, the old container (linuxgsm-docker) is still listed as a member of the folder. If you click on the folder, the old container doesn't show up, and there isn't any way to remove the container (besides editing the /boot/config/plugins/docker.folder/folder.json file directly).
  3. It happened again sometime today after 1200 EDT. Output from dmesg -w: [180253.133938] general protection fault, probably for non-canonical address 0x995d43662ef36987: 0000 [#1] SMP NOPTI [180253.134046] CPU: 12 PID: 26023 Comm: node Tainted: P W O 5.10.28-Unraid #1 [180253.134106] Hardware name: Supermicro Super Server/H11SSL-i, BIOS 2.1 02/21/2020 [180253.134170] RIP: 0010:nf_nat_setup_info+0x129/0x6aa [nf_nat] [180253.134222] Code: ff 48 8b 15 ef 6a 00 00 89 c0 48 8d 04 c2 48 8b 10 48 85 d2 74 80 48 81 ea 98 00 00 00 48 85 d2 0f 84 70 ff ff ff 8a 44 24 46 <38
  4. Unraid crashed yesterday and again last night. This has been happening pretty regularly, and I don't really know why this is happening. I'm attaching diagnostics data and a screen shot from the IPMI of the crash. I had disabled the syslog (I have since re-enabled it), so I didn't capture those logs. Hopefully the diagnostics can show why this server keeps crashing on me.
  5. Not yet, I was hoping someone with more experience then I have would be able to parse the logs and confirm my suspicions. Since I don't know exactly when the server is crash, or why, I was only guessing about the NVIDIA trans-coding based on the screenshot.
  6. I had another crash today, this time I was able to get the logs from the syslog server. The log is from the local syslog setting, and the is from the remote syslog server setting. Based on the screenshot from the original crash, I think this might have something to do with the GPU Transcoding in Plex, but I'm not completely sure how to best troubleshoot that. Any assistance would be greatly appreciated. syslog- syslog-
  7. I saw how to setup systlog, and I have configured it (but after the two crashes). Hopefully I don't need them, but I now have access to them if there is every an issue. I'll clear out the system share, as far as the 50g docker.img, space is cheap. I knew once I get this working, I was going to play with Docker and get some more familiarity with it, so I decided to just increase the size.
  8. I recently added the old drives from my prior NAS to my new Unraid server, and also added a 2nd parity drive (both parity drives are brand new.) The first time it was doing the parity rebuild, the server crashed with a kernel panic. I rebooted the server, and had to reinstall my docker containers since the docker image broke (I don't remember the specifics, I just remember finding a guide on the forums for how to fix the issue). I started rebuilding the parity this morning, and just had another kernel panic. This time I was able to capture a screen shot from the IPMI shown here: