January 30, 20233 yr Hello all, What was a unclean shutdown was actually a crash of the unraid vm I was running inside proxmox. The why: 1) unraid does file-sharing amazingly well, 2) want to get more knowledge of proxmox, 3) already got a proxmox node, 4) this motherboard has 2nvme slots for (one for cache, the other one is for vms on proxmox), 5) has 4 2,5G nics where my old board has only 1 1G nic 6) power consumption. Well in short: unraid kept on crashing after half hour or so. Did not matter if I was using the q35 or i440fx - even tested it with OVMF and SeaBIOS. Did change much.. Yesterday I gave up and removed the proxmox installation from the nvme and booted unraid normally, from usb. The bootprocess did not go much further then unpacking the image - The installation of proxmox needed some tinkering. I had to add xdriver=vesa and nomodeset to the grub_cmdline_linux_default otherwise the proxmox installation would crash on switching to the graphical installer.. But now back to unraid. My knowledge about slackware is limited. Starting unraid os normally would crash - I rebooted and tabbed to add xdriver=vesa and nomodeset to the cmd. After that unraid seemd to be booting but I tried this couple of times but keeps on crashing. Even had an nice amiga 500 copperlist at somepoint - It is deffo not the memory - I equipped the board with two matching quality brand (if kingston is still a quality brand) sodimms and passed memtest flawlessly. Does any unraid devs/engineers can make anything out of this "screenshot" - I really would like unraid to work with this motherboard. I think that there is something unraid does/want that is somehow not allowed since proxmox work (also installed couple of containers in it) and people are reporting that truenas / iESX also works on this motherboard
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.