Das_Pflanze
Members
-
Joined
-
Last visited
Everything posted by Das_Pflanze
-
Nearly a week later I can conclude: It probably came from macvlan. First memtest did finish 5 runs without an error. So it probably wasn't the RAM. After setting up a extra vlan for all of my docker containers, that have their own ip, I now had no macvlan stack traces anymore and my server never crashed since then. So I guess the problem is solved.
-
Ok, thank you. After looking somewhat more into the memtest version on unraid I now know, that its not a gpu issue. I have UEFI Boot enabled. After putting another memtest version on the stick I'm now running a memtest. I'll report when at least one run is complete.
-
Ok, well that's what i feared. Ok, could macvlan call traces have to do with it? I just switched to ipvlan today. Another issue I'm facing now is that memtest won't work over ipmi. It stops with "loading /memtest". I guess it outputs on my Quadro P600 that I added for transcoding. Sadly I can't get to the server in the next days. Is there a way to disable specific GPUs for memtest? There is no option in the bios for it and I tried append vfio-pci.ids=10de:1cb2 in the syslinux configuration but that didn't work either.
-
Hey everyone, I'm using unraid since like 5 years and currently installed an additional nvme SSD for appdata stuff (mostly plex) while still using a sata ssd as array cache. Since a few weeks I have issues with unraid getting unresponsive or a crashed docker service. After getting syslog written to my sata ssd I found following errors: After restarting my server everything is fine again. Now I'm not sure if I should replace the NVME SSD or check the RAM. Sadly I wasn't able to run a memtest yet as it won't show any screen when started over IPMI. Can someone point me in the right direction? unraid-diagnostics-20230807-1044.zip Thanks!
-
Hey everyone, I always used unraid with access based share enum = Yes in Samba extra configuration. After updating to 6.11. none of my systems (MacOS, Windows) could access shares with \\ip-address\ or smb://ip-address/. Accessing them with \\ip-address\sharename or smb://ip-address/sharename still worked fine. After uncommenting the line in the settings, I can again see all shares, but I rather would see only the shares the connecting user has access to. There is another topic about this issue in the general support forum: unraid-diagnostics-20221007-1507.zip
-
I've already made two reddit posts (first and second, which led me here), but I guess it's better the create a real bug report. So I've got a "new" used PC and I created a fresh 6.8.3 install usb stick. So 6.8.3 boots fine but if I update to 6.9.0 RC2 on the running unraid or create a new 6.9.0 RC2 stick it won't boot. I get to the boot menu but after choosing "Unraid OS" or "Unraid OS with Gui" it gets stuck after /bzimage...ok /bzroot...ok and /bzimage...ok /bzroot...ok /bzroot-gui...ok I enabled debug mode in syslinux and got another line on startup, so it says: /bzimage...ok /bzroot...ok early console in setup code PC specs: z170h4-ea Intel Core i7 6700 16GB DDR4 2133 GTX 970 (tried it with and without it) Edit: As I tested right now: No, 6.9 Stable won't boot either.