Firewire drive Device Removal error

I have three (3) firewire enclosures and only one of them works with my intel Mac. All three work great with my old G4 laptop and iMac but now I connect them to this new intel Mac and I get the beach ball that spins and can not read the drive. Well actually I can read the drive for maybe a minute before it locks up and in some cases it dismounts by itself and give me a Device Removal error. I have tried them one at a time and only one of the enclosures seams to work without any issues, the other two will work fine on the G4 but not on the intel. One of the enclosures that I have trouble with I formatted the hard drive using the intel Mac with Disk Utility and still no luck. Could this be a driver issue with the intel Mac? I know it's not the hard drive because I swap it into the other enclosure and it works fine. So what gives? Any suggestions would be helpful. Rick
Mac Pro   Mac OS X (10.4.8)  

Took your advise and called Apple support concerning this issue. Apple support person was not surprised by the front port causing some issues when transferring large amounts of data. Even though the rear ports could handle this with no problems. He reported that the front ports are similar to a hub and are there for convenience for small transfers and are not hard wired into the motherboard like the rear ports. He suggested that for large file transfers should always use the rear ports or a powered hub such as on the back of the Mac HD Monitor. So there you go... not what I was looking for in a answer but makes sense. Hope this will help others not waste a lot of time wondering why some issues pop up when using the front ports. Rick

