Benches Vintage and obsolete

7

Firewire Drives wont mount after G3 update to O...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Please help. I have a G3 (blue and white tower) running an AVID Express Meridian system

I have an old Maxtor drive that used to mount fine on it. I did all my back up to it.
I recently updated to 9.1 and now my firewire drive wont mount.
I have tried everything.

I have found old articles about this but none were resolved.
Unfortunatly Firewire does not allow to go back to an older driver while the OS has been updated.

I checked all my Firewire Extentions and they are as follows:
Maxtor Cardbus Enabler 1.0
Maxtor FW Enabler 2.0.1
Maxtor USB Support Shim 3.4
Maxtor USB Support Driver 3.4
FW Authoring Support 1.1
FW Enabler 2.8.2
FW Support 2.7
Fire SCSI Expert 1.7.2
Fire SCSI Support 1.7.2
Fire SCSI RBC RAID Enabler 1.7.2
Fire SCSI Maxtor Enabler 1.7.2

Any help would be greattly appreciated. Time is of the essence for me.

Sincerely,

Juan Carlos

7 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Juan Carlos,

    "Unfortunatly Firewire does not allow to go back to an older driver while the OS has been updated."

    The first question I always ask is "What is your route to yesterday?"

    Do you have a backup drive with your old system? Did you update driver's on the Maxtor? Is it your only drive? You say that "I did all my back up to it." Pardon the questions. For some people, they think of a copy of a file on the same hard drive as the original is a backup.

    The fastest alternative I can think of is to get another hard drive and format it to the old OS. Boot from it and then see if it will recognize the drive. Do you have Disk Warrior? Do you have Data Rescue? Updating drivers should not affect the data, only the ease with which you can see that data.

    An example of update issues can be seen here:

    http://www.eweek.com/article2/0,1895,1721385,00.asp

    "
    But some users have said that after updating to Mac OS X 10.3.6, their computers no longer recognize external FireWire 400 hard drives. When attempting to mount their drives, users report getting messages asking if they want to eject, initialize or retry.

    But some users who tried mounting and opening these same drives on OS X systems of version 10.3.5 and older reported that all drive data were intact. ... Many users contacted by eWEEK.com have reported no such problems; the issue seems to be limited to drives built around some chip sets.

    Users of some MacAlly, LaCie and Maxtor drives have said their external FireWire drives worked properly after the 10.3.6 upgrade. In addition, some users said that updating the firmware of their hard drives resolved the situation."

    I would use the first approach of booting from an older system and verifying and backing up critical data before updating firmware. Having redundant systems will minimize total lockouts from important files.

    Also, read Don Archibald's comments in this discussion:

    http://discussions.apple.com/thread.jspa?messageID=5169537&#5169537

    The point in question is "Be sure to select the option to install OS 9 drivers, else OS 9 will not be able to mount that drive nor to use it for booting from OS 9. "

    You need to backup all important files before updating and then make sure the necessary drivers actually installed properly.

    Finally, this guy reinitialized his drive and THEN Data Rescue could find his files.

    http://www.macintouch.com/panfirewire.html

    Look for the topic labeled 'recovery' and read the notes. Initializing a drive to recover files is a last resort. Proceed at your own risk. That was just one user's last ditch effort.

    Ji˜m

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Jim,

    Thanks for your reply. I will look into all the articles. I had read some already. I wanted to clarify that there is nothing wrong with the drive itself. I can mount it on my old G3 iBook and even on my new G5. Its OS9.1 that has a problem with it.

    I bought a new firewire drive yesterday and backed up all the date in it, just in case.

    -Yes I formated the drive in question in OS 9.
    -I do not have OS X in that computer at all. In my other computers OS X doesn't seem to have a problem recognizing the Maxtor in question.
    -When I say I had backed-up all files from the blue and white G3 onto the old Maxtor... I did, except the system folder, so its not so easy to restore the old computer to 9.0
    -Also, the reason I updated to 9.1 to begin with was to be able to browse the internet. The browser on OS9 wont open most sites, including Mac's. Obviously I prefer to find a way to mount the Maxtor on OS9.1 so that I can have my cake and eat it, too. Going back to OS9 would be second choice as I would not have the internet access I need on that machine.

    I do tried DiskWarrior but it was unable to re-do the directory. The error said to try Norton's.

    I tried Norton's and was able to mount the drive when I started from the Norton's Disk but it was a pain to run it because its configuration has changed from OS9 to OS9.1. I had to install Norton's onto an external drive and run it from there. Disk doctor made the problem worse as it disrrupted the drive's directory and then it would not mount anywhere. I did the Norton "undo" and now the drive was back up using the Norton's CD as a start up. Its the only way it show in that computer, so I am slowly copying the media from it to my AVID drives.

    When I am done, I think I will try reformatting the old Maxtor however, in anticipation, I opened both Maxtor Utilities while booting up on OS9.1 and Nortons and neither see the drive connected at all. Neither does the machine's Disk Doctor, Disk Untility, nor AVID drive utility, so the mystery remains as to how to get that drive to be recognized, at least, so that I can reformat it on OS9.1 and begin to use from scratch (backing up my System folder this time, he he)

    Any thoughts on this last issue would be welcomed.

    Thanks again.

    JC

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Suggest you go ahead & update (free) to OS 9.2.2. May "fix" the problem.

     Cheers, Tom

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Tom. Thanks for your suggestion but, alas, my AVID system wont run in 9.2 and that is what I use that computer for.

    I did solve the problem as follows.

    Since I was able to mount the drive using Norton's CD. I made a note of the extentions int hat system folder and copied them to a zip.

    I then went back to my G3 and disabled all the additional Maxtor and FireWire Extensions and copied the two that the Norton's CD was using
    Firewire Enabler 2.8.4
    Firewire Support 2.8.4

    That seemd to do the trick.

    I hope this helps someone else.

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Juan,

    Great diagnostics and persistence. Thanx for posting back with your solution.

    Jim

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    So if I may test my understanding:

    Some of the Extensions that were shipped with the product got in the way later when Apple updated its software. The later Apple Extensions tried to "take over" the functions the manufacturer's Extensions had been providing, and they fought each other.

    Is that an accurate description?

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Grant I think that is exactly what was happening. The new extentions didnt offer any additional functionality, instead they somehow confused the computer about recogizing the Maxtor Firewire drive (by the way the same was happening to my iOmega Zip drive, which now mounts and works smoothly)

    Best,

    Juan Carlos