-
Notifications
You must be signed in to change notification settings - Fork 940
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raspberry Pi bootloop after 12.3 update (usb related) #3362
Comments
Same issue with Raspberry Pi 3, 32-bit, with Zooz ZST10 usb dongle. |
I tried reproducing the issue here but I might be still missing something that's triggering the issue, so I'd like to gather following information about your setups:
Also, the following logs from some of you will be very useful:
|
For me it's as follows:
As far as pattern goes. It all seems to be USB protocol controllers that are having issues. For me it's a Zwave usb controller, I think I saw zigbee controller usb as well. -EDIT- It's not my strongsuit, so couldn't get dmesg info. Is there a way to kinda freeze the system to stop everything else but CLI commands? Anyway, did manage to get the failed boot log, see below.
|
Closed accidentally |
|
Here:
|
dmesg log
ha host logs log
|
The following also crashes the system:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
@playaz44 This issue tracks booting problems in Raspberry Pi platform only. VM installations are running a different kernel version, please create a separate issue for that. Also, please check the host console when the issue occurs, something should be (hopefully) printed there. |
Similar issues in downgrading back to 12.2 as #3352 (comment) and #3352 (comment) |
I have found raspberrypi/linux#6100 that reported highly similar issue with 6.6 kernel a while ago, claiming 6.6.29 (which isn't in the stable branch yet) fixed the issue, so checking if it's the case for us might be worth a try as well. Here's a custom dev build with the latest RPi Linux from the master branch: If there's anyone who could give it a try (i.e. install it on an SD card and follow the same steps that lead to the boot loop with fresh 12.3), it would be much appreciated 🙏 Please note you need to be logged in on Github in order to download the artifacts, and that all the images are wrapped in an extra .zip archive, so you must first unpack that before you follow the standard flashing procedure. |
The 32-bit image resulted in the same crash unfortunately. |
I tried the rpi3-64 image, and got the same result. dmesg output
|
@mvdnes Thank you very much. Can you try adding |
Tested with the image from above, by only changing the cmdline parameters. Unfortunately, it still crashes for both of the options. |
@mvdnes Thank you, I finally managed to reproduce it reliably here too - starting Z-Wave add-on with Z-Wave.me UZB stick seems to crash it every time. I am not able to reproduce it with any of the Zigbee sticks I have here, even if I set up a simple testing network. It is also reproducible on RPi OS with the I will report this issue to the RPi kernel repo, but I want to make sure we're not chasing ghosts and the cause is the same. Can you retry (hopefully for the last time) and make sure the parameters are properly set? In
Just disabling the FSM is not sufficient. Alternatively, adding |
I have added the dmesg log of dwc_otg.fiq...=0
However, the config.txt line with dmesg log of dtoverlay=dwc2
|
@That-one-Joe Interesting, that is slightly different from what I see with the Z-Wave stick - there the system cannot recover when I just remove the USB stick (unless watchdog kicks in and reboots the device - are you sure it's not the case? You should be able to figure it out from the system uptime). Also I wonder if this issue is also resolved by adding |
I thought of a freeze at first too. But after connecting the pi to a monitor, the CLI clearly showed bootloop behavior. And if it was actually frozen, nothing would happen if I would disconnect the Z stick. But as it is not frozen but bootlooping, the first time it boots after the Z stick is disconnected it boots all the way (without the zwave functionality of course). If this is not the case for you, I'd advise creating a seperate issue. |
I can't comment without closing the issue for some reason. So re-opened again. |
Hi, |
Shut down the PI from HA and then done unplug the power cable to it. |
Updated all the way to: Then added dtoverlay=dwc2 to config.txt Can confirm this works with my Zwave stick. I did have to start Zwave JS, enable watchdog and start on boot. 2 full reboots of the Pi 3b+ after that, but then started working properly. Is stable for about 12 hours now. |
Not sure if this is a related issue or flaky hardware. I'm running HA-OS on a Pi5 with an SSD on an NVME Base and a PoE hat. I've got a USB2 extension running to a cheap USB2 3-port hub and that has dongles for Bluetooth, Zigbee and RFXCom. I've been having trouble not with boot loops but with all the devices on that USB connection going offline and showing initialisation failed, retrying. Sometimes an unplug and re-plug fixes it but mostly it requires a reboot. It could just be that the cheap USB2 hub was too cheap but I'm trying the dtoverlay option (I SSH'd to 22222 and then did "vi /mnt/boot/config.txt") to see whether stability improves. It previously ran for hours or a few days before failure so I'm going to be waiting for something to NOT happen but I'll come back and update either way. |
I have the usb drive connected to my pc, but i don't have the config.txt file. So what can I do? |
If you're definitely using HomeAssistant OS on a Raspberry Pi booting from a micro SD card there should be a small FAT partition that is recognised by Windows. You will probably need a USB reader for MicroSD cards to slot the card into. |
i found that partition, but no config.txt |
It's possible that your Pi isn't booting off that card and could instead be booting from something like an M.2 SSD or a USB memory stick. You might want to run that z.exe through virustotal as it could be malware. |
A quick how-to so you don't have to remove the SD Card to edit config.txt.
|
I need to foolproofly fix this without physical access to my pi4. Attaching to the container and creating new boot directories doesn't really sound foolproof to me. Is it realistic a further update with HAOS could resolve this? |
Just an FYI, my USB fell apart again after adding this option and required a reboot. Still not sure quite why but it doesn't look like it's related to this issue at least. I'll have to start digging through logs and open a different thread. If anything does suggest it's related, I'll come back :D Cheers all. |
It's my understanding this is a pi3(b)(+) specific kernel issue. So yes, your issue is different. |
@Cenedd Exactly, WilcoSnel is right, your issue seems to be a different one. I also think that some people took these steps unnecessarily, so the release notes have been adjusted to clarify what's the issue and how to work it around. In your case it's not clear what's the root cause, so complete Host logs would be helpful in this case - please open a different issue for that. |
@Caligo82 If you're already running HAOS 12.3 or 12.4 and your Pi doesn't lock up and/or reboot with the USB devices connected, you don't need to do anything. And if you're seeing any stability issues, same as above applies to you. |
Yes I'm currently running HAOS 12.3 on a Raspi4 with a Conbee II, and no Lockup yet. I thought this was introduced with 12.4. Earliest I will get physical access to this PI is in two weeks. So I'm hesitating to take the plunge here.... |
Same for me- HA crashed after that recent update. HA running on Pi4 with Sonoff Zibee 3.0 Hub |
Just tried again with the SonOff Zigbee hub unplugged- HA boots happily but how can I get the Zibee stuff working again?? |
This worked for me, but, instead to use ssh I've mounted the partition in my linux desktop. |
Im not sure this is related, I have HAOS on virtualbox and with zwave stick my VM freezes often and without its fine, on 12.4 |
Also mounted via Linux and the fix worked! Upgraded from 12.3 which my Zooz USB worked |
You just made my day! I've been trying to figure out why my system was crashing for a week. Before updates, the system would crash approximately every 2 to 3 days, then become unavailable for 24 to 48 hours. After the last updates, the system was completely stuck with the following configuration:
By unplugging the Zigbee key, I was able to access the system and disable the watchdog and autostart of Z2M, which allowed me to have access to HA. But of course no more automation including Z2M. Thanks thanks thanks ! @Pico1965, I had the same problem here because HA is not installed via Docker, so the command is not available. I was able to access the config.txt file by plugging the SSD (for my part) into another PC then mounting the partition via Gparted (under Linux) because the partition was not mounted automatically. The tip that helped me earlier in the discussion was to find the "small FAT partition". I hope that from now on the system will be more stable and that I will no longer have crashes after a few days! |
The |
Seems to be working here as well (RPi 3b):
|
Describe the issue you are experiencing
After upgrading to 12.3 my HA started bootlooping. Noticed that after I disconnected my Aeotec Z-Stick ZW090 it booted again and ran fine (without my Z wave network of course).
What operating system image do you use?
rpi3-64 (Raspberry Pi 3 64-bit OS)
What version of Home Assistant Operating System is installed?
12.3
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
No response
The text was updated successfully, but these errors were encountered: