HD Recovery help.
22 messages in this thread
Advise Needed: I have done it. Managed to wipe out 279 Megs of stuff….
I feel SICK! What happened was that I used messydos incorrectly. I
managed to format the first 80 tracks of my HD. The total number of blocks
ruined by my stupidity were not that many but…. I have an Oooold copy of
Disk Mechanic that has NEVER worked for me. I asked the owner at a show
about it and he said to call for an update. Well I'm not a big fan of his
company but…. Does anyone know the current address phone? I have the
original disk right in front of me and guess what? No number nothing!
Anyone have any advise on another program I should get maybe> this is the
worst? H e L p! !?!?
Jay,
Try DiskSalv.
Don
Don,
DiskSalv probably won't work on the hard drive because you must
restore to a floppy, and my experience with DiskSalv is that once you fill
one floppy disk, that's it. I have had little success with DiskSalv on a
hard drive including many lock ups and gurus. In fact, it rarely works
successfully restoring even floppies. Version 1.42 invariably gurus
immediately after recovery and before finishing. I've never gotten it to
work to restore a hard drive.
Steve,
I am not sure why you would say that BUT, I just resurrected a 47 meg
partition on my hard drive last night using disksalv. I have 5 partitions
on my drive and the command was simply disksalv dh3: to dh2: . It TOOK
AWHILE but I wound up losing ONE file.
Scott
Well, in my case I don't have a second partition large enough, which you
apparently do. However, I've never been able to get disksalv to work
completely through a recovery without guru'ing. I guess it works for you,
which is all that counts.
Jay,
I just used DiskSalv 1.42 to recover a single file on my "Janus" Drive
to RAM: using the ASK option. You can restore to any device you want, not
just floppies. It takes a while, but if the data is still there (hasn't
been formatted/reused) it works pretty well.
You are probably right about only being able to fill up one floppy. But
if you want to spend a little time you could probably restore a bunch of
single files.
Kevin Ushko
Edmonton, Alberta
Kevin,
I've tried many times, but disksalv 1.42 consistently gurus when
I've tried it, but if it works for you, great. I've not had that success.
What size is your stack when you try and run disksalv?
Steve
Steve,
Good point — stack size might be a problem. I run with a 20k stack
size.
-sja
I got soooo sick of running into stack problems that I finally cranked it
up to 50K. 🙂
Steve
Steve,
I always run a stack of 40000.
Steven,
I've used DiskSalv _many_ times from HD. And no, it must not go to
floppy only. You can restore to any device. When I accidently delete a
file on one HD I'll "disksalv dha: dhc: ASK". Works just fine.
-sja
Steve,
I've never been able to get disksalv to work reliably for restoring
files without gurus. I know I can restore to another hard drive, but you
must first have another hard drive (or partition) to which files may go.
In my case, if the large partition goes I have no other partition large
enough. Even the small partition is to large to recover to the large
partition because the large one is mostly full. I just wish I knew why
disksalv won't work reliably on my system.
Steven,
I still don't see a problem — restore to floppy. When disksalv fills a
disk you get a prompt that says "DISK FULL Insert New Disk Into Device
DF0:, Format or Continue [?]". I just tried it, it works fine. I usually
don't do this since I do have enough unused HD space.
Steve,
Well, I seem to have received universally similar reactions to what
I thought was not too controversial an issue! I can only say that my
experience with disksalv has not been at all like everyone else who has
replied. I have tried putting in the next disk, but disksalv has always
locked up or guru'd once that was done. Further, it has never successfully
completed a recovery of any kind without guru'ing at the very end of the
recovery or during it. The older version, 1.3 or 1.2, always seemed to
work, but 1.4 and 1.42 have not. That's my experience, which now appears
to be rather unique. I guess I can only conclude that something in my
system setup conflicts with disksalv, and that none of those who have
replied must have a similar setup. That would be all I could think of to
explain my unusual experience. Perhaps you know of something that disksalv
doesn't like and could relate that to me, then I could determine why I have
a problem no one else seems to experience. I have also had similarly
disappointing experience with the new program, recover-II, recently posted.
When I try to log into df0: it gurus. BTW I have tried disksalv both with
Blitzdisk running and without, so I am pretty sure that's not the problem.
Steven,
I believe that DiskSalv requires some of the standard WorkBench files
(like the Disk-Validator). If you are attempting to salvage your SYS:
partition, then that could cause the types of problems you are
experiencing, as DiskSalv inhibits it's source drive at the DOS level, so
it appears as "Not a DOS disk" to the system. Consequently, the files
normally found on SYS: can't be found while it is running. An alternative
would be to boot from a floppy-based workbench disk when attempting to
salvage from your standard SYS: HD partition.
Hope this helps…
…BobR
White Wolf Productions
Bob,
Well, all the standard files are on the hard drive, although the c:
directory files have been replaced with their arp equivalents. However,
everything in l: or libs: directories are there. I don't believe I have
ever tried booting from a floppy to recover from the hard drive, but that
wouldn't be a factor when trying simply to recover one floppy to another.
DiskSalv works fine across multiple floppies. When it fills one up it ask
what you want to do. If you press 'c' for Change it will prompt you to
switch to a new floppy.
Greg
Greg White / MicroSearch 72230,1617
We listen to our customers..carefully
Greg,
I know, but when I try that disksalv gurus on me or locks up, but
it won't work on my system.
Sorry to barge in here but I used Disksalv once to restore my hard drive
and I did it from one partition to another. Naturally the destination
partition was empty. I believe I had about 22 megs or so on the partition I
used Disksalv on.
I have had lots of problems with my HD's and this was how I had to
correct one. Mostly, I get a read/write error on start-up, especially if it
sat for awhile. A warm reboot is always successful.
At this time I'm using a Trumpcard 500 with an 84 meg Seagate but my
problems were much worse when I had a Syquest hooked up to it.
Anyway, Disksalv really saved me a LOT of time and I was even going to
write a thank-you note to Dave H. but you know how good intentions are:-).
If I misunderstood your message or anything, my apologies in advance.
SKip,
No problem. I had been relating my unsuccessful experiences with
DiskSalve 1.42.
Jay,
It's unlikely that you can recover files if you actually formatted
the tracks, because the format process doesn't erase files, it actually
writes new data to the tracks. Probably, you needn't worry about getting a
new copy of that program, but rather restoring files some other fashion.
You could try DiskDoctor as a way of restoring what is restorable, then
copying that to backup disks, reformatting the entire drive and then
restoring the recovered files.