Starting old HAOS on new Proxmox install fails Unknow filesystem

My Proxmox installation failed due to OS drive dying.

HOAS disks are separate and should be good (but not backup-ed regularly my bad)
So my old installation looks like this:

-rw-r----- 1 root root 32G Sep 26 10:52 vm-100-disk-2.raw
-rw-r----- 1 root root 528K Sep 26 10:34 vm-100-disk-3.raw
-rw-r----- 1 root root 32G Sep 26 10:32 vm-103-disk-1.raw

vm-103-disk-1.raw is the disk from the old system.
When I try to start it from that disk (after adding it to fresh installation):
image
I get error: Unknown filesystem

The original installation is about 1 year old was there any change that would block it from using older fs?
Any way I could install old HAOS to use the old drive and make backup?

I noticed that the older installation has drives created in opposite order UEFI drive and then System
-rw-r----- 1 root root 4.0M Jun 8 2025 vm-103-disk-0.raw
-rw-r----- 1 root root 32G Sep 21 14:12 vm-103-disk-1.raw
I tried to copy vm setup and just use those drives but the VM does not start then does not even give any output to console saying graphic output not started.

Thank you
Adam

Hi, are you using different filesystems for your old and new Proxmox setup?
I had a similar problem coming from a ZFS setup and wanted to restore on ext4

No both use ZFS

But I also tried to mount this drive under debian VM but it does not see any file system there
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 32G 0 disk
├─sda1 8:1 0 30.3G 0 part /
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 1.7G 0 part [SWAP]
sdb 8:16 0 32G 0 disk

Disk /dev/sdb: 32 GiB, 34359738368 bytes, 67108864 sectors
Disk model: QEMU HARDDISK
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: 0x3b01adcf

Sorry man, other then saying to think about better backup strategy (regularly, offloading) I cannot help you. :face_with_diagonal_mouth:

My HAOS disk was broken when the supervisor went down
In case somebody find them self in this situation I think I am on a good route to restore it.
I used this to recover original partitions using vm with mounted original disk:
testdisk /dev/sdb

they were not in good state to use on new installation but they had automated backups:
supervisor/backup/automatic_backup_2026_9_2_2026-09-19_05.12_08002636.tar

encrypted encription key for them is found in:
supervisor/homeassistant/.storage/backup

Looks like I will be able to recover everything so happy ending.

Lesson again - do backup - make sure you can recover them!

Thank you