Hi Everyone,
I am new to HASS and I’ve been enjoying setting up my first installation and seeing the benefits it brings to my home. My first install was on an old x64 box just to try out HASS. I had it really well configured and running nicely but now there is a problem, I think it is disk corruption, HASS won’t start up and I didn’t get as far as making a backup yet.
The box takes ages to boot and it will eventually get to the GUI login screen and I can log in. Also I can sometimes SSH into it but I can’t get HASS to start.
I have bought a Radxa Rock to run HASS on and I was about to transfer over to it when this problem happened. If I have access to the config files etc can I transfer them over to my new installation?
My original install was on Debian 13 using Docker but my new installation will be using the HAOS fork for Radxa.
From journalctl -b I get these errors/warnings which don’t mean much to me:
Mar 12 20:51:18 HomeAssistant kernel: ACPI: SPCR: [Firmware Bug]: Unexpected SPCR Access Width. Defaulting to>
Mar 12 20:51:18 HomeAssistant kernel: [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)
Mar 12 20:52:28 HomeAssistant systemd-udevd[348]: /usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO="alsa_r>
Mar 12 20:52:28 HomeAssistant systemd-udevd[348]: /usr/lib/udev/rules.d/90-alsa-restore.rules:18 The line has>
Mar 12 20:52:28 HomeAssistant systemd-udevd[348]: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_r>
Mar 12 20:52:28 HomeAssistant systemd-udevd[348]: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 The line has>
Mar 12 20:52:44 HomeAssistant systemd[1]: dev-disk-by\x2duuid-c19e0953\x2d6543\x2d46f8\x2daf6e\x2d9d4680eca35>
Mar 12 20:52:44 HomeAssistant systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-c19e0953\x2d6543\x>
Mar 12 20:52:56 HomeAssistant systemd[1]: systemd-journal-flush.service: start operation timed out. Terminati>
Mar 12 20:52:56 HomeAssistant systemd[1]: systemd-journal-flush.service: Main process exited, code=killed, st>
Mar 12 20:52:56 HomeAssistant systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'.
Mar 12 20:52:56 HomeAssistant systemd[1]: Failed to start systemd-journal-flush.service - Flush Journal to Pe>
lines 911-945client_loop: send disconnect: Broken pipe
I have HAOS installed and ready to go on my new Radxa box and would have loved to have just made a backup from the old box and upload to the new.
Any helpful suggestions would be really welcomed at this point, thank you.
Hello,
something is wrong with your /etc/fstab probably.
You can look into it to check that /etc/fstab reports mounted disk correctly setup.
Did you changed the disk order? I mean do you have 2 disk and changed something maybe in bios?
running in terminal command sudo blkid
you will see a list of mounted devices, these should be correctly setup in the file /etc/fstab, to see it type command in the terminal: sudo nano /etc/fstab
If it is a docker container you can save something accessing the volume mounted folder, you should have setup it in the volume section when creating the docker.
Then you should be able to recreate a docker container with the old files mounted and make anything with data there, like a backup.
Thank you for your detailed help. I will work through those steps and try to diagnose what the problem is with this box as I’d like to keep it as a backup system.
Amazingly I managed to get a backup done! I left the box switched on (even though it was quite unresponsive and it wasn’t even responding to pings!) as I could see the HDD led was flashing. I came back to check on it after a few hours and I could ping it again so I fired up browser on my laptop and I got into the UI! It was very slow but I set a manual backup going and went away to do something else. When I came back the network had dropped out again and I lost the UI.
I left it on overnight could I could still see the HDD thrashing away and when I tried the UI again this morning it let me back in again and in the backups section I could see that there was (1)
It must have taken hours to do the backup but it had obviously kept working after I lost the UI.
I fired up my new Radxa box and tried uploading the backup - it works perfectly and I’m very relieved. The Radxa Rock 4C+ is way, way faster than my 10 year old Celeron based machine even though both have 4GB RAM.
Hi, welcome to the forum and good you managed to get that backup!
Tip for the future: backup, backup, backup…
If you start making a lot of modifications (automations/scripts, dashboards, configuring integrations and apps, …) you will be pissed for not having done so when things go south!
If a great deal of your house is running on HA and it fails: if you live alone, it’s only you but if with other housemembers, you might get it hard to defend the time/cost you invested to automate the place.
Also: please take the time to mark the post that holds the solution.
You do that by selecting the three dots under the post:
Then select the check box:
By doing so:
this thread can be useful to other users as well (this thread comes up as solution when starting a thread which is similar to yours).
this prevents that someone else steps in trying to help
