nanobsd image

Jack Mc Lauren jack.mclauren at yahoo.com
Sat Nov 10 08:26:12 UTC 2012


>It's hard to guess what's going on with a description of "messages

>like..." rather than the actual messages verbatim.  But if I had to
>guess at this point, I'd lean towards a difference between SATA devices
>being "ad0" and "ada0" which might be different between target systems
>based on the BIOS settings on each system for whether to present the
>drives as legacy/compatible IDE versus AHCI.  The options used to build
>the kernel also have some effect on ad0 vs ada0, but I'll admit to being
>in a complete state of confusion over that because of working on systems
>using 8.x, 9.x and 10.0 every day, and I've completely lost track of
>what behaviors are seen in which versions.

>-- Ian

Thank you Lan. this is the whole message, and what i do :

##################################################
If you have invalid mount options, reboot, and first try the
following from the loader prompt :
                set vfs.root.mountfrom.options=rw
And then remove the invalid mount options from /etc/fstab.
 
Loader variables:
vfs.root.mountfrom=ufs:/dev/da0s1a
vfs.root.mountfrom.options=ro
 
Manual root filesystem specifications:
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
                <fstype>:<device>
Mount <device> using filesystem <fstype>
da0 :      eg. Ufs:/dev/da0s1a
<UFD 2.0 Silicon-Power8G PMAP> Removable Direct Access
SCSI-4 device
                Eg. Cd9660:/dev/acd0
da0: 40.000MB/s transfers           This
is equivalent to:
mount –t cd9660 /dev/acd0/
da0: 7388MB (15130624 512 byte sector: 255H 63S/T 941C)
                ?              List valid disk boot devices
                <empty
line>     Abort manual input
mountroot >
mountroot>?
List of GEOM managed disk devices:
                da10s1a   da0s4   da0s3  da0s1   da0
###################################################

I have to set the mount root manually :
Mountroot>ufs:/dev/da0s1a
The system does not do this automatically. Fstab file is
correct as you can see the “loader variables”.
What’s the problem ? I am so confused !!!
The point is that we don’t dace this problem on one our
system !!!
by the way, I have copied the image on a flash memory.


More information about the freebsd-embedded mailing list