Recent content by RafaelT

Yes! it did, and I did not realize it, given that "/" was mounted on the nvme as expected. Thanks a lot! All the other small hickups are gone, too.

root@pve:~# blkid /dev/disk/by-id/* /dev/disk/by-id/ata-WDC_WD20EFAX-68FB5N0_WD-WX11AC967XEN: PTUUID="eb9b1199-fad6-4a44-a7bc-d680020b6b48" PTTYPE="gpt" /dev/disk/by-id/ata-WDC_WD20EFAX-68FB5N0_WD-WX11AC967XEN-part1: PARTUUID="109f6187-e335-4aa3-8e64-d38c114f7d85"...

root@pve:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ├─sda1 8:1 0 1007K 0 part ├─sda2...

root@pve:~# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. E: /etc/kernel/proxmox-boot-uuids does not exist. root@pve:~# cat /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates...

I cannot think of a reason why I should have deleted this file on purpose. I didn't mess with the boot, until you pointed out about the missing installed kernel. I boot via legacy bios and am using the default filesystem. I cannot find the booted kernel anywhere and all I know about linux...

Now, I'm really off. I just don't get it. How can this be? apt-get remove apt-get remove pve-kernel-5.4.124-1.pve .... root@pve:~# pve-efiboot-tool refresh Running hook script 'proxmox-auto-removal'.. Running hook script 'zz-proxmox-boot'.. Re-executing...

I guess I made the problem worse by trying to reinstall the kernel... root@pve:/boot/grub# uname -a Linux pve 5.4.124-1-pve #1 SMP PVE 5.4.124-1 (Wed, 23 Jun 2021 13:47:09 +0200) x86_64 GNU/Linux root@pve:/boot/grub# ls -las /boot/vm* 14192 -rw-r--r-- 1 root root 14529568 Jul 2 16:22...

root@pve:~# modinfo dm_crypt modinfo: ERROR: Module alias dm_crypt not found.

Whoops, how the heck did that happen? Anyway, I rebooted the machine. Nothing really changed. I note that there is a kernel in ls -las /lib/modules/5.11.22-1-pve/ total 6144 4 drwxr-xr-x 4 root root 4096 Jul 13 15:02 . 4 drwxr-xr-x 3 root root 4096 Jul 13 15:02 .. 4...

I did root@pve:~# ls -las /lib/modules total 12 4 drwxr-xr-x 3 root root 4096 Jul 13 15:02 . 4 drwxr-xr-x 65 root root 4096 Jul 14 21:22 .. 4 drwxr-xr-x 4 root root 4096 Jul 13 15:02 5.11.22-1-pve root@pve:~# pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.4.124-1-pve) pve-manager: 7.0-8...

Hello, I want to recover the files in a vm I had on another disk. I already got the old local-lvm running, but I couldn't seem to get the data. It was an archlinux installation, using luks and lvm. What I got so far: root@pve:~# kpartx -a /dev/mapper/pve--OLD--1ED18B1F-vm--102--disk--0...

I would be happy, if I would be able to just recover the files on my old disk. I tried root@pve:~# kpartx -avr /dev/mapper/pve--OLD--1ED18B1F-vm--102--disk--0 pve--OLD--1ED18B1F-vm--102--disk--0p1 : 0 409600 /dev/mapper/pve--OLD--1ED18B1F-vm--102--disk--0 2048...

@Dunuin Ok das ist interessant, danke für die Info @Treptower Ähh Ich würde gerne meine Sackgasse verlassen. Die alte Platte habe Ich schon gebootet. Allerdings muss irgendwo stehen, das er das lvm device "pve" will: Egal von welcher Platte Ich boote aus dem Bios, er landed immer in der "neuen"...

Die müssten doch auch noch auf der Platte sein, oder? Ich habe allerdings schon versucht, das alte root zu mounten. root@pve:~# mkdir /mnt/oldroot root@pve:~# mount /dev/mapper/pve--OLD--1ED18B1F-root /mnt/oldroot/ root@pve:/# ls -las /mnt/oldroot/etc/pve/ total 8 4 drwxr-xr-x 2 root root...

I guess I'm a step closer: I managed to install a lvm via Datacenter->Storage and point it to the old disk. I just still don't get how to use vm-102-disk-0 as a VM