> I tried 'dd_rescue if=<partition> of=<steenking big file>' but didn't > succeed. > It told me repeatedly that <partition> wasn't a device or file. I don't know > why!
The partition table couldn't be read at boot during the first attempt, but ... > But on the other hand, knoppix had recognized it the second one worked. Nothing to do with distros. > the hd from being seen previously; using 'cp -r * <emergency partition>' can > sometimes work when 'dd_rescue if=<partition> of=<steenking big file>' won't Yes but that should have been obvious if the partition isn't full. dd_rescue copies the whole partition, therefore guaranteed all the faulty bits. cp -a copies all the files, which will miss those disk blocks not occupied by any file (or directory). If you're really lucky, all the damage is in usused disk blocks, though you'd probably only know of disk defects then if you were running smartmontools. If the primary objective is to rescue the files, try cp first. Resort to dd if the filesystem is damaged enough that files can't be found. Never attempt to fsck on the damaged disk unless you're out of other options (like lack of safe disk space). Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
