Hi, I started an update, but after that, the HASS is not booting.
The HASS is on SD card in RPi and I’m using Linux on my PC.
I could not find any general recovery steps.
$ ping 192.168.42.42
PING 192.168.42.42 (192.168.42.42) 56(84) bytes of data.
From 192.168.42.42 icmp_seq=1 Destination Host Unreachable
How can I get it back and running?
An update of what?
OS, core, an addon, a third party integration?
Hook a keyboard and monitor up to your pi to see what is going on.
Worst case, flash a new install and restore the full backup that you made before updating. The one you copied off the card to a safe place.
I was updating everything, the OS, the core, and add-ons.
How do I hook up a monitor to RPi? There is no HDMI, DP, or anything…
I will have to read about copying backups …
Nevertheless, I’m slowly losing faith in a system that destroys itself with an update - this is even worse than M$ Windoze - that will only crash at worst…
Yes there is.
Oooh, it’s a micro HDMI… I thought its a USB, never heard about micro HDMI… ok then, as soon as buy a cable, I can try looking inside…
Ok, I got the cable and it says “Bad cluster number 0 … Firmware not Found” Seriously, how bad a system has to be to fuckup itself with an update?!
BTW the SD card can be still read in a reader connected to the computer.
I also read some opinions that the SD card might be the issue - old, bad blocks, etc…
Pass completed, 0 bad blocks found. (0/0/0 errors)
I don’t know, is 0 bad blocks enough to blame the SD card?
Assuming you connected it to a windows computer to test it might have skipped the Linux partitions. So I would certainly be suspecting the SD card is faulty.
Nothing to do with the update if your card is failing. e.g. A database write could eventually cause the same thing.
Also please watch your language. This is an all ages forum.
You are assuming wrong
I used badblocks -v /dev/sdb
$ lsblk
sdb 8:16 1 58G 0 disk
├─sdb1 8:17 1 32M 0 part
├─sdb2 8:18 1 24M 0 part /run/media/pilnyt/disk
├─sdb3 8:19 1 256M 0 part /run/media/pilnyt/disk3
├─sdb4 8:20 1 24M 0 part /run/media/pilnyt/disk1
├─sdb5 8:21 1 256M 0 part /run/media/pilnyt/disk2
├─sdb6 8:22 1 8M 0 part
├─sdb7 8:23 1 96M 0 part /run/media/pilnyt/hassos-overlay
└─sdb8 8:24 1 57.3G 0 part /run/media/pilnyt/hassos-data
$ sudo badblocks -v /dev/sdb
Checking blocks 0 to 60768255
Checking for bad blocks (read-only test):
done
Pass completed, 0 bad blocks found. (0/0/0 errors)
Just to to super-sure, the badblocks didn’t skip any partition:
Note - code block can be scrolled separately - I tested all 8 partitions.
$ sudo badblocks -v /dev/sdb1
Checking blocks 0 to 32767
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
$ sudo badblocks -v /dev/sdb2
Checking blocks 0 to 24575
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
$ sudo badblocks -v /dev/sdb3
Checking blocks 0 to 262143
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
$ sudo badblocks -v /dev/sdb4
Checking blocks 0 to 24575
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
$ sudo badblocks -v /dev/sdb5
Checking blocks 0 to 262143
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
$ sudo badblocks -v /dev/sdb6
Checking blocks 0 to 8191
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
$ sudo badblocks -v /dev/sdb7
Checking blocks 0 to 98303
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
$ sudo badblocks -v /dev/sdb8
Checking blocks 0 to 60054510
Checking for bad blocks (read-only test):
Pass completed, 0 bad blocks found. (0/0/0 errors)
Is there any other test I can run to check the SD card?
I also hate it when you pay that much for a piece of software and those programmers who make themselves rich by just tapping on a keyboard don’t do their work…
So if it cannot be blamed on SD card it gets silent, huh?
Maybe that, but it can be something else too…