Displaying 3 results from an estimated 3 matches for "114.435".
2017 Mar 03
0
Solved Re: imaging a drive with dd
On 03/02/2017 11:57 PM, Robert Moskowitz wrote:
> The following worked:
>
> # dd if=/dev/sdb of=cubietruck.img bs=512 count=6268927
>
> 6268927+0 records in
> 6268927+0 records out
> 3209690624 bytes (3.2 GB, 3.0 GiB) copied, 114.435 s, 28.0 MB/s
>
> So bs= IS the drive blocksize.
>
> This is the result of trying a number of different values for bs and
> count.
2017 Mar 03
8
imaging a drive with dd
I am building a mailserver and with all the steps, I want to image the
drive at various 'checkpoints' so I can go back and redo from a
particular point. The image is currently only 4GB on a 120GB drive.
Fdisk reports:
Disk /dev/sdb: 111.8 GiB, 120034124288 bytes, 234441649 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size
2017 Mar 03
3
imaging a drive with dd
On Thu, Mar 02, 2017 at 09:06:52PM -0500, fred roller wrote:
> On Thu, Mar 2, 2017 at 8:36 PM, Robert Moskowitz <rgm at htt-consult.com>
> wrote:
>
> > dd if=/dev/sdb of=os.img bs=1M count=3210
> >
>
> I would recommend bs=512 to keep the block sizes the same though not a huge
> diff just seems to be happier for some reason and add status=progress if
> you