Cannot connect to my Green after powercut :( Please Help!

Ok, so i just bought a Green a few days back. Got it working nicely and also set-up a separate data disk. Everything’s been wokring fine.

Then i had a power cut. Now i can’t connect to the device by browser or App. The Green’s IP address was fixed and FING is finding it ok at 192.168.1.184. The Green unit shows a solid white light and the green and yellow LEDs are flashing. Automations are not running.

I can ping the device fine from a terminal window.

Not sure what to do…any ideas? Must I reset?

Hello
Connect a display directly to the green with a HDMI cable to see what messages appear on the screen.

2 Likes

oh cool. Thank you for that idea. Lemme go check that.

It says “Waiting for the Home Assistant CLI to be ready…”

According to some posts on this forum, maybe HA could not mount your data disk.
Search this forum form more info.

thanks. It’s quite shocking to me. After many problems with HA on RPi’s some years back I left the community and have been using Hubitat where i didnt experience any such hardware or OS type issues (although plenty of other zigbee related nonsense). So I came back and purchased a Green thinking it would be much more simple to operate nowadays and that by now these kinds of issues would be resolved. Sad to see that HA is still a complete can of worms sigh :frowning:

Check the logs

ha host logs -vf
ha supervisor logs -vf
ha core logs -vf

You may have a small typo. 2nd word should be host, not hos

1 Like

Not a complete can of worms… just takes a bit of tweaking to get a power-cut-safe setup. I do appreciate your frustration though. Sorry I can’t be of help as I don’t run HAOS.

Any sign of life on the data disk itself (lights, noise etc)? Hardware could have died when the power got cut, or fried when it was restored.

i’m going to try connecting a mouse and keyboard this evening and see if i can run those commands. I’m a bit of a novice noob on all this. I believe i need to reboot it and interrupt the boot up so that i can try these commands. I did try removing the SSD that id connected and moved the data to to see if maybe that was the issue but the Green still stopped at the “waiting for CLI” message. I’m not sure if I should reconnect the drive now or not.

oh my, this is interesting. So i rebooted the Green and watched for the various messages coming up. I noticed two that said “low voltage connected”. Then “unable to read the hardware clock”

So I moved the power supply to a UPS I’ve got and it’s now booted up and seems fine. All my automations and devices seem to be fine!

Oh my, that was an unexpected bonus to start the weekend here. I thought I was going to be in for some stressful engineering :slight_smile:

I did still see an error message after the “waiting for CLI to be ready…” message. It says:

IO error, dev sda, sector 5068248 op 0x0:(READ) flags 0x80700 phys~seg 23 prio class 2

I have no idea what that means. Is part of the SSD wonky? Can i do something to fix this?

Thanks everyone for the kind assistance. It’s beyond what i was expecting :)_

There is a red light and a blue one which flickered a bit during the boot-up. I cant feel anything when i hold the drive and zero noise. Well, its a WD Green SATA SSD so i suppose nothing is rotating inside :slight_smile:

Now the Green has booted up but there is still an error message that came up that maybe refers to this drive. I noted it above in the thread.

I’d try to force a file system check via the fsck.mode=force kernel argument. If that doesn’t help re-install HAOS. SD Cards and eMMC storage seem to be more susceptible to corruption from brownouts/power cuts.

How is it connected. The SATA disk… You may be overrunning the power output capacity of the green.If it’s on usb with no additional power inject (not using a powered USB hub) that’s probably your issue.

Yes, I just connected the disk to the hub via a SATA to USB-A connector. How should I connect it then? You mean put a powered USB hub between them?

Yes exactly powered USB hub.

Also FYI bonus info… do NOT put any Bluetooth zigbee ZWave or whatever dongles on the same hub or anywhere near the same USB hub - USB3 is basically 3Ghz and close enough to the 2.5 drive interference drives dongles nuts.

At the end of the day a Green is a Pi. All pi have very limited power on the USB rail.

A few dongles by themselves have been known to overrun the power rail (it’s not something a bigger ps on the green can fix. It’s sending everything it can)

So, one big voltage hungry SSD can EASILY overrun the power and. If that’s the disk you’re running from… *blip

Put it on a POWERED USB hub and that’s a non issue just keep it away from your dongles.

I believe Green is less than a PI, max output on 1 usb-port(2.0) is 1A, on a Green , and the " Power-Supply" which comes with it is ofcause also only providing 1A … Bonus it hadly uses any Power :laughing:

1 Like

Power supply for green is 12v @ 1A: 12W
Power output from usb is 5v @ 1A: 5W.

There’s an additional 7W used to power the green & other stuff. It’s not running on free energy :wink:

I have no idea what your “point” with your commend is, and Yes there’s nothing wrong with my “Math” capabilities, and i do also have a power-meter, so im TOTALLY aware how much my Green “Draw” ( Including under load such as Nightly backup and monthly updates etc ) … beside all my other Utilities and Devices

Another “off Topic” is, i dont have de-sampled it just for adding a battery, And i Also have had 3-4 “Powercut’s” First one as a test "to see if it came online again when power came back, and 2-3 "accidently " fu ,
And I Never had issues, neither DNS, NTP or other “network” related , with my Green :wink: :wink: :wink:

BTW. it has 2 usb ports :wink: count the W again … that is if you have any intention of drawing full load on both