Two issues with fresh install 14.2 on Pi 4

M

Michael Nayor

Issues with fresh install 14.2 on Pi 4

1. At boot (most times) I get Mounting from ufs:/dev/ufs/rootfs failed with error 19 and the prompt mountroot>. This a timeout whilst trying to mount the root file system from a 500MB USB SSD Disk. Is there a file where, for example, the timeout could be increased?

2. There are 8 versions of mdns in freshports.org. openmdns works, but is unmaintained, so which of the other 7 would be a better choice?
 
Michael Nayor said:
1. At boot (most times) I get Mounting from ufs:/dev/ufs/rootfs failed with error 19 and the prompt mountroot>. This a timeout whilst trying to mount the root file system from a 500MB USB SSD Disk. Is there a file where, for example, the timeout could be increased?
Click to expand...
Try in /boot/loader.conf kern.cam.boot_delay="10000". The value of "10000", if necessary, can be increased, or decreased.

From /boot/default/loader.conf
Code: 
#kern.cam.boot_delay="10000" # Delay (in ms) of root mount for CAM bus
                             # registration, useful for USB sticks as root

Question 2 I can't tell.
 
Michael Nayor said:
Issues with fresh install 14.2 on Pi 4

1. At boot (most times) I get Mounting from ufs:/dev/ufs/rootfs failed with error 19 and the prompt mountroot>. This a timeout whilst trying to mount the root file system from a 500MB USB SSD Disk. Is there a file where, for example, the timeout could be increased?

2. There are 8 versions of mdns in freshports.org. openmdns works, but is unmaintained, so which of the other 7 would be a better choice?
Click to expand...

2. I don't know if it can help but there is a thread that talks about it
S

Thread 'What is Zeroconf?'

Zeroconf (Zero Configuration) simplifies network configuration. It takes care of IP allocation for network devices so the user doesn't have to set this up manually. Zeroconf can be used even when DHCP isn't working correctly. With manual set up or with DHCP, two network devices can inadvertently be set for the same IP address and cause a conflict. Zeroconf makes sure that a network device is allocated to an IP address that is not occupied by another network connection. In Zeroconf, network administration uses device labels, rather than knowing IP addresses. These device labels are...
  • Thanks
  • Like

1. That's strange I don't have that delay, my RPI4 runs since 13.x, successfully updated to 14.x, now on 14.2, no SD card only a SSD drive connected via USB3, no keyboard or monitor, only serial connection if needed. I've used the image provided by FreeBSD nothing fancy.

Just in case here is my /boot/loader.conf, I can't tell if I've changed things here or not, I don't remember sorry.
Code: 
 ~ > cat /boot/loader.conf
# Configure USB OTG; see usb_template(4).
hw.usb.template=3
umodem_load="YES"
# Multiple console (serial+efi gop) enabled.
boot_multicons="YES"
boot_serial="YES"
# Disable the beastie menu and color
beastie_disable="NO"
loader_color="NO"[code]
 
This is not easy to diagnose. The first step though, when dumped out to a mount root prompt is to use the question mark. ?

It will list all available drives in your system. It contains alot of "gobblygook" but the key part is the end of every entry.

The "gobblygook" is disk UUID. A disk identifier. The second important part are the disk partitions. These are what you need to manually try.

ufs:/dev/mmcsd0p2 for example.

These problem can arise when /etc/fstab is pointing to the wrong disk partition. Usually we use disk labels but they can interfere sometimes.
 
Lots of helpful replies with maybe more to follow, but I'm away from home so won't be able to get back to this till the weekend. Thanks.
 
Phishfry said:
This is not easy to diagnose. The first step though, when dumped out to a mount root prompt is to use the question mark. ?
Click to expand...
Yups... in specific lsdev and lsefi are invaluable commands here.

With special mention of efi-show (+ -set & -unset), lsmod, lszfs and of course load and boot.

It's kind of mindblowing if you stop to think about what this critter can actually do for you. I totally gave up on Linux loaders like Grub and/or LILO because of it.
 
You must log in or register to reply here.
Back
Top