FireWire drive issues: Personal File Sharing link A good number of readers have experienced problems with FireWire drives since installing the Update, including an inability to mount such drives. Keith Bumgarner describes a FireWire problem that, in his case, appears to be linked to Personal File Sharing and is fixed by installing OS X 10.3 on the affected drive:
"We've had some intermittent problems with Firewire drives not mounting but traced all of the problems to Macs with Personal File Sharing enabled. After a FireWire drive (800 or 400) was subjected to an environment where Personal File Sharing was active, it would behave 'badly' on any Mac, sometimes taking forever to mount, sometimes not at all, sometimes only after a couple of on/off cycles. Formatting and reformatting the drive, even with different disk structures, did not help, nor did tinkering with any aspect of the OS (we ran 10.3.5-10.3.7 during all of this and found no difference in the degree of problem due to OS version). Various directory repairs and O&P adjustments did nothing either. What we did finally discover was that writing OS 10.3.x to a drive 'gone south' completely resurrected it. The drives we ended up testing and repeating the problem with were one Western Digital 120GB in a custom case from Granite, and two Maxtor 320GB and 465GB [drives], controller firmware rev912 (Oxford).
"Since [installing OS X 10.3] to the drives the problems have completely cleared up with no repeat occurrence. All drives mount perfectly now no matter the circumstances or hardware. The Macs we tested this all on were a desktop G5 dual 1.8GHz, a new iMac G5 20", an older 450MHz dual G4, and a 15" Titanium 667MHz PowerBook. We can even initialize the drive after the OS install and it's still OK; there's no need for the OS to be present on the drive. We can, however, start the cycle all over again by simply enabling Personal File Sharing on any of these Macs while the drive(s) are connected and mounted. The problems start upon the very next reboot after enabling Personal File Sharing. (Simply turning off Personal File Sharing did not help the problem.)"