#HA hardware failue
1 messages · Page 1 of 1 (latest)
what are you running on?
what hardware do you have?
it could be a cpu failure, it could be something causing errors on the cpu, like a misbehaving pcie card or something
a laptop and I have no idea what hardware is in there. all I know is that it's a pentium
what I find weird is that it only happens if the battery is in
without further information then its unlikely people will be able to help.
you could see if there's a bios update for the system.
although honestly, if it works fine with the battery out then just leave it out and call it a day.
I'd need to see if I can get info on it
it's a really old comptuer so I have no idea where I'd even get a bios ofr it
You probably want to remove the battery anyways if you use it 24/7.
fair. it just sucks if I ever want to move it somewhere
I'm not sure if HAOS has a MCE log file somewhere to debug this further. The joys of using a niche OS.
Maybe you can do a memory test?
I'm not sure how
would that be in the bios?
Put a memtest86 on a USB drive and boot it. I recommend using ventoy for this.
if it's a memory issue, why would taking the battery out solve it?
I notice that it seems to follow some sort of pattern
every ~330 seconds or 5.5mins
No idea. I have no clue why involving the battery causes it either.
it could be the BMS that's causing issues and that's its reporting interval. it depends how the BMS is attached to the system.
You can try ha host logs -vf to follow the host logs. Might provide more information.
on the computer itself?
Right in that HA CLI.
aw man I gotta get out of bed
then its unplugged from the network anyway?
You can also use a SSH addon or just the GUI.
wait what
I can just use the gui?
I don't prefer it but yeah. Kind of.
the bluetooth dongle is spamming the logs
I'm not sure if kernel messages will be logged there though.
it looks like it does?
Yeah just checked.
Most of the time when we debug stuff the GUI is usually broken in some way so using the CLI via keyboard & monitor or a SSH client is common.
In this case the GUI's log can be used, of course. I just don't often think about it due to that.
it's still the same info for what I an tell
I installed the stable update today with the pamac GUI als I always do, but unfortunately it resulted in a major error: on the reboot my laptop got stuck on an error message stating: [ 0.245300] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 5: ae00000000 40110a [ 0.245300] mce: [Hardware Error]: TSC 0 ADDR fef873c0 MISC 78a0000086 [...
if it is the ram, I may have some ram lying around
if it's not soldered on
I first noticed it when I upgraded from HA 2025.5.3 so I had to downgrade back to it and haven't upgraded since. But then it's also happening on 2025.5.3 so idk
Use memtest86 first until it passes to check. Try both with and without battery.
if I have a usb stick lying around somewhere
How did you flash HAOS?
Less than a gig or so. Depends on the version you use.
I have no idea where any of my USB sticks are. tehey just diappeared
:<
and I had several
found both lol
also @scenic bear which site?
Whatever you want. I usually use the passmark one.
which test? there's like 15 of them
or just start test?
It will start what you want automatically.
75% done, no errors
Is this with the battery connected?
yup
That's bad because that would have possibly been a simple fix.
yeah
took the battery out and it still throws those messages but it's not crashing
nope it's still crashing. I wish I knew what the failure was
Same.
@scenic bear I've replaced the CMOS battery in the laptop. It was reading 2.66v so we'll see how it holds up
so far it's not crashing
I don't think I've ever heard of a low CMOS battery to cause crashing. 2.7V~ isn't empty either.
maybe not crashing crashing but it would just suddenly shut off
no warning, just off
I spoke too soon. It just shut off