/bin/sh: Shared object has no run-time symbol table

mbzadegan

Active Member

Reaction score: 3
Messages: 184

Hi,

I was booting from FreeBSD-10.0-BETA3-amd64-memstick.img but my PC stopped at:

Code:
/bin/sh: Shared object has no run-time symbol table
Enter full pathname of shell or RETURN for /bin/sh:

At this state I entered /bin/csh but the FreeBSD installer did not start. How can I run the FreeBSD installer to install FreeBSD from a memory stick onto my HDD partition?
 

kpa

Beastie's Twin

Reaction score: 1,848
Messages: 6,318

I can not replicate this issue on i386 version of the same memstick image. Are you sure the USB stick you used is a good one? How did you write the image to the stick?
 
OP
mbzadegan

mbzadegan

Active Member

Reaction score: 3
Messages: 184

kpa said:
I can not replicate this issue on i386 version of the same memstick image. Are you sure the USB stick you used is a good one? How did you write the image to the stick?

With two different pen drives, I run:

# dd if="FreeBSD-10.0-BETA3-amd64-memstick.img of=/dev/da0 bs="10240" conv="sync"
 

wblock@

Beastie Himself
Developer

Reaction score: 3,740
Messages: 13,851

Do not use quotes with dd(1) parameters:
dd if=FreeBSD-10.0-BETA3-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

The bs value is from decades ago, and conv=sync will only help if the file is corrupted... when it would be better off failing. So I'd use:
dd if=FreeBSD-10.0-BETA3-amd64-memstick.img of=/dev/da0 bs=64k

However, I doubt that this would cause the problem shown in post #1.
 

kpa

Beastie's Twin

Reaction score: 1,848
Messages: 6,318

I also tried the AMD64 memstick image and still couldn't reproduce this problem. There must be something peculiar about the machine you're using that causes the installer to fail.
 

phoenix

Administrator
Staff member
Administrator
Moderator

Reaction score: 1,290
Messages: 4,099

Start investigating the hardware on that system.

Run a RAM checker, double-check all the cables are seated correctly, make sure your PSU is powerful enough, reseat all the PCI/e cards, run a CPU checker, etc.
 
Top