r324353: boot failure: failed with error 19

[Warner Losh]

On Fri, Oct 6, 2017 at 6:10 AM, O. Hartmann <ohartmann at walstatt.org> wrote:

> I run a small appliance on an APU from PCengines. This box is bootet via
> SD card, the
> image is created by a modified NanoBSD, which creates GPT/UEFI
> partitioning and booting
> images.
>
> That worked until two days ago (I do not track the revision numer) when I
> wrote (via dd)
> the last image out. Today, I tried to boot r324353 and it fails at tthe
> boot loader:
>
>
> mountroot: waiting for device /dev/ufs/dsks1a...
> Mounting from ufs:/dev/ufs/dsks1a failed with error 19.
>

That's odd... But likely a race....  It could be that dd'ing the new
partition, however, was made from an image that didn't have the proper ufs
label.

What's the rev of the last version that worked?

Warner


> I can proceed by manually issuing at the loader propmpt
>
> ufs:/dev/gpt/dsks1a
>
> and booting proceeds as expected.
>
>
> Something seems wrong with the UFS labeling lately.
>
> The gpt layout looks like this:
>
> gpart show -l:
>
> =>      40  60751792  mmcsd0  GPT  (29G)
>         40       130       1  boot  (65K)
>        170         6          - free -  (3.0K)
>        176   2057288       2  dsks1a  [bootme]  (1.0G)
>    2057464   2061725       3  dsks2a  (1.0G)
>    4119189   1048576       4  dsks3  (512M)
>    5167765  55584067          - free -  (27G)
>
> From dmesg. I can provide this last output:
>
> [...]
> mmcsd0: 31GB <SDHC SD32G 3.0 SN 01801299 MFG 09/2015 by 39 PH> at mmc0
> 50.0MHz/4bit/65535-block Trying to mount root from ufs:/dev/ufs/dsks1a
> [ro]...
> uhub0: 4 ports with 4 removable, self powered
> Root mount waiting for: usbus1
> uhub1: 2 ports with 2 removable, self powered
> Root mount waiting for: usbus1
> ugen1.2: <vendor 0x0438 product 0x7900> at usbus1
> uhub2 on uhub1
> uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on
> usbus1
> uhub2: 4 ports with 4 removable, self powered
> mountroot: waiting for device /dev/ufs/dsks1a...
> Mounting from ufs:/dev/ufs/dsks1a failed with error 19.
>
> Loader variables:
>   vfs.root.mountfrom=ufs:/dev/ufs/dsks1a
>   vfs.root.mountfrom.options=ro
>
> Manual root filesystem specification:
>   <fstype>:<device> [options]
>       Mount <device> using filesystem <fstype>
>       and with the specified (optional) option list.
>
>     eg. ufs:/dev/da0s1a
>         zfs:tank
>         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> Trying to mount root from ufs:/dev/ufs/dsk1a\^[[D\^[[D\^[[D\^[[Cs
> []...
> mountroot: waiting for device /dev/ufs/dsk1a\^[[D\^[[D\^[[D\^[[Cs...
> random: unblocking device.
> arc4random: no preloaded entropy cache
> Mounting from ufs:/dev/ufs/dsk1a\^[[D\^[[D\^[[D\^[[Cs failed with error
> 19.
>
> mountroot> Invalid file system specification.
>
> mountroot> Trying to mount root from ufs:/dev/gpt/dsks1a []...
> arc4random: no preloaded entropy cache
> GEOM_ELI: Device gpt/swap.eli created.
> GEOM_ELI: Encryption: AES-XTS 128
> GEOM_ELI:     Crypto: hardware
> Link state changed to up
>
> [...]
>
>
> Can someone look into this?
>
> Kind regards,
>
> Oliver
> --
> O. Hartmann
>
> Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
> Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
>