USB vs. firewire hard drives

So USB connected HDs aren't that great? Firewire is the way to go? I just bought a MyBook, USB connected. Should I be regretting this already?
Thanks.

Hi schmoel,
I generally prefer Firewire even when I had a PC.
The nice thing when having a Firewire drive is, that USB almost always comes with it.
I also came to the conclusion, that the Apple implementation of USB is always way slower than Firwire on a Mac.
Other than that I think you won't regret ist (if you really do).
But if you can give the USb drive back and get a Firewire one, I would say do it.
Have Fun
Stefan

Similar Messages

  • How can I use a firewire hard drive on a new Macbook with one USB-C only?

    How can I use a firewire hard drive on a new MacBook with only one USB-C?

    kaz-k is correct about FireWire not being supported by any possible connector or adaptor to USB-C and never will.  However, there is no such thing as a FireWire Hard Drive.  There are only SATA (or if it is a really old one, ATA,) drives in a FireWire enclosure.  If you can remove the drive from the case/enclosure - bust it open somehow if it is a glued-up unit - then the drive can be placed into a regular USB3 enclosure. Then it can connect to the new MacBook via any one of the adaptors Apple sells.

  • New Extreme:  Using USB/FW hub w/FireWire hard drive

    I have two laCie external hard drives, one a USB/FireWire and one FireWire only. There are hubs available that have both USB and FireWire ports. If I connect both the USB and the FireWire drives to such a hub, and then connect the hub to the USB port on the new Airport Extreme base station, will my computer be able to read the FireWire drive as well as the USB drive? That is, can I use the hub to link both the USB hard drive and the FireWire hard drive using the USB port on the Extreme? Thanks very much for any thoughts.
    PB 15" 1.0 Ghz 1.25G RAM   Mac OS X (10.4.5)  

    I have two laCie external hard drives, one a
    USB/FireWire and one FireWire only. There are hubs
    available that have both USB and FireWire ports. ...
    I am planning to attach the same two hard drives (Firewire only and USB/Firewire) to an Airport Extreme BS. Lacie was advertising the connectablility of several HDs with Firewire to build a cluster when I bought the "Firewire only" drive 2004. So my suggestion:
    1. connect the HDs via Firewire
    2. connect the USB/Firewire HD to the Airport Extreme
    Unfortunately I cannot test this setup because I will only buy the USB/Firewire HD and the Airport if someone tells me it will work.
    Would step 2 cause the same problems as using dscott1000s hub, or do these USB/Firewire drives have a USB-Firewire-bridge?
    Thanks for any comments or "test reports"!
    Power Books G4   Mac OS X (10.3.9)  
    Power Books G4   Mac OS X (10.3.9)  

  • Journaling External FireWire and USB 2.0 Hard Drives?

    I have several FireWire and USB 2.0 Hard Drives which I have always formatted as "Mac OS Extended (Journaled)".
    I have been told that journaling is a waste of time with external HDs and, if anything, will slow them down slightly.
    What is the general consensus on this forum?

    Thank you for the swift response Malcolm.
    I better explain why after all these years I am having doubts.
    I am awaiting the delivery of a new piece of kit - a Western Digital HD TV Media player. Basically, you put your hi-def videos (H.264) on a USB 2.0 HD, plug it into the media player which is then plugged into your HDTV.
    I have got hold of the manual which says that the supported USB file systems are "FAT32, NTFS and HFS+ (no journaling).
    So I was wondering whether I will have to format the HD without Journaling to make it work?

  • External Firewire Hard Drive is not recognized

    Hello
    I have a LaCie External Firewire Hard Drive (like this one (http://www.lacie.com/us/support/support_manifest.htm?id=10105). Since it uses a fireware 400 cable, I bought a FireWire 800-400 adapter, the one from moshi that is sold in the mac store.
    I have tried connecting it to both ports in the external harddrive, connecting and disconnecting and still is not recognized. Any idea and suggestions?
    I already tried in another computer, with windows xp, and the hard drive works.
    Thanks.

    Hi, oops, I have more than 1 mac & I apologize for assuming you are a multiple mac owner..
    You could visit your local Apple Store or Local Apple Approved Service Agent.
    You could try connecting via USB if your external HD has the capability, it could also be a bad cable.
    You can check the Finder -> Preferences & the Show These Items..
    You can reboot with the Ext HD connected & see if it shows up on your d/top...L

  • Install XP on External FireWire Hard Drive

    Can someone help me install Windows XP onto an External, FireWire, Hard Drive? I can format and partition the drive with the XP CD, but it won't install XP onto the drive.
    It says something about access rights and BIOS or CMOS. I don't think Macs have either a BIOS or a CMOS. I've tried correcting disk permissions with Disk Utility, but it wouldn't do it. It probably doesn't have access.
    So does any body know how to do this?

    Hi Megabyte,
    sad to say but Windows can not be installed to an external Firewire Harddrive.
    And this is not a OSX BootCamp issue, but 'designed' by Microsoft to not be doable.
    Only way I know is with an USB connected external harddisk and described here: http://tubeshards.wordpress.com/2006/12/05/install-windows-to-a-macintosh-usb-dr ive/
    regards
    Stefan

  • Networking a firewire hard drive from a Mac and access the drive from a PC

    I'm trying to network a firewire hard drive from my Mac and access that hard drive from a Windows XP PC. I can see the main internal hard drive but I cannot see the firewire hard drive. Does anybody have a solution or work around?
    Many thanks,
    Roy

    Thanks SO MUCH! Not only does it work, BUT IT IS FREE!!!!
    See, I have two firewire (external) HDs, connected to a Mac, connected to a PC, connected to a USB external HD... now I can share files from the USB HD to the firewire HDs!
    Gotta love technology!
    Matthew

  • Eject Firewire Hard Drive, Won't Stop Running

    I upgraded my Early 2009 Mac Pro OS to 10.9 today, but I found a problem about my external firewire hard drive.
    If I eject firewire hard drive under 10.8, the hard drive will stop running/rotating. Then I unplug the firewire cable. After I upgrade to 10.9 OS, the firewire hard drive will not stop running/rotating after I eject it. I cannot see any external hard drive icon on desktop, but I can hear the hard drive running sound.
    I'm not sure if it's safe to unplug cable under running condition after succeful eject. How's many people have the same problem with me?
    Thank you!

    I have a dozen OWC cases and they have all continued to work (but can't say about 10.9) and they are getting "dated."
    Apple though often changes drivers, IOKIt and how external drives are treated, 10.5.0 thru 10.5.2 the rules changed and changed back and forth. Some drives had to be off during startup. Users have had trouble with 10.6 as well with their drives, often USB and/or FW from major vendors (WD etc) not working.
    Do either of you get the "drive was not ejected properly" message on the next time you do connect and power it back on or after a restart?
    One of the reasons I prefer waiting for the .2 or later releases.

  • Using an external firewire hard drive + interface at the same time?

    Hi Guys,
    It seems that the issues I am having with BFD2 not streaming properly might be to do with the slow USB transfer rate. (Thanks to everyone who has helped with this issue!)
    So... I am thinking of getting an external firewire hard drive for my iMac.
    Thing is, my audio interface also uses firewire (Mackie Onyx 1220)... can they share using a hub? Will one slow the other down? What if I also run another hard drive on firewire for my audio, will two FW drives and the audio interface all be able to share the one firewire port using a hub?
    At the moment, all my drives have their own direct USB port, is going to shared firewire a step forward or a step backwards?
    Cheers and thanks,
    Mike

    Gorwel Owen1 wrote:
    On my G4 (roughly 30 % the power of your MBP)
    Is this with an external drive and interface?
    No Interface (yes, I use built in audio), but that shouldn't make a difference in CPU use.
    I have four Internal drives. But that shouldn't make a difference either
    That is very dependent on what you put on these tracks
    I was thinking mainly about recording i.e. 8 simultaneous tracks whilst playing back up to about 16. I generally avoid plug-ins until mixing anyway. Sounds like I should be OK.
    Absolutely.
    but when logic overloads (when the CPU can't process audio in realtime anymore) Logic simply stops playback.
    When I tried using a drive and interface on the same bus a few years ago I experienced minor glitching rather than stopping. Perhaps Logic has been improved in this respect.
    P.S. How do you 'quote'in the forum?
    Just above the field where you type replies in, there are 5 symbols - they are buttons.
    The first three work on selected text (making it Bold, Italic and Underlined). The abc-tick is spell-checking and the " sign means Quote. When you click it, the message you reply to is inserted wherever your cursor is.
    The preview tab lets you see how the message will look, giving an opportunity to edit. You cannot edit in preview mode though, just look. Only in Compose can you edit.

  • External Firewire hard drive won't mount after 10.4.10 update

    I see many posts about USB drives not mounting after 10.4.10 update. Just lending my voice to that issue (my USB drive won't work either) as well as the 10.4.10 update breaking Firewire drives.
    Hope a fix is coming. No backups are scaaaary.

    How to fix the problem of a missing external Hard Drive (Firewire) after it vanishes from you desktop after installing 10.4.10 update.
    I have a iMac PPC (Non intel). Aparently my system upated installed the wrong version of 10.4.10 and thus my external firewire hard drives a 320 GB Westerndigital My Book, and Acomdata 80 GB, and aWestern Digital 160 GB media center all vanished from the desktop.
    The instructions below should be credited to several different people. I found various version of these steps in the Discussion. I combines a few of them into this one 10 step fix and it worked for me. I hope it works for you.
    1) Shut down you computer
    2) Unplug all peripherals (i.e USB and Firewire, I left computer power plug in as well as ethernet and Keyboard+ Mouse) and leave along for 30 Minutes
    3) Restart holding down the Command (Apple) + Option + P + R keys for three startup bongs, then release the keys and your computer will start up as usual.
    4) Verify and repair disk Permission using Disk Utility. (Several things were repaired here)
    5) Instal 10.4.10 Combo PPC
    6) Restart Again
    7) Again repair Disk permissions (None of mine needed to be repaired fyi this time)
    8) Unplug Power cable and Firewire cable from External Hard Drive (leave along for 1 minute)
    9) Reconnect power to Firewire External Drive first then the Firewire cable to the drive second, then the firewire cable from the Drive to the computer last.
    10) Turn on your Firewire Drive... you will head it spin up and eventually show up on your desktop just like it did before the 10.4.10 update.

  • Is it possible to connect an external USB 2.0 hard drive to a Thunderbolt Display?

    Hello,
    Is it possible to connect an external USB 2.0 hard drive to a Thunderbolt Display and back up a MacBook Air to the external hard drive using Time Machine?
    I intend to connect my MacBook Air to the Thunderbolt Display using a Thunderbolt cable.
    I would also like to connect my printer via USB 2.0 to the Thunderbolt Display. Will this also work?
    Effectively using the Thunderbolt Display as a USB hub or docking station.
    Regards,
    Ben

    Ok, thanks.
    My 1 cable to ThunderBolt Display objective
    MacBook Air -> (via 1 x Thunderbolt cable) -> Thunderbolt Display -> (via 1 x USB cable) -> USB 2.0 external hard drive
    I would like to know if this configuration is possible and Time Machine will run correctly.
    Your 2 cable suggestion (I think)
    MacBook Air -> (via 1 x Thunderbolt cable + 1 x USB cable) -> Thunderbolt Display + USB 2.0 external hard drive
    This configuration requires 2 cables to disconnect/reconnect from my MacBook Air.

  • Unstable firewire hard drives performance in 220 volts countries

    Over the years, I often travel back and forth to the US, Asia and Europe with my MacBook Pro and external firewire hard drives, which were purchased in the USA.  While in Europe or Asia, which generally runs on ~220 volts, I've had several experiences whenever I daisy chained more than 1 external firewire hard drive to my laptop, either the connection was very unstable, resulting in drives randomly unmounting; or my current dilemma where the 2nd drive is not mounting at all.  I never experience these issues at all while I'm in the US.  My guess is that the difference in voltage (110 vs. 220) or cycles (60 Hz vs. 50 Hz) is affecting the drives somehow.  I have experienced this with G-drives, and the Newertech Voyager Q and Wiebetech Traydock which are well built, reliable enclosures.  I pair the enclosures with Seagate or Hitachi drives.  All the enclosures' AC adapters specifically state that they're rated for 100-240 volts.  I thought hooking all my drives to a 2000 watt voltage transformer would solve the problem but it didn't.  Using 1 firewire drive is not a problem, but the daisy chaining seems problematic.  The dilemma is I MUST daisy chain the drives for backup purposes and just for general data wrangling.  Plus my MacBook Pro only has 1 firewire port.  My laptop and firewire port is not the problem, as I've upgraded several times over the years.
    My questions are:
    1. Has anyone else ever experienced USA drives acting funky in 220 volts countries?
    2. Anyone have an idea for a solution to this problem?
    Thanks so much,
    HL
    PS. On perhaps a related note, when I plug my MacBook Pro into a 220 volts outlet and lay my wrists below the keyboard, there is a current or vibration that I do not feel when I'm in the US.

    There is no difference in the power delivered to the computer or the drives, it's 12-15v wherever you are, and it's DC so there are no cycles, I think this is not the right tree you're barking up.

  • External USB 2.0 hard drive reconnects on its own after power-down

    I have an external USB 2.0 hard drive which I'm trying to power off (after unmounting all partitions, of course) using:
    $ udisksctl power-off --block-device /dev/sdb
    When I do this, the drive spins back up after a few seconds. Only when I issue the same command again does the drive stay powered off.
    I'm running:
    linux 3.13.7-1
    udisks2 2.1.3-1
    This is what I see in the journal log when I:
    - Plug in the drive's USB cable
    - Issue the power-off command
    - After the drive spins up again, issue the command again
    Mar 29 19:51:01 miki-desktop kernel: usb 1-5: new high-speed USB device number 10 using ehci-pci
    Mar 29 19:51:01 miki-desktop kernel: usb-storage 1-5:1.0: USB Mass Storage device detected
    Mar 29 19:51:01 miki-desktop kernel: usb-storage 1-5:1.0: Quirks match for vid 1058 pid 0704: 8000
    Mar 29 19:51:01 miki-desktop kernel: scsi12 : usb-storage 1-5:1.0
    Mar 29 19:51:01 miki-desktop mtp-probe[21301]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:04.1/usb1/1-5"
    Mar 29 19:51:01 miki-desktop mtp-probe[21301]: bus: 1, device: 10 was not an MTP device
    Mar 29 19:51:02 miki-desktop kernel: scsi 12:0:0:0: Direct-Access WD 5000BMV External 1.75 PQ: 0 ANSI: 4
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Write Protect is off
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Mode Sense: 23 00 00 00
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
    Mar 29 19:51:02 miki-desktop kernel: sdb: sdb1 sdb2
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] No Caching mode page found
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Assuming drive cache: write through
    Mar 29 19:51:02 miki-desktop kernel: sd 12:0:0:0: [sdb] Attached SCSI disk
    Mar 29 19:51:47 miki-desktop udisksd[21107]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
    Mar 29 19:51:47 miki-desktop udisksd[21107]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:04.1/usb1/1-5/remove
    Mar 29 19:51:47 miki-desktop kernel: usb 1-5: USB disconnect, device number 10
    Mar 29 19:51:47 miki-desktop kernel: usb 2-5: new full-speed USB device number 9 using ohci-pci
    Mar 29 19:51:48 miki-desktop kernel: usb 2-5: not running at top speed; connect to a high speed hub
    Mar 29 19:51:48 miki-desktop kernel: usb-storage 2-5:1.0: USB Mass Storage device detected
    Mar 29 19:51:48 miki-desktop kernel: usb-storage 2-5:1.0: Quirks match for vid 1058 pid 0704: 8000
    Mar 29 19:51:48 miki-desktop kernel: scsi13 : usb-storage 2-5:1.0
    Mar 29 19:51:48 miki-desktop mtp-probe[21555]: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:04.0/usb2/2-5"
    Mar 29 19:51:48 miki-desktop mtp-probe[21555]: bus: 2, device: 9 was not an MTP device
    Mar 29 19:51:49 miki-desktop kernel: scsi 13:0:0:0: Direct-Access WD 5000BMV External 1.75 PQ: 0 ANSI: 4
    Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Write Protect is off
    Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Mode Sense: 23 00 00 00
    Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
    Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
    Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
    Mar 29 19:51:49 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
    Mar 29 19:51:52 miki-desktop kernel: sdb: sdb1 sdb2
    Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] No Caching mode page found
    Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] Assuming drive cache: write through
    Mar 29 19:51:52 miki-desktop kernel: sd 13:0:0:0: [sdb] Attached SCSI disk
    Mar 29 19:52:20 miki-desktop udisksd[21107]: Powering off /dev/sdb - successfully sent SCSI command START STOP UNIT
    Mar 29 19:52:20 miki-desktop udisksd[21107]: Powered off /dev/sdb - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:04.0/usb2/2-5/remove
    Mar 29 19:52:20 miki-desktop kernel: usb 2-5: USB disconnect, device number 9
    What is interesting is that on first connect, the drive is using ehci-pci driver, then after the first try powering it off, the drive appears to reconnect using the ohci-pci driver. Not just that, it appears to 'jump' from one USB bus to another. How is this even possible?
    $ lspci
    00:00.0 Host bridge: NVIDIA Corporation MCP73 Host Bridge (rev a2)
    00:00.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a2)
    00:01.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:01.1 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:01.2 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:01.3 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:01.4 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:01.5 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:01.6 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:02.0 RAM memory: NVIDIA Corporation nForce 630i memory controller (rev a1)
    00:03.0 ISA bridge: NVIDIA Corporation MCP73 LPC Bridge (rev a2)
    00:03.1 SMBus: NVIDIA Corporation MCP73 SMBus (rev a1)
    00:03.2 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1)
    00:03.3 Co-processor: NVIDIA Corporation MCP73 Co-processor (rev a2)
    00:03.4 RAM memory: NVIDIA Corporation MCP73 Memory Controller (rev a1)
    00:04.0 USB controller: NVIDIA Corporation GeForce 7100/nForce 630i USB (rev a1)
    00:04.1 USB controller: NVIDIA Corporation MCP73 [nForce 630i] USB 2.0 Controller (EHCI) (rev a1)
    00:0a.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
    00:0b.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
    00:0c.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
    00:0d.0 PCI bridge: NVIDIA Corporation MCP73 PCI Express bridge (rev a1)
    00:0e.0 IDE interface: NVIDIA Corporation MCP73 IDE (rev a2)
    00:0f.0 Ethernet controller: NVIDIA Corporation MCP73 Ethernet (rev a2)
    01:06.0 Multimedia audio controller: C-Media Electronics Inc CMI8738/CMI8768 PCI Audio (rev 10)
    02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4550]
    02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV710/730 HDMI Audio [Radeon HD 4000 series]
    $ lsusb
    Bus 001 Device 009: ID 1058:0704 Western Digital Technologies, Inc. Passport External HDD
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 007: ID 15ca:0101 Textech International Ltd. MIDI Interface cable
    Bus 002 Device 003: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
    Bus 002 Device 002: ID 046d:c001 Logitech, Inc. N48/M-BB48 [FirstMouse Plus]
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Before the first power-off attempt:
    $ lsusb -t
    /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 4: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M
    |__ Port 5: Dev 9, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    After the first power-off attempt:
    $ lsusb -t
    /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 4: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 5: Dev 10, If 0, Class=Mass Storage, Driver=usb-storage, 12M
    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M
    Does anyone know how to fix this problem? Is it a device quirk, a driver bug or something?
    Last edited by ackalker (2014-03-29 19:21:04)

    Just to be sure, I rebooted my system, shut down lightdm from another VT, made sure that really nothing is using the drive, no partitions are mounted, no services that could try to use the drive (except udisks2.service, could this one be the problem? But how am I supposed to use the udisksctl command when the service isn't running?).
    Tried the same command again. same result: I needed to run it twice in a row for it to 'take'.
    What I find even more fascinating: how can a USB device jump from one USB bus to another like that? I've honestly never seen anything like this before :-)
    Last edited by ackalker (2014-03-29 19:35:29)

  • Large OS 8.6 Compatible Firewire Hard Drive?

    I'm needing a larger firewire hard drive, which must able to back up my older Macs (running 9.1 and 8.6)
    However the newest 500GB ones all seem to list OS 10.x as their minimum requirement. (Not sure whether this is the minimum for doing stuff like formatting and partitioning, or whether these drives will not mount at all under OS9)
    Can anyone suggest a large firewire external drive which will mount and perform backups under OS 8.6 ?

    It should look somewhat like this:
    xxxx% sudo du -x -h -d 1 /
    Password:
    24K /.fseventsd
    1,9G /.Spotlight-V100
    0B /.TemporaryItems
    0B /.Trashes
    0B /.vol
    17G /Applications
    9,0M /bin
    0B /cores
    4,5K /dev
    1,2G /Developer
    14G /Library
    1,0K /net
    0B /Network
    10,0G /opt
    4,4G /private
    6,8M /sbin
    4,0G /System
    157G /Users <------ in this example this folder contains the most GB's
    1,7G /usr
    4,0K /Volumes
    xxxG / <------ xxx GB : this is the total for all folders above.
    So the results are presented one folder at a time in alphabetical order (?) with the total at the end.

  • Firewire Hard Drive corrupts OS Lion and will not boot

    I have re-installed OS lion on my macbook pro 5-6 times now. There seems to be some conflict with my firewire hard drive enclosure which causing it not to boot shortly after using it when restarting. I am trying to get all my data off this hard drive.
    When I boot in Verbose Command + V
    I get this error which goes into a loop and does not allow the computer to boot.
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    ERROR: Firewire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
    I end up having to reinstall the OS every time and it fixes it temporarily.

    Fixed it without even reinstalling the OS this time. I connected a firewire 400 cable between the mac book pro and my other mac and held down the "t" key to boot the dead macbook pro as a hard drive on my other mac. The hard drive didn't show up but it seem to get it out of the loop it was locked in not allowing it to boot and unable to reinstall the OS. After restarting it booted right back up like normal.
    This was an easy fix if my enclosure caused this problem again and does not allow my computer to boot after using the FW 800 cable.

Maybe you are looking for