Re: [OT] Random Errors
Re: [OT] Random Errors
- Subject: Re: [OT] Random Errors
- From: robert delius royar <email@hidden>
- Date: Sun, 14 Nov 2004 15:42:29 -0500 (EST)
- Organization: An Apple OS X end user
- Priority: NEW
Sun, 14 Nov 2004 (14:24 -0500 UTC) Ken Mankoff wrote:
Hi Group,
I'm pretty sure this is off-topic, but I don't know where else to post.
Anyway, 90% of my work is through the X11 interface, so thats where I noticed
this problem. And I sense it is a low level filesystem problem, and this
group might have some expertise in that area.
I just had to respond that I too found some odd file-system errors show up
about 18 hours after updating my PB to 10.3.6. I had the first Kernel panic
in many months, followed by a few others. I thought my internal drive was
physically damaged because after many "no problem" disk verifies from the
Install CD, I finally got a "minor header error" which would not repair.
Two errors I found that were not there the day before the update were links
to non-existant files in directories or applications which also showed new
Nov 6 files, and thousands of soft links that had a file mod date/time of
Dec. 31, 1969 19:00. These all over the machine.
I checked my backup to confirm that the mod date/time problem did not exist
on it.
I had recent backups and bought a (larger) replacement disk. After
restoring and reinstalling the 10.3.6 update. I found that symlinks cannot
be changed (i.e. I could not get a fixed modtime). I think this is already
known and discussed before. I also discovered that my old drive was
revivable in a firewire enclosure once zeroed and now shows no errors.
However, I have also found that if I allow the OS to sleep drives when it
sees fit (power management auto), it will occasionally sleep a firewire
drive and not be able to wake it. But it seems unaware that it cannot wake
the drive, so it either panics or posts an error saying I should not remove
a drive without dismounting it.
I have not filed a bug report because there seem to be too many variables to
pin down the errors' causes. But I was happy that zeroing the drive made it
show up fine. S.M.A.R.T. never showed errors by the way, but the drive made
click noises--only when a FireWire connection was active--which it has not
since and had not before. I suspect that something about the attempts to
work around vendor's firmware problems may have triggered errors in some
systems that did not suffer from those errors.
This is the first time I have ever been able to recover a hard drive that
seemed to be failing so thoroughly. On my PC I used to have to replace
drives at least every 18 months, and I cannot recall getting one of those to
work again with a simple formatting.
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden