| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1159.1 | DiskSalv First | GLORY::SHIVES | | Fri Feb 12 1988 13:07 | 9 |
|
DISKDOCTOR's reputation is not very good actually. I think I even
read a note from someone in CBM that one should use DISKDOCTOR as
a last resort. I have had to use DiskSalv on two occasions and
I think it works quite well. (DiskSalv can be found on Fish Disk
20.) I think there is another disk salvage program, but I can't
think its name.
Mark
|
| 1159.2 | Sectorama? | MDKCSW::DAVIS | That's not a BUG, it's a FEATURE! | Sat Feb 13 1988 20:11 | 5 |
| The 'other' disk repair utility you may be thinking of is Sectorama (also
on a fish disk). I've used DiskSalv with good luck a couple of times, but
I've never tried Sectorama.
...richard
|
| 1159.3 | Normal "error" messages | TLE::RMEYERS | Randy Meyers | Sat Feb 13 1988 21:46 | 20 |
| Re: .0
> Later on I tried DISKDOCTOR on a disk on which I've never had
> any trouble. According to the DISKDOCTOR that disk was corrupt
> too.
How did DISKDOCTOR indicate that the disk was corrupt? I think it is
normal for DISKDOCTOR and DISKSALV to issue all sort of "informational"
messages about finding duplicate keys, etc. It is reporting inconsistencies
in the storage of deleted files and parts of deleted files on the disk.
These programs issue the message because they assume that the directory
structure is bad, and derive what the directory structure is from
redundant information stored in the headers of each block. If they find
the remains of a deleted file, they assume that the file is intact and
valid until they come across an inconsistency in the file structure.
When such an inconsistency shows up, the program issues a message.
That is why whenever you run DISKDOCTOR (or DISKSALV) you get a ton
of messages issued. It is also why any deleted (but intact) files on
the disk are undeleted by running these programs.
|
| 1159.4 | Diskdoctor messages | UTRTSC::VIS | | Mon Feb 15 1988 07:49 | 27 |
| Re: .3
> If they find
> the remains of a deleted file, they assume that the file is intact and
> valid until they come across an inconsistency in the file structure.
> When such an inconsistency shows up, the program issues a message.
So the inconsistency's should always come from deleted files, if my disk
is intact.
The messages are somthing like:
Replacing file <fl_nm1>
Replacing file <fl_nm2>
Replacing file <fl_nm3>
Replacing file <fl_nm4>
Replacing file <fl_nm5>
Replacing file <fl_nm6>
Replacing file <fl_nm7>
Replacing file <fl_nm8>
Copy theses files to another disk and reformat this disk!
These "Replacing files" should probably be the files that are consistant.
How about the last message. Did the DISKDOCTOR mess up the diskstructure??
or does it want you to get rid of your already deleted files?
Thanks for your replies so far,
Eric.
|
| 1159.5 | Just a good idea | TLE::RMEYERS | Randy Meyers | Mon Feb 15 1988 10:21 | 8 |
| Re: .4
The reason that diskdoctor requests that you copy the files to a new
disk is that it assumes that the disk is corrupt since you had to run
diskdoctor on it.
If the disk itself was physically going bad, getting all the files you
want off of it and onto another disk is a very good idea.
|