Problem with external FireWire drive

Two weeks ago I purchased a 1 tb Iomega ultra drive with FireWire 800/Firewire 400/USB 2/ESATA to use for back ups. I plugged it in the Firewire 800 port of my iMac. It worked fine until early this morning. I noticed there was a problem first because it was taking forever to log off or restart the computer with the drive connected and second that Time Machine had stopped doing backups a few hours previously and the drive was no longer recognized by OSX. I can plug it into a USB 2 port and it works fine. I have two Lacie drives daisy chained from the same Firewire 800 port - so the port is just fine. Thus it appears that the problem is with the Firewire 800 connection on the Iomega drive. Time Machine works with USB but I bought the drive for its flexibility. In future I might want use it as a bootable drive plus Firewire 800 is faster than USB 2. Any idea if this could be a software problem? I hate to return this drive since a) I would need to securely erase it first; b) I would have no time machine backup until I received a replacement (though I am doing less frequent conventional backups on 3 other drives (ie subsets of my files since none of the other drives are large enough for a single time machine backup plus I like redundancy); c) it is a pain to pack up and return.
So my question is: should I bother or just live with USB 2 and hope that the FireWire problem does not mean the drive is a piece of junk and should not be trusted for anything?

I called the store where I bought the drive and was told I have up to 30 days to return it. So I tried plugging it into the firewire 800 daisy chain (at the end) and now it's working again. So I will watch it closely over the next few days to see if this happens again within the 30 day return period. Also by registering online at the Iomega website, I now have 3 year warranty.
Also from reading other threads about firewire issues, it appears that intermittent firewire problems may be more prevalent than I would expect (based on previous experience with a variety of firewire drives from many vendors).

