Recently I searched for diskimage programs and came across this program http://www.dubaron.com/diskimage/ but I haven't tried it. That program is for windows. There are other 2 programs for linux which you might consider and they are for linux. Clonezilla (I wasn't succesful with that, due to other reasons, but might work for you) and the 2nd option which I prefer is g4u. g4u you rescue to ftp server. upload the files to a ftp server. This might help. I will try later today g4u and tell you. I use g4u to backup ntfs filesystems.
As for your questions: What makes you think that if you put another usb hd you will start from 137 and up? To recover file names try to look here: http://forums.getdata.com/computer-data-recovery/90-why-cant-recover-filenames.html Maybe their program will help. as for identifying the file name in the gz file, might be tricky. Usually the file name appears in the first line (header). So in general cat of the first line or head should do the trick. I did once such a thing on a movie. In the first line appeared the format of the file and the name. I could see it in Microsoft word. On Sat, Jan 3, 2009 at 9:31 AM, Amos Shapira <amos.shap...@gmail.com> wrote: > 2009/1/3 sara fink <sara.f...@gmail.com>: > > One thing that comes to mind is to do the following: > > > > boot with a knoppix or other livecd. ntfs will be mounted. Some of the > disk > > will be readable. In such case you can backup on other disk. > > > > after that boot windows with a recovery disk if you have. > > I already tried to use SysRescueCD 1.0 and Ubuntu live cd in rescue > mode to no avail. > > I connected the IDE drive via a clunky IDE->USB external enclosure > borrowed from a computer shop which read lots of data (with many > errors) until around 137Gb then stopped. I later read in Wikipedia > that 137Gb is the limit of pre-ATA-6 controllers > (http://en.wikipedia.org/wiki/AT_Attachment#Drive_size_limitations) so > maybe I hit that limit and have to find another external USB enclosure > (the disk is 200Gb) > > In the meantime, I also ran testdisk on the created image which > identified some partitions but said it can't recover any of them - at > least one of the partitions is larger than the "disk". > It all sits right with not having the full drive imaged (137Gb instead > of expected 200Gb). > I also ran photorec on the recovered image which extracted tons of > files but so far I haven't identified the ones I'm interested in - > photorec doesn't restore file names. > > BTW - is there a smart way to identify specifically compressed tar > files? Photorec gives them all ".gz" extension and "file" by itself > doesn't look into the .gz content to tell me the format inside it. I'd > rather avoid re-inventing this wheel if possible. > > Thanks, > > --Amos > > ================================================================= > To unsubscribe, send mail to linux-il-requ...@cs.huji.ac.il with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail linux-il-requ...@cs.huji.ac.il > >
