Hello and thanks for looking.
I've been struggling to understand what has happened to my system after what I would consider a fairly straightforward attempt at cloning my drive to a new smaller drive with Clonezilla. From my perspective, I did nothing to the original Proxmox drive and yet somehow ended up in a state where it will not boot and I get the mentioned error.
To give some context, what I originally did was:
I'm hesitant to take many troubleshooting steps in similar posts since I'm already in a state where I don't understand how I got here (I'm quite clear that I never did anything to the boot drive other than the clone process) and I don't want to make a bad situation worse by further fiddling with things I don't understand.
My immediate goal is to just get the M.2 NVME back-up and running as it originally did if at all possible. I had a fairly large amount of VMs/Containers setup and really can't stand the thought of having to set them up from scratch again. I also had a script that I was able to cobble together to auto mount my Unraid VM so that I could share it with the other VMs and I can no longer find the information on how I did it or even what it was called (something like a Proxmox system script or similar?).
Longer term, I'd still like to get it running on the new and smaller PCI-E NVME, which it seems like the best way to do might be via backing-up the VM's and restoring them one-by-one and also trying to find and copy that custom script I made to auto mount my Unraid setup. That says if anyone has any idea on how I might be able to do this with a clone type operation, that would be incredible.
I would note that I am not super handy with all of this and have been trying to stumble my way through a lot of my setup, so please bear with ignorance as I intentionally went in over my head as a way to better learn all of this as I transition away from Windows completely.
Any help or insight you all could provide would be greatly appreciated. Thank you.
I've been struggling to understand what has happened to my system after what I would consider a fairly straightforward attempt at cloning my drive to a new smaller drive with Clonezilla. From my perspective, I did nothing to the original Proxmox drive and yet somehow ended up in a state where it will not boot and I get the mentioned error.
To give some context, what I originally did was:
- Install new smaller PCI-E NVME
- Boot to Clonezilla from USB
- Use some custom configuration to try to clone main M.2 to smaller PCI-E NVME
- Clone appeared to complete but was unsuccessful with some errors at the end presumably due to the size different
- Attempt to boot to old M.2
- Boot was successful and PvE was accessible via web, however none of my existing VMs/Containers were there (it was as though it was a fresh install)
- Tried booting between the old M.2 and new PCI-E and both seemed to boot in the above state and looked the same (which my mind says should not be possible since the clone failed)
- Finally boot back to the M.2 and tried to delete the partitions on the PCI-E NVME from within the PvE Storage web interface but kept getting some error about something being in use or something along those lines (again not sure how this was possible since it was a failed clone)
- Eventually managed to delete some of the partitions, but not all
- Eventually just pulled the PCI-E NVME out altogether
Found volume group "pve-OLD-00E718C8" using metadata type lum2 21 logical volume(s) in volume group "pve-OLD-00E718C8" now active Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline)Check rootdelay= (did the system wait long enough?)- Missing modules (cat /proc/modules; ls /deu)ALERT! /dev/mapper/pve-root does not exist. Dropping to a shell!BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash) Enter 'help' for a list of built-in commands.I'm hesitant to take many troubleshooting steps in similar posts since I'm already in a state where I don't understand how I got here (I'm quite clear that I never did anything to the boot drive other than the clone process) and I don't want to make a bad situation worse by further fiddling with things I don't understand.
My immediate goal is to just get the M.2 NVME back-up and running as it originally did if at all possible. I had a fairly large amount of VMs/Containers setup and really can't stand the thought of having to set them up from scratch again. I also had a script that I was able to cobble together to auto mount my Unraid VM so that I could share it with the other VMs and I can no longer find the information on how I did it or even what it was called (something like a Proxmox system script or similar?).
Longer term, I'd still like to get it running on the new and smaller PCI-E NVME, which it seems like the best way to do might be via backing-up the VM's and restoring them one-by-one and also trying to find and copy that custom script I made to auto mount my Unraid setup. That says if anyone has any idea on how I might be able to do this with a clone type operation, that would be incredible.
I would note that I am not super handy with all of this and have been trying to stumble my way through a lot of my setup, so please bear with ignorance as I intentionally went in over my head as a way to better learn all of this as I transition away from Windows completely.
Any help or insight you all could provide would be greatly appreciated. Thank you.