Hi All, wow what a 24 hour period I've had. I'm looking for some help and going to try and give as much information as I can.
I am not a linux or proxmox power user by any means. I do this for fun and when I get the urge to do learning.
Last night I was trying to get a new CentOS 7 minimal image to mount one of my NFS shares that OMV was providing.
(this is issue number 1, but low priority)
I installed nfs-utils on the client and ran
I decided to update omv and then realized it was running low on space I gave for omv OS.
So I shut down the VM. Went to the proxmox gui, went into the hardware section of my vm and highlighted the sata0 local-lvm:vm-101-disk-0 and increased the size 1gig. This was more to just stop the low disk space alerts.
When I went to start the VM it gave me the following boot loop.
(problem 2, high priority)
Thinking that I screwed my self. I detached that vm disk and added a new one with 8GB to do a fresh install of OMV.
I got to the part where it tells me to select the drive and i select the one that is not my pass through drive.
I then get an error
Last I check omv only took 2gig
I did some googling and it apears newer version of omv require the same amount of swap as ram or something... I don't know how to do that with out build a whole new VM.
I gave up on trying to reinstall the omv for the time being and thooght I'll just pass the disk that is used for my NAS storage to a different VM so I can atleast back it up.
I passed that disk through to a ubuntu vm i use for a dedicated gaming server.
(problem 3, highest priority)
When i went to start the vm. I got the same boot loop error as before.
I had been prepping to remove this VM, but I needed one last look through it to make sure I got all my scripts and configs backed up... So being able to boot this VM again would be great.
I tried to run a
I'm having a really hard time understanding why adding the pass through drive to the 2nd VM screwed anything up with the boot drive.
So Now I have an 8TB external drive I picked up. I'd been planning to start backing up my NAS for a while anyway, but this just tells me I really need to start.
Issue list:
I will be more than willing to answer questions as to other troubleshooting I have done or run any diagnostic commands I can. I've spent 5 to 6 hours of the past 24 trying to get these resolved, I don't want it to seem like I've got a problem and put no effort into fixing it.
Any assistance on any of the issues would be appreciated.
Thank you!
I am not a linux or proxmox power user by any means. I do this for fun and when I get the urge to do learning.
Code:
My Setup:
R710
ProxMox 5.4-13
2 raid arrays
250gb raid 1 - proxmox runs here. I believe the lvm and lxc images are here too.
2tb raid 1 - This was passedthrough to my omv vm
4 - lxc containers
103
105
106
107
4 - VMs
100
101
102
104
DNS/DHCP is provided by my ERX router.
This set up has been working for about two years now.
Last night I was trying to get a new CentOS 7 minimal image to mount one of my NFS shares that OMV was providing.
(this is issue number 1, but low priority)
I installed nfs-utils on the client and ran
sudo mount -t nfs -vvvv x.x.x.x:/export/serverstuff /home/nick/scripts
and continually got operation not permitted
, but i could see on omv the client was being authenticated.I decided to update omv and then realized it was running low on space I gave for omv OS.
So I shut down the VM. Went to the proxmox gui, went into the hardware section of my vm and highlighted the sata0 local-lvm:vm-101-disk-0 and increased the size 1gig. This was more to just stop the low disk space alerts.
When I went to start the VM it gave me the following boot loop.
(problem 2, high priority)
Machine UUID xxxxxxxxxx
Booting from Hard Disk...
Boot failed: not a bootable disk
Thinking that I screwed my self. I detached that vm disk and added a new one with 8GB to do a fresh install of OMV.
I got to the part where it tells me to select the drive and i select the one that is not my pass through drive.
I then get an error
Failed to partition the selected disk. This probably happened because the selected disk or freespace is too small to be automatically partitioned.
Last I check omv only took 2gig
I did some googling and it apears newer version of omv require the same amount of swap as ram or something... I don't know how to do that with out build a whole new VM.
I gave up on trying to reinstall the omv for the time being and thooght I'll just pass the disk that is used for my NAS storage to a different VM so I can atleast back it up.
I passed that disk through to a ubuntu vm i use for a dedicated gaming server.
(problem 3, highest priority)
When i went to start the vm. I got the same boot loop error as before.
I had been prepping to remove this VM, but I needed one last look through it to make sure I got all my scripts and configs backed up... So being able to boot this VM again would be great.
I tried to run a
qemu-img check vm-100-disk-1
and it saysqemu-img: Could not open 'vm-100-disk-1': Could not open 'vm-100-disk-1': No such file or directory.
I'll be honest, i'm not sure if qemu-img is the correct diag tool here..I'm having a really hard time understanding why adding the pass through drive to the 2nd VM screwed anything up with the boot drive.
So Now I have an 8TB external drive I picked up. I'd been planning to start backing up my NAS for a while anyway, but this just tells me I really need to start.
Issue list:
- My dedicated game server VM wont boot, says "booting from hard disk. Boot failed: not a bootable disk."
- OMV server has the same error as above
- If I can't get omv or the vm back how do I get the data of my disk and put it on my usb hdd. (can i do that from proxmox somehow?)
I will be more than willing to answer questions as to other troubleshooting I have done or run any diagnostic commands I can. I've spent 5 to 6 hours of the past 24 trying to get these resolved, I don't want it to seem like I've got a problem and put no effort into fixing it.
Any assistance on any of the issues would be appreciated.
Thank you!