Help using dd
in [UK Linux]
|
Prev: Firefox/DNS problem, possibly due to two ADSL lines, advice needed
Next: spamassassin with thunderbird
From: alexd on 4 Dec 2009 13:59 Meanwhile, at the uk.comp.os.linux Job Justification Hearings, Simon J. Rowe chose the tried and tested strategy of: > jasee wrote: > >> Thanks but I'm stupid: would the path to the file be >> of=/hdc/path/to/filename? > > Yes, i == input, o == output, Just for the sake of clarity, if you've got something mounted on /hdc/ then that's correct. If you're thinking that /hdc is a device name, then no, it's not correct. -- <http://ale.cx/> (AIM:troffasky) (UnSoEsNpEaTm(a)ale.cx) 18:34:30 up 6 days, 22:24, 7 users, load average: 0.07, 0.27, 0.43 Plant food is a made up drug
From: jasee on 4 Dec 2009 14:17 Simon J. Rowe wrote: > jasee wrote: > >> I'm using dd to recover a corrupt partition or a least some of the >> files in it, >> The basic command is dd if=/dev/some source partition if=/dev/some >> target bs=4096 conv=notrunc,noerror >> This is from an NTFS partition to an NTFS partition, is it possible >> to send >> this to a file rather than a partition? and how would I do this if >> it was on another partition eg hdc? > > If the disk has bad sectors then you want dd_rescue instead, > Whats the advantage? Some versions dd_rescue and ddrescue (seperately maintained, I know) will copy in reverse if there is a bad block, but simple dd will continue using 'noerror' AFAICT.
From: jasee on 4 Dec 2009 14:27 alexd wrote: > Meanwhile, at the uk.comp.os.linux Job Justification Hearings, Simon > J. Rowe chose the tried and tested strategy of: > >> jasee wrote: >> >>> Thanks but I'm stupid: would the path to the file be >>> of=/hdc/path/to/filename? >> >> Yes, i == input, o == output, > > Just for the sake of clarity, if you've got something mounted on > /hdc/ then that's correct. If you're thinking that /hdc is a device > name, then no, it's not correct. Well the device is /dev/hdc1 actually (two partitions hdc1 and hdc2) so is it of=/hdc1/path/to/filename? I haven't created a seperate mount point.
From: Simon J. Rowe on 4 Dec 2009 17:20 jasee wrote: > Whats the advantage? Some versions dd_rescue and ddrescue (seperately > maintained, I know) will copy in reverse if there is a bad block, but > simple dd will continue using 'noerror' AFAICT. But dd will merely skip the bad block so you'll have a hole in your FS. dd_rescue will (at worst) substitute a block of zeros so you have a chance of rescuing data. Simon
From: Denis McMahon on 4 Dec 2009 17:46
jasee wrote: > alexd wrote: >> Meanwhile, at the uk.comp.os.linux Job Justification Hearings, Simon >> J. Rowe chose the tried and tested strategy of: >> >>> jasee wrote: >>> >>>> Thanks but I'm stupid: would the path to the file be >>>> of=/hdc/path/to/filename? >>> Yes, i == input, o == output, >> Just for the sake of clarity, if you've got something mounted on >> /hdc/ then that's correct. If you're thinking that /hdc is a device >> name, then no, it's not correct. > > Well the device is /dev/hdc1 actually (two partitions hdc1 and hdc2) so is > it > > of=/hdc1/path/to/filename? > > I haven't created a seperate mount point. If it was auto mounted by fuse, system might have put it in /media/some_drive If you mounted it manually, you must have given it a mount point. What does the output of "mount" say? There should be a line in that output showing the /dev/(h|s)d?[n] and the associated mount point, eg /dev/sdf on /media/TREKSTOR Rgds Denis McMahon |