OS X disk error message?

Trying to understand some disk error messages and whether I need to do
any partial or complete reinstalls.

Apologies for this lengthy post but I thought the error messages were
important to include.

I'm new to OS X. And this is the first disk error message I've had in OS
X.

This all happened on my PB G4 Ti w/OS X 10.2.3. The drive is partitioned
with OS X and the OS 9 for Classic on the partition that had the error
messages. There are other partitions for OS 9 and several for docs.

I decided to test booting from the OS 9 partition. So I changed the
startup disk while in OS X and restarted. All was well.

Then when switching back to the OS X partition I went to the Startup
Disk panel in OS 9. It gave me a panel showing both the partitions on
the left and system folders on the right. I hadn't seen that before
since I went from OS 8.6 to OS X. I selected one of the OS X system
folders on the right after hi-lighting the OS partition on the left. In
hindsight in trying this again after the repairs, I should have just
hilited the OS X partition and not any of the system folders.

At any rate, I then restarted and it didn't boot back into OS X but
again into OS 9 and then near end of boot gave a message that a disk was
unrecognizable and did I want to initialize it. I selected cancel and
didn't initialize. I restarted again and same thing happened.

Then I used the OS 9 disk first aid and got the following message:

Checking disk "OS X".
Checking "Mac OS Standard" volume structures.
Problem: Invalid BTree Header, 0, 0
Checking wrapper System file.
Checking "Mac OS Extended" volume structures.
Checking for locked volume name.
Checking extent BTree.
Checking extent file.
Checking catalog BTree.
Checking catalog file.
Problem: MountCheck found serious errors.
Checking catalog hierarchy.
Checking volume bit map.
Problem: Overlapped extent allocation, 4, 3690
Problem: Volume Bit Map needs minor repair, 4, 114
Checking volume info.
Problem: Volume Header needs minor repair, 1, 0
The volume "OS X" needs to be repaired.

I proceeded to repair and got the following report from Disk First Aid:

Checking disk "OS X".
Checking "Mac OS Standard" volume structures.
Problem: Invalid BTree Header, 0, 0
Checking wrapper System file.
Repairing the disk.
Checking "Mac OS Extended" volume structures.
Checking for locked volume name.
Checking extent BTree.
Checking extent file.
Checking catalog BTree.
Checking catalog file.
Problem: MountCheck found serious errors.
Checking catalog hierarchy.
Checking volume bit map.
Problem: Overlapped extent allocation, 4, 3690
Problem: Volume Bit Map needs minor repair, 4, 114
Checking volume info.
Problem: Volume Header needs minor repair, 1, 0
Repairing the disk.
The volume "OS X" was repaired successfully.
Volume "OS X" had overlapping extents. Two or more files were accessing
the same disk block. Aliases to the damaged files have been created in
the folder "OS Xamaged Files".
Use the Finder's "Show Original" command on the aliases to locate the
damaged files. We do not recommend opening the original files.
Instead, the original files should be deleted or replaced from backups.


There were two files in the Damaged Files folder:

One called: Apple File Service Erro #1C241.03 1
I was able to find its original and deleted it.

The other was called: system.log
That one I couldn't find the original, the path said it was in a folder
named "private" but there were no folders visible in that partition with
that name.

I then ran DiskWarrior. It didn't find any problems.


So, trying to figure out:

What caused the problem?

Is it totally repaired?

Should I try to find this other damaged file?


Thank you for any education and suggestions. Appreciate the help.

--
Please send email to: nwhiii at yahoo dot com

Thanks. I found it. It was invisible.

But now I don't know how to delete it. :-(

There are actually two folders titled "private" but one is empty with a
modification date of 6 months ago. The other contains a number of
folders and is dates today.

Is there an easy way to delete such files?

Will it cause any problems if I don't delete it?

I gather I'm being paranoid thinking I may need to re-install OS X
because of this?

Appreciate the help.



In article <>,
(Tacit) wrote:

> >What caused the problem?
>
> You had a corrupt directory. It happens.
>
> >Is it totally repaired?
>
> It will be when you delete the system.log file. It's probably not in a
> folder
> called "private," it's probably in a folder called ".private". Note the
> period
> at the start of the file name. In OS X, that means the folder is
> invisible. You
> can use Sherlock to find and delete files in invisible folders.

--
Please send email to: nwhiii at yahoo dot com

In article <>,
(Tacit) wrote:

> >What caused the problem?
>
> You had a corrupt directory. It happens.
>
> >Is it totally repaired?
>
> It will be when you delete the system.log file. It's probably not in
> a folder called "private," it's probably in a folder called
> ".private". Note the period at the start of the file name. In OS X,
> that means the folder is invisible. You can use Sherlock to find and
> delete files in invisible folders.

Look in /var/log.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF

In <OM->
Norm Harris <> wrote:
> Thanks. I found it. It was invisible.
>
> But now I don't know how to delete it. :-(
>
> There are actually two folders titled "private" but one is empty with a
> modification date of 6 months ago. The other contains a number of
> folders and is dates today.
>
> Is there an easy way to delete such files?

Stop. Do not delete /private.

system.log lives in /private/var/log. /private/var is symlinked (similar to
aliased) to /var. To delete system.log, open a Terminal window and enter
this command:

sudo rm /private/var/log/system.log

Provide your login password when prompted.

When done, run fsck again.


--
Jennifer Mullen