It works fine. I restored the VM from a backup and I changed the procedure a little bit.
# fdisk -l /dev/xvda Disk /dev/xvda: 14 GiB, 15032385536 bytes, 29360128 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xb607ef98 Device Boot Start End Sectors Size Id Type /dev/xvda1 * 2048 27265023 27262976 13G 83 Linux /dev/xvda2 27265024 29360127 2095104 1023M 82 Linux swap / Solaris # lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT loop0 squashfs /snap/amass/770 loop1 squashfs /snap/core/8689 loop2 squashfs /snap/amass/671 loop3 squashfs /snap/core/7270 xvda ├─xvda1 ext4 3aed92f4-f9db-4e41-bb44-a4ea0cfc05a1 / └─xvda2 swap ea7fa869-0054-4b8e-ae14-64c55d69203f [SWAP] xvdb └─xvdb1 ext4 07c7f4fe-be16-460e-abee-cb382c3497d4 /home Le mer. 25 mars 2020 à 16:43, <dhorf-hfref.4a288...@hashmail.org> a écrit : > On Wed, Mar 25, 2020 at 04:21:29PM +0100, GD rub wrote: > > > Device Boot Start End Sectors Size Id Type > > /dev/xvda1 * 2048 29360127 29358080 14G 83 Linux > > /dev/xvda2 18946048 20969471 2023424 988M 82 Linux swap / Solaris > > urgh! be super careful there. > your xvda2 is currently overlapping / in the middle of your xvda1! > > that means your rootfs is currently corrupted in an _interesting_ way. > > if you have snapshots left for the vm from before the resize, > consider keeping/reverting! (check with qvm-volume and/or lvs) > > if not ... i recommend deleting xvda2 (and moving swap to xvdc), > then running a full fsck on xvda1 from outside the vm, or flagging > it for fsck and rebooting. > > > > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CANE5ERZxfBeHqeQ0Bp696RiM8-XLmOkW2GMZ34i5r8UkLWNnsg%40mail.gmail.com.