[SOLVED] Upgraded pve disk to new nvme. Attempting to mount pve--OLD failing.

[flinte]

I got a new small nvme disk for my pve installation so I installed a fresh copy of PVE to it and I am attempting to mount pve--OLD to copy my /etc/pve directory to the new installation but I seem to be missing something. It tells me that XFS is an unknown filesystem yet xfs is installed and I cant modprobe it?

root@pve01:~# mount -t xfs /dev/mapper/pve--OLD--A3AAC529-root /mnt/restore/

mount: /mnt/restore: unknown filesystem type 'xfs'.

root@pve01:~# /sbin/modprobe xfs

modprobe: FATAL: Module xfs not found in directory /lib/modules/5.15.74-1-pve

root@pve01:~# apt install xfsprogs

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

xfsprogs is already the newest version (5.10.0-4).

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@pve01:~# find / -iname xfs

/usr/lib/modules/5.15.30-2-pve/kernel/fs/xfs

/usr/lib/modules/5.15.83-1-pve/kernel/fs/xfs

/usr/share/initramfs-tools/hooks/xfs

/usr/include/xfs

 

[Lukas Wagner]

Hi,

The xfs kernel modules should be part of the pve-kernel-5.15.* packages.

From the error message from modprobe it seems that you are currently running kernel '5.15.74-1-pve', but the find command below indicates that that version is not installed?

What does uname -r say? What is the output of apt list --installed | grep pve-kernel?
It appears that a newer kernel is installed, 5.15.83-1 - so a reboot to boot that newer kernel could fix the issue.

 

[flinte]

Ok but I have rebooted several times. The PVE iso on my usb drive I installed from was 7.2.1, the first thing I did was update and reboot. Now I am wondering if it is booting off the grub on the old hard drive.

root@pve01:~# uname -r
5.15.74-1-pve
root@pve01:~# apt list --installed | grep pve-kernel

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

pve-kernel-5.15.30-2-pve/stable,now 5.15.30-3 amd64 [installed]
pve-kernel-5.15.83-1-pve/stable,now 5.15.83-1 amd64 [installed,automatic]
pve-kernel-5.15/stable,now 7.3-1 all [installed]
pve-kernel-helper/stable,now 7.3-2 all [installed]
root@pve01:~# uptime
 08:33:25 up  9:35,  1 user,  load average: 0.00, 0.00, 0.00

 

[flinte]

I rebooted it again, fully powered it off then back on and watched it come online. It again booted kernel '5.15.74-1-pve'. I tried to update/upgrade again and it shows no updates available. Any recommendations for manually setting the new kernel as default in grub? Any clue why I am having to go through this manually as it has always been automagic in the past?

 

[flinte]

I found update-grub. Still no idea why I would need to do this manually.

oot@pve01:~# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.83-1-pve
Found initrd image: /boot/initrd.img-5.15.83-1-pve
Found linux image: /boot/vmlinuz-5.15.30-2-pve
Found initrd image: /boot/initrd.img-5.15.30-2-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
root@pve01:~# update-grub2
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.83-1-pve
Found initrd image: /boot/initrd.img-5.15.83-1-pve
Found linux image: /boot/vmlinuz-5.15.30-2-pve
Found initrd image: /boot/initrd.img-5.15.30-2-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done

 

[flinte]

and after reboot I have the same situation. Its not updating grub.

 

[flinte]

I rebooted again this time and I chose my other, assumedly old, pve install on the sata disk. It showed the .83 kernel as an option. So either I have the wrong one I am chosing as a default uefi boot option (which I dont think so) or the update-grub command is updating the wrong one. Anyway I have the new kernel version booted and the correct / on the nvme and pve--OLD on the sata are still showing. I can mount the pve--OLD now and I follower this procedure and it seems to have worked to migrate my PVE install to a new smaller nvme disk! Thank you for the help!

 

[Lukas Wagner]

Glad you could figure out the problem; and thanks for marking the thread as resolved!