4.4 > 5.2 upgrade > grub error: unknown filesystem

[fammed]

I upgraded one of my 4.x Proxmox servers to 5.2 today following the directions[1] below and have grub error after rebooting.

After the reboot this came up:
https ://imgur.com/a/kKXlHUj

and then after fsck'ing Grub is lost:
https ://imgur.com/a/cmAwRNc

Is this salvageable?

[1] https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0

 

[wolfgang]

Hi,

as the error message tells, you have to do an fs check.
Use a live CD like the PVE installer in debug mode or Ubuntu live image.
Then you can run an fs check.

 

[fammed]

Hello, I did run fsck from the busybox prompt. The picture is now attached at the first link:
https ://imgur.com/a/kKXlHUj

I rebooted after and now have the "unknown filesystem" grub error as shown in the second screenshot. Do you mean I should run fsck again from (from PVE installer boot cd)

Thank you

 

[janos]

Hi,

Please try to boot your server from a live CD (live ubuntu, systemrescuecd etc) and try to mount /.

 

[fammed]

Hi, Thanks.
I booted 5.2 into rescue but it cannot seem to find the boot disk (pics at link below) so tried 16.04 "rescue broken system". It got farther but still grub problems. Going to try and get grub installed on /sda again.

https ://imgur.com/a/WEbdggM

What is the "unknown filesystem" error about? Does this mean the Proxmox kernel doesn't have ext4 support in it, or is it grub that is lacking ext4? I tried doing `insmod ext4` at the grub prompt but got the same error

 

[Alwin]

In the last link it says, error: no such device: rpool. This more looks like from a ZFS installation. In our rescue mode, you can hit CRTL+D and after the wizard loads, hit Abort. This will drop you to a fully functional shell. There you should be able to repair your system.

 

[fammed]

gave up. reinstalled.
Thanks for the help anyway