I thought maybe something was in RAM too so I rebooted the unRAID server, nope, still have the two Windows 10 folders with the two vdisk images. After the reboot I tried to start up the VM again, and it booted, but into Windows setup again. 

 

Yes, all my files should be on the SSD which is an unassigned disk.

Do you have something in your go file which is creating /mnt/windowsVM and then mounting something there?

I don't know, how can I check?

I thought maybe something was in RAM too so I rebooted the unRAID server, nope, still have the two Windows 10 folders with the two vdisk images. After the reboot I tried to start up the VM again, and it booted, but into Windows setup again. 

 

Yes, all my files should be on the SSD which is an unassigned disk.

Your test wasn't really a fair test.  Do this:

 

Settings - libvirt - disable (this will disable all the VMs)

Settings - docker - disable

Reboot

Then

ls /mnt

 

That'll give us the info if docker / libvirt is automatically recreating the folders in /mnt or if UD is actually mounting them there.  If those folders still exist in /mnt then the xml is incorrect as the SSD is mounted in /mnt/windowsVM.  If the folders don't exist then it *appears* that somehow you inadvertently deleted the vdisks from the SSD

 

I don't know how to do this from the gui >Settings - libvirt - disable (this will disable all the VMs)

So what I did was went into settings, VM Manager and disabled VM's.

I then went into settings Docker and disabled the docker.

I will now reboot and post the results of ls /mnt

I don't know how to do this from the gui >Settings - libvirt - disable (this will disable all the VMs)

So what I did was went into settings, VM Manager and disabled VM's.

I then went into settings Docker and disabled the docker.

I will now reboot and post the results of ls /mnt

Same thing.  Not at the machine, but I swear I remember the settings icon to be libvirt and not vm manager (running 6.3 though)  Could be completely out to lunch (usually am)

So from the console, this is the output of ls/ mnt

 

 

root@Backup:~# ls /mnt
disk1/  disk2/  disk3/  disks/  user/
root@Backup:~# 

 

Unfortunately when I go into the windowsVM folder I have: Drivers/ ISO/ WIndows\ 10/ Windows\ 10/

 

And when I browse into my SSD, I still see the two Windows 10 folders with the two disk image files.

 

Should I open a support case with Lime-Tech?

In linux WIndows is different from Windows

I know, how can I delete the wrong one, or would you guys advise some other course of action? Oddly enough I was surprised to see that my docker was enabled on this server, I don't recall enabling it and can't imagine why I would of as I don't run any dockers on this server.

So from the console, this is the output of ls/ mnt

 

 

root@Backup:~# ls /mnt
disk1/  disk2/  disk3/  disks/  user/
root@Backup:~# 

 

Unfortunately when I go into the windowsVM folder I have: Drivers/ ISO/ WIndows\ 10/ Windows\ 10/

 

And when I browse into my SSD, I still see the two Windows 10 folders with the two disk image files.

 

Should I open a support case with Lime-Tech?

But here's where we stand

 

Either a VM or docker is creating the /mnt/windowsVM folder

 

You've got 2 windows 10 folders within /mnt/disks.  One named WIndows and Windows.  Only way to resolve that is via the command line.

 

Net result is that dealing with this stuff via the forum is possible, but very time consuming and aggravating for both yourself and people here as we bounce back and forth and things sometimes get lost in translation.

 

A support thing via Teamviewer either done by Limetech or a user here will probably be the fastest way of solving everything with the least amount of headaches for all involved.  I'd do it myself, but wouldn't be able to do it until Sunday though.  Maybe LT or someone else can get you up and running prior to that.

 

I don't mind paying for a support incident with Lime-Tech but I'll wait a little first and see if someone can suggest a fix, I'm relatively competent at the command line with some guidance.

 

Thanks for your help guys!

I don't mind paying for a support incident with Lime-Tech but I'll wait a little first and see if someone can suggest a fix, I'm relatively competent at the command line with some guidance.

 

Thanks for your help guys!

I hope I didn't come off as don't want to help you here.  Just that you brought up the subject...

Thanks guys, figured it out on my own, via SSH, I deleted the WIndows\ 10 folder and modified the path in the settings of the VM which I hadn't noticed were set to WIndows, once I did that the VM booted and its all good.

 

Thanks again for all your help, couldn't of fixed it with you!

 

AM

Not at all Squid, no worries.