Problem with virtual machine (partition on zfs-pool disk dissappeared)

VDR

New Member
Dec 16, 2020
3
1
3
45
Hi, I have today problem with ac power and my serwer crashed :/
The first problem was with /dev/mapper/pve-root. Server boot to initramfs.
I make fsck /dev/mapper/pve-root, repair failsystem and proxmox run.

But have problem with one vm which cannot boot: no bootable device found.

root@pve-radom:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 6120004 0 6120004 0% /dev
tmpfs 1228208 9440 1218768 1% /run
/dev/mapper/pve-root 17156896 3068088 13194244 19% /
tmpfs 6141032 43680 6097352 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 6141032 0 6141032 0% /sys/fs/cgroup
local73GB-ZFS 69073024 128 69072896 1% /local73GB-ZFS
zfs-pool 1996891776 128 1996891648 1% /zfs-pool
/dev/fuse 30720 16 30704 1% /etc/pve
tmpfs 1228204 0 1228204 0% /run/user/0

root@pve-radom:~# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
local73GB-ZFS 68G 2.16M 68.0G - 0% 0% 1.00x ONLINE -
zfs-pool 3.62T 975G 2.67T - 63% 26% 1.00x ONLINE -
root@pve-radom:~#

root@pve-radom:~# zpool status
pool: local73GB-ZFS
state: ONLINE
scan: scrub repaired 0B in 0h0m with 0 errors on Sun Dec 13 00:24:02 2020
config:

NAME STATE READ WRITE CKSUM
local73GB-ZFS ONLINE 0 0 0
sdb ONLINE 0 0 0

errors: No known data errors

pool: zfs-pool
state: ONLINE
scan: scrub repaired 136K in 30h8m with 0 errors on Mon Dec 14 06:32:58 2020
config:

NAME STATE READ WRITE CKSUM
zfs-pool ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
sdc ONLINE 0 0 0
sdd ONLINE 0 0 0
sde ONLINE 0 0 0
sdf ONLINE 0 0 0

errors: No known data errors
root@pve-radom:~#



root@pve-radom:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
local73GB-ZFS 1.89M 65.9G 96K /local73GB-ZFS
zfs-pool 708G 1.86T 140K /zfs-pool
zfs-pool/vm-100-disk-0 436G 1.86T 436G -
zfs-pool/vm-101-disk-0 8.26G 1.86T 8.26G -
zfs-pool/vm-103-disk-0 261G 1.86T 261G -


The vm-100-disk-0 is problematic :/

root@pve-radom:~# fdisk -l /dev/zfs-pool/vm-100-disk-0
Disk /dev/zfs-pool/vm-100-disk-0: 300 GiB, 322122547200 bytes, 629145600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
root@pve-radom:~#

I cannot found any partition ? :o

It will be something like that:
root@pve-radom:~# fdisk -l /dev/zfs-pool/vm-102-disk-0
fdisk: cannot open /dev/zfs-pool/vm-102-disk-0: No such file or directory
root@pve-radom:~# fdisk -l /dev/zfs-pool/vm-103-disk-0
Disk /dev/zfs-pool/vm-103-disk-0: 300 GiB, 322122547200 bytes, 629145600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 8192 bytes
I/O size (minimum/optimal): 8192 bytes / 8192 bytes
Disklabel type: gpt
Disk identifier: 3FA34880-0F69-11E9-B62F-37BE991644A3

Device Start End Sectors Size Type
/dev/zfs-pool/vm-103-disk-0p1 40 1063 1024 512K FreeBSD boot
/dev/zfs-pool/vm-103-disk-0p2 2048 4196351 4194304 2G FreeBSD swap
/dev/zfs-pool/vm-103-disk-0p3 4196352 629143551 624947200 298G FreeBSD ZFS

Partition 1 does not start on physical sector boundary.
root@pve-radom:~#

What happened ??
 
It`s more complicated ;) I recognize that it`s a freebsd with encrypted zfs partition.
I dont know what happen but proxmox don`t see a bootable partition.
But when I started this vm with CD Live Freebsd and boot from it, I can attach encrypted geli partition, import zpool and mount filesystem. And see all the files.
So good news - all data are recoverable ;)

Actually try found info how recover a bootloader and boot from disk not cd-rom.
But I think, it`s FreeBSD issue not a Proxmox.
 
  • Like
Reactions: Alwin