Firewire G4 won't *stay* mounted; Norton problems?
Paul Soderman
don't think that OS X has anything to do with this problem, as it started
before I even installed the new system.
I have a couple of external firewire drives hooked up (they share a firewire
port and are "daisy chained"). Had no problems with these drives, which
mostly are used for backups, before a few weeks ago. Lately I find that the
Mac doesn't mount one drive (this would be the one in a firewire
shell/case/enclosure that I bought a year or 2 ago). The problem did occur
at least once with the other, a Maxtor external firewire drive (in which I
replaced the 80 G drive with a 120 G one).
Anyway, I'd be getting messages from Norton that there were directory
problems and the like and would I like to fix them; usually I did.
Regardless of the fixes, though, the Mac would eventually fail to recognize
or mount the FW disc. I find that even after re-initializing the disc and
backing up again onto it, that the disc will fail to properly mount. This
has taken place on several drives I have laying around, as I figured that I
may have had a hard drive that simply had mechanical problems.
I've snooped around on Google and the Web and have determined that possibly
Norton's is the culprit, possibly the FileSaver application, but I'm not
sure. I cannot figure out though, why it seems that the disc will be mounted
after I reinitialize it but then somehow the Mac won't recognize it quite
quickly; almost as if the initialization and mounting won't *stay*, or that
it in some way fades. I don't know why this has just started happening,
although I should report that I've been plugging in and removing other
drives for backup copies that I bring to work; perhaps the enclosure has a
problem? If so, though, I'd think that the Mac wouldn't be able to
initialize or "see" anything that was in that case/enclosure at any time.
Any suggestions? Thanks for any help!
Paul
Dave Balderstone
should not be anywhere near a moder Macintosh computer.
Filesaver is evil incarnate, and has always been a horribly buggy piece
of garbage that should never have been released.
I suspect Norton is the source of your problem.
My advice is to reformat the drives, burn your Norton software, and
rejoice in your newfound freedom.
--
It's probably time to change my sig line, eh?
Paul Mitchum
> I'm running OS 9.2.2, as well as 10.3.3 on another partition, on my G4. I
> don't think that OS X has anything to do with this problem, as it started
> before I even installed the new system.
>
> I have a couple of external firewire drives hooked up (they share a
> firewire port and are "daisy chained"). Had no problems with these drives,
> which mostly are used for backups, before a few weeks ago. Lately I find
> that the Mac doesn't mount one drive (this would be the one in a firewire
> shell/case/enclosure that I bought a year or 2 ago). The problem did occur
> at least once with the other, a Maxtor external firewire drive (in which I
> replaced the 80 G drive with a 120 G one).
Buy new cables.
--
"Maybe the mothers of our nation should remind us
That we're sitting too close
To the television"
simpl...@yahoo.it
<Kidp...@comcast.net> wrote:
> Any suggestions? Thanks for any help!
Trash Norton.
Rob.
Kent Clarke
Since you've had this problem since before OS X, it's probably not
software. Are the external drive power supplies failing? They do seem to
cook themselves if they are rated at the minimum necessary to run the
drive, and behave in the way you describe.
A possibility might be some software confusion if you've installed the
system support files for different drives. My Maxtors had their own OS9
extensions, but you could use Apple's stock ones. On OS X, I notice some
of my Fantom utilities can't read my Maxtor drives and vice-versa.
Maybe clean this up?
If the drives are dropping off the desktop, I'm not surprised that
Norton found some problems.
Norton used to complain constantly about drive errors under Jaguar.
After one of the Panther upgrades, my Norton miraculously stopped
finding the errors. Gee.