Console errors galore

Installation Home Assistant OS
1

Hi

I am starting to get swathes of errors in the console, after having some issues where HA will occasionally hang and not be accessible via the web interface. After being rock solid for a year or two.

It is running on an Intel NUC, just as the full HA operating system.

I thought at first it was an issue with the onboard e1000e ethernet NIC, as some others have had issues with it on other Linux sites, but I suspect I have some corruption in the install on an update somewhere along the line, and this might be a red herring. Likely the Bluetooth issues too, but I’m no expert. The ext4-fs errors worry me.
It’s installed on the NVME drive, so unlikely it’s actually failing?

Sorry for just photos!

20231104_091114
20231104_0911141920×1440 330 KB

20231104_170545
20231104_1705451920×1440 396 KB

20231105_020736
20231105_0207361920×1440 454 KB

20231106_100320
20231106_1003201920×1440 121 KB

I wanted to run fsck, but no matter what I do, it wont let me as the umount doesn’t work; says it’s still busy.

Was using this from another thread:

systemctl stop systemd-journald
umount -A /dev/disk/by-label/hassos-data
fsck.ext4 /dev/disk/by-label/hassos-data

Any thoughts on what to try? Why I can’t unmount, and if fsck is the right path to chase?
Any other info from me that would help diagnose?

Thanks!!

2

You have both networking and storage issues. First I would try a USB ethernet adapter. Then see if the rest of the errors have been fixed.

3

Thanks - would I likely need to do anything such as disable the internal NIC in BIOS you think, or just chuck in the adapter and swap cables?
Will track one down to try and report back.

4

So sda8 is failing. I am not running a supported system so my questions here might be irrelevant. First, is /dev/sda8 a system drive or a drive for HA? If you can access your /etc/fstab file, you may be able to disable this drive from mounting, but could be detrimental without not knowing your setup. You might be able to also use the command #lsof which will show what files have been launched and are presently opened on that device. Kill them, then un-mount the drive. Should work unless it’s your boot device (which would be unusual).

5

It would be best practice is you disable the NIC in BIOS, so system does not see it and attempt to load the drivers.

6

I wish I understood half of what you are saying, haha!
It’s just a NUC7i3BNK with the one SSD drive, with Home Assistant OS installed directly, so no other drives or special partitions.

7

So I managed to get FSCK to work, which cleared the EXT4 errors, but I still have tonnes of the Bluetooth errors.

Are you saying my SSD might be failing?

20231108_081004
20231108_0810041920×1440 468 KB

Where to go next?

8

I suggest you try to disable Bluetooth and then test if everything works. If it does enable BT and try to fix that. One step at a time.

9

Thanks, this cleared it. Who knows. Disabled the NUCs Bluetooth in BIOS - gave up on it, and got a USB unit with a nice big antenna.