Similar Messages

  • Post-Install Problem with External Firewire drive

    I just installed Tiger 10.4.3 and the computer would not reboot. It would stop prior to the Starting Mac OS X progress bar and gray out letting me know that the computer needs to restart.
    I finally got it to boot successfully by unplugging or turning orr my external Maxtor Firewire drive. The external drive was plugged during the install process (mistake?)
    Via Software upgrade, I upgraded to 10.4.6 in the hopes that this would solve the issue. No luck and when turning the drive on, it immediately goes right to the gray screen and lets me know it will need to reboot.
    Is this a known problem with a known solution? Did I FUBAR my drive somehow? Any suggestions for righting to ship?
    Thanks!
    Rob P

    OK, last one before dinner. I found the panic log. here is what it says:
    Description: Panic (system crashes) log
    Size: 12.39 KB
    Last Modified: 5/25/06 6:39 PM
    Location: /Library/Logs/panic.log
    Recent Contents: ...
    panic(cpu 0): 0x400 - Inst access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000857F4 0x00085C24 0x000287B4 0x0008F6A8 0x000927B8
    Proceeding back via exception chain:
    Exception state (sv=0x24051780)
    PC=0x00000020; MSR=0x40009030; DAR=0x11F23B98; DSISR=0x40000000; LR=0x16FE0DEC; R1=0x1227BB90; XCP=0x00000010 (0x400 - Inst access)
    Backtrace:
    0x16FE0C58 0x16FE08DC 0x16FE043C 0x0021FFAC 0x0021FDA8 0x002206F8 0x00220D54 0x002111D0
    0x00211194
    Kernel loadable modules in backtrace (with dependencies):
    com.maxtor.iokit.IOFireWireMxBt(2.0d1)@0x16fdf000
    dependency: com.apple.iokit.IOFireWireFamily(1.4.0)@0x233d3000
    Exception state (sv=0x22F58A00)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    Kernel version:
    Darwin Kernel Version 6.8:
    Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC
    Does this help anyone???
    Rob P

  • Problem with External Hard Drive - Firewire

    I have a problem with a *300GB Venus DS3 Hard Disk* / USB 2.0 - Firewire 400 (not sure if 400).
    I have a +Mac G4 (1GHz Power PC G4 / 1GB DDR SDRAM)+ running +Mac OS 10.3.9.+
    I connect Venus hard disk through USB cable and no problem. But when I want to connect it via Firewire it doesn´t appear in the desktop.
    If I go to *System Profile* it says that there is a device connected to the FireWire port but i can´t see it in the desktop and if a open *Disk Utility*, there is no other hard disk besides the internal, so I can´t mount the Venus DS3 Hard Drive.
    I looked in the internet and found this page -> http://american-media.com/support/downloadDDDS2316CBK.html
    I was about to download the *Firmware Update* but i read this:
    AMS is not held responsible for any damage caused by misusage of this utility! Use at your own risk and be aware that your warranty might be void! DO NOT CHANGE
    ANY SETTINGS WITHOUT CONSULTING TECHSUPPORT. Do not distribute or post these files on the internet!
    I searched in Internet and found that many persons had issues connecting Hard Drives using Firewire port and read some tips (like unplugging all the usb firewire devices unless mouse and keyboard, disconnect AC cable, wait 15 minutes, ...) but couldn´t fix the problem.
    I also wrote several emails to the manufacturer of Venus hard drives (American-Media) but so far no answer.
    I would really appreciate it if someone could tell me how to connect the Venus DS3 to a Mac G4 (OS 10.3.9) via FireWire.
    Thank you very much

    I suspect the problem is in the size of the drive. You say the drive was formatted for Mac and Windows. How did you do that? With older Macs, there is a 128 gB limit on drive size.
    Here is a link to a third party disk utility that claims it gets around the size limit:
    http://www.SpeedTools2.com/
    Another possibility is to connect the drive to a Windows machine and re-format it into 3 volumes, each less than 128 gB. The Mac should be able to see the partitions.
    Sidebar comments:
    • The way I read the information on the AMS web page that you cited, you do not need a driver. And that is consistent with my experience with firewire enclosures.
    • Inside the AMS enclosure, the drive is a standard ATA/IDE drive. That you can use the drive with a USB connection is proof the drive itself is working.
    • The "bridge" is a key component in FW conectivity. (That is a piece of circuitry that sits between the IDE drive and the FW connection. It is inside the enclosure.) It appears your enclosure has the Oxford 911 chipset on the bridge. That is good.

  • Backup problems with external hard drive

    I bought a WD passport external hard drive and copied my itunes library onto a file there. I re-set the location of the library on itunes to the drive on the external hard drive. So far I have not deleted anything from my computer hard drive. However, when I am in itunes and click onto a song, nothing comes out of my speakers. Everything looks normal, as if the track is playing, but nothing is happening. I tried buying a new track off of itunes online, downloaded it, and installed it on my ipod; it plays fine, on my ipod, but will not play on the computer. Something is obviously wrong, but I can't figure out what has happened. Any help out there?
    Thanks!
    Delany

    It sounds to me like your iMac is on it's last legs....at least the internal hard drive. If you can't make a new Time Machine backup I would advise you replace your iMac as soon as possible.
    Assuming your three-week old backup is sound you should have no problems moving everything over to a new Mac. I would recommend you use the Setup Assistant that appears when you start up the new Mac (and note: It only appears the first time you start the new Mac; you can move everything over later on via Migration Assistant, but you may see issues with accounts if you opt for that route).
    I don't think you need the Genius Desk for Setup Assistant. You only have to power up the new iMac, answer a few questions....select "....From Another Disk..." When it asks how you want to move everything over....connect up your Iomega external drive...and wait for it to finish. (Could take several hours depending on the amount of data you're moving).
    A couple of notes:
    1.  If your Iomega is a Firewire drive you'll need a Firewire to Thunderbolt adapter to connect it to your new iMac.
    2.  If you need to load CDs or DVDs remember the new iMacs don't contain an optical drive. You would need to get an Apple SuperDrive or third part external burner if you need that functionality.
    I'm puzzled by the comment made in Seventy One's post questioning the reliability of the new iMacs. I upgraded from a 24" early 2008 model to a 27" model and everything works flawlessly. I hardly ever see the beachball anymore.

  • Issues with External Firewire Drive

    I have a Lacie external 160G HD connected via Firewire to my multiple motherboard replacement Rev. A iMac G5. The drive worked fine until about a month ago, approximately the time I installed 10.4.6. It now can see the drive, I can open files on the drive, but cannot copy anything to or from the drive. It gives me a type 36 bad data message. I've run Disk Utility on it and the iMac and repair permissions. I also connected the drive to my Powerbook G4 and it works fine.
    I contacted Mac support last night regarding this issue. Predictably, they suggestion I wipe the external and try it. If that fails, I reinstall the OS on the iMac. Obviously I'm hesistant to try either as a shot in the dark, and I think they're particularly dubious suggestions considering the drive is working fine on the Powerbook (which is also running 10.4.6.)
    Any suggestions?

    I think you need to call AppleCare again & carefully explain that the drive works fine with another Mac, & thus the advice to wipe the drive is inappropriate. If you still get resistance, politely but firmly ask to speak to the rep's superior. This usually will be a "Product Support Specialist" with more knowledge of proper troubleshooting procedures.
    However, be aware that there may in fact be a problem with the iMac's install, so the advice to reinstall the OS is not unjustified. Also, Apple doesn't have to support third party devices by the terms of your AppleCare agreement, so concentrate on the fact that you have had multiple hardware replacement problems.
    Running Apple Hardware Test might give you some indication of the problem's cause, so do that before calling again.

  • Error code 36 (problems with external hard drive)

    I have just upgraded to Yosemite and am now having major problem with my external western digital hard drive.  I cannot create new folders and when I hit command N I get error code 36.  I also cannot move files from one folder to the next.  When I try to move them I get the error message: "The operation cannot be completed because a file of that name already exists" and that simply isn't true.  None of the files' names exist in the other folder.

    Ok, It appears to be the fault of Western Digital.  I ejected the hard drive and then plugged it back in and it said that the drive was broken but I could still read the files and it told me to save the files on another disk and reformat.  So it was just a coincidence that I upgraded to Yosemite at the same time that my external hard drive broke.

  • Permissions problem with External Hard drive.

    Hi,
    I've been using my external hard drive for almost a year now and out of the blue last night I ran into a interesting problem. For some reason I couldn't transfer any files to a thumb drive and shortly after I realized I didn't have Read and write permissions for any files on my mac, and everything required my password to get to. I went into disk utility and repaired the permissions and the list went on forever. Upon completion of that nothing was resolved.
    SO! I popped in my Snow leopard disk and did a repair of the permissions and system through there hoping that would fix it. I than booted up the main drive and got stabbed in the face with a HUGE error message upon the apple loading screen with a "MISSING DRIVER" "KERNAL ERROR" "CORRUPT FILE" etc.
    I went back and did a restore from my external harddrive hoping that would work, and it did. I can access my time machine backups from my external harddrive but cannot do so through my own control.
    What should I do? Should I reformat my external harddrive? Which would suck because I'm a paranoid freak and if something would happen during the reformatting I will lose literally over a year of work that is crucial.
    error message upon opening my backup
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201061.png
    error message upon trying to backup
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201-1.png
    icon of backup drive
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201062.png
    Can anyone shed some light?

    nomhak wrote:
    I went back and did a restore from my external harddrive hoping that would work, and it did. I can access my time machine backups from my external harddrive but cannot do so through my own control.
    What is that, a "clone?" What do you mean by "cannot do so through my own control."?
    What should I do? Should I reformat my external harddrive? Which would suck because I'm a paranoid freak and if something would happen during the reformatting I will lose literally over a year of work that is crucial.
    Again, what's on that drive? Do you have a clone and TM backups on the same external? If so, are they in the same partition?
    error message upon trying to backup
    http://s91.photobucket.com/albums/k302/nomhak/?action=view&current=Screenshot201 0-03-01atMarch1-201-1.png
    This one says you need to repair or reformat the disk; that means your backups are corrupted.
    Try to do a +*Repair Disk+* (not permissions) on it.
    If there are errors that Disk Utility can't fix, or the +*Repair Disk+* option is grayed out (meaning OSX has already determined that it can't fix it), post back.

  • Problems with External Hard drive, will not mount and errors in disk utilit

    i have a powerbook g4 aluminum. i have an external hard drive for it. a simple tech 100gig portable drive, almost brand new. i dont know what happened to it, but one day i was starting my computer up with it attached. it wounldnt fully start up, said "waiting for local disks" so i uplugged the external hard drive. now it wont mount and will only show up in the disk utility of my friends macbook. i tried to verify and repair, and this is the message i got.
    Verify and Repair disk “UNTITLED”
    ** /dev/disk1s1
    could not read boot block (Input/output error)
    Error: The underlying task reported failure on exit
    1 non HFS volume checked
    1 volume could not be repaired because of an error
    Im in mexico writing a book and so i really need help on this one guys.

    Hi, hjbugs, and welcome to Apple Discussions. Disconnecting the drive while your Powerbook was accessing it probably caused your problem. It may be repairable using DiskWarrior or TechTool Pro, but if you don't have access to one of those and aren't going to buy one, reformatting the drive with Disk Utility may be the only other way to make it usable again. If it contains data you need to recover first (i.e., data that isn't also stored on your internal HD or other storage media), download the free demo version of one of the data recovery utilities mentioned in this thread and use it to see what is recoverable. If the files you need are recoverable, buy the full version of one of the utilities and recover them.

  • Having problems with External Hard Drives on my Laptop

    Ever since using linux i've always had the same problem. Whenever i connect a hard-drive, it keeps disconnecting/ spitting input-ouptut errors.
    I thought it was because of the hard-drive failing, which turned out to be the problem with my last two, but i'm using another one (Seagate MomentusXT 500GB) and i'm getting the same problem.
    I had just reformatted this hard drive from NTFS to Ext4 using Gparted, so maybe that's the problem? I'm really kind of lost.
    I mount my HDD like this:
    sudo mount /dev/sdd1 /mnt/usb
    and unmount like this:
    sudo umount /mnt/usb
    It connects initially, and i'm able to put stuff onto it. I was able to put a whole TV series on it successfully, but when i tried copying my music onto it it failed and alot of the music didn't copy, giving me these errors:
    ile system
    cp: cannot create directory ‘/mnt/usb/music/Clawfinger’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Cake’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/The Glitch Mob - Discography’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Bastille - Bad Blood (The Extended Cut)’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/ARCTIC MONKEYS - DISCOGRAPHY (2005-13) [CHANNEL NEO]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/NIRVANA DISCOGRAPHY @320Kbps CbR Mp3 [TuGAZx]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/The Doors - STUDIO DISCOGRAPHY’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Tiesto - Red Lights (2014.Dance)’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Tiesto - A Town Called Paradise (Deluxe Edition) 2014 320kbps CBR MP3 [VX]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Daft Punk - Discography - 1994-2013’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Pink_Floyd_Greatest_Hits’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Calvin Harris - Discography - 2007-2013’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Weezer [Discography]’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/MGMT’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Blackmill’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Avicii - Discography’: Read-only file system
    cp: cannot create directory ‘/mnt/usb/music/Zedd’: Read-only file system
    cp: preserving times for ‘/mnt/usb/music’: Read-only file system
    I can then unmount and mount the HDD again, and try again, but i keep getting the same problem.
    Here's my dmesg:
    [22951.444217] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [22966.616452] usb 1-1: device descriptor read/64, error -110
    [22981.892003] usb 1-1: device descriptor read/64, error -110
    [22982.155518] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [22997.327767] usb 1-1: device descriptor read/64, error -110
    [23012.603571] usb 1-1: device descriptor read/64, error -110
    [23012.867002] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [23017.881048] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23017.881078] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23023.098593] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23023.302055] usb 1-1: device not accepting address 19, error -62
    [23023.462289] usb 1-1: reset high-speed USB device number 19 using xhci_hcd
    [23028.476297] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23028.476314] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23033.693797] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23033.897336] usb 1-1: device not accepting address 19, error -62
    [23033.897435] usb 1-1: USB disconnect, device number 19
    [23033.903973] sd 10:0:0:0: [sdd] UNKNOWN Result: hostbyte=0x01 driverbyte=0x00
    [23033.903976] sd 10:0:0:0: [sdd] CDB:
    [23033.903977] cdb[0]=0x2a: 2a 00 03 90 e5 10 00 00 f0 00
    [23033.903982] blk_update_request: I/O error, dev sdd, sector 59827472
    [23033.903985] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478464)
    [23033.903987] buffer_io_error: 4990 callbacks suppressed
    [23033.903988] Buffer I/O error on device sdd1, logical block 7478178
    [23033.903990] Buffer I/O error on device sdd1, logical block 7478179
    [23033.903991] Buffer I/O error on device sdd1, logical block 7478180
    [23033.903992] Buffer I/O error on device sdd1, logical block 7478181
    [23033.903993] Buffer I/O error on device sdd1, logical block 7478182
    [23033.903994] Buffer I/O error on device sdd1, logical block 7478183
    [23033.903995] Buffer I/O error on device sdd1, logical block 7478184
    [23033.903996] Buffer I/O error on device sdd1, logical block 7478185
    [23033.903997] Buffer I/O error on device sdd1, logical block 7478186
    [23033.903998] Buffer I/O error on device sdd1, logical block 7478187
    [23033.904015] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478524)
    [23033.904027] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478554)
    [23033.904050] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478584)
    [23033.904066] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478614)
    [23033.904080] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478644)
    [23033.904095] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478674)
    [23033.904110] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478704)
    [23033.904124] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478734)
    [23033.904139] EXT4-fs warning (device sdd1): ext4_end_bio:317: I/O error -5 writing to inode 16777759 (offset 0 size 8388608 starting block 7478764)
    [23033.905630] sd 10:0:0:0: [sdd] UNKNOWN Result: hostbyte=0x01 driverbyte=0x00
    [23033.905632] sd 10:0:0:0: [sdd] CDB:
    [23033.905633] cdb[0]=0x2a: 2a 00 03 90 e6 00 00 00 f0 00
    [23033.905639] blk_update_request: I/O error, dev sdd, sector 59827712
    [23033.906165] Aborting journal on device sdd1-8.
    [23033.906176] JBD2: Error -5 detected when updating journal superblock for sdd1-8.
    [23033.906270] EXT4-fs (sdd1): Delayed block allocation failed for inode 16777761 at logical offset 0 with max blocks 2048 with error 30
    [23033.906272] EXT4-fs (sdd1): This should not happen!! Data will be lost
    [23033.906276] EXT4-fs error (device sdd1) in ext4_writepages:2395: Journal has aborted
    [23033.906793] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.906801] EXT4-fs error (device sdd1): ext4_journal_check_start:56: Detected aborted journal
    [23033.906802] EXT4-fs (sdd1): Remounting filesystem read-only
    [23033.906803] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.906808] EXT4-fs (sdd1): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 16777762; err -30
    [23033.907641] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907644] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907690] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907692] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907736] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907738] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907771] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907773] EXT4-fs (sdd1): previous I/O error to superblock detected
    [23033.907805] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907845] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907886] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907919] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23033.907947] EXT4-fs error (device sdd1): ext4_find_entry:1289: inode #16515073: comm cp: reading directory lblock 0
    [23034.490498] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880225074480
    [23034.490502] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802250744c8
    [23220.391199] usb 1-1: new high-speed USB device number 54 using xhci_hcd
    [23235.563509] usb 1-1: device descriptor read/64, error -110
    [23250.839126] usb 1-1: device descriptor read/64, error -110
    [23251.102653] usb 1-1: new high-speed USB device number 55 using xhci_hcd
    [23266.274917] usb 1-1: device descriptor read/64, error -110
    [23281.550616] usb 1-1: device descriptor read/64, error -110
    [23281.814174] usb 1-1: new high-speed USB device number 56 using xhci_hcd
    [23286.831502] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23286.831579] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23292.049048] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23292.252556] usb 1-1: device not accepting address 56, error -62
    [23292.412732] usb 1-1: new high-speed USB device number 57 using xhci_hcd
    [23297.426714] xhci_hcd 0000:00:14.0: Command completion event does not match command
    [23297.426728] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23302.644273] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
    [23302.847753] usb 1-1: device not accepting address 57, error -62
    [23302.847781] usb usb1-port1: unable to enumerate USB device
    Anyone know how to fix this?

    There is a whole lot of bad going on there.
    There are problems both drive errors and USB errors.  I don't believe it.
    I have a hunch the drive is starving for power. 
    USB devices are supposed to function all the way down to 4.25V.  Not all do.
    USB ports are supposed to be able to deliver 4.25V at the end of the cable at 500mA.  Not all do.
    USB 2.0 devices are not supposed to draw more than 100mA unless they negotiate for more.  Some violate that.
    USB 2.0 devices are never supposed to draw more than 500mA. Some violate that.  Especially disk drives.
    My guess is that your drive is drawing excess current and the voltage drop through the port and cable are dropping you below 4.25; or at least below the voltage that your drive goes "Tango Uniform"[1].   Does your drive have the option for external power?  If so try it.  Following up on wtx's comment;  USB 3.0 is capable of delivering more power.   Also, some drives have used a cable that violates just about every aspect of the USB specification:  A "Y" cable that plugs into two host ports to provide more power to the guest.  I despise this solution with every fiber of my electrical engineering existence; never-the-less, you might try one.
    edit:  [1] Teats Up.
    Last edited by ewaller (2015-04-04 17:02:04)

  • Problem with External Hard Drive

    Hi,
    I'm having trouble with my External Hard Drive, a 300GB Iomega USB. Everytime i use it with my iMac G4 it disconnects by itself and i get the "Device Removal" message after 20 minutes or so. This occurs even though the Mac hasn't moved, the Hard Drive and its wire wasn't moved and even when I'm not doing anything on my Mac. This occurrs in all three of the USB ports even though other devices plugged into them work fine.
    It's a problem with your External Hard Drive and/or its wire i hear you say. However, the External works fine when plugged into my Windows Laptop.
    Any help would be much apreciated as all my music, movies and work are on my External.
    Thanks in advance,
    K

    Hi there:
    You may have to use a Mac disk utility on the external USB hard disk drive, since the error
    you see is likely caused by some defect. And the symptom is in how the drive fails to mount.
    Perhaps a tool like Disk Utility could see what kind of errors, but not fix them; if this is the
    case, a more specific tool such as DiskWarrior (for the Mac OS your machine has) may help.
    Depending on the level this problem exists, the drive may be repairable through use of one
    of the disk utility type of tools; or it may need to be erased, reformatted, etc. So, if there is
    some kind of error in the directory or other portion, DiskWarrior could probably fix it and not
    interfere with the data on the drive... Or, that's the hoped-for outcome.
    And that direction is likely one to pursue. For the sake of discussion, you - do - have extra
    USB cords, just in case you have one that does not like Macs? A diabolical PC infiltrator?!
    Good luck & happy computing!

  • IPhoto problem with external flash drive

    I'm trying to transfer some pictures from IPhoto to my external flash drive but it won't allow me to.

    Hi jschmidt33,
    Welcome to Apple Support Communities!
    Try following along with the article below, if you follow those steps you should be able to save photos to your external drive or any other folder on your computer's internal drive.
    iPhoto '11: Export a photo
    http://support.apple.com/kb/ph2438
    When you email, print, publish, or export a photo from your iPhoto library, iPhoto asks you to choose the size, also known as resolution. The settings you choose depend on what you want to do with the photo.
    To change a photo’s size or file format, you export the photo. You might want to export photos so that you can import them into another application.
    To export photos:
    Select the photo or photos you want to export.
    Choose File > Export.
    At the top of the Export Photos window, click the File Export button.
    To specify the file type for the exported photo, choose an option from the Kind pop-up menu:Original: Exports the photo as it was originally imported into iPhoto, before editing.Current: Exports the photo in its current format. If you imported a RAW-format photo and then edited it in iPhoto, the photo is exported as a JPEG file.JPEG: If you choose this format, choose an option from the JPEG Quality pop-up menu. The higher the quality, the bigger the photo. For example, if the photo will be used on a website where optimal quality for printing isn’t required, you could choose Low to save storage space on the website.TIFF: A lossless file format that works well for transferring photos between computers and applications.PNG: Another lossless file format popular for web images.
    To change the size (resolution), choose an option from the Size pop-up menu:
    For photos to be emailed or mainly viewed onscreen, these settings compress the photos (making them smaller):
    Small: Use for photos you email or publish to websites where you don’t expect anyone to download and print your photos.
    Medium: Use when you or your recipients have a reasonably fast Internet connection, such as DSL. This setting is not suitable for making prints.
    Large: Use this setting when you and your recipients have a very fast connection. This size can be used to print small to standard-size photos (2 by 3, 3 by 5, and 4 by 6 inches).
    For photos to be printed or published for download, these settings provide maximum detail for final prints:
    Optimized: Use for larger prints and for publishing photos to websites for others to download and print. With this setting, photos are slightly compressed to a smaller file size so that they download faster without compromising quality.
    Actual Size/Full Size: Use to make high-quality prints in small to large sizes, or to upload photos to websites so that others can download and print them. This setting matches the actual size of your photo, so it may take longer to upload or download.
    Specify your other options:Include checkboxes: If you choose JPEG or TIFF from the Kind pop-up menu, you can include titles, keywords, and location information with the exported photos by selecting the checkboxes.File Name: Choose whether to export photos in sequence, or by their filenames, iPhoto titles, or album name.Prefix for sequential: If you choose Sequential from the File Name pop-up menu, you can specify text to appear before each number (for example, Birthday01, Birthday02, and so on). This step is optional.
    Click Export.
    Choose where to save the exported photo files, and then click OK.
    iPhoto works best with JPEG files, the standard format for data compression of still pictures. If you experience problems working with a non-JPEG file in iPhoto, use a different image-editing application to convert the image to JPEG.
    Good luck!
    -Jason

  • When is Apple going to fix the problem with external hard drive not working on Lion?

    As for everyone else external hard drive does not work with Lion.
    When will Apple fix this problem. Do they just ignore the customer : (

    Copy off all your data off the NTFS formatted drive to another drive
    Open Disk Utility in the Applications>Utilities folder
    Select your external NTFS drive on the far left,  should have the drive makers name, a ID perhaps plus the word "media"
    Click the Partition Tab, click the big box and click 1 Partition
    If you want a Mac only drive > Option: GUID >format OS X Extended (Journaled)
    If you want a Mac/PC drive (for over 4GB sized files) > Option: MBR > format exFAT
    If you want a Mac/PC drive (for the most compatibility with other devices, Win XP, but only under 4GB sized files) > Option: MBR > format MSDOS (FAT or FAT32)
    Give it a name and click Apply.
    You can also search Microsoft for a free exFAT download if you have Win XP.
    https://discussions.apple.com/message/16276201#16276201

  • [SOLVED] Problem with external USB drive started yesterday

    My system freezes for about 65 seconds at the login screen. After 65 seconds, I can login and everything is normal afterwards.
    I discovered that I can eliminate the freeze by disconnecting the external USB drive from the PC. Here are the error messages from kernel.log when the drive is connected:
    Oct 15 23:10:14 localhost kernel: [ 17.035091] usb 1-1.3: device descriptor read/64, error -110
    Oct 15 23:10:29 localhost kernel: [ 32.155955] usb 1-1.3: device descriptor read/64, error -110
    Oct 15 23:10:29 localhost kernel: [ 32.325394] usb 1-1.3: new high speed USB device number 4 using ehci_hcd
    Oct 15 23:10:31 localhost kernel: [ 34.045126] MediaState is connected
    There is supposed to be a kernel boot option (irqpoll) to prevent this from occurring. However, that option seems to no longer work for kernels after 2.6.39. If I try using it with Arch, the system will not boot, saying all the CPU's failed.
    I also don't understand why this just started happening yesterday, as the USB drive has been connected to the PC longer than I've been using Arch. Also, my kernel has not been updated since I installed Arch on Oct 8.
    Does anyone know another fix or workaround for this problem?
    Thanks,
    Tim
    Last edited by ratcheer (2011-10-17 01:30:08)

    Problem solved
    I feel stupid, but I also feel better. I turned off the PC, disconnected the power from the USB drive for about 15 seconds, reconnected the power, rebooted, removed the irqpoll kernel option, and Ubuntu started, perfectly. I need to learn that the USB drive just goes freaky sometimes and remember to do this. But, this is only the second time I've had to do this in months of use.
    Tim

  • Hardware or software problem with external hard drive?

    Hi folks.  I have an OWC Mercury Elite external hard drive  with a capacity of 500GB.  I'd been using it to back up my iMac for about 1 1/2 years by copying my "home user" folder into the external drive.  I was keeping about three old backups on the external hard drive and there was plenty of capacity left.  Then all of a sudden when I tried to back up, I got an error message that said something like, "cannot copy Desktop5 because of insufficient space."
    I tried to fix the problem by deleting all but my most recent backup, but it didn't help.  Right now, the external drive is showing "Capacity" of 465.64GB with 11.69GB listed as "Available."  I have a complete backup of 32.63GB and a partial backup of 15.46GB on the external drive, but otherwise I can't find anything else on it.
    Is this problem caused by my external drive, my operating system, or something else (i.e., ignorant operator)?  Many thanks in advance for any help you can give.
    Regards,
    John

    pushprogress wrote:
    ...Then I went to empty the trash...175,000 items in there.  Gotta get around to that more often!
    Easy thing to miss, especially with an external drive that you are mounting and unmounting. Glad to hear you're back in the water.

  • Aperture 3 problems with external hard-drives

    Because of an external drive failure I had to move my Aperture Library 350+gb to another external hard-drive (iMac only has 500 gb internal drive). It is working; however, about 2500 photos are referenced, the rest are managed masters. No problem apparently with masters. But cannot reconnect with referenced files because the external drive is now deceased and cannot be dismounted. (Please continue reading before firing off an answer telling me to repair the database with Opt Command at start up. That did not solve my problem.)
    I know how to individually reconnect files which were located on a (now) offline (permanently) volume. But is there no easier way to get Aperture to recognize that a drive no longer exists and a new drive has taken its place? (Yes. I have read about using SQLite Database Browser to change the UUID of the drive to the new drive. But this seems bizarre that a high end program like Aperture 3 requires users to tweak the database to get Aperture to recognize a new drive.) I have installed the most recent Aperture update. There was one today I believe. No help.
    Thanks for your input.

    paulfresh wrote:
    it also appears to be mavericks... I don't have any software programs installed for both my OWC and lacie drives and they still wont eject properly under Mavericks
    No, it doesn't appear to be Mavericks. All good here on the five Macs in my studios and all attached drives. But blame Apple if it makes you feel better.
    http://www.theregister.co.uk/2013/11/05/western_digital_fesses_up_to_mavericks_d ata_loss_mess/
    Cheers
    Pete

Maybe you are looking for