Tag Info

New answers tagged


What dd reads when you run dd if=/dev/cdrom of=foo2.iso is not a file (there is no such thing on a physical CD), but a number of 4KB sectors. If the length of the image file you wrote is not an exact multiple of 4KB = 4096, there will be some padding at the end. You can safely ignore it.


You're using Bash-like syntax and operators ($(command), ${...//}), but running it by sh, which on Android is not Bash by default.


Compressibility of a disk image depends a lot on what kind of data is stored in there, how much of it is used or has ever been used (without being explicitely erased during the whole life of that drive). In short, it's impossible to tell. 77% is completely plausible as are 0% (a disk full of videos/oggs) and 99% (an empty, recently erased with zeros disk). ...


I've just used a modified version on a virtual Linux Mint box to clone a physical hard drive on an ageing RedHat server. I ran the following as root on the virtual box: ssh root@ "dd if=/dev/cciss/c0d0" | dd of=/dev/sdb is the physical Red Hat Enterprise Linux 2.1 box. /dev/sdb is a new virtual disk, which when finished cloning ...


Those are incomplete reads. It should go away if you add iflag=fullblock. By default, dd will happily accept smaller blocks from a pipe, if there isn't more data readily available. With the iflag, dd will wait until a full block of data has been gathered, or EOF. In regards to data consistency there should be no issue, so you should be getting correct ...

Top 50 recent answers are included