HD Data Recovery
category: offtopic [glöplog]
Again: Don't try to fix the original disk! Just salvage what you can. As long as you still can...
Quote:
I'm totally lost on what you are actually doing right now.
raer: i don't do shit right now. I have a break. The last thing i did was running spinrite over the night and it only came to 7.7% founding mostly unrecovered sectors.
what do you mean by not fixing the original disk? you mean doing it physical or using other tools (like spinrite)? i am not doing anything physical to it, until its my last option which i will not until ive tried everything. well, since spinrite allready claimed there was alot of unrecovered sectors and it took ages to get there, it may be that the whole shit is totally b0rked anyway. i think i have an early redhat linux distro on a cd somewhere. downloading a new one will take ages on this slow inet connection. blah. but yes, as long as i can have access to both disks (the real working one on my laptop now and the defected one (thats connected externally via usb cable)) and i can boot into a linux distro after having ddresuce etc on the same dvd-disc i could try it! but since it was ages since i used linux and currently am no linux user it will take some time to set this up. and i would have to ask for help here on the bbs. but that after ive downloaded or seen if i could boot up the redhat distro i have somewhere (but i guess and afraid its not bootable (but only an installer).
or of course i could put ddrescue on a usb-pen as long as i get access to it. and run it from here.
(sorry, couldn't resist)
Reminds me of MSD on my 486:
gasman: hehe, lovely
Quote:
or of course i could put ddrescue on a usb-pen as long as i get access to it. and run it from here.
Yes. Do a raw, direct copy. Do not try to fiddly with the broken disk it will only break more. You can not repair it. You get you data to another disk. The start of the disk looks ok, so you might find data there. The rest will be lost probably.
I have no idea how spinrite works, but when doing rescue cloning and encountering damaged area, the software should try its best to jump over it, rescue the easy bits somewhere else first and finally
come back there later. The reason is that trying to read that area is a) damn slow and b) likely to mess up the drive further.
Yeah, and lister to raer. Your disk is in terminal phase. It will eventually come to screeching halt (with some luck, literally).
come back there later. The reason is that trying to read that area is a) damn slow and b) likely to mess up the drive further.
Yeah, and lister to raer. Your disk is in terminal phase. It will eventually come to screeching halt (with some luck, literally).
Fair call raer, I went on a tangent after 1 of you posts
Listen to rear, rudi.
Clone the disk & make do with waht you can. I apologise for trying to leading you down the wrong path with my advice - normally for me at work a fucked windows mbr is a 5 min job with a windows boot disk, fixmbr and chkdsk.
gparted or clonezilla can copy a partition but probably best to stick to dd or ddrescue for redundancy. + "lots" for slitaz!
Quote:
If the mbr is fucked why not just fixmbr off a windows boot disk - or am I missing something?
Listen to rear, rudi.
Clone the disk & make do with waht you can. I apologise for trying to leading you down the wrong path with my advice - normally for me at work a fucked windows mbr is a 5 min job with a windows boot disk, fixmbr and chkdsk.
gparted or clonezilla can copy a partition but probably best to stick to dd or ddrescue for redundancy. + "lots" for slitaz!
Giggles at gasman.