bisk

Interesting that a flash drive is being redirected, I honestly don't remember doing that, but I guess I did 🤷‍♂️ I started the array with VM Manager disabled Ran "mv /usr/local/sbin/qemu /usr/local/sbin/qemu.old" Enabled VM Manager Edited JasonVM in XML View to remove the section suggested, but when I try to save the changes I'm getting the following error - "VM creation error. Cannot check QEMU binary /usr/local/sbin/qemu: No such file or directory" and then the VM is removed from VM Manager. I was able to restore my VM Metadata since I've got a backup though. Here are the steps that I took to get things working again Disabled VM Manager Started the array Ran "mv /usr/local/sbin/qemu /usr/local/sbin/qemu.old" Enabled VM Manager Disabled Autostart on all of the VMs Stopped the array Rebooted Started the array Edited JasonVM in XML View to remove the section suggested I was able to manually start the VMs now Enabled Autostart on the VMs that I wanted to start with the array Thanks for the assistance in getting me back up and running!

Without being able to start the VM service, how can I do that? From what I can remember, I wasn't passing the flash drive or a USB controller into the VMs, but I was passing some USB devices.

I'm having an issue when I enable and start the VM Service, my USB Flash Drive starts to report offline and becomes unreadable. As suggested in the GUI, I have attached a diagnostic bundle from after enabling the service and the flash drive going offline. This issue started happening after I had a faulty CPU in my system. I have replaced the CPU and everything runs fine until I enable the VM service. homeserver-diagnostics-20240408-1112.zip

Thanks for the assistance. I was never able to get the system to stay up long enough to start the array in maintenance mode. I replaced the motherboard, but was still having the same issue. Thankfully I still had an old AM4 CPU kicking around, so I put that into the system and everything looks stable now. Time to RMA my 18 month old 5700G CPU. Part of my troubleshooting yesterday I replaced my USB, but that one seems to have issue dropping when starting the array (diagnostics attached). I've tried multiple USB ports too. I bought a new key, but now I'm getting an error that I've replaced my USB key twice over the past year and I can't update the key for the new USB key. I opened a support case to hopefully allow me to update the key to either the new USB key or the original good USB that is now blacklisted. homeserver-diagnostics-20240330-1248.zip

OK, the machine was responsive long enough in Safe Mode so that I could click Start, but rebooted while starting the array. syslog

I enabled syslog export to the USB key and attached that. Unfortunately I'm not able to collect another diagnostic file since the server freezes a few seconds after booting without even starting the array. syslog

Looks like the memtest completed and passed, so the memory looks good

I updated to 6.12.9 this evening and when I tried to start the array the server would become unresponsive or reboot. After rebooting the server, I reverted back to 6.12.8 and still had the same issue of the server freezing/rebooting when starting the array. Next I tried change the port that the USB Key was plugged into and also replacing the USB Key, but those didn't resolve the issue either. Not sure what's going on since I haven't really made any changes lately, so I'm assuming that this might be a potential hardware issue. I've attached a diagnostic and hopefully that can shed some light on the issue. homeserver-diagnostics-20240328-2004.zip

I tried to access my Unraid server this morning and it looks like it unexpectedly rebooted a few minutes before I tried to access it. As far as I know, nothing was happening with the server at that time since I had just woken up. There have been no hardware changes to the server a quite some time either. I've attached a diagnostic report from before I started the array. Hopefully someone will be able to see a reason why it may have rebooted. Also, I've been seeing an issue with my drives not staying spun down. I'm assuming that one of my Dockers is accessing the drives and spinning them up. homeserver-diagnostics-20240229-0659.zip

Looks like my server rebooted for some reason during its monthly parity check. I did replace the unraid USB key yesterday, so hopefully that’s not the cause. I’ve attached a diagnostic report. In addition, I seem to get errors with Plex stating that there isn’t enough space to play the file when I try to start watching something. Restarting the Plex docker resolves the issue. Hopefully you can see something in the diagnostics for this too. Thanks homeserver-diagnostics-20240102-0919.zip

I was able to resolve the issue by going into the RetroNAS Config, going to settings and setting the password. I reused the same password, but it looks like the samba service needs to have the password set after it's installed.

I created a RetroNAS VM using SpaceinvaderOne's RetroNAS_inabox Docker Container. The VM gets created successfully, but for some reason I'm not able to access the SMB shares from any of my devices (Widows, Mac and Batocera). I logged into the console with "retronas" as the username and password, launched the config utility (retronas) and changed the username and group from pi to retronas per the Docker's instructions. I installed the Samba and Batocera configs and didn't receive any errors. From my Windows, Mac and Batocera machines I can connect to the RetroNAS VM via IP or hostname, but when I try to connect to the share I'm prompted to authenticate and I tried using "retronas" for the ID and password, but I'm getting an access denied error. I've attached pictures of the RetroNAS configuration, output from the Samba service, Batocera config and logs.

The Fix Common Problems Plugin is reporting that /var/logs is full. I've attached my diagnostics for review. homeserver-diagnostics-20200220-1859.zip

Is it possible to update the version to the Beta code? I have a case open with Ubiquiti and they’ve asked me to update my Controller to 5.12.60, but the admin login page says that it’s version 5.12.35.

I went through all of the cabling again and all of my drives are being detected and I’m running through a recovery of Disk 1 and Parity 2. Thanks for the help guys! Now I need to looking into flashing my IBM M1015 and Intel RES2SV240.