Solved [solved] FreeBSD 12.1 memstick install crash at boot

Pascal.D

New Member


Messages: 3

Hello,

I am trying to do a fresh install (my first install since FreeBSD 7).

I use the following image: FreeBSD-12.1-RELEASE-i386-memstick.img
The hardware is a Samsung NC-10 (non modified).
The hardware does not seem to have any issue. Windows XP and Linux are still running on it and do not report any hardware fault.
My goal is to replace them with FreeBSD.

I did not find a way to capture the boot log.
So please find below everything I can see.

When I boot from the USB stick, the boot process start crashing after "Starting devd."
I get:
Code:
  devd: bind: No such file or directory
  /etc/rc: WARNING: failed to start devd
I may miss a previous error, but the screen size does allow me to see more.
This may be enough as the following errors may be due to this one, but for the the sake of completeness, the following errors then occur:

After "Generating host.conf."
I get:

Code:
eval: cannot create /etc/host.conf: Read-only file system
repeated 3 times.

Then after "Creating and/or trimming log files
I get:

Code:
eval: cannot create /var/run/syslogd.sockets: No such file or directory
Then after "Starting syslog."
I get:

Code:
eval: cannot open pid file: No such file or directory
  protect: option requires en argument -- p
  Usage: protect [-i] command
              protect [-cdi] -g pgrp | -p pid
  ld-elf.so.1: assert failed: /usr/src/libexec/rtld-eld/rtld.c:1035
When I boot in single user mode I can go to the shell.
I have tried to get the boot log with dmesg (in single user mode) but I get:

Code:
ld-elf.so.1: /lib/libelf.so.2: unsupported file version
That's all I can say for the moment.

Regards,
Pascal.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 9,286
Messages: 33,826

Make sure you verify the checksum before burning. It's possible your earlier issues were caused by a corrupted image file (corrupted during download).
 
OP
P

Pascal.D

New Member


Messages: 3

So, finally, it works, with all versions.

SirDice:

I verified the checksum and the syntax of my dd command.

Yes it was a corruption. But not of the image file.
The culprit is the USB key. Somewhere in the middle of the key blocks are dead.
This does not prevent the boot, but creates random crash.

I did not suspect this because the key is quite new and has been barely used, and dd did not report any errors.

Regards,
Pascal.
 
Top