HassOS fsck issue on proxmox

Installation Home Assistant OS
1

Hello folks!

Home Assistant Core 2022.6.7
Home Assistant Supervisor 2022.05.3
Home Assistant OS 8.2

I am running a script installed version of hassos 8.2 under proxmox 7.2, and I got errors on my virtual disk now. The OS got poblems to write sometimes, and so the whole fs switches to read only. It all started after activating snapshot backups under proxmox.

Maybe my question is silly, but until now I have not managed to run a fsck.ext4 on the hassos disk (/dev/sda8). Using ssh console of hassos fsck always shows erros like that:

bash: fsck.ext4: command not found

Is it somehow possible to stop the proxmox vm, and fsck the virtual disk on that level?

I tried fsck.ext4 /dev/pve/vm-100-disk-1, but that also got me to another error…

/dev/pve# fsck.ext4 /dev/pve/vm-100-disk-1
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/pve/vm-100-                               disk-1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Any ideas for me?

Thanks!!

2

Hi @HudecityDave, same issue a few days ago, even after trying a lot of methods it was not possible to restore the machine.
Fortunately I was able to copy the latest backup archive locally to another disk and then deploying a new VM was a piece of cake with tteck script: https://raw.githubusercontent.com/tteck/Proxmox/main/vm/haos-vm.sh.
An then during wizard on the webpage, I just uploaded my backup archive and almost everything was backup to business, except for addons.

Regarding the Proxmox issue, I faced the same, I’ll try to select the mode “stop”, so the VM is first shutdown before taking a snapshot.

Best,

Tim.