jonny_blaze

Thank you for reading my post. I installed a new windows 11 VM and everything was working great. I have my Gpu passed through as well as an NVME usb 3 drive hooked up to the USB C port on my graphics card. I upgraded to the new 7.1.2 build yesterday and now it doesn’t show up in My Computer. I tried restarting, I tried upgrading the driver using the virtio folder. I tried disabling and reenabling the usb 3.1 and usb c passthrough and I still can not get it to show up. Any reason this may be happening. I also installed the latest nvidia drivers. thank you for your help.

Just a follow up, I was able to do a reconfig and add the drive back into the array. I was also able to do a parity sync and everything seems back to normal now. I guess the issue was either with the old SAS card or its cables. I replaced both with newer versions. Thanks to everyone who helped me figure this out.

Well I am kind of a noob ….how do I do that?

ok here are my diagnostics. I thought of a work around. I was able to mount the disk with unassigned devices, share the drive and pull the data off the drive to a usb hdd. But this just tells me the drive is probably still good and that if I replace it with a new drive and a new parity drive, whos to say this wont continue to happen? ares-diagnostics-20231220-2056.zip

well I changed out the SAS card and cables and now my parity drive and disk 2 will not be recognized by Unraid. Do I have to change out the drives and lose the data that was on disk 2? Or do I need to start fresh and clear out all the drives? I am relatively lucky as I do have a back up server that has most of but not all the data lost. Could there be other issues with the MB or something else I am not thinking of? Your help would be most appreciated. Thank you.

My server is having major issues with constant UDMA CRC read errors. Now my parity drive and disk 2 are said to be bad. The array will not boot. I ran an extended Smart test on disk 2 and its said that its fine. Now I am at a loss as I need this server to either boot with disk 2 so I can replace the parity drive or with the parity drive so i can rebuild the array. Also was wondering if my SAS card could be causing all these errors and if I should replace it. Is there any way to get unraid to ignore the udma errors and just boot? I am kind of a noob with unraid. I posted my diagnostic files here. ares-diagnostics-20231130-2359.zip

Here is the diagnostic zip file apollo-diagnostics-20230604-1425.zip

I have a 6 disk system, a combination of 4 and 8 TB drives. While some of my drives are up to 75% full, I have one 4TB drive that has no data on it whatsoever. I am curious if you can set disk utilization say up to 50% before another empty drive is used? I would like to balance the usage of all the drives and not have 1 empty and others at 75%. Thank you for your input.

Here is the diagnostic zip file. ares-diagnostics-20220619-1223.zip

I keep getting the following error when trying to pass through my graphics card on my unraid server. Any help would be most appreciated.

Yes I would like to see this as well. So that the only port you have to open on your router is 443. I believe Kemp has it free to run on the cloud with AWS or Azure. They also have it free to download and run as a VM. The example I saw was run on VMware and hence was downloaded as an OVF. It’s pretty sweet how this was set up. I am not that familiar with the different VM formats to know if this would or wouldn’t work in the Xen environment.