I noticed that my Linux MariaDB is not responding anymore and i noticed that the File ist still in an "Operation" when i was looking the the domains folder.

How do i get the File out of the Cache whitout Breaking my VM and DB. At the moment i cant start the VM and it just boots into the shell and not the image it self.

fix your share settings your telling the vdisk to live on a share that is also moving the file to another disk...

the share shouldn't have a second disk set:

 

You may need to stop all dockers. push mover to manual push the file and edit docker seting to put the vdisk1.imd on 1 disk at one location.
WebUI > Main > Move

Settings> Dockers:

didnt work, mover moved the file now and its gone but the VM still boots in shell.

OK, next edit the vms xml and look for where the vdisk img and its data path points too

 

As mover did its job as it supose to.

You have a share that point to 2 storage locations. and the data is moving that data between 2 locations.

Alos, a services may be pointed at 2 different location to have this error.

 

Regardless This is a misconfiguration.

as this should now be one one disk:

 

not 2

where do i find the XML ?

? by editing the vm
click the picture of the VM go to edit

at the top right click the toggle to show the xml

your looking for the tag disk and need to fix the path to the vdis1.img

 

general edit will go to form view:

IN this case as example my path is system vmachines the name of the vm the vdisk.img

 

as mover moved the file and its not at that location, you need to explicit have mover set up as 1 vdisk.img

remove the share setting to that vm path so the vdisk exsit and runs form 1 disk

and edit/fix the vm xml to point to the correct vdisk.img as a direct path.
 

you need to edit your domain share and eithe have the data set to cache or disk1 per your setup.

 

^as you have this under domains configured... as i'm not sure which way you pointed it... but mover will move the file from 1 location to the next.

you need the vm off and have mover run to move the data per its current configuration.

(this is to rescue the VM vdisk image as it currently split in 2 disk locations...) otherwise that VM is now dead ...

as atm this should only exist either on disk 1 or cahce per your previous picture data...

To fix so this doesn't happen again...

Then edit the domain share and ONLY HAVE Primary storage set.

Now that mover has it in one location and the domain share is fixed, the vidsk as 1 file is located somewhere that need fixed in the VMs XML.

(not enoth info to assit. need picture of your share tab...)

 

As Normally vms are stored on the cache disk.

You shouldn't use the fuse system /mnt/user it should be a direct path /mnt/disk1/domains etc... when fixing hte vms xml to restore where teh vdisk1.img is located...

Ether im Stupid or the VM is just broken, i set the path tho the Disk1 and it still dont work.

I need a picture from your shares tab:

 

example, as the storage column has the data I need.

 

I need a picture of your file manager of /mnt/user/domains/Maradb as in first picture to confirm file location

Edited January 8, 20251 yr by bmartino1
typo

 Im just gonna declare it as Dead, but stil thank you for explaining and your help.

 

Correct now that file manager shows the vidsk in 1 location and the vm xml is pointed to that vdisk1 image file. if the VM done't boot the vdisk image is corupted and will not funtion.

editing the xml location to point directly to the VMS vdisk at this stage should work. the direct path should be /mnt/disk1/domains/maradb/vdksik.img <corect any spelling and actual path as it is case sensitve..)

 

as teh vdisk was broken into 2 seperat parts beforem coming one again new data old data to the vidsk.img is most likly coreupted for tryign to move or hold /replace data that is not seen at the host level and in the virtual level inteh Hard disk the mover replacing the file overwrote large section of the virtual disk...

 

I'm not aware of any other forms of recvoery at that stage. as the vdisk should now be at host disk1 pathing

if domain share is set primary storage to disk 1 then with out editing the VM xml the vdisk is loaded correctly

 

as the path /mnt/user/domains is hard/symlinked to the disk set under shares.

 

as domains should now be fixed you may have to recreate or restroe the DB via a sql backup if you made one.

outside of snapshots/vm plugin. why a vm of this when a docker would runn faster and smother.?

 

I would direct you to use Mariadb docker:

 

and set a path for the physical mariadb data on unraid...

i had a VM becaus the Docker had some errors i cant explain and just wont work so i just set up a Linux VM and installed MariaDB ther and it worked flawles at second 1.

Since this was only for Nextcloud its not a big loss, i wanted to replace this App anyways whit something else more Performant that isnt slow as hell.

And the VM still wont boot after setting the new path, i just call it a day here. Thanks four your Time and Help m8.