Home Assistant VM on Proxmox Full and can’t boot

Configuration
1

Buffer I/0 error on deu sda8, logical block 40922920, lost async page write

333301] I/0 error, deu sda, sector 487979264 op 0x9: (WRITE_ZEROES) flags 0x800 phys_seg O prio cl

3343991 Aborting

journal on device sda8-8.

334926]

EXT4-fs

(sda8): ext4_do_writepages: jbd2_start: 13312 pages, ino 10223768; err -30

336380]

EXT4-fs

error

(device sda8) in ext4 _reserve_inode_write:5861: IO failure

337320]

EXT4-fs

error

3384551

(device sda8): ext4_dirty_inode:6065: inode #262154: comm systemd-journal:

Hey so I made a pretty stupid mistake… I set up frigate with snapshots for activity at the front door not realizing how quickly it would build up (I live in NYC).

The Home Assistant is now full and even though I resized the disk, I can’t get it to boot. How can I access the files to clear it up and hopefully get it booting again?

I did plan on mapping the Frigate storage on an external NAS but I thought I’d be able to go a week without doing so- that was obviously wrong lol.

Thanks in advance for any help.

1 Like
2

as a new yorker my self i must first say:
Modern Monetary Theory: A Primer - Page 114 - Politics and World Issues - T NATION

your gonna have to ssh in and manual delete the media

3

Just wait until you find out I don’t have the SSH add on installed……….

4

Don’t need it, should be able to access terminal in proxmox. It’s as if you had an hdmi into a device running ha you’d see the screen that says home assistant with your ip details etc… I don’t run proxmox anymore so I forget what it’s called

5

In proxmox web page click on HA VM, then on the right side click on “Console”

1 Like