GottaGame9000

Changed Status to Solved

Well I can't believe i'm saying this. But that worked. I went from F11 to F12 on my bios version on my Z390 AORUS PRO WIFI. I also made sure to set the iGPU to enabled and have it be the default gpu (I have a gtx 1650 also in there). Something about those actions seems to have worked. Thanks for the suggestion.

Here's what I found Improve xrdp preformance edit /etc/xrdp/xrdp.ini "max_bpp=25" and change to max_bpp=128 "crypt_level=high" and changed to "crypt_level=none" reboot There was a few other ideas about tweaking the desktop environment or using RemoteFX features. Idk. its a lot smoother now, but its still capped to 50hz

I have a slightly different setup then @Rishumacher but here's what i got and what I accomplished. I've got a i9-9900K (with a iGPU) and a GTX 1650. I initially setup a new Ubuntu VM (using br0) and used VNC to get the latest updates that the OS would fetch and installed xrdp. I then downloaded the VGA Bios for the 1650 from https://www.techpowerup.com/vgabios/ and using the regular gui interface I set the 1650 as the primary for the VM and directed it towards the vBios. I plugged in a spare monitor to the 1650 video out and launched the VM and that worked. Ubuntu saw the 1650 and offered to download the offical drivers and then I tried xrdp. I sorta worked? I don't know why but I just had a black screen and when I used a native keyboard I passed through to the VM anything I opened using that appeard on the xrdp screen? Anywho I shut down my VM & unplugged my spare monitor and started the VM back up. I was able to xrdp again, but this time I got a desktop interface (its not the normal one I get when I natively use the VM???). It works, but the performance is awful. Very choppy and I couldn't adjust the resolution or refresh rate. I'll see if I have to mess with any xrdp settings or something to fix that

I'm curious about this topic as well. I was able to install the Nvidia drivers with VNC as GPU1 and the GTX1650 as GPU2. I then make the 1650 the primary and i'm able to RDP to my linux VM via xrdp (once i figured out how to to setup br0) but then the system doesn't see my GTX1650

In case anyone was interested to know the results. I followed the instructions titled ""The "Remove Drives Then Rebuild Parity" Method"" on the Shrink Array wiki page. And I was able to unassign the two data drives I wanted to remove (after manually moving all the files off them ahead of time). My parity & parity2 are currently being rebuilt, so as long as my remaining drives don't fail during this window of parity sync all should be well. I am able to access my shares and the content in those shares seem to be working no problem. Now to wait 24-30Hrs...

You just use the New Config tool to re-order the disks. I can't remember if you have to enable the "preserve current assignments" option or not. But I did preform a New Config a few weeks ago to re-order the disk ahead of time and they are now in the order I want them listed in the array.

Hey guys, I've got an 8 Disk array (x2 Parity & x6 Data). I've been using krusader to move files from /mnt/disk# to /mnt/disk# in preparation to shrink the array by removing Data Disk #5 & #6. My shares settings aren't currently targeting Disk #5/6 for use. Once I remove all my data off those two disks onto other disks (and run a parity sync) would I be ready to start following the wiki page about Shrink array?

Thanks for the info. Shame we still don't know why the swap failed when the log said it completed. At this point the main suspect is having another drive getting precleared at the same time might've caused intereferance...Best of luck to anyone else. I'll redo the parity swap after the other drive is done with its preclear and hope that resolves the issue...

Could be a possibility...say I wait for the PreClear on the other drive finish. If I kick off the parity swap procedure again I sohuldn't lose any data right? Any risk of data loss if I restarted the server?

I didn't do anything else. I was out at the movies watching the new SpiderMan during the time the parity should've finished and I come home and crashed afterwards. Didn't even touch the server.

I got some advice to preform the parity swap procedure in order to upgrade my parity drive and use the old parity for a data-rebuild of a failed drive. I think I started the procedure on 12/20 and it completed 12/21, but when I looked at my Main Array page the Start array button wasn't enabled, but instead looked like it was asking if I wanted to preform a copy operation again...any advice? https://wiki.unraid.net/The_parity_swap_procedure https://www.youtube.com/watch?v=MMlR0TMeKsI syslog.txt

Yes after reading up on the parity swap technique I believe this will be the solution to get my system stable. Once I preform this step I will work replacing the other parity drive and then shrink my array. Basically get my array in order in the old hardware before I migrate over to the new hardware.

(Ryzen- Current Server) x2 Parity:: x2 WD Red 8TB || x5* Data Disks:: x2 WD Red 8TB, x2 WD Red 5TB, x1* WD Red 6TB ( Intel-New Server) x2 Parity:: x2 WD Red 18TB || x3 Data Disks:: x1 WD Red 18TB, x2 8TB I'm planning to move to a new server with my data intact and a new data disk configuration (see above) & turn my current server into a off site backup with the remaining drives. Currently my 6TB hdd is dead in my current server (sounds like a record player when it powers on and won't show in BIOs). So currently one of my parity drives is emulating the content that was on the 6TB. What is the best/safest way to go about handling the migration? Do I first replace (inside the current server) 1 parity disk at a time until both are replaced with the 18TBs. Pre-clear the freed up 2x8TB and have one be the rebuild for the failed 6TB & the other replace one of the 5TB? Then ??somehow?? consolidate the data from the "now" 1x5TB,4x8TB,1x18TB to 1x18TB & 2x8TB? Then move my Unraid USB and drives into the new server? Thoughts? Ideas?