fdisk -l .../dev/sdb1 system -invalid argument 1m #### dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M conv=sync

[swjatoslaw gerus]

fdisk -l 

/dev/sda1
...
/dev/sda6

/dev/sdb1  w95 FAT32

Solaris (11.2)  bs=16k freebsd=1m

Author performed that what freebsd stated  .in email to author.. 1048576

possibly new sandisk must formated for ubuntu,than possibly can see
file after mounting with ls -lsar,to  date can see with more

will check solaris ,freebsd,ubuntu publication




-- 
  swjatoslaw  gerus
  milstar2 at eml.cc

On Fri, Dec 30, 2016, at 11:19 PM, Polytropon wrote:
> On Fri, 30 Dec 2016 22:07:31 +0100, swjatoslaw gerus wrote:
> > this questions was answered before 
> > 
> > for linux   not 1m ,but  1048576 without suffiks
> > that work file is sended to /dev/sdb1
> 
> But read with caution: /dev/sdb (no "1" appended) needs to
> be the device the file has to be written to. Remember:
> /dev/sdb1 is the 1st partition of the 2nd disk unit,
> /dev/sdb1 is _the_ 2nd disk unit, and _that_ is where
> the image needs to go - it represents a whole device
> content.
> 
> 
> 
> > but  plug sandisk  16 gb before start , notebook can not start
> 
> This is to be expected because the stick hasn't been
> prepared correctly. Again:
> 
> 	# dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb bs=1M conv=sync
> 
> is the correct command here. That kind of mistake can
> be summarized as "fat fingers"... ;-)
> 
> 
> 
> > file after mounting can see with more, but can not see with ls -lsar
> 
> You can even "more /dev/sdb1" and "more /dev/sdb" without
> mounting it, there is no relation.
> 
> 
> 
> -- 
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...

-- 
http://www.fastmail.com - Email service worth paying for. Try it for free