FYI: Example mountroot time boot-success (da0) vs. "shutdown -r now" mountroot time failure (pass0 for some reason)

Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: Mark Millard <marklmi_at_yahoo.com>
Date: Sat, 15 Oct 2022 21:03:10 UTC
In the below, look for da0 vs. pass0 :

da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
da0: <Samsung PSSD T7 Touch 0> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number S5K5NJ0R108412D
da0: 40.000MB/s transfers
da0: 953869MB (1953525168 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>

vs.

pass0 at umass-sim0 bus 0 scbus0 target 0 lun 0
pass0: <  > Fixed Processor SCSI device
pass0: Serial Number S5K5NJ0R108412D
pass0: 40.000MB/s transfers
Mounting from ufs:/dev/gpt/BPIM3root failed with error 22; retrying for 3 more seconds
Mounting from ufs:/dev/gpt/BPIM3root failed with error 22: Invalid fstype.

From ---<<BOOT>>--- to the above show no differences
in the captured outputs, checked via a tool (BBEdit
on macOS). But I show more context below anyway.

Boot success:

---<<BOOT>>---
. . . (no differences) . . .
usbus1: 480Mbps High Speed USB v2.0
ugen1.1: <DWCOTG OTG Root HUB> at usbus1
uhub0 on usbus1
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
mmcsd0: 32GB <SDHC SL32G 8.0 SN 40D1A6D0 MFG 03/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-block
bcm2835_cpufreq0: ARM 900MHz, Core 250MHz, SDRAM 450MHz, Turbo ON
Release APs
Trying to mount root from ufs:/dev/gpt/BPIM3root []...
uhub0: 1 port with 1 removable, self powered
ugen1.2: <vendor 0x0424 product 0x9514> at usbus1
uhub1 on uhub0
uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on usbus1
uhub1: MTT enabled
Root mount waiting for: usbus1 CAM
uhub1: 5 ports with 4 removable, self powered
ugen1.3: <vendor 0x0424 product 0xec00> at usbus1
smsc0 on uhub1
smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus1
smsc0: chip 0xec00, rev. 0002
miibus0: <MII bus> on smsc0
smscphy0: <SMC LAN8700 10/100 interface> PHY 1 on miibus0
smscphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ue0: <USB Ethernet> on smsc0
ue0: Ethernet address: b8:27:eb:5e:35:df
Root mount waiting for: CAM
Root mount waiting for: CAM
ugen1.4: <Samsung PSSD T7 Touch> at usbus1
umass0 on uhub1
umass0: <Samsung PSSD T7 Touch, class 0/0, rev 2.10/1.00, addr 4> on usbus1
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
da0: <Samsung PSSD T7 Touch 0> Fixed Direct Access SPC-4 SCSI device
da0: Serial Number S5K5NJ0R108412D
da0: 40.000MB/s transfers
da0: 953869MB (1953525168 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
. . .

"shutdown -r now" failure:

---<<BOOT>>---
. . . (no differences) . . .
usbus1: 480Mbps High Speed USB v2.0
ugen1.1: <DWCOTG OTG Root HUB> at usbus1
uhub0 on usbus1
uhub0: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
mmcsd0: 32GB <SDHC SL32G 8.0 SN 40D1A6D0 MFG 03/2016 by 3 SD> at mmc0 50.0MHz/4bit/65535-block
bcm2835_cpufreq0: ARM 900MHz, Core 250MHz, SDRAM 450MHz, Turbo ON
Release APs
Trying to mount root from ufs:/dev/gpt/BPIM3root []...
uhub0: 1 port with 1 removable, self powered
ugen1.2: <vendor 0x0424 product 0x9514> at usbus1
uhub1 on uhub0
uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on usbus1
uhub1: MTT enabled
Root mount waiting for: usbus1 CAM
uhub1: 5 ports with 4 removable, self powered
ugen1.3: <vendor 0x0424 product 0xec00> at usbus1
smsc0 on uhub1
smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus1
smsc0: chip 0xec00, rev. 0002
miibus0: <MII bus> on smsc0
smscphy0: <SMC LAN8700 10/100 interface> PHY 1 on miibus0
smscphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ue0: <USB Ethernet> on smsc0
ue0: Ethernet address: b8:27:eb:5e:35:df
Root mount waiting for: CAM
Root mount waiting for: CAM
ugen1.4: <Samsung PSSD T7 Touch> at usbus1
umass0 on uhub1
umass0: <Samsung PSSD T7 Touch, class 0/0, rev 2.10/1.00, addr 4> on usbus1
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
pass0 at umass-sim0 bus 0 scbus0 target 0 lun 0
pass0: <  > Fixed Processor SCSI device
pass0: Serial Number S5K5NJ0R108412D
pass0: 40.000MB/s transfers
Mounting from ufs:/dev/gpt/BPIM3root failed with error 22; retrying for 3 more seconds
Mounting from ufs:/dev/gpt/BPIM3root failed with error 22: Invalid fstype.

Loader variables:
  vfs.root.mountfrom=ufs:/dev/gpt/BPIM3root

Manual root filesystem specification:
  <fstype>:<device> [options]
      Mount <device> using filesystem <fstype>
      and with the specified (optional) option list.

    eg. ufs:/dev/da0s1a
        zfs:zroot/ROOT/default
        cd9660:/dev/cd0 ro
          (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

  ?               List valid disk boot devices
  .               Yield 1 second (for background tasks)
  <empty line>    Abort manual input

mountroot> ?

 
FYI for the example, output line split for readability:

# uname -apKU
FreeBSD OPiP2E_RPI2v1p1 14.0-CURRENT FreeBSD 14.0-CURRENT #49
main-n258610-ba7319e9091b-dirty: Fri Oct 14 18:27:46 PDT 2022
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA7-nodbg-clang/usr/main-src/arm.armv7/sys/GENERIC-NODBG-CA7
arm armv7 1400072 1400072

Notes:

Technically, I strip an escape sequence that occurs a lot in
one chunk of the captured text and strip carriage returns as
well, to make the captures more readable before doing the
comparison. The captures span back into the RPi* firmware
output, not just the FreeBSD output.

===
Mark Millard
marklmi at yahoo.com