Hi All,
I have been running Proxmox for years and it has always been very stable. For the most part I run Linux KVMs with only 1 Windows KVM.
The Windows KVM was Windows 7 Pro and had been running since the summer very stable. I decided to upgrade to Windows 10 Pro and since that time I would get a daily crash with the BSOD relating to PFL or memory issues. It wasn't a big issue since it was my Windows sandbox VM.
Thursday I decided to try an fix the issue I was having with it. I started doing to updates to Proxmox to make sure it was up to date and when it was updated I added the source list for Proxmox 4.1 and started the dist-upgrade.
My fault I did not read the migration instructions (until after) and this is when everything began to blow apart. By the end, it would not even boot. I pulled the drive and installed Proxmox 4.1 fresh from a CD on a new drive.
All of my VM storage is on iSCSI. However, my network/storage/VM config files were not backed up. I shutdown and added the original drive back in. When I booted up I realized I had a problem with the LVM names being the same so I ended up changing the names on the original drive from pve to pve_old. This way there was not any conflicts.
The bad part is this: when I mounted the original drive and went the the /etc/pve directory it is now empty. I have searched high and low for answers trying to figure out how to retrieve this data to no avail. The one bit of hope I have is this.
When I run:
You can see there are not any errors.
End of Part 1.
Thanks,
ProxMox
I have been running Proxmox for years and it has always been very stable. For the most part I run Linux KVMs with only 1 Windows KVM.
The Windows KVM was Windows 7 Pro and had been running since the summer very stable. I decided to upgrade to Windows 10 Pro and since that time I would get a daily crash with the BSOD relating to PFL or memory issues. It wasn't a big issue since it was my Windows sandbox VM.
Thursday I decided to try an fix the issue I was having with it. I started doing to updates to Proxmox to make sure it was up to date and when it was updated I added the source list for Proxmox 4.1 and started the dist-upgrade.
My fault I did not read the migration instructions (until after) and this is when everything began to blow apart. By the end, it would not even boot. I pulled the drive and installed Proxmox 4.1 fresh from a CD on a new drive.
All of my VM storage is on iSCSI. However, my network/storage/VM config files were not backed up. I shutdown and added the original drive back in. When I booted up I realized I had a problem with the LVM names being the same so I ended up changing the names on the original drive from pve to pve_old. This way there was not any conflicts.
The bad part is this: when I mounted the original drive and went the the /etc/pve directory it is now empty. I have searched high and low for answers trying to figure out how to retrieve this data to no avail. The one bit of hope I have is this.
When I run:
Code:
root@moxy002:~# fsck -f -v /dev/pve_old/root
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
52486 inodes used (0.83%, out of 6291456)
837 non-contiguous files (1.6%)
94 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 2949/17/0
747464 blocks used (2.97%, out of 25165824)
0 bad blocks
1 large file
38191 regular files
4164 directories
855 character device files
4530 block device files
3 fifos
8 links
4707 symbolic links (4530 fast symbolic links)
27 sockets
------------
52485 files
root@moxy002:~#End of Part 1.
Thanks,
ProxMox
