#Home Assistant CLI not starting! Jump into emergency console
1 messages ยท Page 1 of 1 (latest)
What happens in the console?
Got the same issue, pi was unpowered for few weeks and now when powering it up it does this
Might try enabling wifi as some ppl had success with that
Oh
I think i know what my issue is
Trying wifi to see if that works
Nope, it does get an ip tho
Doesn't work after reboot either
Is that SSD connected via a powered USB HUB?
Please try
journalctl -ru hassos-supervisor.service
journalctl -ru docker.service
journalctl -rk
It's just usb to sata cable directly connected to the pi
That often causes corruption because the pis seem to be very bad at providing reliable USB power. I don't know why.
Dang
Worked fine until it was powered off for a while
I can access the files on my pc if i need to
Let's check the logs first.
Will do when i come back from da store
Seems we have similiar issue, I am using SSD to USB3
@clever bobcat
I should have probably told you tomscroll to the newest logs.
my bad, does that mean just scroll to end?
or do I use something like -XE or something
Wherever is newest. By default it's usually at the end.
I think we concentrate on the supervisor for now as it has a dependency error.
Or at least had. Seems to have fixed itself?
I'll get logs now from newest, but I've just tried to run login
see if anything happens
login is only needed in the HA CLI, not the emergency console. It's what puts you into the "emergency console".
I edited the commands above so the newest logs will be at the top now. Reverse order. Might be easier that way.
This is
Systemctl status hassos-overlay.service
Yep. The supervisor seems to have major issues. I'd try to manually recreate it. Give me a second to find my post. I helped someone else with this a while ago.
But these overlay issues you see above are not a good sign. The OS is mostly read only but some things are not and those errors are not normal.
โ๏ธsystemctl stop hassos-supervisor
โ๏ธdocker stop hassio_supervisor hassio_cli
โ๏ธdocker rm hassio_supervisor hassio_cli
โ๏ธdocker system prune -af
/usr/sbin/hassos-supervisor
On last command, I get this
I'd probably recommend a reflash and restore at this point.
They are in the last partition of the disk in a supervisor/backup/ directory.
Backups are meant to save you from, among other things, disk failure/corruption, so storing them on that very same disk is ill advised ๐
/usr/sbin/hassos-supervisor was not meant as an argument to that docker command. It's its own command.
Oops ๐คฃ
I can't remember why I shared the full path rather than just hassos-supervisor but I probably had a reason.
haha
So this bit
/usr/sbin/hassos-supervisor
should be docker /usr/sbin/hassos-supervisor ?
You can also just run hassos-supervisor. Above is just the full path to that binary/script.
Seems to be WiFi related.
when i run "hassos_supervisor"
I get
/bin/ash: hassio_supervisor: not found
It's a -, not a_.
๐
If you get the CLI back I'd also run ha supervisor repair and ha host reboot. I don't trust the system yet And as the message said, give it some time. Pis are not the fastest devices.
Yeah when I run hassos-supervisor
jq: error: Could not open file /mnt/data/supervisor/updater.json
i know ๐
:<
See if a reboot changes anything. The overlay service failing concerns me.
have had to wait few times for it to do its thing
Yeah, nothing with reboot
when I sun status on hassos-overlay I'm gettingl ogs like
can't create /mnt/overlay read-only file system
I'd recommend a re-flash then. Having to muck around in the OS can sour you on the HAOS experience ๐
Thanks for the help, I'm gonna try mess around with it in breaks of work whilst I wait for weekend so I get full day to reset it up and reflash all lightbulbs
the fact date us Mon May 27 is probably a problem too
But if you do want to play around. You can see the service file with systemctl cat hassos-overlay and cat /usr/libexec/hassos-overlay shows you what the script it executes does.
"usr/libexec/hassos-overlay" no such file ๐ฆ
Yeah it seems like it can't mount the disk or the mount point does not exist.
You can check findmnt -T /mnt/data/supervisor.
You need to write it with the slash just like me.
As for the data mount you can also check systemctl status mnt-data.mount and systemctl --failed.
But like I said, this would be running an armada of commands and there's no guarantee for a fix.
Ah so basically look a the files and try to execute them one by one
in hope it fixes?
No.
oh haha my bad
thx, working again
Yay. I'd recommend you get a powered USB HUB and set up backups to remote storage so in case something like this happens again you can restore things.
maybe i do have to ๐
well i do have a usb hub but its currently hooked to my pc ๐ and its not small either ๐คฃ
i do have smaller one somewhere
idk where the power cord is tho xd
What matters is that's it provides power itself.
nvm, found the hub but the power cord is somewhere ๐
I thought the sata cable itself was fine, as this issue doesn't seem to be related? I don't think the Sata 2.5" SSD require as much power as the little tiny ones
All I can tell you is that SSD corruption has occurred for people here in the past and was fixed by adding a powered USB HUB in-between.
It's one of the reasons I don't like/recommend pis: https://gist.github.com/Impact123/6ee130240bdc6a7fed2d5224616544a0
i will host ha on somehere else eventually but this is what i had on hand ๐
It's not the case but the pi's USB ports. I don't own one any more so I cannot test. I can only base it on what I've experienced here and read otherwhere.
Ah
Seems like your network is not working either. Is it connected via ethernet?
No WIFI
Hmm. I'd recommend you try with ethernet.