🚀 go-pugleaf

For it is a logical, not a physical problem, there should be another
possibilit to reformating. There is only a wrong/missing entry in the
directory, so the main issue should be to get rid of the affected
files.

Three solutions I can offer:
1. You used a third-party formatting util, than you can just delete the
partition in question and than re-create it, without affecting the other
partitions. If you used Apples formatter, than you are out of luck (almost).
There is a chance that whan installing another driver (HDT, Silverlining),
that new driver can take over the partition map. If not, all partitions
are lost, if it can: delete the affected partition and recreate it.

2. Try to get rid of the "undeleteable" files (disable file sharing beforhand):
a. Hold down Option (= "alt") while emptying the trash.
b. Try to replace them with files of the same name.
c. Try to replace the folder they are in with a folder of the same name
d. Try to stuff the files/folder with the "trash originals" option enabled.
e. Try to encrypt the files, which will automatically delete the originals.
f. There are some utils to quicken the empty trash command by bypassing
some finder checks. That may do the trick (don't ask me for a specific name).
Also there are some file editors that can directly delete files.
g. Open Norton editor, go to node 591, write down all files indexed there
and erase as many as possible of them. Then try all the above again on the
remaining files. In Norton editor, you could also check if the undeleteable
files are protected or have the busy flag set. Uncheck that flags.

3. Do a crash curse: either you survive or the data of the affected partition
will go to hell:
Open Speed Disk, perform a "check files":
If you have luck, speed disk finds the error and gives you a repair option.
It is very safe to let speed disk repair the problem, for it can only dedect
some very special problems and only repairs if it is quite sure about it.
If no error, or it is unrepairable, defragment your partition. If you have luck,
it can finish the task. If it cannot, try over again. You could also check if
you could delete the files after an interuption, or if NDD can do some repairs
befor retrying to defragment. The risk is that if Speed Disk cannot recover from
an error, the partition's directory will get messed up to quite unusabilty.


Joerg Erdei



maingram@unity.ncsu.edu (Michael A Ingram) wrote:
>Hi
>
>I have a Mac under Systen 7.5 with an attached APS 730MB external SCSI
>harddrive.  The drive has 5 partitions.  Yesterday I started noticing Disk
>I/O errors and crashed when I tried to use a particular partition named
>"As Yet Untitled".  I ran Norton 2.0.1 and Disk First Aid for Sys 7.5 and
>the results are below.  In short I was told that ther is a problem that
>neither can fix.  I conferred with an APS technician and he said the best
>I can do is to reformat the drive.
>
>For the time being, I'd like to avoid that because I have no way to back
>up the information I have stored.  Though it is not critical, I would not
>like the burden of regathering/creating it.  I have deleted files I could
>immediately spare, and in hopes of saving myself temporarily from any
>anguish, I moved everything  I could to the other four partitions.
>
>What I would like to know is if there is any potential for this problem to
>migrate to the other partitions?  Also, is there anything I can do to save
>reformatting?
>
>Thanks!
>
>DISTK FIRST AID RESULTS
>      Checking disk „As Yet Untitled¾.
>      Checking disk volume.
>      Checking extent BTree.
>      Checking extent file.
>      Checking catalog BTree.
>      Problem:  Invalid sibling link, 4, 580
>      Rechecking catalog file.
>      Test done. Problems were found, but Disk First Aid cannot repair them.
>
>NDD 2.0.1 RESULTS
>      Norton Disk Doctor
>      Report for „As Yet Untitled¾
>      Tuesday, January 9, 1996 6:01 PM
>
>      System Information:
>      Machine Name:
>      8 Megabytes of RAM
>
>      System Area Status:
>      The Boot Blocks check out OK and indicate that this is a bootable disk.
>      The Volume Information Block is OK.
>      There were some problems with the Directory.  These problems have
>NOT been fixed.
>
>      Disk Statistics:
>      This is an HFS disk.
>      146,575,360 bytes total disk space.
>      54,533,120 bytes used by 550 files in 79 folders.
>      2,094,080 bytes used by the system area.
>      89,948,160 bytes available on the disk (87,840K free).
>
>      Disk Technical Information:
>      This disk was initialized on Wednesday, April 19, 1995 7:29 PM
>      This disk was last modified on Tuesday, January 9, 1996 4:12 PM
>      There are 57,256 allocation blocks on this volume.
>      The Allocation Size is 5 blocks (2,560 bytes).
>      The volume bit map starts at sector #3.
>      The first sector represented in the volume bit map is #19.
>
>      File Status:
>      550 files were scanned.
>      374 had resource forks.
>
>      The following files could not be read and are probably damaged.
>      You should remove these files from your disk.
>      As Yet Untitled:cannot delete:JPC001E.JPG
>      As Yet Untitled:cannot delete:JPC001F.JPG
>{BTW, I CANNOT DELETE THESE FILES}
>
>      Technical Summary of Repairs:
>      700:1802, A problem was found in the disk's directory.
>      Node=591, Error=missing index record.
>      Status: Unable to fix.
>
>      612:38, Some files on this disk are possibly damaged.
>
>      Summary:
>      Some problems were found with this disk.  NDD did not fix these problems.
>
>--
>M!ke
>maingram@unity.ncsu.edu
>http://www2.ncsu.edu/eos/users/m/maingram/mikespace/mikespace.html
>I believe in a government OF the people BY the people and FOR the people