Thread: Iomega Firewire hardrive problem
08-09-2008, 07:38 PM #1
Iomega Firewire hardrive problem
- Member Since
- Aug 09, 2008
This is my first post - am in need of advise,
Have recently bought a new I-mac 10.5.4, and my external Iomega FW 250 gig would mount with no problem (used to use Emac). Then it stopped mounting, and now it's not even detected in system profiler, or Disk Utility. Had this problem when I had the emac and had to pay to recover the files. Am finding this very annoying and don't understand why it would detect and mount, and then stop.
Ran disk repair when it didn't mount ( but was detected ). Last time I checked disk utility, it doesn't appear.
Cannot underestimate how much I would appreciate some help with this
(What's everyones view on Iomega, I'm not impressed thus far)
08-09-2008, 11:55 PM #2
- Member Since
- Jan 23, 2008
- Fort Worth, Texas
- Late 2013 27" iMac, iPad 3, iPhone 6s+, iPhone 6+, 3 iPods, El Capitan
Sounds like you have an intermittent defective Iomega drive on your hands. I would get what data off the drive that you can (if you can) and retire that drive.
Like you I have never been impressed with Iomega. Having used their removable drives ever since the days of the "Bernoulli Box" and more lately their Zip drives, I've experienced many failures. I no longer use anything from Iomega.
08-10-2008, 05:35 PM #3
- Member Since
- May 18, 2008
- Banks Peninsula, Canterbury
- MacMini 4.1, OS 10.11 and 10.6; Macbook Pro 8.2, OS 10.11, MacBook 4.1, OS 10.6.8
(Originally called Firewire bug page. Changed the name of the problem for better clarity)
In Mac OS X 10.5.2, there are some instances where the Finder may not load with External hard drives according to the Apple knowledgebase
In Mac OS X 10.4.9, it was found that Western Digital MyBook drives put an unsupported addon for their drives to use in Macintosh HD -> Library -> Launch Daemons called com.WD.WDDriveServices.plist. Removing that file fixes the ability of those drives to be read.
Starting with Mac OS X 10.3, it became apparent that the firmware of a Firewire hard drive case needed to be upgraded to avoid not being able to be read by Mac OS X in some cases. Turns out that this is not the only cause of a non-hardware related issue that could cause Firewire hard drives to be readable on some machines yet not others when using the same Firewire cables. It has been found that these causes are the most likely and should be tested for in this order:
1. The PRAM needs zapping. Note, if a machine is 3 or more years old, PRAM zapping should only be attempted after verifying that the clock (also known as backup battery) is fully charged. Similarly, the NVRAM may need resetting.
2. The firewire ports need resetting, or the PMU needs resetting.
3. Spotlight indexing on the hard drive needs turning off. This is only an issue under 10.4 (Mac OS X Tiger). For more on why this may be an issue see the section on this FAQ on 10.4 Issues.
4. Dust in the firewire ports.
5. Installed firmware on the Firewire bridge of the hard drive is not fully compatible with the operating system. Check the manufacturer's support line (in this case e-mail firewire AT lacie.com) for updated firmware.
6. The operating system's Firewire drivers are not properly installed. This may happen if you used system specific disks for another Mac to install the operating system, or the directory is damaged, or the preferences for the firewire are not working.
Update: see post about "LaCie HD stopped mounting with Firewire". Most informative.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By boston in forum OS X - Operating SystemReplies: 8Last Post: 05-16-2014, 12:57 AM
By jshulman10 in forum Other Hardware and PeripheralsReplies: 5Last Post: 07-29-2010, 10:22 PM
By BarelakedNadies in forum Other Hardware and PeripheralsReplies: 1Last Post: 05-06-2008, 08:30 PM
By wngriff in forum Apple DesktopsReplies: 1Last Post: 06-03-2006, 11:44 PM
By HelpMyiMac in forum Apple DesktopsReplies: 10Last Post: 01-24-2005, 08:48 PM