home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ARM Club 3
/
TheARMClub_PDCD3.iso
/
hensa
/
diskmanager
/
fsck_1
/
!QuickFix
< prev
next >
Wrap
Text File
|
1996-12-22
|
3KB
|
76 lines
If you have a broken disc and you just want to fix it as fast as possible
without reading all the fsck help files, this quick guide to the disc fix is
for you.
You just have to search for your problem in the 'Problems' list and then read
the corresponding solution in the 'Solutions' list.
If something goes wrong during the fix you should read all the other docs to
search for more info and eventually contact the author.
After the fix, please read the "!SHAREWARE" file, it's important!
Remember that the programs 'fsck' and 'hardfix' can keep a logfile of what
they print on the screen: if something goes wrong, the logfile can help the
author to discover and fix the problem. To use the logfile option, add:
"-l <filename>" (where <filename> is the name of the logfile to create)
to the 'fsck' and 'hardfix' command line.
Before using 'fsck' or 'hardfix' you should save the disc data to a file
using:
"hardfix -s <savefilename> <discname>"
If something goes wrong during the fix you can always restore the map. See
the file 'hard_help' for more informations about how to restore a saved file
and why you should never do this!
In the examples below I assume that the broken disc is drive 4 on Filing
System ADFS (like the internal RiscPC IDE): when you have to use the command,
change it to suit your configuration (eg. use IDEFS::5, SCSI::4, etc. instead
of ADFS::4).
Problems:
1) CheckMap reports "Map inconsistent with directory tree"
2) Some file cannot be loaded and deleted (the computer hangs)
3) A directory cannot be opened ("Broken directory" error)
4) Trying to create a new file on the disc causes a computer hang or some
strange error.
5) The disc cannot be opened/accessed ("Disc not understood - has it been
formatted?" error)
Solutions:
1) Use 'fsck' on the disc, for example:
"fsck -f ADFS::4"
If it asks you to create a directory called 'lost+found', reply 'y'.
When it finishes, look inside the 'lost+found' directory: load the files
and check inside the directories to see if there is something useful for
you. If you want to keep some of these files or directories, *copy* them to
another directory and *delete* them from 'lost+found'.
Then, try fsck again to see if the disc is fixed.
2) Use 'eliminate' on that file, for example:
"eliminate ADFS::4.$.dir.file"
If you are sure of what you are doing (ie. you are eliminating the right
file!), reply 'y' to the question it asks you.
Now run 'fsck' as described above in Solution 1 to fix the disc that
should now be 'inconsistent'.
3) As in Solution 2, run 'eliminate' to remove the directory and then 'fsck'
to fix the disc.
4) Use 'hardfix' on the disc, for example:
"hardfix ADFS::4"
It will show you what's wrong and will fix it. It should report problems
about "free chunks linked list", "unresolved links" and "wrong checksums".
Then it will ask you if you are sure to save the fixes to disc and you
should answer 'y'. After the fix you should run 'hardfix' again to see if
the problems were effectively corrected and eventually 'fsck' to see if
the map is good:
"fsck ADFS::4"
Remember that 'hardfix' is a really dangerous program and so you should
read the 'hard_help' file before trying to use it.
5) As in Solution 4, use 'hardfix' and then 'fsck'. In this case 'hardfix'
should report problems about "corrupted maps" and "wrong checksums".