dolivas27

I have updated to the latest and still have the errors anything else I can check?

@Djoss Thanks for the update very much appreciated. All seems to be work well now..... Thanks Again, Dean

Thanks guys this also fixed it for me. Very much appreciated......

Ok well that didn't work so at this point I think I am screwed. Everything I backup on the disk I can read but none of the images are readable there weird thing is all the image show as small size like the one I am really working on only shows a size of 39.8MB Is the problem because it was a Btrfs files system and windows has no idea how to tell the true size? I should have not wiped the cache drives but I was in such a panic to get my Data back and the system up and running. I was able to get everything else off the cache drive but none of the VM's work and I can't read anything from the images.

Ok I have tried to add the img as a second drive on a new Win10 VM I have built but it does not show up and when I got to the diskmgmt in windows it wants me to initialize the disk. I did not and did a rescan of the disks and it does show the disk now see the picture. But when I click on the F drive, I get this message and can not access the files or anything on the disk. It shows the file system as RAW? All I need is a few files off the image I did not have them backed up (BONE HEAD MOVE ON MY PARTS) Any thoughts? Thanks, Dean

So no one can tell me how to mount this image to retrieve my data?

That is kinda what I did. 1. I created a new VM and used the old vdisk.img 2. The setting you see are from the new VM I created I am not sure what the old setting were. 3. This the problem the VM was created a long time ago and I don't remember or have the Machine and bios setting I do know it was using OVMF. Is there any way to get the machine info from the libvirt.img

Ok to be clear the cache pool has been reformatted after I was able to get the files (Or so I thought)

Ok guys and Gals I need some help…. I have been running UNRAID for over 5 years maybe more and have never had a problem the other day I upgraded the server to 32GBb of memory from 16GB. Well something went horribly wrong and I lost my cache drive. I have two 500GB SSD for the cache pool upon rebooting the system after adding the ram one of the cache drive had an error so after looking at it, I might have bumped a cable when installing the ram. So, after fixing what I thought was the issue I re-added the drive back to the cache pool and that is where the real problem started long store short it wiped the drive and I lost the ability to start the cache pool. So, I was able to mount one of the drives and backup the data at this point I need to reinstall all the dockers and VM and I guess I have no choice but to start over because nothing seem to work right on a few of the dockers that I have tried I will deal with that. At this point I have a VM disk which I desperately need to get the files off of it. It was a VM of my ScreenConnect Server and has all of my client’s remote sessions on it. I cannot get the VM to startup is there a way to just mount the VM so I can get the files off of it? I have tried to attach it to and new running Windows 10 VM as a second disk but I can not read the image PLEASE HELP SO STREESED RIGHT NOW….. Here is what the XML files looks like. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10 SC</name> <uuid>931b6586-25f8-34fb-7fa0-89e110fc8c69</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/931b6586-25f8-34fb-7fa0-89e110fc8c69_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Test/vdisks/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.141-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:c9:ab:fe'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Thanks, Dean

Ok I figured it out I needed to change the server name in the letsencrypt proxy-config file. Everything is now working the way it was. I am still getting this error when I log in to the controller through the proxy, I am sure it’s not the container. If anyone could lead me in the right direct to solve the problem, I would appreciate it. This is the error that always pops up on the controller while I connected remotely. WebSocket connection error This is what the console in chrome shows for the error, but I am not sure on what to look at? WebSocket connection to 'wss://***.*****.com/wss/s/default/events' failed: Error during WebSocket handshake: Unexpected response code: 400 O.open @ components.v5.10.17.1.js:167 I blocked out the address it does not show ***.*****.com but the correct address. Thanks for the help, Dean

First thanks for the update much appreciated. I noticed that port 10001 is set to TCP should it not be UDP? Also, I have this error when trying to connect the controller from my external host name? It was working be for and if I stop the new controller and fire up the old controller it connects just fine any ideas where to look? 502 Bad Gateway nginx/1.14.2 Thanks, Dean

Ya I fully understand that and have seen it before PLEASE don’t stop because of a few that have no patience. Thanks again…..👍

It’s time to back off and thank them for what they do for us!!!! This is starting to get ridiculous if don’t like the way things are right now roll your own…. CHBMB I just wanted to say thanks for doing your best at keeping this up to date. Your efforts are greatly applicated.

Yes mine had the extra unify xml file so I compared the two and the one with the (1) was the correct xml so I removed the other one and renamed the xm1 (1) to just xml and restarted the docker and all it perfect now. It also fixed the problem with the network changing from proxynet to bridge. Thank you for leading me in the right direction to fix the problem I also found and problem with my plex docker having the same problem..... 👍

Same problem I am having I reported it on the 9th and have not heard anything. Thanks for confirming I was not the only one with the problem for now I am just ignoring the update ready.

First thanks for the excellent Docker! I have a few questions I have it all setup and running well then, a few days ago the docker reported that an update was ready, so I told it to update and then when I tried to access the Web UI is says we do not support upgrading from version 5.9.29? As you can tell I am running what is considered the unstable version so why is it telling me there an update? If I edit it and add this back to the Docker it re-installs the 5.9.29 and all is well except it still says an update is available? One last question I am adding this line to the Docker under the Repository line linuxserver/unifi:unstable it seems to me that it is ignoring the unstable tag am I putting it in the wrong location?

+1