Upgrade From 4.0 to 4.1

[matthew]

I had proxmox 4.0 running for couple months then did apt-get update then upgrade to move to 4.1 proxmox. This is on Supermicro hardware with 3 sata drives using ZFS to do a RAID1 type setup. Everything seemed fine until I decided to reboot. No longer have access to server. Any idea what would cause that? I have 2 hour drive to server or fee for remote hands to find out more info. Nothing important on this server yet fortunately.

 

[matthew]

Apparently its a Kernel panic.

From cropped photo I have received.

1.926083] ---[ end Kernel panic - not syncing: VFS: Unable to mount root f -------------
on unknown-block(0,0)

This is on a Proxmox 4.0 install after updating to 4.1 and rebooting. Its installed on three 4TB sata drives with ZFS all 3 in a RAID 1 fashion.

 

[wolfgang]

Hi,
do you make a apt-get dist-upgrade or only apt-get upgrade?
because if you make make only an upgrade the you do not get the latest kernel.

 

[matthew]

I did not do the the dist-upgrade. Could that cause the crash?

 

[aderumier]

apt-get upgrade only upgrade installed packages

apt-get dist-upgrade also install new packages from dependencies.

So you should always use dist-upgrade, or it could give you breakage like this.

 

[wolfgang]

Yes because you have now a new zfs package and an old kernel (exactly old zfs module).
And they are have to be the same version.

please use in future always dist-upgrade

 

[matthew]

I thought dist-upgrade was for moving from one major release to another. Would this only be necessary when moving from say 4.1 to 4.2 or something like that?

 

[spirit]

I thought dist-upgrade was for moving from one major release to another.

Well, that's true because debian/ubuntu never add new packages in a current release version.

Would this only be necessary when moving from say 4.1 to 4.2 or something like that?

Always use dist-upgrade with proxmox, because new packages can be included at any time.