Re: RPi5 via EDK2 sitting idle: eventually got various "/: inode ???: check-hash failed" and . . .

On Sat, 13 Jan 2024 at 19:43, Mark Millard <[email protected]> wrote:

> I left the  RPi5 booted but idle and had not looked at it
> since. Well, I just looked and /var/log/messages shows:
>
> . . .
> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2256]: New IP Address (ue0):
> 192.168.1.153
> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2260]: New Subnet Mask (ue0):
> 255.255.255.0
> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2264]: New Broadcast Address
> (ue0): 192.168.1.255
> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2268]: New Routers (ue0):
> 192.168.1.1
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901792: check-hash
> failed
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901812: check-hash
> failed
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901796: check-hash
> failed
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901808: check-hash
> failed
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901821: check-hash
> failed
> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> . . .
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979160: check-hash
> failed
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979164: check-hash
> failed
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979163: check-hash
> failed
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979154: check-hash
> failed
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979159: check-hash
> failed
> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901792: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901793: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901809: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901812: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901794: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901795: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901796: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901797: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901798: check-hash
> failed
> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> . . .
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979163: check-hash
> failed
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979154: check-hash
> failed
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979155: check-hash
> failed
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979158: check-hash
> failed
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979159: check-hash
> failed
> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 67307605 at
> offset 0: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1
> timesJan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 512: mangled entry
> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at
> offset 8: mangled entry
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901792: check-hash
> failed
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901793: check-hash
> failed
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901809: check-hash
> failed
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901812: check-hash
> failed
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901794: check-hash
> failed
> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> . . .
> Jan 13 04:15:45 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 04:15:45 R64-RPi-4-3-2v1p2 kernel: /: inode 85979159: check-hash
> failed
> Jan 13 04:15:45 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 04:16:04 R64-RPi-4-3-2v1p2 kernel: /: inode 91271591: check-hash
> failed
> Jan 13 04:16:04 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
> Jan 13 04:16:04 R64-RPi-4-3-2v1p2 kernel: /: inode 91271627: check-hash
> failed
> Jan 13 04:16:04 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
>
> # uptime
> 10:53AM  up 2 days, 17:42, 2 users, load averages: 0.22, 0.23, 0.18
>
> Unfortunately, this is my build, not an official snapshot test:
>
> # uname -apKU
> FreeBSD R64-RPi-4-3-2v1p2 15.0-CURRENT FreeBSD 15.0-CURRENT #100
> main-n266876-e183039f0882-dirty: Sat Dec  9 08:18:38 UTC 2023
>  root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA53-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA53
> arm64 aarch64 1500006 1500006
>
> . . .
> So I've since rebooted the RPi5 with:
>
> # uname -apKU
> FreeBSD generic 15.0-CURRENT FreeBSD 15.0-CURRENT #0
> main-n267507-a61d2c7fbd3c: Thu Jan 11 06:26:30 UTC 2024
>  [email protected]:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC
> arm64 aarch64 1500008 1500008
>
> to see how it does. Technically the  USB3 media has the Rock64
> snapshot with the msdosfs material copied over from the rpi-arm64
> snapshot. But the microsd card has the EDK2 that is used.
>

I'm not sure if its related to your USB storage problem but I did notice
that at least one USB device in my setup disconnects and reconnects every
couple of minutes:

Jan 14 13:54:32 freebsd14-rpi5 kernel: ugen0.4: <PixArt USB Optical Mouse>
at usbus0 (disconnected)
Jan 14 13:54:32 freebsd14-rpi5 kernel: ums0: at uhub2, port 4, addr 3
(disconnected)
Jan 14 13:54:32 freebsd14-rpi5 kernel: ums0: detached
Jan 14 13:54:34 freebsd14-rpi5 kernel: ugen0.4: <PixArt USB Optical Mouse>
at usbus0
Jan 14 13:54:34 freebsd14-rpi5 kernel: ums0 on uhub2
Jan 14 13:54:34 freebsd14-rpi5 kernel: ums0: <PixArt USB Optical Mouse,
class 0/0, rev 1.10/1.00, addr 3> on usbus0
Jan 14 13:54:34 freebsd14-rpi5 kernel: ums0: 3 buttons and [XYZ]
coordinates ID=0
Jan 14 13:55:34 freebsd14-rpi5 kernel: ugen0.4: <PixArt USB Optical Mouse>
at usbus0 (disconnected)
Jan 14 13:55:34 freebsd14-rpi5 kernel: ums0: at uhub2, port 4, addr 3
(disconnected)
Jan 14 13:55:34 freebsd14-rpi5 kernel: ums0: detached
Jan 14 13:55:36 freebsd14-rpi5 kernel: ugen0.4: <PixArt USB Optical Mouse>
at usbus0
Jan 14 13:55:36 freebsd14-rpi5 kernel: ums0 on uhub2
Jan 14 13:55:36 freebsd14-rpi5 kernel: ums0: <PixArt USB Optical Mouse,
class 0/0, rev 1.10/1.00, addr 3> on usbus0
Jan 14 13:55:36 freebsd14-rpi5 kernel: ums0: 3 buttons and [XYZ]
coordinates ID=0