Latest Upgrade seems to have killed my install

Hi Guys,

Did the latest update through the webpage and my install seems borked. Often after doing an update on my Raspi 3 I would have to do a hard reboot to get the webpage back and the thing running again. A couple of times it was twice before it came back. This time however, it seems totally dead. I can’t load the webpage, I can’t SSH into it, I can’t ping it. Visually, the Raspi 3 seems to be running, lights are on, network traffic lights flash, but I can’t get into it.

Any suggestions to start troubleshooting?

1 Like

I did a capture of what I get on the HDMI after bootup. Looks like some errors with the SD card.

2.12062 J MNCBIRO! card_busy_detect! error sending status cmd, status Ox8C blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc } blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; } a img { border: 0px; } li[style='text-align: center;'], li[style='text-align: right;'] { list-style-position: inside;} .plain pre, .plain tt { font-family: monospace; font-size: 100%; font-weight: normal; font-style: normal; } .plain div.plain_line { white-space: pre-wrap; } a { color: #0000EE } a:visited { color: #551A8B } div.pgp_marked_message { display: none; } body { font-family: Segoe UI; font-size: 12pt; background-color: #FFFFFF; color: #000000; margin-left: 0px; margin-right: 8px } .plain pre, .plain tt { font-family: Segoe UI; font-size: 12pt; } blockquote { display: none }
7164932 pcblko: retrying write for general error
2168359 mocbiko: card_busy_detect: error sending status cnd, status 0x80
7171215 mmcblko: retrying write for general error
7174636 ] mmcblko: card_busy_detect: error sending status cnd, status Ox809
7172387 mocb Iko: retrying write for general error
7180820 mmcblko: card_busy_detect: error sending status cmd, status OxB09
71836611 mmcblko: retrying write for general error
7187096 mmcblko: card_busy detect: error sending status cmd, status Ox809C
7189967 ] mmcblko: retrying write for general error
7192785 JBD2: recovery failed
71955931 EXT4-fs (mncblkop8): error loading journal
ED) Failed to mount Hassio data partition.

systemctl status mnt-data.mount' for details.
NDI Dependency failed for Docker persistent data.
ND) Dependency failed for HassIO AppArmor.

Starting Create Volatile Files and Directories...
Reached target Hass0S overlay targets.
Started Create Volatile Files and Directories.

Starting Update UTMP about System Boot Shutdown..
{ 1 Started Update UTMP about System Boot/Shutdown.
Reached target System Initialization.
) Listening on D-Bus System Message Bus Socket.
Starting Docker Socket for the API.
J Started HassOS mark boot partition as good.
I Started Daily Cleanup of Temporary Directories.
1 Reached target Timers.
3 Listening on Avahi MDNS/DNS-SD Stack Activation Socket.
3 Listening on Docker Socket for the API.
Reached target Sockets.
Reached target Basic System.
E] Started D-Bus System Message Bus.

I Started Hardware RNG Entropy Gatherer Daemon.
Starting Hassos Configuration Manager...
Starting Rauc Update Service...
Starting Bluetooth for BCM43xx..
78579651 uart-p1011 3f201000.serial: no DMA platform data
I Started Hassos Configuration Manager.
8] Started Rauc Update Service.
8638952 Bluetooth: Core ver 2.22
8641775 NET: Registered protocol family 31
8644519 ] Bluetooth: HCI device and connection manager initialized
8647360 Bluetooth: HCI socket layer initialized
8649968 Bluetooth: L2CAP socket layer initialized
8652497 Bluetooth: SCO socket layer initialized
8667931 Bluetooth: HCI UART driver ver 2.3
8670660 Bluetooth: HCI UART protocol H4 registered
8673319 Bluetooth: HCI UART protocol Three-wire (HS) registered
8675845 Bluetooth: HCI UART protocol Broadcom registered
) Started Bluetooth for BCM43xx.
Starting Bluetooth service...
6 Reached target Hassio hardware targets.
J Reached target Multi-User System.
Starting Update UTMP about Systen Runlevel Changes..
Started Update UTMP about Systen Runlevel Changes
Started Bluetooth service.
Reached target Bluetooth.
88016501 Bluetooth: BNEP Ethernet Emulation) ver 1.3
8801228 Bluetooth: BNEP filters: protocol multicast
8806739 Bluetooth: BNEP socket layer initialized

Did you check if the IP of the Pi is still the same? Can you ping the Pi?

Could be a full or corrupted SD card.

Here is a bit more

