Please help. Today there was planned maintenance on our powergrid, so I shutdown Home Assistant from the gui as I should well before the mainentance started. I’m running it on a RPI4. Now that the power is back online, I started the RPI. The webgui is now no longer accessible: connection refused. I am able to ping it’s IP address, so I guess the OS is running. SSH is returning connection refused as well.
Is there any way to get access via SSH, so I can at least check some log files? I already placed an empty ssh file in the root of the boot partition, but that does not help.
I would connect it to a tv / monitor to see what the console says.
What’s the help page say? Change the port number from 8123 to 4357 (help)
ip:4357 also gives connection refused
Will go to the store and buy a micro hdmi cable tomorrow
In which case I would check the router to see if that actually IS the IP address. Devices don’t typically change their IP address when they are powered up, even when they get an address over DHCP. But if EVERYTHING has been shut down, then there is no reason that devices will have received the IP address they had before - UNLESS you specifically told the router to reserve those IP addresses
I am absolutely sure this is the correct ip address, I got a dhcp reservation for it. Also it can only be pinged when it’s connected, so I’m 100% sure
SSH is port 2222 not port 22. So that’s the first thing to be aware of.
Second - I’d perhaps pull power from the Pi for 30 seconds and plug it back in, in case it was something silly (which has been seen before) - where because it couldn’t speak to a time server when booting, it just hangs. So maybe if the internet connection was not back up when Home Assistant was booted - it didn’t boot fully.
Yes, tried 22222 as well, same result unfortunately. It has been off the power for more quite some time when I put the ssh file, so that does not help either
Let me try it again, just to be sure, maybe the timesync issue …
however, I’m a bit hesitant to pull the power again incase of sd corruption
The blank ssh file does not apply to the Home Assistant OS, it’s very much for the Raspberry Pi OS, and as far as I am aware only for first boot after flashing the SD Card.
To enable the developer ssh mode on Home Assistant, is more involved - the ssh add-on, if it is running would not give you access to the root file system, it’s just a docker container, with some basic tools installed, and the ha cli tool.
You’re wadding into troubled waters. If you don’t have a current backup, don’t mess with the underbelly of HA.
If you do have a current backup, restoring the backup should take less than an hour. That would likely be the fastest way to get back up and running.
Yes, I have backups. Before reinstalling and restoring a backup I wanted to try and get it working. I guess that’s my only option now
Outside of the user area of HA is very technical. The easiest way that I have found to get into the backend is portainer. What to do after you’re in, that I can’t help you with.
Add alex beigium’s repository to the addon store.
then use admin as user with homeassistant for the password.
I just want to say if I was in your position, which I have been, knowing what I know now, I’d go right for the reinstall. I back my system up daily using the google drive addon just for this reason.
Anything I should keep in mind when reinstalling? I have an additional USB stick in my RPI for storing the data. Should I reinstall with or without the USB stick? I guess the backup also contains the data that is stored on the USB stick?
I guess it depends on how the stick is defined in ha. My install is edging 6gig, it keeps all the data but I don’t know how that works with outside storage. I’m afraid I can’t answer that question.
If you plan on restoring from a connected USB stick do yourself a favor and copy the data somewhere else too before you start, just to be on the safe side.
Im restoring from a network drive. USB stick is unreadable in Windows so I cannot copy the data, unless I do a raw bitwise clone I guess
That’s not strictly true - there are ext3/4 drivers available for windows.
I just connected a monitor via hdmi and it seems like my usb thumb drive is corrupted/broken/whatever. There is no /dev/sda. lsblk only shows mmcblk and zram partitions.
journalctl shows (among other stuff):
Job dev-disk-by/x2dlabel-hassos\x2ddata.device/start filed with result timeout
Dependency failed for HassOS data partition
Dependency failed for Grow File System on /mnt/data
Dependency failed for Docker application Container Engine
I do have a backup file copy job running that copies the backups externally, now I have to find a way to get these restored…Any suggestions?
Use a more suited storage (SSD), re-install and do a restore from the backup would be my suggestion.