Juzzotec

Hi all, I think I found the culprit or I suspect it to be the case for my setup. if I enable the wifi in vfio and attach it to the vm in config, the vm basically has a bad time. It’s like it doesn’t know what to do with 2 network services, I remove revert this change and things work perfectly. This is a guess but an observation for anyone else that is stuck.

Thought I would come back on here to provide an update, I reverted everything on my VM to basic. Meaning I removed the GPU assigned and all USB and other attachments, back to a basic VNC VM. Also removed VFIO mapping of my GPU and rebooted. VM shutdown was still crashing Unraid. Then I upgraded to v7.0.4 beta, basically YOLO because I am not sure why this issue was so persistent. Confirmed things are working well in v7.0.4, noticed things look different in unraid going from v6 to v7. Especially in the VM Space. Started with the basic setup; Guess what? booted and shut down very fast. Slowly enabled all my devices and everything is working perfectly now. Also, my GPU is working without vBIOS dump and I prefer it this way too. Magically, things are back to previous config on new OS v7. The only difference is adding the following line in my VM, wondering if this breaks things because it did fix my bluetooth not starting issue. Scared to try it in case it ruins everything again... 😁

Bump, can I please get some help with this?

Hi guys, I recently setup my unraid server with new hardware and GPU to use the VM functionality for gaming. Everything is working fine including passing through the GPU with vBIOS which I was able to edit after saving. I passed through Wifi, Bluetooth and an NVME drive including all 1660 Super Nvidia components from VFIO IMMUO group. The problem is shutdown of the my VM crashes my Unraid, the only way I can bring back the GUI is by performing a GUI restart from command line using the command below. /etc/rc.d/rc.php-fpm restart So when thats done, I can access the GUI but clicking on the VM tab hangs the Unraid GUI again. I am not sure how to troubleshoot this issue but I am hoping I can get some help because other than this issue, everything else is working fine. I downloaded my diagnostics and attached it to this post. Thanks. montanalab-diagnostics-20241110-2253.zip

This post saved my sanity, not only did it fix my bluetooth but that edit to the kvm line did allow me to save the config within the GUI xml editor. Thank you so much! :)

Thank you very much I will look into your recommendation. So Xteve automically kills the connection once the vpn drops??

Does Xteve VPN have a kill switch configurable? or Is it better to use regular Xteve with OPVN_Privoxy if that has a killswitch available? Everything is currently working for me with Xteve_VPN but worried about disconnect and exposed?

Thank you, rebooting now 🙂

Hmmm for some reason... changes in theme park are not changing my UI?

Thanks, no wonder my disks are not automatically spinning down. Is Never the default value? I just changed it to 3 hours and will test and report back overnight. What does everyone else set this as? 1 hr, 4, hrs...

This is something I noticed recently as well... my disks never spin down unless I initiate it manually. Open files shows no shares accessed, only cache... hddtemp disabled from grafana-unraid-stack docker. I checked Disk Settings and Default spin down delay: is set to Never. I have not touched this setting at all! does never mean, never spin disk down or 0 mins delay to spin down. Could that be something enabled by default since 6.9.2?

Change to vmxnet3 worked for me too, thanks for the fix.... for anyone else that finds this thread (take note) 👍 👍 👍

bump

Hi Guys, Can someone please look into my diagnostics for issues with my VM? every day I go into my Unraid GUI and notice that my Win 10 VM has crashed. I didn't want to provide brief information so I have attached my diagnostics. Your help appreciated. Thanks, Juzzo horizonlab-diagnostics-20210724-1821.zip

I cant add the channel mappings? none of them match...? confused... configuration went through fine until trying to add channels to plex.

Thanks trurl! Will the recreate process use the same file system as the old drive and is there a problem using a mix of xfs and reiserfs in an array?

Replace a Single Disk with a Bigger One 1. Stop the array. 2. Power down the unit. 3. Replace smaller disk with new bigger disk. 4. Power up the unit. 5. Start the array. When you start the array, the system will reconstruct the contents of the original smaller disk onto the new disk. Upon completion, the disk's file system will be expanded to reflect the new size. You can only expand one disk at a time. IS this method redundant now? Stop the array Unassign the old drive, if it's still assigned Power down [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing) Install the new drive Power on Assign the new drive in the slot of the old drive Go to the Main -> Array Operation section Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives All of the contents of the old drive will be copied onto the new drive, making it an exact replacement, except possibly with more capacity than the old drive.

Good to hear

A disk needs to be outside the array to preclear, it's part of my procedure. Install disk Check detected in webgui Make sure removed from array and take note of serial number Run the preclear list command Run the preclear on drive Insert into array Your adding into array, so no drives available?

Thanks alot Joe L & trurl Installed screens and everything is good

Try and have a spare (precleared) drive on hand. That 30+ hour wait time after one of your drives fails seems more like 60+. I just added a 3TB parity drive and now I need to keep a look out for a good deal on a shelf-spare. I like the idea of having a separate box to preclear drives and test plugins. Best of luck with your system! Cheers man, u too I'll try and grab a spare ASAP. Wanted to ask, are any of you guys per clearing through telnet, what happens when the session dies?

I think one cycle is enough for me man, it takes 30+ hours for 1 drive only 3TB. If I do 3 cycles it would take 90hours to preclear, that sounds like overkill in my opinion

Is your data important or easily replaceable? Also if you don't use preclear then when you add a disk to the array the whole array will be unavailable while unRAID writes zeros to the drive. The time will vary based on drive size but for a 2TB drive it will likely be ~9 hours. If you preclear it first your array stays available while the drive is being precleared. The other reason to preclear a drive is to exercise a drive to find a bad drives. Most drives die within the first ~100 hours or run to their warranty period or longer. Thanks man for the details, I'm new here and learning all the time. So I guess I'll stop being impatient and just preclear all my drives This is going to take 1 - 2 weeks to have up and running with plugins shares per clears etc but slow and steady wins the race I guess.

New to unraid, pre clearing takes so long. Is it really necessary guys?