after dd freebsd performed, tryed check /dev/sdb1(notebook can not start with flash)
freebsd at edvax.de
Fri Dec 30 14:43:39 UTC 2016
On Fri, 30 Dec 2016 02:32:56 +0100, swjatoslaw gerus wrote:
> after dd freebsd and solaris on new sandisk ultrafit 16gb
> performed,tryed check /dev/sdb1(notebook can not start with flash)
How "and"? How did you manage to put two (!) images on
one and the same boot media? This looks wrong.
If you prepare a FreeBSD boot USB stick with the memstick
image, using dd, this stick will boot FreeBSD (_from_ the
stick), nothing else.
> 1. fdisk -l ...dev/sdb1 c W95 FAT32 (LBA)
That looks wrong as well. A FreeBSD memstich, if created
properly, does not look like a FAT32 file system.
> 2.mkdir /home/user/mnt
> 3.mount -f pcfs /dev/sdb1 /home/user/mnt
That shouldn't even be possible with a properly written
FreeBSD image. From "man mount_pcfs" (Solaris):
mount attaches an MS-DOS file system (pcfs) to the
file system hierarchy at the mount_point, which is
the pathname of a directory. If mount_point has any
contents prior to the mount operation, these are
hidden until the file system is unmounted.
I'm not sure what you did (successfully?) mount, but it
doesn't really look like anything FreeBSD-related...
> or ubuntu 16.04 not compatible
I cannot imagine that it should be impossible to create a
FreeBSD USB stick from Ubuntu. You don't need more than dd
and the memstick image. CHeck your process again, compare
to the online documentation.
> 4.more /dev/sdb1
> some great file started with
> Loading keymap
> oadertoo large
> Non-system disk
> Press any key to reboot
> folloving text not readable
It is _not_ a text file, so you cannot display it with
the "more" pager. You're literally reading the stick,
and at its beginning, there is binary (!) boot code,
which you cannot actually read. :-)
Instead, after mounting, you should have issued the
# ls /home/user/mnt
so you can check what's on the media - on a file system
level, not on "bare bits & bytes". ;-)
> what is false ? must be cleaned for second dd attempt ?
In best case, remaining data is overwritten by dd, so
there is no need to remove anything prior to a new
> or problem is multiboot scenario ?
It shouldn't be. Booting from USB should have priority
over whatever is stored on the computer's hard disk.
Again, make sure that your PC's BIOS/UEFI has booting
from USB enabled.
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
More information about the freebsd-questions