search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
5.06k stars 992 forks source link

USB drive reboot loop on 13.1 #3558

Open pafnow opened 3 months ago

pafnow commented 3 months ago

Describe the issue you are experiencing

Since I upgrade to 13.1, my HA OS box keeps restarting. After reboot, and fsck command is started on my USB connected drive. If I unplug the drive, no fsck is launched and no reboot happen. I looked at journalctl and see this error : 

Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
 0000: f0 00 01 00  00 00 00 0a  00 00 00 00  00 1d 00 00    ................
 0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
 (g-io-error-quark, 0)

Seems to be related to https://github.com/storaged-project/udisks/issues/1153

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

13.1

Did the problem occur after upgrading the Operating System?

Yes

Hardware details

HP EliteDesk 800 G1 USB connected WD 2.5 inch drive

Steps to reproduce the issue

NA

Anything in the Supervisor logs that might be useful for us?

Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdb': Unexpected sense data returned:
 0000: f0 00 01 00  00 00 00 0a  00 00 00 00  00 1d 00 00    ................
 0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
 (g-io-error-quark, 0)

### Anything in the Host logs that might be useful for us?

```txt
Seems to be related to https://github.com/storaged-project/udisks/issues/1153

System information

No response

Additional information

No response

github-actions[bot] commented 1 day ago

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.