Date: Sun, 14 Jan 2024 13:58:20 +0000 From: Doug Rabson <dfr@rabson.org> To: Mark Millard <marklmi@yahoo.com> Cc: FreeBSD ARM List <freebsd-arm@freebsd.org>, Mike Karels <mike@karels.net> Subject: Re: RPi5 via EDK2 sitting idle: eventually got various "/: inode ???: check-hash failed" and . . . Message-ID: <CACA0VUio=cPzLnYUFtHFG38=w_0HYhVzryunT6bsiiWwzKeL_Q@mail.gmail.com> In-Reply-To: <00474FCE-E6FA-4112-B7C3-D4FA83410474@yahoo.com> References: <00474FCE-E6FA-4112-B7C3-D4FA83410474.ref@yahoo.com> <00474FCE-E6FA-4112-B7C3-D4FA83410474@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000b72340060ee84a68 Content-Type: text/plain; charset="UTF-8" On Sat, 13 Jan 2024 at 19:43, Mark Millard <marklmi@yahoo.com> 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 > root@releng3.nyi.freebsd.org:/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 --000000000000b72340060ee84a68 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Sat, 13 Jan 2024 at 19:43, Mark Mi= llard <<a href=3D"mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>> wr= ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px= 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(= 204,204,204);padding-left:1ex">I left the=C2=A0 RPi5 booted but idle and ha= d not looked at it<br> since. Well, I just looked and /var/log/messages shows:<br> <br> . . .<br> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2256]: New IP Address (ue0): 192= .168.1.153<br> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2260]: New Subnet Mask (ue0): 25= 5.255.255.0<br> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2264]: New Broadcast Address (ue= 0): 192.168.1.255<br> Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2268]: New Routers (ue0): 192.16= 8.1.1<br> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901792: check-hash faile= d<br> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901812: check-hash faile= d<br> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901796: check-hash faile= d<br> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901808: check-hash faile= d<br> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901821: check-hash faile= d<br> Jan 12 03:01:43 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > . . .<br> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979160: check-hash fai= led<br> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979164: check-hash fai= led<br> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979163: check-hash fai= led<br> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979154: check-hash fai= led<br> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 12 03:03:16 R64-RPi-4-3-2v1p2 kernel: /: inode 85979159: check-hash fai= led<br> Jan 12 03:03:16 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901792: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901793: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901809: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901812: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901794: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901795: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901796: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901797: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:01:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901798: check-hash faile= d<br> Jan 13 03:01:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > . . .<br> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979163: check-hash fai= led<br> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979154: check-hash fai= led<br> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979155: check-hash fai= led<br> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979158: check-hash fai= led<br> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:03:18 R64-RPi-4-3-2v1p2 kernel: /: inode 85979159: check-hash fai= led<br> Jan 13 03:03:18 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 67307605 at offset= 0: mangled entry<br> 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 51= 2: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:19 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 512: mangled entry<br> Jan 13 03:05:20 R64-RPi-4-3-2v1p2 kernel: /: bad dir ino 71554318 at offset= 8: mangled entry<br> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901792: check-hash faile= d<br> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901793: check-hash faile= d<br> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901809: check-hash faile= d<br> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901812: check-hash faile= d<br> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 04:15:42 R64-RPi-4-3-2v1p2 kernel: /: inode 901794: check-hash faile= d<br> Jan 13 04:15:42 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > . . .<br> Jan 13 04:15:45 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 04:15:45 R64-RPi-4-3-2v1p2 kernel: /: inode 85979159: check-hash fai= led<br> Jan 13 04:15:45 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 04:16:04 R64-RPi-4-3-2v1p2 kernel: /: inode 91271591: check-hash fai= led<br> Jan 13 04:16:04 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > Jan 13 04:16:04 R64-RPi-4-3-2v1p2 kernel: /: inode 91271627: check-hash fai= led<br> Jan 13 04:16:04 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times<br= > <br> # uptime<br> 10:53AM=C2=A0 up 2 days, 17:42, 2 users, load averages: 0.22, 0.23, 0.18<br= > <br> Unfortunately, this is my build, not an official snapshot test:<br> <br> # uname -apKU<br> FreeBSD R64-RPi-4-3-2v1p2 15.0-CURRENT FreeBSD 15.0-CURRENT #100 main-n2668= 76-e183039f0882-dirty: Sat Dec=C2=A0 9 08:18:38 UTC 2023=C2=A0 =C2=A0 =C2= =A0root@CA72-16Gp-ZFS:/usr/obj/BUILDs/main-CA53-nodbg-clang/usr/main-src/ar= m64.aarch64/sys/GENERIC-NODBG-CA53 arm64 aarch64 1500006 1500006<br> <br> . . .<br> So I've since rebooted the RPi5 with:<br> <br> # uname -apKU<br> FreeBSD generic 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-n267507-a61d2c7fb= d3c: Thu Jan 11 06:26:30 UTC 2024=C2=A0 =C2=A0 =C2=A0root@releng3.nyi.freeb= sd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 aarch64 1500008 150= 0008<br> <br> to see how it does. Technically the=C2=A0 USB3 media has the Rock64<br> snapshot with the msdosfs material copied over from the rpi-arm64<br> snapshot. But the microsd card has the EDK2 that is used.<br></blockquote><= div><br></div><div>I'm not sure if its related to your USB storage prob= lem but I did notice that at least one USB device in my setup disconnects a= nd reconnects every couple of minutes:</div><div><br></div><div>Jan 14 13:5= 4:32 freebsd14-rpi5 kernel: ugen0.4: <PixArt USB Optical Mouse> at us= bus0 (disconnected)<br>Jan 14 13:54:32 freebsd14-rpi5 kernel: ums0: at uhub= 2, port 4, addr 3 (disconnected)<br>Jan 14 13:54:32 freebsd14-rpi5 kernel: = ums0: detached<br>Jan 14 13:54:34 freebsd14-rpi5 kernel: ugen0.4: <PixAr= t USB Optical Mouse> at usbus0<br>Jan 14 13:54:34 freebsd14-rpi5 kernel:= ums0 on uhub2<br>Jan 14 13:54:34 freebsd14-rpi5 kernel: ums0: <PixArt U= SB Optical Mouse, class 0/0, rev 1.10/1.00, addr 3> on usbus0<br>Jan 14 = 13:54:34 freebsd14-rpi5 kernel: ums0: 3 buttons and [XYZ] coordinates ID=3D= 0<br>Jan 14 13:55:34 freebsd14-rpi5 kernel: ugen0.4: <PixArt USB Optical= Mouse> at usbus0 (disconnected)<br>Jan 14 13:55:34 freebsd14-rpi5 kerne= l: ums0: at uhub2, port 4, addr 3 (disconnected)<br>Jan 14 13:55:34 freebsd= 14-rpi5 kernel: ums0: detached<br>Jan 14 13:55:36 freebsd14-rpi5 kernel: ug= en0.4: <PixArt USB Optical Mouse> at usbus0<br>Jan 14 13:55:36 freebs= d14-rpi5 kernel: ums0 on uhub2<br>Jan 14 13:55:36 freebsd14-rpi5 kernel: um= s0: <PixArt USB Optical Mouse, class 0/0, rev 1.10/1.00, addr 3> on u= sbus0<br>Jan 14 13:55:36 freebsd14-rpi5 kernel: ums0: 3 buttons and [XYZ] c= oordinates ID=3D0<br></div><div><br></div><div>=C2=A0</div></div></div> --000000000000b72340060ee84a68--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACA0VUio=cPzLnYUFtHFG38=w_0HYhVzryunT6bsiiWwzKeL_Q>