Fwd: for information was stated frofreebsd beforeFwd: Re: Fwd: dd -bs=BYTES read and write up to BYTES at a time system -invalid number 1m #### dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M conv=sync

[swjatoslaw gerus]

-- 
  swjatoslaw  gerus
  milstar2 at eml.cc

----- Original message -----
From: swjatoslaw gerus <milstar2 at eml.cc>
To: Warren Block <wblock at wonkity.com>
Subject: for information   was stated frofreebsd beforeFwd: Re: Fwd: dd
-bs=BYTES  read and write up to BYTES at a time        system -invalid 
number 1m   #### dd      if=FreeBSD-11-RELEASE-amd64-memstick.img
of=/dev/sdb1 bs=1M       conv=sync
Date: Sat, 31 Dec 2016 21:24:23 +0100

for information   was stated from freebsd before

was entry from author
#####################

>> fdisk -l
>> system  dev/sdb1      (new Sandisk ultrafit 16 gb)
>>
>>  dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M
>>  conv=sync

was answer from system
######################
 system -invalid  number 1m  

-----
some suggest from Freebsd

That is disscusion for developer or  sysadm,not for author,which try
to install first os in life

was forced to do that,after two installation linux   16.04 32bit and
16.04.1 64 bit from two different  sysadm
was performed with multiple errors
#################################


From: Valeri Galtsev <galtsev at kicp.uchicago.edu>
To: Polytropon <freebsd at edvax.de>
Cc: swjatoslaw gerus <milstar2 at eml.cc>, freebsd-questions at freebsd.org


 On systems that do not support size suffixes (such as
> Linux dd might), you need to "manually multiply", for
> example:
>
> 	dd if=<image> of=<device> bs=1024k
>
> Or, if the "k" suffix isn't supported,

To add to that: note that power of 2 is always a good idea. With block
devices matching _some_ number of blocks is always beneficial as, if bs=
"number of block + some fraction of block", then beginning from second
"count" there will be extra transfers to block device (even though the
result of dd will be OK, you are making it slower).

The vital where you _should_ use "bs=2048" i


-- 
  swjatoslaw  gerus
  milstar2 at eml.cc

----- Original message -----
From: Valeri Galtsev <galtsev at kicp.uchicago.edu>
To: Polytropon <freebsd at edvax.de>
Cc: swjatoslaw gerus <milstar2 at eml.cc>, freebsd-questions at freebsd.org
Subject: Re: Fwd: dd -bs=BYTES  read and write up to BYTES at a time    
   system -invalid  number 1m   #### dd     
if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M      
conv=sync
Date: Tue, 27 Dec 2016 13:32:09 -0600 (CST)


On Tue, December 27, 2016 12:08 pm, Polytropon wrote:
> On Tue, 27 Dec 2016 13:18:33 +0100, swjatoslaw gerus wrote:
>>
>>
>>
>> dd  help  ....dd -bs=BYTES  read and write up to BYTES at a time
>>
>>   system -invalid  number 1m   ####
>
> On systems that do not support size suffixes (such as
> Linux dd might), you need to "manually multiply", for
> example:
>
> 	dd if=<image> of=<device> bs=1024k
>
> Or, if the "k" suffix isn't supported,
>
> 	dd if=<image> of=<device> bs=1048576
>
> Note that this unit has to be converted as 2^10 = 2014
> (instead of 10^3 = 1000). See "man dd" to check what
> your version of dd implements.
>

To add to that: note that power of 2 is always a good idea. With block
devices matching _some_ number of blocks is always beneficial as, if bs=
"number of block + some fraction of block", then beginning from second
"count" there will be extra transfers to block device (even though the
result of dd will be OK, you are making it slower).

The vital where you _should_ use "bs=2048" is when you dump a track of
CD/DVD. (especially when doing recovery of badly damaged CD, then few
extra options are a must to make exact sector for sector copy or bit for
bit, even though in some unreadable areas they are are filled with
zeroes). The last is due to fact fact that data sector size it equal to
2048 on CD or DVD (think in the terms of 12 bit integer, they probably
expected poor programming, thus likely used 12 bit integer (11 bit value
+
1 bit sign) as opposed to 12 bit unsigned integer; but note, I'm just
guessing here).

I'm sure someone will add more details or correct me if I got something
wrong here.

Valeri

>
>
>> fdisk -l
>> system  dev/sdb1      (new Sandisk ultrafit 16 gb)
>>
>>  dd if=FreeBSD-11-RELEASE-amd64-memstick.img of=/dev/sdb1 bs=1M
>>  conv=sync
>> system -invalid  number 1m   ####
>
> The command is correct, just adjust the bs= parameter accordingly.
>
>
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
>


++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++

-- 
http://www.fastmail.com - Accessible with your email software
                          or over the web


-- 
http://www.fastmail.com - Or how I learned to stop worrying and
                          love email again