@olivierlambert Yep cool, thanks for your help
Latest posts made by simonk83
-
RE: Unable to display files in File Restore (failed to setup loop device)
-
RE: Unable to display files in File Restore (failed to setup loop device)
@olivierlambert Thanks for that. Well it seems fine in the main XO so I guess it's a problem with the community version, or at least my install of it (plus something to do with that single VM). Who maintains the community version?
-
RE: Unable to display files in File Restore (failed to setup loop device)
@olivierlambert Ah thanks, it has indeed expired. Is there any issue having both XO's running at the same time by the way?
-
RE: Unable to display files in File Restore (failed to setup loop device)
@olivierlambert Ohh I think I've already used it actually. I'll boot up the VM and check.
-
RE: Unable to display files in File Restore (failed to setup loop device)
@olivierlambert said in Unable to display files in File Restore (failed to setup loop device):
Okay, well We don't have a known issue with that on our support so I suppose it was "env" related
Aaaand now it's broken again haha. I'll try what you said and give it a go in XOA when I get a chance, see if it's the same there.
-
RE: Unable to display files in File Restore (failed to setup loop device)
@olivierlambert Well... I was just typing out a response about how I can select the smaller partition called Linux just fine but not the bigger partition called root, but when I clicked on root this time it loaded just fine....
Can't really explain that. I did reboot the VM again a bit ago, but I tried it straight after that and it still didn't work. Now a couple of hours later with no changes at my end it's fine. Odd!
-
RE: Unable to display files in File Restore (failed to setup loop device)
@olivierlambert One does, but that seems fine with the file restore...
-
RE: Unable to display files in File Restore (failed to setup loop device)
Sorry, quick question just because it'll probably save me hours of googling
The log says
failed to setup loop device for /dev/debian-vg/root
If I run lsblk -fs in the VM I get:
lsblk -fs NAME FSTYPE LABEL UUID MOUNTPOINT xvda1 ext2 728f3ff5-b4e4-4c49-8440-1afca3bedffb /boot └─xvda xvda2 └─xvda debian--vg-root ext4 e91dbbbe-5fc8-4631-8693-00fdea49cfcf / └─xvda5 LVM2_member 0IfZhR-hixh-FPMO-nvSc-EdMa-l3Fh-JCFyC3 └─xvda debian--vg-swap_1 swap 3e7fab19-8bb2-47da-bb16-a829010e1d51 [SWAP] └─xvda5 LVM2_member 0IfZhR-hixh-FPMO-nvSc-EdMa-l3Fh-JCFyC3 └─xvda
So is it that XO is trying to mount /dev/debian-vg/root but it's actually /dev/debian--vg/root ??
EDIT: Nope, never mind:
simon@dashboard:/dev/debian-vg$ ls root swap_1
Hmm.
EDIT2: If I run the same command in the VM I get:
simon@dashboard:/$ sudo mount --options=loop,ro --source=/dev/debian-vg/root --target=/tmp/tmp-751rBsQbj6YN1TI mount: mount point /tmp/tmp-751rBsQbj6YN1TI does not exist
So is XO failing to create that first? I guess not as the error would probably indicate such
-
RE: Unable to display files in File Restore (failed to setup loop device)
@olivierlambert Yep fair enough.
It's only that one VM so I guess it's that, I'll have a dig around.
-
RE: Can't increase RAM on VM through XO (Memory Constraint Violation)
@olivierlambert Yep for sure, and your support here is so good it's not a huge problem, but I more feel bad bothering you with stupid questions more than anything haha