testdasi

No way to know without someone actually owning the board. Even different BIOS versions can result in different IOMMU groups.

Can you do it with root user? 😱

The VM. VM booting SeaBIOS + Q35 = BSOD at boot.

Q35 machine. Do you have this section of code in the xml, before </domain>? If not, add it. Otherwise your GPU runs at PCIe x1. <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.speed=8'/> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.width=16'/> </qemu:commandline>

I think Unraid defaulting to i440fx is a legacy thing because Q35 used to be rubbish with Windows some years ago with the old qemu. From Unraid 6.6 onwards though, the progress made in qemu was good enough to make Q35 at least on par with i440fx and potentially even superior with regards to PCIe passthrough. I remember seeing posts in forum about some GPU that would not passthrough without Q35. A few tips for you: Q35 doesn't like SeaBIOS + Windows. So make sure you are on OVMF i.e. boot UEFI before switching. Start a new template. I think the i440fx pci -> Q35 pcie move is way too complicated for the Unraid GUI to handle. Don't forget that last bit of code to add manually to the xml. Wasted me an hour wondering why the F my 1070 doesn't work. <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.speed=8'/> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.width=16'/> </qemu:commandline>

About 25TB. Took me 10 days, 2 of which on 150Mbps, 3 on 250Mbps (because my old router can't handle gigabit) and the rest on 1Gbps. Average speed is about 30MB/s but given 2/3 of the object counts are my offsite backup which are full of tiny files in the KB range, that's not too shabby. Compare that with Crashplan which last took 10 days to backup 200GB worth of files in the MB ranges and I'd say it's a huge improvement.

Oh dear. My prayers for you and your family, mate.

Hi Max. I suggest you post a request in the feature request forum. Not saying that LT will implement that but there's a better chance than posting in this old topic.

Simpler solution. Try updating right after a reboot?

It's a Linux kernel problem. People are already trying to help to find workarounds but if it's not fixed in the kernel, there is no guarantee whatsoever that these workarounds would work for everyone. Don't blame the tires when the engine breaks. You can't possibly expect everyone on the forum to drop everything to give you (free) bespoke advice on an on-demand basis. Such expectation is also not acceptable. Best course of action for you is to use the last Unraid version that works.

Everything hangs when a disk is spinning up - that's to be expected. A disk refusing to spin up doesn't sound like a UD problem. My HDD spins up fine when accessed.

Some major updates: Many thanks to @DZMM for helping me with rclone. Rclone has allowed me to move most of my content up to the cloud, run parity less (better speed) and reduce my local storage needs (got rid of the 8TB Archive and 6TB Black - may get rid of the 8TB Iron Wolf in the future - my array now only serves as local backup and offline storage for some short-term content in case the Internet is down.). Plex works perfectly fine with cloud storage, even on my old 150/150 connection. Nobody in the household noticed my move to the cloud. It was that transparent. I won't tell anyone and see how long it takes for someone to notice. My upgrade to 1Gb/1Gb is more of a quality of life addition since I can do my offsite backup to the cloud more quickly. Will get rid of Crashplan as my offsite backup service. While they were great in the past, their recent move to business-only has exposed their shortcomings vs other business-level solutions. Speed and ease of restoration are the 2 biggest sore thumbs. My workstation VM is "upgraded" from i440fx to Q35. I'm delighted to announce, the GPU fans no longer stop while idling without MSI Afterburner! That means my PM983 can idle under 45 degrees regularly. I think once Unraid moves on to a more recent qemu, the default Win10 template should use Q35, which has better support for PCIe. At the moment, I have to manually add the codes below to the xml; otherwise, my PCIe runs at x1. <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.speed=8'/> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.width=16'/> </qemu:commandline> The latest Linux kernel + F12 BIOS seem to make disabling Global C State Control less stable. For extremely strange reasons, that manifests as out of memory errors if I try to reserve more than 50% of RAM all at once (e.g. start my workstation VM). So if you disabled Global C State Control in the past and now seem to have some instability, maybe try enabling that with the latest BIOS.

Up from 6.7.1. No issue to report. Even my dual NIC doesn't have the same DNS problem.

When I was testing out various configs, I simply use User Scripts and do a simple cp to create a copy. I reckon someone more verse in shell script can sure create a folder based on time and cron it every hour or something.

That sounds like network problem. Install the Tips and Tweaks plugin and try disabling NIC Flow Control and/or NIC Offload to see if it helps.

Create a separate topic with a proper report of your problem and attach diagnostics. Posting a 3-line complaint on every release topic will not get you the necessary help.

When you transfer 1 single very large file (pick you 70GB mkv for example), what speed do you get? Does it flat line or fluctuate?

So is it just newer kernel and restoring sqlite support?

What makes the plugin not easy?

Upgraded from 6.7.0. Forgot that I upgraded and tried to do it again.

A memory leak due to a docker, at least in the cases I have seen, causes Linux to panic and kill some processes to free up more memory. Your shfs errors suggest shfs can't allocate memory which is a different problem I think.

You have a lot of these: Jun 24 14:01:13 Server shfs: error: shfs_readdir, 1301: Cannot allocate memory (12): filler: F464A7E26B25ED562EAF3576C2FB0B702F2D1255 (2019_05_26 18_07_02 UTC) Looks like memory problem. You might want to resit your RAM sticks and then run memtest.

Oops sorry I missed the "instant" keyword. It is not instant because Unraid will try to copy the file to the unionfs location and then delete the original. Unionfs isn't smart enough to realise the RW location is on the same media as your original.

What is your unionfs line in your mount script? That sounds like you set your mount_rclone as the RW location so when you copy file over, it tries to upload to gdrive live during the transfer. rclone_upload is instant because it's local until you run the upload script.

I am also very much interested in the <$200 part. I have looked around but have not found anything at that price point.