Lost access to HA on HA Blue. Disk is full

Installation Home Assistant OS
1

Hi, I need help.

It looks like my frigate nvr has filled the disk with clips overnight. I just want to know how can I access the drive in order to delete the clips in the folder and change the config, so this won’t happen again.

I can’t access shares over samba and can’t access over ssh any more.

I have backups, but I only want to use that option as a very last resort.

Is there any way?

2

plug in monitor and access directly?

3

I tried already mounting flash storage through live Ubuntu image, but couldn’t set permissions to delete clips in the media folder.

At least I was able to copy my Node-Red folder - the last thing that was modified since yesterday’s morning backup.

So now I am restoring my backup, can’t have anything in non-working state longer than few hours.

I was hoping the media folder would be easily accessible and writable outside of Home Assistant when storage is physically connected to another PC. Anyway, thanks for a suggestion.

4

sudo doesnt need permissions

sudo rm whateverthefilenameis
OR
sudo rm *.mp4 to remove all clips

5

It didn’t let me remove files because I wasn’t the owner of the files. It wouldn’t let me change ownership, either.

6

Ownership ultimately belongs to system files are mounted on and root user (sudo) is king

7

Well too late now, I flashed a new image and tried to restore my backup only to discover none of them are working… When I type my password HA restarts and returns errors in supervisor:

Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/backups/manager.py", line 251, in _do_restore
    backup.restore_homeassistant()
  File "/usr/src/supervisor/supervisor/backups/backup.py", line 467, in restore_homeassistant
    self.sys_homeassistant.refresh_token = self._decrypt_data(
  File "/usr/src/supervisor/supervisor/backups/backup.py", line 212, in _decrypt_data
    data = padder.update(decrypt.update(b64decode(data))) + padder.finalize()
  File "/usr/local/lib/python3.9/site-packages/cryptography/hazmat/primitives/padding.py", line 159, in finalize
    result = _byte_unpadding_check(
  File "/usr/local/lib/python3.9/site-packages/cryptography/hazmat/primitives/padding.py", line 101, in _byte_unpadding_check
    raise ValueError("Invalid padding bytes.")
ValueError: Invalid padding bytes.

I am about to give up, this really surprised me. I am shocked that backups can be so unreliable. All my recent daily backups are causing this. I think the only option for me is to use the last known working file from a year ago, basically before I moved backups to Google Drive…

8

I think you can access all the files from snapshot

If so, you can pull the config folder including hidden .storage folder and use that to restore from older backup or from new install

9

When I was trying to delete all the recordings, at the same time I managed to copy most of the data, so I before restoring old backup I will try to manually move everything over to new installation. I imagine it will take a long time to make sure everything works without any major errors.