shadowlord

Thanks. I was not aware of the onboard controller with Ryzen board issue but will look into it more. Unfortunately, I have already updated to the latest BIOS because the board didn't support the Ryzen 5600x processor, so that as an option is out. I am aware of the USB-disconnect issue which is I why I upgraded in the first place, my previous motherboard was old didn't have enough SATA ports... the plan was to upgrade to this motherboard and then move those USB drives to the internal.

Diagnostics attached. Looks, Ike I'm seeing read errors on all the other disks now and they've been taken offline. I hope I haven't lost everything. server03-diagnostics-20220307-0126.zip

I'm using Unraid 6.9.2 I had just gotten things somewhat stable and up and running (10 days into my trial). Things were looking really good. I had just added all my drives to the array and copied all my data over it. The parity disk took all weekend to sync, but it was done. Now I had some new hardware finally arrive, so shut the old server down, and swapped out the motherboard, CPU and RAM. That was a bit of sideshow, as I had a motherboard that had an outdated BIOS which did not recognize my new Ryzen 5600x, but once I got that sorted, I popped in my unraid flash drive and fired it up. It said one of my disks had a write error, and took it offline. The disk itself seems to be fine, so I followed another thread on this forum, took it out of the array, and then put it back in again. Unraid now says it's reconstructing the disk from parity. Great! However, unraid now says in the corner that it's missing the key file. And, of course, I had not yet backed up my USB key to the cloud. What do I do? I can't do anything for the next 15 hours while the disk is being reconstructed.

Because the VM gets stuck after boot, I can't even SSH into the VM in order to update the fstab file nor change the video drivers. I have a hunch that the issue may be disk/fstab related and that needs editing. In the meantime, I have created a fresh Fedora VM from scratch and making a clean install from the ISO, which is working, although obviously the services have to be reinstalled and reconfigured. From this experience, I suspect that the issue in the migrated-VM is with the UUID. For the next step, I will attempt to edit the /etc/fstab file externally to adjust the UUID.

I'm a long time Linux user who is just getting started with UnRaid. I was running a Fedora 35 server on my hardware (physical/bare silicon), and have used qemu-img to image the SSD into a .img file. I would like to run that image within unRaid in a VM as it has a number of services configured. I created a new Fedora VM with a fresh .img file within the webgui, and then stopped the VM and edited VM to point to my Fedora.img file. When I try to start up the VM, I can see the grub boot menu with the correct kernels from my Fedora 35 install, but then it gets stuck after that. I suspect that a setting in the image needs to be adjusted so that the image can boot. is there a manual or guide on how to convert a Linux server to an img file and set it up to boot from within unRaid? Or can someone tell me what I need to change to get my Fedora VM to boot? (Eventually, I will migrate various services off of this Fedora server into unRaid, but I need to keep the current Fedora server running during the current transition period to minimize downtime of other services.)