flic

got ya! but that plugin requires that the VM is already started to attach the USB devices. thats my dilema: the VM wont start if those USB devices are not connected at launch and the devices, in my case the KVM USB keyboard and mouse, wont show up in the device list until I switch them up

Just noticed that I can remove the USB keyboard and mouse while the VM is running So, same rule here: why cant I add the USB keyboard and mouse after the VM has started?

Here's the situation: I have a monitor with KVM switch that is connected to a regular PC and to the Unraid server. I want to pass the keyboard and mouse to a Windows10 VM on Unraid. To do that I have to switch to another PC (or RDP to the reg PC) to make the keyboard and mouse available to the Windows10 VM Edit page. So far, so good, no issue. But when I am on the reg PC, which is now the active keyboard/mouse of the KVM switch) when I want to start the Windows10 VM, below error is thrown: "Did not find USB device..." Yes, absolutely right! But, Unraid should discard any USB devices missing and not throw any errors. Most if not all USB devices are plug&play and should not prevent the OS from booting. So, is it possible to review the VM starting rules to avoid checking for missing USB device? Please, let me know if you need +info on this issue or context Thanks in advance

yep, got it Looks like falty cables. I changed both Thanks trurl

I do. its just that Disk3 had a few gigs left. Once full then Disk4 will be in service

when I pushed on the disk power cable, I heard the drive spinning up. Now its up and greed so, I just have to remove Disk4, Start the array then shut it down and put back the Disk4, right?

Last thing I did is to Gather a folder (out of the Disk4 to Disk3) with unBalance plugin. Then I cleared the stats and boom! 1st the Disk4 had the red X the same for Disk3 a few seconds later. server-diagnostics-20200802-1627.zip

What should I do to recover Disk #3? Disk #4 has no data

when it starts or reboots, hit the F2 a few times, you will enter the BIOS menu

1-You need to change the rez to 1920x1080 then boot then restart 2-You need to change the rez back to 1280x800 kinda freaking sucks!

why are you saying that Splashtop is faster than no-VNC? Ive install it and g, there's a major lag with the mouse-cursor. is that normal?

I do not touch the XML between boots

that needs to be changed at every damn reboots? and twice!: 1-You need to change the rez to 1920x1080 then boot then restart 2-You need to change the rez back to 1280x800 kinda freaking sucks!

both drives are connected via USB 3.0 interface. I know each drive must have unique IDs, but they are put there (I cannot change them) So, you seem to tell me that your plugin is not compatible with external bays like USB? I wanted to get away from Microsoft Space Storage but it looks like I will have to go back until something better comes along

I cannot add 2 drives of the same brand because they have the same IDs When I change the Device Moint Point of the second drive, that (stupid thing) changes the DMP of the first disk I cannot be the 1st one who ran out on this issue vs=2020.07.03a

great! ran "Dynamix File Integrity" after and 0 file corrupted kudos to unRAID dev team 😎

xfs_repair worked! Parity-Sync/Data-Rebuild in progress... brb in +16 to report

ok thanks trurl. I will try that

Somehow 1 drive of my array got corrupted. So, I replace it. It show "Unmountable: No file system" on the far right of the drive Then start the array to start the recovery of the drive. So far so good. After +16 hours of "Parity-Sync/Data-Rebuild in progress." my drive still says "Unmountable: No file system" Should the Parity-Sync/Data-Rebuild reformat my drive and rebuild the data that was on the drive?

maybe use "Unassigned Devices" and delete the partition

dont tell me I have to set the "Use Cache Disk" in the share settings. This is huge files (Movies) share so it has to reside exclusively on the array, not the cache. My understanding of a cache drive is as follow no matter how the share is configured: Client file -> Server cache -> Server storage

xfs formatted cache does not behave as a caching drive: copy to a share bypass it completely

ok. doing lots of diff re-configurations, I remember seeing the same 1 drive as btrfs

isnt it suppose to be btrfs?

dunno whos the "i"diot who came out with the "i" in the middle, but thats debatable too...most likely those same drive manufs to avoid law suits... I learn in college that a KB is 1024 bytes and no ones will make me call it a KiB LOL