Tom help me!

RKfreestyler

New Member
Apr 2, 2017
17
0
1
34
Hello Tom!

I have a big problem.

A partition was removed from a VM.

I restored it but i cannot seem to mount it back to the VM?

How do i do that, i only get "thats not a mount point"

I tried Mount /dev/pve/vm-105-disk-1 /105
Mount /dev/pve/vm-105-disk-1 /XXXXXXX6(machine name)
Mount /dev/pve/vm-105-disk-1 /pve/data
And more
 
You subject is a bit weird. Better choose a description of your problem.

Please post your vm config:

> qm config VMID

and your storage:

> cat /etc/pve/storage.cfg

and the location of your restored disk.
 
  • Like
Reactions: Dan Nicolae
Sure thing!

Qfa2xKH

3wlpWLK

Dont mind SSD2 N2 its from another node
 
You subject is a bit weird. Better choose a description of your problem.

Please post your vm config:

> qm config VMID

and your storage:

> cat /etc/pve/storage.cfg

and the location of your restored disk.
thre u go
 
Your VM config shows NO disk defined (only cdrom), so of course you can't mount it (if you boot from that cdrom, otherwise you don't even boot). Sorry but from the first comments you wrote seems that you don't really have a clue of how things works (no offence), so is very hard figure out how to help you at this point.
 
Your VM config shows NO disk defined (only cdrom), so of course you can't mount it (if you boot from that cdrom, otherwise you don't even boot). Sorry but from the first comments you wrote seems that you don't really have a clue of how things works (no offence), so is very hard figure out how to help you at this point.
Its a VHD not a silly ISO.
A VHD cant be booted from a CD-rom or do you put your harddisks in you CD at home XD
 
Its a VHD not a silly ISO.
A VHD cant be booted from a CD-rom or do you put your harddisks in you CD at home XD
In your config you have boot disk as sata0, but there is no sata0 entry as storage, so probably you boot with cdrom as fallback sequence.
So the only storage defined is ide2, that points to a ubuntu iso. Do you mean that the ubuntu iso is your VHD?
If so, just check if the /var/lib/vz/ubuntu-16.4...iso is present, and with rw (read write) attribute.
If so, once you boot and you are in the vm, the command "lsblk" will show you what the vm sees as devices/partitions.
Create a mountpoint and mount (mkdir ...) the desired partition, i.e.
# mkdir /mnt/mymountpoint
# mount /dev/sda2 /mnt/mymountpoint
if is ok for you, add a fstab entry (with proper syntax) to have it mounted automatically at boot
Btw, please copy and paste as text not as image, is much easier point out the interesting part. You can use the 'code' tags to have it properly formatted.
 
In your config you have boot disk as sata0, but there is no sata0 entry as storage, so probably you boot with cdrom as fallback sequence.
So the only storage defined is ide2, that points to a ubuntu iso. Do you mean that the ubuntu iso is your VHD?
If so, just check if the /var/lib/vz/ubuntu-16.4...iso is present, and with rw (read write) attribute.
If so, once you boot and you are in the vm, the command "lsblk" will show you what the vm sees as devices/partitions.
Create a mountpoint and mount (mkdir ...) the desired partition, i.e.
# mkdir /mnt/mymountpoint
# mount /dev/sda2 /mnt/mymountpoint
if is ok for you, add a fstab entry (with proper syntax) to have it mounted automatically at boot
Btw, please copy and paste as text not as image, is much easier point out the interesting part. You can use the 'code' tags to have it properly formatted.
No, The VHD was lost. I have now recoverd it after alot of messign around but it wont show in the VM.
How can i get the VHD to be mounted to that exact VM?
 
No, The VHD was lost. I have now recoverd it after alot of messign around but it wont show in the VM.
How can i get the VHD to be mounted to that exact VM?
I'm just shooting in the dark.
It's really hard help you since you provide confusing and partial info. I've googlead a bit, and I've found in this forum that VHD are first converted into something that QEMU can understand, like a qcow2 file.
If you use one of your 2 file based storage (local or ss2n2), you have to recreate the VM from scratch with the disk on one of the above storage, then replace the newly created file with your converted VHD.
BUT
When you say "won't show in the VM" I thught that you were running the VM and INSIDE it you did not see it.
Now I think you mean that does not show in the GUI config. You say you have "recovered it", so it's basically a fact of editing the vm config file (i.e. 100.conf) and add a line that points to that storage/file_or_block_device.
like, just as examples of different storage type / location / controller have a line like
Code:
scsi0: local:101/vm-101-disk-1.qcow2,size=8G
or
ide0: local-lvm:vm-100-disk-1,size=35G
OMHO You should experiment a little in a different server, become more familiar with Proxmox and it's storage models, and then try to fix your problem.
Hope the above helps in guiding your search the right solution for you.
 
Hello!

1.one cannot run a VM on a disk that is not mounted.(basic understanding of how a computer works, therefour i did not mention it). im am sorry if i took something for granted.
2.i have not edited the VM config yet.

3. "file (i.e. 100.conf) and add a line that points to that storage/file_or_block_device.
like, just as examples of different storage type / location / controller have a line like" this is really helpful if you could say were this file location is?
(this could be the solution i was looking for :D )
 
I'm just shooting in the dark.
It's really hard help you since you provide confusing and partial info. I've googlead a bit, and I've found in this forum that VHD are first converted into something that QEMU can understand, like a qcow2 file.
If you use one of your 2 file based storage (local or ss2n2), you have to recreate the VM from scratch with the disk on one of the above storage, then replace the newly created file with your converted VHD.
BUT
When you say "won't show in the VM" I thught that you were running the VM and INSIDE it you did not see it.
Now I think you mean that does not show in the GUI config. You say you have "recovered it", so it's basically a fact of editing the vm config file (i.e. 100.conf) and add a line that points to that storage/file_or_block_device.
like, just as examples of different storage type / location / controller have a line like
Code:
scsi0: local:101/vm-101-disk-1.qcow2,size=8G
or
ide0: local-lvm:vm-100-disk-1,size=35G
OMHO You should experiment a little in a different server, become more familiar with Proxmox and it's storage models, and then try to fix your problem.
Hope the above helps in guiding your search the right solution for you.
I will be werry gratefull if this works :D
 
Hello!

1.one cannot run a VM on a disk that is not mounted.(basic understanding of how a computer works, therefour i did not mention it). im am sorry if i took something for granted.
2.i have not edited the VM config yet.
You don't "mount" the virtual disks in Proxmox (like seems you were trying to do in your first post). You have to have the virtual disk available in proxmox (different storage technology so different ways to have that) and "link" it to the vm in the vmid.conf file, so QEMU/KVM sees them as block device and, INSIDE the VM (= by the OS of the VM) mount them and use them.
The config file you showed in the picture has no reference to the "virtual" disks that the VM should use, you don't tell us in what storage it was, and when you state "A partition was removed from a VM" in your first post is very different from what you really mean, AFAIU... maybe you meant that a virtual disk was deleted from the vm config? Deleted from proxmox itself (i.e. the .qcow2 file)? How (if just in the config, through GUI it was listed in "unused" section of the config itself, easy to re-link)?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!