RPi4 w/ Debian 11 + HomeAssistant: Hang on Boot/Not loading RootFS?

I’m going to use this new Debian box (laptop with SSD) for home assistant and move away from MicroSD.

I assume DD is an imaging tool, can I create an image of the rootFS on this card and mount that on the nw debian box so I can alter permissions on the docker folder and copy my containers out?

DD is a bit copying tool, so it will make a copy that is bitwise identical.
You should be able to mount it, but boot on it could be more tricky with the underlying hardware being different.
Test it before you scrap the SDcard!

OK so here’s where we’re up to.

New Debian 11 box is up.
SD card was toast, but managed to rip a full image off it onto the debian box and it’s ultimately still readable.
Imaged that onto a smaller SD card I had here after shrinking the image.
Original raspberri pi and HA instance is now up and running and I am currently waiting for it to do a full backup (the HA level one (complete and downloaded on new host)
It wouldn’t add the repository for the google drive backups and it seems that add-on broke at some point in the past as I only have a full backup from a year ago but I’ll have a closer look.

So it was the SD card as was first suggested but from here I will need some assistance to restore/migrate my HA over to the new Debian machine as I’ve bee unimpressed with the RPi4 BT and WIFI stability.

Given I have a docker environment AND the HA instance, what is the best way to go about migrating off this RPi4?

From what I understand, full google backups should include add ons but I’ not sure about HA level ones.

The I also need to migrate my docker containers and the attached volumes 0_0

Have since managed to create a full backup of the old HA box and restore it on the new host which has gotten me 90%of the way there.

My issue now is debian itself will not “see” the BMS I’m trying to connect to via Blutetooth, it can see my other laptop/phone etc and my phone can seethe BMS on Bluetooth without issue.

Any ideas? I’m on bluez 5.66, when I do a scan I note the powered and discoverable status constantly flick back and forth.

[CHG] Controller 9C:B7:0D:55:CD:A1 Powered: no
[CHG] Controller 9C:B7:0D:55:CD:A1 Discovering: no
[CHG] Controller 9C:B7:0D:55:CD:A1 Class: 0x002c010c
[CHG] Controller 9C:B7:0D:55:CD:A1 Powered: yes
[CHG] Controller 9C:B7:0D:55:CD:A1 Class: 0x00000000
[CHG] Controller 9C:B7:0D:55:CD:A1 Powered: no
[CHG] Controller 9C:B7:0D:55:CD:A1 Discovering: no
[CHG] Controller 9C:B7:0D:55:CD:A1 Class: 0x002c010c
[CHG] Controller 9C:B7:0D:55:CD:A1 Powered: yes

When it was on the RPi4 this was not an issue.

There is. Lot of poor performing BT adapters out there.
On the HA Bluetooth section you can find a list of high performance adapters.

1 Like