steve1977

Based upon the errors (afk so can't fully check) it looks like you were trying to install a previously installed app and your flash drive either dropped offline or is suffering from corruption Any suggestion how to fix the dockers. I deleted all dockers and even the docker img. I set up a new docker img. Still no luck to get any docker container setup.

6.4.0_rc10b

That's what I had done. Above error message is when installing a docker container from the community app. Any other ideas how to repair it?

Looks like dockers may not be what I should have started to use. I deleted all of them and created a new IMG file. However, I can still not create new containers. See error messages below when trying to create a new container: Warning: simplexml_load_file(): /boot/config/plugins/dockerMan/templates-user/my-SABnzbd.xml:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 435Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 435Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 435Fatal error: Uncaught Error: Call to a member function xpath() on boolean in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php:436 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php(465): getXmlVal(false, 'Name') #1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php(721): getUsedPorts() #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(381) : eval()'d code(17): require_once('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(381): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(62): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 436

I just started playing around with dockers, but looks more difficult than I'd anticipated. After getting everything to work, now everything stopped working after I restarted Unraid. Plenty of error messages, but let me post the most obvious ones below. Any idea how to solve this? Configuration not found. Was this container created using this plugin? Warning: DOMDocument::load(): Document is empty in /boot/config/plugins/dockerMan/templates-user/my-SABnzbd.xml, line: 1 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 235Warning: DOMDocument::load(): Document is empty in /boot/config/plugins/dockerMan/templates-user/my-radarr.xml, line: 1 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 235Warning: DOMDocument::load(): Document is empty in /boot/config/plugins/dockerMan/templates-user/my-sonarr.xml, line: 1 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 235

MC gave me some choice "skip - skip all - retry". First I hit "skip", but this felt that there was no end. When I hit "skip all", it just stopped everything and got me back to the starting screen. Feels MC is too difficult for me to use Will give it a shot with Win10 now. This has a simple "cut and paste". So, I know what I am doing.

Ah, true, of course. MC also failed and only copied 10% of the disk. I am back to trying my luck within the VM by mapping them and work with Windows. Maybe this gets me more than just 10% of the disk. Any other advice?

This is a new and very weird issue. Most likely has something to do with passing through my Nvdia GPU... I now have two Win10 VMs. Both of them are running fine individually. I am passing through my Nvidia GPU to one of them. I am now trying to pass-through my USB keyboard or USB mouse. Just to one of the VMs (the one, to which I also passthrough the GPU). UPon adding either the USB mouse or USB keyboard, I can no longer start the VM. Instead I am seeing the following error message: *** internal error: qemu unexpectedly closed the monitor: 2017-11-16T13:46:54.708230Z qemu-system-x86_64: -chardev pty,id=charserial0: char device *** redirected to /dev/pts/4 (label charserial0)*** 2017-11-16T13:46:58.875101Z qemu-system-x86_64: -device usb-host,hostbus=2,hostaddr=2,id=hostdev3,bus=usb.0,port=2: Warning: speed mismatch *** trying to attach usb device "JMS56x Series" (super speed) to bus "usb.0", port "2" (full+high speed)*** 2017-11-16T13:46:58.991854Z qemu-system-x86_64: -device usb-host,hostbus=2,hostaddr=2,id=hostdev3,bus=usb.0,port=2: failed to open host usb device *** 2:2 Any thoughts?

Thanks. MC is a bit confusing to me, but I may have got it running. The space on my "new" disk is filling up, so it may be better now. I just noticed that I cannot access my UD (old disk) over SMB. Is this an Unraid limitation or am I over-looking something obvious?

Thanks, will do. I didn't find the move command in rsync, that's why I'd copied. Agree move would be better. Can you share with me the command line syntax for midnight commander? Do I need to use the GUI or can do via command line?

Just finished rsync, but unfortunately only 400GB out of 6TB were copied to the new array. The error messages in putty are incomplete as I can only see the most recent ones. Any idea whether some part of the 5.6TB can still be recovered. As you had mentioned before, the SMART scan completed 60% (and there were only some very few errors), so hop is that not 90%+ will be gone.

@De1taE1even and @danioj. What you guys did is exactly what I'd like to accomplish and I do have a similar setup as you have. Did you end up putting a post with the how-to? I have been trying everything for days, but cannot get it to work out. I have a GTX1050, which I passthrough to my Win10 VM running GFE/gamestream. I have paired Moonlight (on IOS) with gamestream and can see the list of games. When launching the game, I get an error message: "Connection failed failed to launch app". Any idea how to troubleshoot?

Maybe a video is a bit too much of an ask, but any chance to give me some pointers what I can try. I would really like to play PC games on my RPi (Retropie) connected to my main television. Reading in this forum that several has got it working. So, there must be some way. I have a Win10 VM running GFE. I am using Moonlight on IOS to troubleshoot why I cannot get the game to show on Retropie. Moonlight is successfully paired and shows the list of games. I see the gamelist on Moonlight on IOS, but get the error message "Connection failed failed to launch app" when launching the game.

Has this been updated for LE 8.2?

Got it, makes sense. Building parity now and will try to get back as many files as possible tomorrow. Are you referring to what I have done now (i.e., new config)? Or the general practice of replacing a small/broken with a larger/new disk? Data on this disk is just a bunch of movies. If something got lost, its good to know what it is, but not a big deal. Key is to replace the disk to avoid that all is broken. Also, i may even still be under warranty.

My GPU is a GTX1050, so this should not be the issue. Actually, I even have two GTX1050. I created a second Win10 VM with OVMF and now things work. So, Seabios is the issue. I used to have things working with Seabios though. Any idea what I can still try. Would love to keep my first Win10 VM (with Seabios) and now passthrough the second VM. Would this work?

The reason why I had to rebuild the parity in the very first case was that I am upgrading my server to 10TB disks. So, I had to swap out the 6TB parity wih a 10TB parity. I don't think there was another way. I was just unfortunate that the bad sectors occured at the same time that I was rebuilding the parity. From what I understand in this thread, this caused my parity disk to be unusable. I have now removed the disk with the bad sectors and am rebuilding my array. Once this is completed, I will try to copy over the content of the disk and let's see. From what I read here, rsync will be the best way to go and it will only copy the files that are in non-corrupt sectors. For others, it will give me an error message. I assume it is better to wait until my parity is rebuilt to move the old files over. From previous experience, building parity and copying large amount of data makes things very slow. So, let me do one step at a time. Does this now all makes sense? Wish me luck!

was just thinking that i could also do it the other way round. i can start to reconfig and then put the bad-sector-disk as UD and move it back. better to do the “move” via console or through simple copy &paste within a win10 vom (from mounted disk to mounted disk, so i can “see” easier what’s going on? Sent from my iPhone using Tapatalk

I am still not 100% sure whether I fully understand, but let me follow the next steps: * I can add an additional 6TB disk as unassigned disk (UD) * I can the move all files from the "corrupt" disk to the UD ("mv -r") * I can then pull the corrupt disk and put the UD into the old "corrupt" slot * Reconfigure and rebuild parity Makes sense?

Let me clarify - my parity rebuild has completed (the SMART was done after the rebuild created). Actually the error only occured during rebuild. If I were to move the file to an UD, this would take quite some hours. If I were to replace the drive, I would need to rebuild the parity again, then delete the disk and then copy it back. Also, how is rsync different from "mv -r"? I am not fully clear on the exact suggested next steps. Also, why would chkdsk or scandisk not identify corrupt files? I could then just delete the files and rebuild the disk using parity.

I was thinking of fixing or deleting the files within the bad sectors. Copying will take a lot longer and typically copying from corrupt disks turns difficult. So, I a trying to avoid it, but don't like the idea that I have some corrupt files and don't know what they are.

Got it. So, copying indeed may be preferred. Could chkdsk or a variance thereof also be an option?

Don't have the space per se, but could find a way. Would this give me better result than just replacing the disk?

Thanks. Let me do this later and get back to you. I don't mind if I lose a few files from this disk, but would be a pain if I lose the full disk.

Thanks. As you'd anticipated, the SMART failed. Please find attached. Please advice what to do next? Replace the drive and rebuild? tower-smart-20171114-0210.zip