3- You have made error ...#### dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M conv=sync

[Polytropon]

On Sat, 31 Dec 2016 19:35:55 +0100, swjatoslaw gerus wrote:
> 1.bsd orig text
> ---------------------
> To burn the image using dd, insert the USB stick and determine its
> device name. 
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-pre.html
> -----------------------
> performed from author    with  fdisk -l   ... sdb1

This is wrong. As I said several times, /dev/sdb is the device
you need to write the image to, _not_ sdb1. Also fdisk is not
required in _any_ way here.




> 2.bsd orig text
> -------------------
> dd if=FreeBSD-10.2-RELEASE-amd64-memstick.img of=/dev/da0 bs=1M
> conv=sync

That is a fully valid FreeBSD command.



> multiple attempts with   FreeBSD -11.0   /dev/sdb1      bs=1M  ... 
> System( 16.04.1 64 bit  ubuntu)    -invalid argument

It has also been stated several times that a block size
of 1 MB can be expressed as 1M, 1m, and 1048576, depending
on what the dd version you're using does actually implement.
Again, /dev/sdb1 is the _wrong_ target device.



> bsd forum      suggest       not  1M but   1048576

Again, depends on the dd version. For FreeBSD's dd, bs=1M
works totally fine.



>  it is downloaded  ,can see after mounting with  more, not with ls -lsar 
> poweroff plugin   sandisk, notebook blocked black terminal

Again:

1.

You can see a file's content with "more" _without_ mounting.
But you don't _need_ to, and what you see is of no advantage
to you.

2.

You cannot mount a FreeBSD UFS partition natively on Ubuntu,
at least not without adding additional tools.

3.

It hasn't been clear if you ever mounted someting properly.

4.

After initializing the USB stick, boot it. Do not attempt to
mount it, it's neither required nor useful in any way.




> 3.  bsd forum suggest from multiplies authors      -11  
> 
>   Suggest is false      

I have no iead what you're refering to.



>  True  FreeBSD -11.0

That is also false. "FreeBSD 11.0-RELASE amd64" would be the
fully correct name of the version and architecture of the OS
to use. All this information is reflected in the file name
of the image, so you cannot accidentally use the wrong image
due to a naming misunderstanding.

It is up to you to use the _actual_ filename. Some examples
only say something like "dd if=filename.img of=/dev/da0 bs=1M",
and you need to replace "filename.img" with the actual name
of the image you want to use, instead of assuming that there
is some "magical file" filename.img that will reference the
correct actual image file. Placeholders are placeholders. :-)



> 4.  bsd  forum suggest  not   /dev/sdb1   as  in fdisk -l  but  /dev/sdb
> 
>  Suggest is true 

Of course it is. :-)



> in combination with  11.0 ,/dev/sdb, bs=1048576    can not  only
> downloaded
> but after poweroff,plugin,poweron  
> correct starten loader

As it should be.



> ls -lsar not work
> 
> performed  

Again:

It is neither needed nor helpful. I'd even say: Don't try it,
it won't work.



> 1.  cd  /     
> 2. mkdir  /mnt    
> 3. cd  /mnt
> 4. mount -f pcfs  /dev/sdb1   /mnt  (solaris writing )

The FreeBSD image does contain 4 partitions, _none_ of them
is a FAT32 ("pcfs") type file system.



> 5.ls -lsar  /mnt  ... root . root ..   nothing

An empty directory. As expected.



> 6. more  /dev/sdb1    -Yes  can see file with more

This doesn't help you in any way. Try "more /dev/sda" or
"more /dev/sda1", you can "view" your Linux partitions in
the same way - it doesn't do anything.




>  But that is not important ,as loader work -

It _is not_ important.



>  Will read freebsd about partioning and try perform next step

You will find the required information in the handbook. It
provides a good "script" on what will happen and which
decisions you can make.




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...