Hab allerdings diesen Beitrag gefunden:
dd usually the *ABSOLUTELY WRONG* tool to use for pushing around file
systems, since you have to issue the "count" command to cut off the dd
at the end of the partition absolutely correctly or you will leave off
the last few bits of your partition and filesystem, or start copying the
*next* partition and filesystem. It also guarantees you a dd image
exactly the size of the partition on disk instead of the size of the
file system, which may be *vastly* smaller and thus much easier to save
and faster to write.
http://forum.soft32.com/linux2/Resize-Partition-dd-ftopict45930.html
Wie dem auch sei, man kann ja immer noch mit dd images erstellen,(hoffe ich).
Hier ne Anleitung:
http://www.debianhelp.co.uk/ddcommand.htm
full hard disk copy
dd if=/dev/hdx of=/dev/hdy
dd if=/dev/hdx of=/path/to/image
dd if=/dev/hdx | gzip > /path/to/image.gz
Hdx could be hda, hdb etc. In the second example gzip is used to compress the image if it is really just a backup.
Restore Backup of hard disk copy
dd if=/path/to/image of=/dev/hdx
gzip -dc /path/to/image.gz | dd of=/dev/hdx
MBR backup
In order to backup only the first few bytes containing the MBR and the partition table you can use dd as well.
dd if=/dev/hdx of=/path/to/image count=1 bs=512
MBR restore
dd if=/path/to/image of=/dev/hdxAdd "count=1 bs=446" to exclude the partition table from being written to disk. You can manually restore the table.
Kommentare