Starting Rauc Update Service...
7943867 uart-p1011 3f201000.serial: no DMA platform data
{ 1 Started HassOS Configuration Manager.
{ I Started Rauc Update Service.
8725351 Bluetooth: Core ver 2.22
8728092 ] NET: Registered protocol family 31
8731033 Bluetooth: HCI device and connection manager initialized
8733888 Bluetooth: HCI socket layer initialized
8736434 Bluetooth: L2CAP socket layer initialized
8738985 Bluetooth: SCO socket layer initialized
8754183 Bluetooth: HCI UART driver ver 2.3
8757012 Bluetooth: HCI UART protocol H4 registered
87596031 Bluetooth: HCI UART protocol Three-wire (HS) registered
8762207 Bluetooth: HCI UART protocol Broadcom registered
{ ] Started Bluetooth for BCM43xx.
Starting Bluetooth service...
Reached target HassoS hardware targets.
Reached target Multi-User System.
Starting Update UTMP about System Runlevel Changes...
{ 1 Started Update UTMP about System Runlevel Changes.
Started Bluetooth service.
Reached target Bluetooth.
88924131 Bluetooth: BNEP (Ethernet Emulation) ver 1.3
8894872 Bluetooth: BNEP filters: protocol multicast
8897480 Bluetooth: BNEP socket layer initialized
' 0129317 mmcblk: card busy detect: error sending status cnd, status Ox80900
' 0131675 mncblko: retrying write for general error
' 0135095 mncblko: card_busy_detect: error sending status cnd, status Ox80900
' 0137365 mncblko: retrying write for general error
0140760 bike: card_busy_detect: error sending status cmd, status Ox80900
' 0142986 mncblko: retrying write for general error
3221 nncblk0: card_busy_detect: error sending status cnd, status Ox80900
10148594 pcblko: retrying urite for general error
0151963 macblko: card_busy_detect: error sending status cnd, status Ox80900
0154232 pcblko: retrying write for general error
0157606 nncbike: card_busy_detect: error sending status cnd, status Ox80900
0159813 ] nncblko: retrying write for general error
0162060 print_req_error: 90 callbacks suppressed
' 0162064 print_req_error: 1/0 error, deu nncbike, sector 1214464
' 0166587 buffer_io_error: 90 callbacks suppressed
' 0166593 ] Buffer 10 error on dev mncb1k0p6, logical block o, lost async page urit.
' 01711711 print_req_error: 1/0 error, dev mmcblk0, sector 1214472
10173518 Buffer I0 error on dev mmcblk op6, logical block 1, lost async page urita
10175849 print_req_error: 1/0 error, deu ncbike, sector 1214480
' 0178095 Buffer 10 error on dev mncb1k0p6, logical block 2, lost async page write
10180483 print reg error: 1/0 error, deu nncbike, sector 1214488
0182859 Buffer 10 error on dev mmcblk0, logical block 3, lost async page urite

SD card is 32GB so I hope that is large enough. Yeah, starting to think it might have gotten corrupt somehow. I don’t want to have to rebuild this from scratch but I don’t have a recent backup, I don’t think.

Might be too small, don’t know how large your database is etc.

I think you should be able to put your SD card into your PC and extract the configuration files etc. from it.

And MAKE BACKUPS, it’s so easy with hass.io, will take approx. less than 1 minute to set it up.

didn’t know I could grab them off the windows partition. I will try that. Backups were broken for me and would never complete.

How do you get the config files extracted with a Windows PC? I am not seeing anything interesting.

With windows it may require some additional tools but under linux it should work out of the box.

Diskinternals Linux reader is free and easy to use.

2 Likes

Yes, I got that up and running. What files should I be looking for?

I think I found what I am looking for in:

/mnt/data 2/supervisor/homeassistant

Which files should I grab to not lose anything?

Everything in that folder including subfolders.

Alright, I am pretty sure my SD card died. I can’t format it or do anything with it. I bought a new one and loaded Hassio back on it. How do I get the recovered files back on it? I don’t have a Linux machine so I have to do this with Windows. I have tried some Linux partition tools and I can’t write to it, only read.

Linux will run from a USB thumbdrive as a live OS, and does not require installation onto the hardware.

So set up the new hassio, add SAMBA, and copy your backup file over to it.

Alright I will post here as I seem to be back up and running in case someone else has this issue.

Although I was getting read errors, I wanted to attempt a complete image of the SD card to see if it would work. I used Win32DiskImager and it claimed it made a bit for bit copy successfully. I ran it again and imaged a new SD card with the image and by some sort of miracle it booted right up. I took my backup immediately, as you can imagine. I successfully ran the latest update and so far, everything seems fine.

If that didn’t work, I had put PopOS on a thumb drive and I was going to boot into that and attempt to write the folder full of files I talked about a few posts above to a new install of Hassio. Luckily, it didn’t need to go that far.

One other thing. I would highly suggest your SD card purchases for this be the SanDisk High Endurance card. It is a card built for writing long term and is about the best at that. I was using a Sandisk Extreme Pro and it was still six months inside it’s warranty period. We’ll see if they replace it.