From nobody Sun Jan 14 13:58:20 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TCcLZ2cjBz56DX1 for ; Sun, 14 Jan 2024 13:58:30 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TCcLZ0NSlz59H2 for ; Sun, 14 Jan 2024 13:58:30 +0000 (UTC) (envelope-from dfr@rabson.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x72f.google.com with SMTP id af79cd13be357-7833b6bb41bso334332585a.3 for ; Sun, 14 Jan 2024 05:58:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabson-org.20230601.gappssmtp.com; s=20230601; t=1705240709; x=1705845509; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=d/FCc9mRqKJd4KiR5cIvzLAPx9zDZI4sj0C/5ffyRuU=; b=vY0aZELOpWzSB8msxIHqEthSH0S0faVSpt+sOwtFBXa4M8DBZCpGGwnqZQ5kX5rt8v /Ou0Z6nHZUJnvus3qTbnoFQSSPIa5MmohTQWzVvfAN/ffXEoADANMbUyK3HH7jFZOHoQ o86i8CXJknc2KM4kVRCBHpVDoaMFwAkRR9mUhE6Ykzr+VDuAmTr8cieaV5s1rw3BgQKh UET4uR7HMbYpb+NvNKQHz3HEi5w833GvYJcCBXex/girWozAbdLlfd7afbk7MeCbnVsW Pk0Pa/ec9MP75l61qCTdSFuf/VIe0bwtYMWO30No/k5iVy6Il0++jvj+Ckbg7y8RdKvr RumA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705240709; x=1705845509; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=d/FCc9mRqKJd4KiR5cIvzLAPx9zDZI4sj0C/5ffyRuU=; b=YjeqD3UUhyGRzuHzZ78lYfVrGMYrT/FE+m3ppJalhuef3A40c5wH0Xhyg+z2i4kKR7 JJZHKy2GNfcpgwB429FA+AAcF5zHI0YfawOTNiKxvYgSCtRCE8GFkQvsCDE4n14qpY/9 P9PPW6aaAAUtT1H06cDP29dA6/dbEgkYk62LoPltWexAytzEUcHw8uDBm1dr2I7jj2qh 1a5UlUzWrGbxp6UbVCr40cpuexAMgrcKITHXNSLWRfFAROb6Z82y0HScf/7fUDcgSwUu AVwflyEEZSXrPvlGIPvo0eD69GZoK0tLgF3iOX2yR12DCn3ZMyPaXI8IbNtWl24D/tlx 35JA== X-Gm-Message-State: AOJu0YxSEjejcdzm6iWujqyIAADbSOBgnHMrrJ09yw84K3iZrHm0ik69 /mxruNr/toKnTUiQK1RUwboIxv8e0fWUOg4EPWPXXouiJwUYSA== X-Google-Smtp-Source: AGHT+IFkBEyqLQ0z/wD2RNVX191wd5XdMBXSo2GpXmbaZxylVxnE38Hczz6Fn5g6+I3Lk1UYyrzpkO57xXc3E3/bMWc= X-Received: by 2002:ae9:e915:0:b0:783:47b:b1d1 with SMTP id x21-20020ae9e915000000b00783047bb1d1mr4943298qkf.115.1705240708974; Sun, 14 Jan 2024 05:58:28 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <00474FCE-E6FA-4112-B7C3-D4FA83410474.ref@yahoo.com> <00474FCE-E6FA-4112-B7C3-D4FA83410474@yahoo.com> In-Reply-To: <00474FCE-E6FA-4112-B7C3-D4FA83410474@yahoo.com> From: Doug Rabson Date: Sun, 14 Jan 2024 13:58:20 +0000 Message-ID: Subject: Re: RPi5 via EDK2 sitting idle: eventually got various "/: inode ???: check-hash failed" and . . . To: Mark Millard Cc: FreeBSD ARM List , Mike Karels Content-Type: multipart/alternative; boundary="000000000000b72340060ee84a68" X-Rspamd-Queue-Id: 4TCcLZ0NSlz59H2 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] --000000000000b72340060ee84a68 Content-Type: text/plain; charset="UTF-8" On Sat, 13 Jan 2024 at 19:43, Mark Millard 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: 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: at usbus0 Jan 14 13:54:34 freebsd14-rpi5 kernel: ums0 on uhub2 Jan 14 13:54:34 freebsd14-rpi5 kernel: ums0: 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: 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: at usbus0 Jan 14 13:55:36 freebsd14-rpi5 kernel: ums0 on uhub2 Jan 14 13:55:36 freebsd14-rpi5 kernel: ums0: 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


=
On Sat, 13 Jan 2024 at 19:43, Mark Mi= llard <marklmi@yahoo.com> wr= ote:
I left the=C2=A0 RPi5 booted but idle and ha= d 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): 25= 5.255.255.0
Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2264]: New Broadcast Address (ue= 0): 192.168.1.255
Jan 11 05:11:32 R64-RPi-4-3-2v1p2 dhclient[2268]: New Routers (ue0): 192.16= 8.1.1
Jan 12 03:01:43 R64-RPi-4-3-2v1p2 kernel: /: inode 901792: check-hash faile= d
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 fai= led
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 fai= led
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 fai= led
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 fai= led
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 fai= led
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 fai= led
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 fai= led
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 fai= led
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 fai= led
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 fai= led
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 51= 2: 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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 faile= d
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 fai= led
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 fai= led
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 fai= led
Jan 13 04:16:04 R64-RPi-4-3-2v1p2 syslogd: last message repeated 1 times
# uptime
10:53AM=C2=A0 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-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

. . .
So I've since rebooted the RPi5 with:

# uname -apKU
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

to see how it does. Technically the=C2=A0 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.
<= 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:

Jan 14 13:5= 4:32 freebsd14-rpi5 kernel: ugen0.4: <PixArt USB Optical Mouse> at us= bus0 (disconnected)
Jan 14 13:54:32 freebsd14-rpi5 kernel: ums0: at uhub= 2, 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: <PixAr= t 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 U= SB 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=3D= 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 kerne= l: ums0: at uhub2, port 4, addr 3 (disconnected)
Jan 14 13:55:34 freebsd= 14-rpi5 kernel: ums0: detached
Jan 14 13:55:36 freebsd14-rpi5 kernel: ug= en0.4: <PixArt USB Optical Mouse> at usbus0
Jan 14 13:55:36 freebs= d14-rpi5 kernel: ums0 on uhub2
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
Jan 14 13:55:36 freebsd14-rpi5 kernel: ums0: 3 buttons and [XYZ] c= oordinates ID=3D0

=C2=A0
--000000000000b72340060ee84a68--