From owner-freebsd-questions@freebsd.org Sat Dec 31 20:25:09 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF9DEC99FD5 for ; Sat, 31 Dec 2016 20:25:09 +0000 (UTC) (envelope-from milstar2@eml.cc) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A61951688 for ; Sat, 31 Dec 2016 20:25:09 +0000 (UTC) (envelope-from milstar2@eml.cc) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4E0BB20937 for ; Sat, 31 Dec 2016 15:25:08 -0500 (EST) Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Sat, 31 Dec 2016 15:25:08 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=eml.cc; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=pgwnhugihCTt1VdvsjoYa2TYh2I=; b=F8HRtFLBbsySU76lGmHc0 f+bCyspNckxiULpqUxRBwpZvJMjH5ZcxtZAzpQ+dNBwjeGaOfBa/Jq7xWFuesMVs DWif46MbPoAM37RvXCs40bqVgSmNHELgJnh6OUSp1zJuU8ki48NdvQz4eKiobhIw 4V+fWRUytgjOFvPREuPPas= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=smtpout; bh=pgwnhugihCTt1VdvsjoYa2TYh 2I=; b=cyW3dQD23w5Lem9+1UjHAkvucaeMdB8zmWN1FcCFYDUyssicn76FCQY8K Fx9VZZs34GFOBXIBi8NLfp1YmkbyZs4W8MZbm8ItKMitbBYE/PFhZhCRuNvrNt9S ahpoognrTiqJ8OMkKIJ+g7x/13358ooRnctC7It2xeLw706sb8= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 29964626D0; Sat, 31 Dec 2016 15:25:08 -0500 (EST) Message-Id: <1483215908.1994765.833908401.0AE6ACB0@webmail.messagingengine.com> From: swjatoslaw gerus To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-9c115fcf Date: Sat, 31 Dec 2016 21:25:08 +0100 X-Forwarded-Message-Id: <1483215863.1994746.833907873.3CB0C246@webmail.messagingengine.com> Subject: 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 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 20:25:09 -0000 -- swjatoslaw gerus milstar2@eml.cc ----- Original message ----- From: swjatoslaw gerus To: Warren Block 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 To: Polytropon Cc: swjatoslaw gerus , freebsd-questions@freebsd.org On systems that do not support size suffixes (such as > Linux dd might), you need to "manually multiply", for > example: > > dd if= of= 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@eml.cc ----- Original message ----- From: Valeri Galtsev To: Polytropon Cc: swjatoslaw gerus , freebsd-questions@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= of= bs=1024k > > Or, if the "k" suffix isn't supported, > > dd if= of= 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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@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