Hi,

 

My windows server VM is not showing up anymore. I had it installed on an SSD which was not part of the array. The disk still mounts, it still shows the relevant data (or so I think) but the VM won't show up in the Main tab. 

I lost my dockers at the same time but was able to restore with a "my-template". 

However I don't know how to do a similar restore for my VM. 

Could anybody please point me in the right direction? What additional information do you guys need me to post?

I'm on 6.2.4

The fact that you lost your dockers at the same time is a clue. Was your docker.img on the same disk as your VMs? Perhaps it's corrupted. Can you run a file system check on it? You might post your diagnostics too (Tools -> Diagnostics).

Hi. My docker.img is on disk 2 of my array.  My VM is on a separate SSD. Or am I missing your point and should look for something else?

I'll post my diagnostics as soon as I get to a proper computer again (currently only on my phone). 

 

Thanks,

Simon

It's common practice to store VMs and the docker.img on the same storage, typically an SSD cache disk or pool. In the absence of your diagnostics I made the assumption that your setup was similar.

VMs XMLs are stored on the libvirt.img, you're probably using a new blank one, you can set it's location on Settings -> VM Manager -> Libvirt storage location

 

ETA: another possibility is the current libvirt image being corrupt.

Edited February 22, 20179 yr by johnnie.black

Hi,

 

please find the docker.cfg attached. Anything else I can post to help?

 

@johnnie.black Sorry, I'm not quite following. My libvirt storage location is set to /mnt/user/system/libvirt/libvirt.img

You mean this has changed to a blank one and needs to be re-directed? How do I find out where to direct it to? If so how could I do that? Libvirt storage location is not editable.

 

I really appreciate your help.

docker.cfg

 

EDIT: Duh!!! Stopped the array, made the storage location editable. Magic! (I feel pretty stupid...)

Still: where to direct it to know? The vdisk1.img on my SSD? I don't want to ruin anything by trying anything stupid, as I'm still hoping to retrieve my VM as it was, and not having to start from scratch again.

 

Edited February 23, 20179 yr by hometownwesty

28 minutes ago, hometownwesty said:

Sorry, I'm not quite following. My libvirt storage location is set to /mnt/user/system/libvirt/libvirt.img

You mean this has changed to a blank one and needs to be re-directed? How do I find out where to direct it to? If so how could I do that? Libvirt storage location is not editable.

 

If for example it was on your cache and you started the array without it a new one would be created on disk1.

You can only edit the location after stopping the VM manager.

To check if there is more than one use:

 

find /mnt -name libvirt.img

 

Another option is the image being corrupt, to check that we'd need to see your diagnostics.

So I found another libvirt on my disk2 (where my dockers were as well) and redirected my vm path accordingly. 

Still my VM doesn't show up (restarted and rebooted). 

What else can I do?

What parts of my diagnostics do you need and what format? I attached the dockers diagnostics above, but that doesn't seem to help you understanding what my problem is. And as you can see from my posts, I'm really dependent on your kind help

2 hours ago, hometownwesty said:

What parts of my diagnostics do you need and what format?

 

Tools -> Diagnostics

 

PS: it's normal for find to show 2 paths for libvirt, e.g., one in /mnt/user and the other in /mnt/disk, it's the same file, if there was another in /mnt/cache then there would be a duplicate.

 

Please find everything attached that Diagnostics spit out.

Thanks

disk.cfg

docker.cfg

domain.cfg

go

ident.cfg

network.cfg

share.cfg

smart-one.cfg

smb-extra.conf

super.dat

docker.log

libvirt

syslog.txt

no qemu log files

√---------h.cfg

a-----a.cfg

B-----s.cfg

D-------s.cfg

d-----s.cfg

i--s.cfg

M----n.cfg

s----m.cfg

S---h.cfg

S---n.cfg

V------n.cfg

v----s.cfg

Samsung_SSD_840_EVO_250GB_S1DBNSAF275424J-20170224-1651.txt

SanDisk_Ultra_Fit_4C530001080807123530-0-0-20170224-1651.txt

ST6000DX000-1H217Z_Z4D00JK6-20170224-1651.txt

ST3320613AS_5SZ036LH-20170224-1651.txt

WDC_WD20EARS-00MVWB0_WD-WMAZA1016855-20170224-1651.txt

WDC_WD60EFRX-68L0BN1_WD-WX41D95PA7VX-20170224-1651.txt

cmdline.txt

df.txt

ethtool.txt

folders.txt

ifconfig.txt

iommu_groups.txt

lsmod.txt

lsof.txt

lspci.txt

lsscsi.txt

memory.txt

ps.txt

vars.txt

unRAID-6.2.4.txt

Next time post just the diagnostics.zip.

 

Don't think you mentioned your cache is unmountable, the original libvirt.img could be there.

No, didn't mention that, as this was new. I just did a reboot, and now my installation key is missing and can currently not be installed. I'm getting an error message. This is the second time recently, and I'm fed up right now. I think I will take a break for today.

Thanks for your enduring attempts to help me.

A break can sometimes be a good idea.

 

Cache is reporting that the missing disk exceeds the redundancy limit, this means your pool was not raid1 (totally or partially) and can't mount without the missing disk, if you still have it just add it back to the pool, if you want to remove it you'll need to follow the procedure on the FAQ.

Edited February 24, 20179 yr by johnnie.black

I fixed the cache issue and re/ran diagnostics. See attachment.

datenfarm-diagnostics-20170225-0911.zip

Run the find command again to see if there's a libvirt.img on your cache pool:

 

find /mnt -name libvirt.img

I found three libvirts. user, user0 and disk2. None of them worked. I'm very close to just setting everything up from scratch again. 

Edited February 25, 20179 yr by hometownwesty

In this case they are all the same, was hoping for one on /mnt/cache.

 

You can just create a new VM and use an existent vdisk, as long as you use the same settings it should work.