Rive

Yes, it did the trick, thank you! The images were succesfully copied, lost about 10 Kb of data in one and 1.3 Mb in another - no difference, they still function as intended. (I heard about ddrescue, but I thought it was a part of DD and that thing cannot ignore I/O errors either)

That fails even in sector-by-sector mode (I use Acronis True Image). I guess, the reason is that the software doesn't have direct hardware access and the system just spits out a bunch of errors and stops operation completely, expecting device/IO reset.

TLDR in the beginning: I found a CLI utility called safecopy (https://safecopy.sourceforge.net/). I'd love to have it in Unraid. But it needs to be compiled - and that's not how Unraid works. How then? Explanation: I have two big VM images on an SSD cache drive with a btrfs partition. The drive is failing (in some way): more than 1000 errors in scrub, btrfs check and repair do nothing. I need to copy these two big files off of the SSD, but when I just use MC, the process gets interrupted with I/O error. Unraid logs show messages like "Apr 2 19:33:01 SRV kernel: print_req_error: critical medium error, dev nvme0n1, sector 176853640", there is lots of them. Why do I need to copy these VM images? Because they still work! Probably nothing serious damaged or lost inside the images themselves. So I know what I'm doing, I only need these two files in whatever damaged state they are now. The rest has been copied already, only these two files are left. I found a program called safecopy (https://safecopy.sourceforge.net/). Apparently it can do the job. But it needs to be compiled, there is a guide. But apparently Unraid lacks compilers and libraries and in general it's not THAT type of Linux. So, how do I compile and run safecopy on Unraid? (And if it's possible to do in a Docker, then how do I do it?) Thank you.

And it did the trick. Just added module_blacklist=i915 to all the append lines in syslinux.cfg and it started to boot. Thank you.

Ok, it was the integrated graphics adapter Intel GMA 3100 - I threw in a GT 210 card, and the system booted just fine. But that shouldn't have been a problem - this forum has some old messages confirming old versions of Unraid were working on this MB and other ones with Intel GMA 3100. Plus the problem technically stays. I don't really want a discrete card in my server just to boot it.

Hey! Been trying to run Unraid 6.11.1 on an Asus P5E-VM DO motherboard with a Core 2 Duo E6750 CPU and 4 Gb of RAM, using the motherboard's video output. The system starts booting normally, but then at some point the screen goes black and everything stops. No network either - it doesn't get an IP from my DHCP. The machine is OK, has a Win 7 instance there. The flash drive is ok, works on another machine - boots to CLI, at least. The flash drive is fresh, no Unraid keys, no trial mode configured. Here I made a video of the boot sequence. Reminding you, that the bars mean no signal but a black screen means that there is a signal (the capture card detects something), but the signal is blank.

Same problem as cherritaker has. 209.222.18.222 is down?

Hey! Having problems with setting up torrents being moved to a diff directory when completed. Tried to change it in the GUI, "Autotools" section - didn't work, but the setting seems to be saved. Then the FAQ says "So rutorrent is purely a web frontend to rtorrent, and as such does NOT modify any settings for rtorrent...", and I still don't get the logic of it. Why the hell would you even have settings in GUI that just don't work? Why to add them to GUI at all? Seems like nonsense to me. Then there is rtorrent.rc file, it has a setting with my folder for torrents being downloaded (incomplete), but I don't see any settings for moving torrents to another directory after completion. BTW, I changed the default directory for downloads in the GUI, and it works the way it should - torrents are being downloaded to the new dir. And the FAQ says it shouldn't have worked.

Well, here we go - after two days of working without any issues HTPC VM and pfSense VM both got frozen after I tried to open a webpage with video in it (Twitch). The diag data is attached, but even without looking into the logs I can tell that HTPC stopped because of its videocard (or USB controller) and pfSense - because of its NIC. P.S. Before I added another USB card and moved some cards to different slots the issue involved HTPC VM and SPC VM (not pfSense). srv-diagnostics-20181003-0139.zip

Ok, I did one more hardware change - I added one more Renesas USB card instead of onboard ASMedia USB 3.1 controller. I used that for my HTPC VM. I haven't done much testing yet, but that seems more stable. I have only one additional question: how do I stub PCIe cards these days? pci-stub.ids? vfio-pci.ids? xen-pciback.hide? Some combination? I really can stub all hardware VMs using, not a problem, but should I?

Well, another issue has happend. I started my SPC VM after booting unRAID and the whole system just got frozen (no error msgs, nothing, and no any connectivity). I reset the machine it and there was no VM tab in the web-interface. Never seen that before. The array is running. No VM tab, but I can see Docker tab. I don't understand what's going on. Tried to reboot several times, the tab still didn't reappear. Now doing parity check. The diag info file is attached. P.S. VM freeze problems started when I updated from 6.3.1 to 6.5.2. But now it's way worse. And I wish I could change hardware, but I can't. Everything was pretty stable on 6.3.1... srv-diagnostics-20180930-0352.zip UPDATE: Got the VMs back. VM functionality was disabled in the settings. Why? How? No idea.

Ok, a small update. I physically tossed cards inside the machine - moved Renesas USB and a network card (the one that pfSense uses) to other PCIe slots. The situation has changed a bit: now sometimes when I start HTPC VM, pfSense freezes with its network card vfio_err_notifier_handler error (never had an ussue with pfSense VM before). BTW, testing is a little bit hard, 'cause half of the times HTPC spends a couple of minutes on Tianocore splash screen and sometimes its USB controller just doesn't work (onboard ASMedia USB 3.1) - the machine seems fine, just no controls besides stopping it from the VM manager... These issues aren't new, HTPC VM has always had them.

Hello! I've always had 2 Windows 10 VMs in my unRAID, let's call them SPC and HTPC. They both have had NVIDIA GPUs and USB controllers passed through from the very beginning. And everything was fine until I updated from some older unRAID to 6.5.2. 1. Now when I start HTPC, my SPC can freeze immediately with qemu-system-x86_64: vfio_err_notifier_handler(harware address) Unrecoverable error detected. Please collect any data possible and then kill the guest In this case the hardware failed is usually the video card with its audio card (sometimes it's Renesas USB card). 2. If I manage to start HTPC and then restart SPC, HTPC might freeze randomly after some time with the same error for its videocard (with its audiocard). 3. Or they just might freeze both randomly, if they work at the same time. What I've noticed: 1. SPC works for weeks if I don't start HTPC. (cannot test vice versa, because I need SPC everyday). 2. If HTPC freezes shortly after boot it usually happens after I go to full screen video (YT in Chrome) or after screensaver starts. What I tried: 1. Reinstalling Win10 on both VMs. 2. Slighly changing VMs parameters like memory and even recreating them completely from the ground with new drive images. Additional info: 1. I turn my unRAID server off when I don't need it (it's not 24/7). In fact I upgraded from older unRAID ver to 6.5.2 because that older ver couldn't shutdown the machine half of the time - it stayed powered on but completely dead. 6.5.2 turns the machine off properly everytime. 2. I have a 3rd VM there - pfSense - and it's never had any issues. 3. I'm running unRAID on Core i7-6850K on an Asus X99 motherboard with 32 GB of RAM. SPC: GTX 1050Ti + Renesas USB controller, HTPC: GT 740 + onboard ASMedia USB 3.1 controller.

Thank you! I'll try both workarounds you offered and report the results. But something tells me that it isn't a state of a VM - looks like it's more related to the server itself, because if I'm getting this issue after server restart no matter what I try, how I restart VMs, it won't go away until I turn the server off and on again.

Sorry, here it is. srv-diagnostics-20170331-1429.zip