Similar Messages

  • When waking from sleep getting "Device Removal" error on Lacie external

    When waking from sleep getting "Device Removal" error on Lacie external drive. This drive is my Time Machine back-up and I don't want to lose it. I don't know if anyone else has seen this error. Let me know.

    Getting this same error since switching from Firewire to USB. I have a Maxtor drive in an Adaptec enclosure. It has it's own power supply and both USB and Firewire 400 connections. Just upgraded to a new Mini from old Powerbook, so no more Firewire 400!
    The big difference between USB and FW:
    With the old PB G4 and Firewire, when I put it to sleep, I could hear the external drive actually spin down. On wake up, It would spin up and mount properly. Now with the Mini and USB, when I sleep the Mini, the external drive NEVER SPINS DOWN. I did some research and found that many drives have built-in power management that basically powers them down after some idle time. So the Mini is going to sleep with mounted drives, at some point later the drive sleeps itself, then when the Mini wakes, the drive's not there.
    Obviously, Firewire is doing a better job of talking to my external than USB. I'm ordering a FW400-to-800 cable and will test this. I also think it has something to do with the chipset/firmware in the external enclosure, as many people are reporting their external USBs behave properly during sleep.

  • Device removal error?

    I picked up a new 500 gig Hitachi hard drive to put into a vantex hd enclosure. Now every time I try and use it, i get a device removal error and the hard drive icon on the desktop disappears. I can't use Time machine or verify my hard drive in disk utilities because it always seems to eject itself. I tried a couple different USB cables and tried rebooting my computer. Both products are new, I'm wondering if it is a hardware problem and if it is, which one, the enclosure or the hard drive?
    Any suggestions?

    Thanks for the suggestion but..
    Tried that this morning and it still doesn't work:( I turn it on, start up Time Machine and it starts backing up the files and then some times it will start backing up 20-30 gigs and then give me the device removal error, or sometimes it only backs up 10-20 mb before giving me that error, but even after it ejects itself the hard drive is still on, but i have to turn it off and then back on again for the disk to remount. I'm leaning towards a hardware problem, just not sure if its hard drive or enclosure. I bought both online and having to send them back is always a pain because they usually just send them back saying they work and tack on another fee. Im hoping to resolve this some other way, but running out of ideas.
    Any other thoughts?

  • Xserve Raid - Devicer Removal Error ?!

    Hi !
    Can anybody help me ?
    Whenever I copy some files from my Macintosh HD on my G5
    to Xserve Raid 30 seconds after start copy process stops and I
    get an Device Removal error.
    I have traid everything and I can't get it right.
    BTW
    is my setup ok ?
    Apple Fibre Channel Card
    Port speed: 2 Gb/s
    Port topology: Arbitrated loop
    Xserve Raid
    Port speed: 2 Gb/s
    Port topology: Arbitrated loop
    Read prefetch: 128 stripes - 8 MB/disk
    Controller cache: on
    Drive cache: on
    Host flushing: off
    Steady Streaming: off
    Raid slices:
    2x250 GB left controller
    2x250 gb right controller
    Disc Utility software raid:
    Striped raid 0
    left + right
    Raid block size (default: 32 K): 256K
    Please help!
    Thx!
    Crowebster

    Hey Kel,
    I've only seen a error -36 on a raid volume twice.. both times were days before a controller failed. I'd try swapping controllers and see if the problem follows the controller...

  • Device Removal Error Notification

    I accidentally stepped on the USB cable of my external hard drive and my computer showed a device removal error notification and that data might have been lost. I know properly ejecting the hard drive clears out the cache, but how can you tell what data was lost. Is it obvious like an entire folder/file would be missing, or would just pieces of data from a file be missing?
    Also, it said data MIGHT have been lost or damaged. Is it possible that nothing happened at all?

    It could potentially damage multiple files, but I would consider it unlikely. More likely it would damage the disk directory, affecting the entire drive, rather than damage more than the file being written. Again, though, I won't say it's impossible.
    I've also tried to run Disk Utility on it to verify the disk, but it says the disk could not be unmounted
    Got any software accessing the drive, such as iTunes, iPhoto, or anything else that might have a file open on the drive?
    As to your query, what you're seeing seems normal. It's telling you how many files it sees (and "files" do not necessarily equal "documents"; it's what a computer considers to be a file, which can include all sorts of invisible items). As to what "clusters" are, there's a good explanation here:
    http://www.dewassoc.com/kbase/hard_drives/clusters.htm
    Regards.
    Message was edited by: Dave Sawyer

  • Device removal error.....   The card reader ejects itself

    Hello, I'm new to macs and purchased a Mac Mini a week ago. Things were going well until I needed to move pictures from a digital camera to my mac.
    I purchased a GE 19 in 1 card reader which is built for mac os x. I hook it up to a usb port and try and look at some pictures. After a few seconds, the card reader ejects itself and I get the "device removal" error. The error will then continue to appear over and over again. When I try to eject the reader using by clicking eject, the reader ejects and only reappears a minute later and ejects itself again. I've tried using another usb port and I know for sure that its not the cable.
    If I can't get any prompt answer here, I'm going to call the Genius bar tomorrow morning and ask about the problem. <Edited by Moderator>

    More often than not, when a card reader or other similar device disconnects from the USB bus because it is drawing too much power. In a card reader, that would not unusually be triggered not by the card reader itself, but by the insertion of a card causing it to read the content and mount the volume on the Mac's desktop. Part of the problem is that while everything is invariably quoted as USB compatible, many such devices don't entirely comply with the USB standard, resulting in conflicts or load demands which may be borderline, or worse.
    You may be able to get more reliable performance from your reader by disconnecting other USB devices when you are trying to use it, or by using it with a powered USB hub. Occasionally, borderline problems can be temporarily resolved by connecting the device to a different port, if necessary switching devices around. Alternatively, it may be that in an attempt to produce a device with the greatest flexibility in terms of media compatibility, they have compromised on components.
    I would generally recommend a card reader designed for the specific card type you need. These are typically far more reliable. If you need to use different types of card media, then be prepared to spent on a well established brand with a reputation in this sector of the market, such as SanDisk.

  • Device removal error when flash drive is plugged in

    I have a 1GB flash drive that I have used for a while with my Windows XP desktop. I switched from a PC laptop to a Mac Book Pro running Leopard. But the Mac Book gave me the drive removal error when I tried to use the flash drive. The PC desktop worked with the drive just fine. So I backed up the flash drive and reformatted it in FAT32. Then I reloaded the files. For a short while I had no problem with the Mac Book. Now I am getting removal errors again. I have been careful not the remove the drive, either from the PC or or the Mac Book, without going through proper procedures. It does no good to "repair" the drive from the Mac Book. Any suggestions?

    Maybe:
    http://www.macobserver.com/tmo/article/usb-3.0-hard-drives-can-cause-wi-fi-inter ference
    Re: 2012 Mini Bluetooth/USB3 Interference
    http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb3-frequency-in terference-paper.html
    usb 3.0 interface for 2010 Mac Pro running Yosemite?

  • PremiereCS3 won't start when firewire drive is removed

    I've had to remove a Lacie firewire drive to reformat it on another system but now Premiere will only flash the loading screen and then dump out (no error messages, just shuts down) when I try to start it. Is there a way to start up Premiere to get some work done while this drive reformats?
    BTW this drive was not used to store any media.
    Thanks in advance.

    Rename your PPro
    preferences file.
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • Device removal error: why does external HD randomly eject?

    I just picked up leopard, and a vantex enclosure and a 500 gb hitatchi enclosure. Whenever I try to run time machine, the external hard drive unmounts but the hard drive is still running. When formatted it coupe times over as a mac OS Extended (Journaled) with a GUID Partition Table. But its still giving me problems. Also when I try to verify or repair the disk it does the same thing. It seems like when its spinning up really fast it doesn't work right.
    please help!!

    I have the exact same problem (but I'm not using time machine)
    Checkout my thread here:
    http://discussions.apple.com/message.jspa?messageID=7074847#7074847

  • Sudden device removal via Firewire 800

    I just purchased a MacBook Pro. I have a LaCie rugged drive that is a clone of my old iBook running Panther. I connected the LaCie via Firewire to the MBP to transfer some files. (Migration Assistant didn't get everything???) The LaCie kept suddenly disconnecting, resulting in a device removal error. I have two different cables; tried them both. It connected to the old iBook last night with no removal error.
    Any ideas??

    Here's what LaCie had to say:
    Thank you for contacting LaCie Technical Support. As the issue you describe is an intermittent issue, it is difficult to pin point the exact issue and an exact resolution.
    Mobile drives are commonly referred to as "Bus Powered" devices. They don't typically require an external power supply, and are powered by the ports on the computer. Ordinarily this is an acceptable amount of power, however, not all machines are capable of running these devices.
    Most mobile drives require approximately 4 watts of energy to run. Most computers produce this, so it isn't a problem. There are exceptions, however. The physical symptom of insufficient power is a soft "clicking" sound. OS behavior can vary.
    * On Mac OS X, the mobile drive can appear as an "Unknown Device" in Apple System Profiler (ASP), appear in an unusual way in Disk Utility, refuse to format with error -36, or have no reaction at all
    * On Windows, the drive can appear with a Code 10 error in Device Manager, appear in an unusual way in Disk Management, refuse to format, or have no reaction at all.
    All mobile drives have a "USB Power Sharing" cable included in the box. If a power problem is suspected, connect this cable to a second USB port on the computer. This will allow the drive to take more power, and can possibly make the difference in allowing it to work. Also, ensure the drive is not connected to a USB Hub of any kind. Connect all bus-powered devices directly to the computer USB ports.
    Let us know the results.
    Thoughts? Anyone?

  • Device Removal message for internal hard drive after coming out of sleep

    Hi,
    I have search the forums and all the info I can find seems to just refer to external hard drives, how ever the problem I am having is with the internal drive.
    When my G5 comes out of sleep mode, shortly after, I get a Device Removal error message then I loose my second drives and have to reboot for them to return. The drive is a 500 GB divided in two partitions, Mac OS Extended (Journaled), in slot B.
    I have used Disk Utility and Tech Tools to check the drive, and the drive passes with no errors. I can't check file permissions as the drive is not a start-up drive.
    This problem just started not long after using a USB thumb drive in the front, maybe just a coincidence or something went haywire after ejecting the USB drive?
    Thanks,
    Bill...

    DaddyPaycheck wrote:
    What brand is the drive?
    Do you have a USB hub to try?
    Have you checked the disk manufacturer's website to see if there are any updated drivers or firmware available and/or needed?
    DaddyPaycheck wrote:
    I have two Western Digital drives in the computer, both partitioned into two drives. One is a 1 TB the other a 500 GB. The 1 TB drive is the boot drive and I installed it about 2 months ago. The 500 GB drive, the one that is disappearing, I installed it about 6 months ago. Both drives pass Disk Utility, and TechTools testing (that is before the one disappears).
    I do not have a USB hub, I have a DVD/RW connected via Firewire, and I have a USB external 320 GB to use for whatever.
    No, I didn't think to check the manufacturer's web site for updates as the drives work fine, just the one 500 MB drive out of the blue I get the Device Removal message. And I am using the G5 at this moment replying here, and so far today I have connected my camera via usb with out issues.

  • Trying to Recover Data from broken Hard Drive - Device Wont Show in Finder

    I just had the hard drive replaced in my intel iMac (the old one isn't working properly). The apple store folks told me they would not do any data recovery off the old drive, but suggested I might be able to get a SATA to USB adapter and plug the old drive in the computer.
    The first time I plugged the old hard drive it showed up in the finder and I began transferring the old file. 6 GB into it the transfer stopped and the the old hard drive disappeared from the finder. Now the drive wont appear in the finder HOWEVER when I unplug it I get the "Device Removal" error.
    A little about my broken drive:
    Its a Western Digital 320 GB. Its not making any clicking sounds or anything, which makes me think it might just be the circuit board which is replaceable. But I don't want to waste $50 on a new circuit board if thats not the problem.
    Any suggestions?

    Basics of File Recovery
    If you stop using the drive it's possible to recover deleted files that have not been overwritten by using recovery software such as Data Rescue II, File Salvage or TechTool Pro.  Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.  Two free alternatives are Disk Drill and TestDisk.  Look for them and demos at MacUpdate or CNET Downloads.
    The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
    Also visit The XLab FAQs and read the FAQ on Data Recovery.

  • Continuous USB Device Removal Messages on certain Flash Sticks since 10.5.2

    I have run into a problem with both my MacBook Air and Mac Pro since running 10.5.2, and this was not fixed in 10.5.3:
    Most Flashsticks appear to be continuously removed and replugged over 5 sec intervals. I continuously get the "Device Removal Warning." These worked before, and do not have the problem running under BootCamp on the same machine, or being assigned to VMWare. An example is an Emprex 4GB stick, which was not cheap, when bought. They also do not have issues on Dells, or Macs running tiger!
    These are plugged directly into the system, no hubs or cables in between.
    There are other brands that do not have the issue.
    Has anybody run into this? This is very annoying.
    -- Harald
    Message was edited by: HaraldS

    I'm seeing that issue with an Adata 8GB stick (www.adata.com.tw).
    That same stick works fine on my MacMini (ppc), Dell 700m, and Lenovo T60p.
    In all cases, I'm always connecting the stick directly to the systems.
    The failure happens at various times after insertion. Sometimes Finder doesn't event display the contents, sometimes I'm able to copy 20MB before the copy hangs. In all cases (dozen times) on the MacBook Air, it never worked reliably.
    The MacBook Air USB port is not (completely?) busted, as it works fine with my Maxtor OneTouch USB2.0 external disk.
    Applications -> Console shows the following messages, starting from device insertion to "Device removal" error message:
    (the rest of this post is only the console log)
    +2008-08-17 4:54:09 PM fseventsd\[26] log dir: /Volumes/JPAUSB8GB/.fseventsd getting new uuid: 5FA60CFC-8EA9-46D5-A0D5-7D20C36C64A0+
    +2008-08-17 4:54:57 PM kernel USBF: 6841.387 AppleUSBEHCI\[0x3c4e000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 3, EP: 1)+
    +2008-08-17 4:55:28 PM kernel USBF: 6872.390 AppleUSBEHCI\[0x3c4e000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 3, EP: 1)+
    +2008-08-17 4:55:34 PM kernel USBF: 6878.390 AppleUSBEHCI\[0x3c4e000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 0, EP: 0)+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM kernel 1-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.cmpt.indexDirectory] \[FSLogMsgID 1230162260] \[FSLogMsgOrder Last]+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    \[repeated 9 times]
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(47 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexPostings, 1531) error:13+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(55 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexPositions, 4) error:13+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(59 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexArrays, 70640) error:13+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in storageTruncate:ftruncate error 13+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(60 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexCompactDirectory, 8) error:13+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(57 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexDirectory, 2056) error:13+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    \[repated 6 times]
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in indexShadowFiles:open err: 13, 0.shadowIndexHead+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexGeneral in notify_lowspace:low space for device 234881028 (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (Error) Volume: LOW DISK SPACE device:234881028+
    +2008-08-17 4:55:37 PM kernel ] \[ErrType IO] \[ErrNo 13] \[IOType Read] \[PBlkNum 31824] \[LBlkNum 31824] \[FSLogMsgID 368749274] \[FSLogMsgOrder First]+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in index_compact:open err: 13, tmp.0.cmpt.indexHead+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(57 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexDirectory, 0) error:13+
    +2008-08-17 4:55:37 PM kernel kNum 31040] \[FSLogMsgID 454989150] \[FSLogMsgOrder First]+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(60 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexCompactDirectory, 0) error:13+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(59 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexArrays, 0) error:13+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(47 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexPostings, 0) error:13+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(55 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.indexPositions, 0) error:13+
    +2008-08-17 4:55:37 PM mds\[20] (/Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F)(Error) IndexCI in ci_ftruncate:ftruncate(64 /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F/tmp.0.c mpt.newTermIDMap, 0) error:13+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (/)(Error) IndexGeneral in SIPersistentIDStoreCreate:Couldn't make psid store at /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:37 PM mds\[20] (/)(Error) IndexGeneral in SIPersistentIDStoreCreate:Couldn't make psid store at /Volumes/JPAUSB8GB/.Spotlight-V100/Store-V1/Stores/BAA51F71-1D1A-4E07-90A9-34CCE9A7FD8F+
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    \[repeated 6 times]
    +2008-08-17 4:55:37 PM kernel disk1s1: device/channel is not attached.+
    +2008-08-17 4:55:40 PM kernel USBF: 6884.390 AppleUSBEHCI\[0x3c4e000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 0, EP: 0)+
    \[repeated 4 times at 6sec interval]
    +2008-08-17 4:56:07 PM kernel USBF: 6911.911 \[0x3dad300] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of hub @ location: 0xfd000000)+
    +2008-08-17 4:56:07 PM kernel disk1s1: media is not present.+
    \[repeated 4 times]
    +2008-08-17 4:56:07 PM kernel disk1s1: media is not present.+
    +2008-08-17 4:56:14 PM kernel USBF: 6918.393 AppleUSBEHCI\[0x3c4e000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 0, EP: 0)+

  • IBook won't load Firewire drive; "unknown device"

    That's the summation via System Profiler. It's a SmartDisk Firelite enclosure but I swapped the old 40 GB drive that failed for a new Seagate Momentus 80 GB drive. My G4 dualie recognizes the new SmartDisk setup fine. It loads immediately and I was able to access via all the utilities. Transfers work well.
    But on the 1.33 iBook the green light appears on the SmartDisk enclosure, but no threat of loading. Only System Profiler identifies something, "unknown device" with 400 capability. When I remove the firewire cable, System Profiler doesn't see anything.
    I had no trouble with the SmartDisk prior to the old drive failing. It worked perfectly on the iBook. My firewire port appears to be okay, since I tried Target Disk Mode with the two computers and it worked well.
    Any suggestions would be greatly appreciated. I Googled and found many issues of "unknown device" related to firewire drives, but none that seemed to precisely fit this case, a drive that was recognized on one computer but not another. Both are running 10.4.11.

    I'm still baffled but tonight I found an acceptable alternative, a Macally 250 Firewire/USB enclosure that I had in my closet but never used previously. The Seagate drive loads on both the dualie and iBook using that enclosure, which is bulkier than the SmartDisk but right now I don't really care.

  • WDM Capture Driver: Device Cannot Start (Error 10)

    I have GeForce3 Ti200 with S-Video In, Out and TV out. I'm trying to run Virtual Dub to view my PS2, which is going into the S-Video In. It said I needed capture drivers, so I went to http://www.nvidia.com, got the ones that come with the Personal Cinema thing and installed them. Those didn't work. Came here and tried the drivers here, those didn't work. Tried other drivers and those didn't work. They all said "Device cannot start (Code 10)"
    I've tried 1.1.6, 1.1.7 and 1.1.9. Any ideas? I've searched on google and seen some stuff about turning off ACPI but I use ACPI, so I'm not willing to do that.

    God I love forums, cause 99.9% of the time someone else has encountered the same problem and then hopefully someone else who found a fix, posts that fix.
    http://www.msi.com.tw/program/e_service/forum/viewindex.php?threadid=5847&boardid=9&sid=db40f75790c98440731e8c20eea03e5b
     Much thanks to Nixus, and everyone who had solutions, but I found a variation of Nixus' solution was what worked for me so that's what I'll recommend.
    "I downloaded the bios files from http://tw.msi.com.tw/autobios/SVga/Bios/Ms8850/v111/ and then downloaded NVFLASH.EXE and booted in dos and flashed the card i had to force the flash though it had some conflict of data or something but i knew it was the right bios and i had made a backup of the current one plust the card has dual bios so i wasnt too worried and it all worked out fine.
    Goodluck with gettin all your cards workin
    Cheers
    Nixus"
    This is what I did anyway:
    1) went to http://www.msi.com.tw and dragged the mouse over 'support' and then clicked on live updates 2. Installed this program.
    2) went to http://tw.msi.com.tw/autobios/SVga/Bios/Ms8850/v111/
     which Nixus brought up,
     and clicked on the install button. Which installed some other software to make this button work, then installed the flashing program. Held my breathe while it updated the vga bios, normally I'd do this from a clean dos 5.0 boot disk I have, and voila, problem fixed.
    Well, not quite. After installing updated vga bios, all nvidia drivers were zapped. Or at least not installed right.
    3) Add/remove programs, uninstall nvidia wdm drivers and vga driver for the 1 billionth time. Reboot.
    4) Install 30.82 whql certified ones, rebooted.
    5) Install wdm 1.19 drivers, reboot
    6) Go into system, and now instead of the exclamation point alongside the nvidia capture driver with that error, it just shows as working. Tried virtual dub, btw program rocks except for that 2 gig file limitation, and changed the source to composite and bingo, video in again.
    So long story short, I updated my 8850 to the updated bios, uninstalled all old nvidia drivers, installed 30.82 and then wdm 1.19 and it worky again. Haven't tried it with det4 drivers yet, didn't feel like pressing my luck.
     If you search in this vga forum using the word "capture" without the quotes, it seems this problem with the 8850 and others is QUITE common :(
     Whatever...updated bios fixed it for me...fine...so long as it's fixed. Bad enough I gotta boot into 98se to use my old large, legal sized mustek scanner on account of no win2k/xp drivers, don't want to have to boot into 98crash_edition ( well technically all 95-me could be called that ) everytime I want to cap something.

Maybe you are looking for