Firewire drives through Cardbus instead of built-in port

Hello everybody,
I currently have three external firewire drives and presonus firebox (firewire) audio card.
This is the way I have them connected now:
Powerbook Firewire400 built-in port->Presonus Firebox->Firewire RAID drive (1+1 stripe)->Firewire single audio drive.
Would I get better performances using the following?
Powerbook Firewire400 built-in port->Presonus Firebox
LaCie Cardbus Firewire 800 port 1 -> Firewire RAID (1+1 stripe)
LaCie Cardbus Firewire 800 port 2 -> Firewire single audio drive.
for 79 I am going to make this purchase if things are supposed to get better..I think the firebox does a little bottleneck the way things are chained now.
I also have a FW800 port on my powerbook, would it be better to use that port for the drives and the FW400 for the presonus? ..but it's the same firewire controller, isn't it? while with a CardBus dedicated Firewire card, I'd get a dedicated controller, TRUE dedicated controller for firewire.
Please share some light I am confused,
a|b

You might get better performance, assuming the card has its own power. I tried a RATOC card without its own power, and the computer was constantly unable to hook itself to an iPod properly. So make sure if you get a card, that it has some sort of A/C adapter, or meets the power needs of what you are connecting to it.

Similar Messages

Add firewire drive to network

Hi,
I've got two emacs connected together via an ethernet router. File sharing is on. I both emacs can see each others sharing folder on the desktop and iTunes music sharing also shows up in both emacs.
I've just added a la cie firewire drive and I am trying to get one of the partitions which is on my desktop to be available to the other emac. But I can't work out how to do this. I've changed the permissions to owner/system and everyone has read/write but that didn't help.
Any help appreciated

Hi,
Okay, the best way to do this is to first go to the Finder. Then, Connect to Server from the Go menu. When the Connect to Server window appears, click browse and double-click on the other eMac's name. Now, you can log into the other eMac just as you would if you were physically on it. After you type in your name and password, click connect and select the volumes you wish to mount. (In your case, you would choose a partition of the firewire drive) You should now be able to access everything on your firewire drive through your local network.
-Jason

Cannot Boot from OSX on external firewire drive

I recently bought a seagate hardrive and installed it in an external firewire casing. I partitioned it into two partitions, and installed osx 10.4.10 on one of the partitions, the same as is running on my Ti Book.
I tried selecting the os on the firewire drive as the startup disk, but when i restart, after the grey screen i get the flashing question mark icon, until the mac recognises only the default osx on the internal drive and boots with that instead.
That not working, i created a clone of my startup disk using DejaVu in my system preferences and saved it on the other, empty partition on the external drive and tried booting from that.
On restarting, i get the grey screen once again as the backlight fires up, and nothing more. the screen remains grey without any further ado until i hold the power button and force it to turn off. then as i start it up again, up comes the flashing question mark icon followed by a boot from the internal drive.
Any Solutions on this?
Many Thanks, Neptune.

Hi Dale,
Whoops- everythings not as smooth as i thought it was!
since i restored my internal drive, a lot of things have been really messed up, starting with, for example, iTunes reverting to version 4 instead of 7. that wasnt a problem, i still had the 7 installer, and soon had my whole music library back again. but the computer appears to have a problem with the handling of graphics. the finder wont create previews of even simple jpeg images, nor will it for video. quicktime wont open any video file, i get some random error message which i cant remember stating it could not open the file. and if i view my finder window in grid icon view, the usual blue mac os desktop image that i keep as a background in the finder window isnt there, instead its pitch black. same goes for the slideshow feature in the application graphic converter, i can start a slideshow and it will scroll through the images, but every image will instead be completely black. there are no scroll bars in itunes. i can scroll down randomly by clicking where the scroll bar should be, but there is nothing visual there at all, no scroll bar, no arrows. when i connect my ipod, the main ipod window of itunes wont display any graphics either, be it the picture of the ipod or the capacity bar indicating usage of the drive for music, videos, data, etc. instead, fine print says something similar to 'cannot display image, quicktime and lzw tiff decompression plugin (?) required' I cant remember word for word what it says, dont quote me on that.
the computer also came to a dead freeze twice in ten minutes, i had to hold the power button down to get it to shut off.
im sure there are other issues too which i havent yet noticed, but even these, i havent the faintest clue what could be causing them!
do you?

Trouble with installing 10.5 from an external firewire drive

I have a family pack of 10.5 and installed it just fine on my macbook. But, I'm having trouble getting my imac DVD player to read the DVD. It just spins and spits it out, and spins and spits it out. The imac is not covered under applecare so spending money to get the DVD drive fixed (which I barely use) is not something I want to do right now.
Anyway, I followed instructions on a this website to install 10.5 from an external firewire drive. (http://iuseapple.com/blog/apple-how-to/advanced-os-x/2007/10/29/how-to-install-l eopard-from-external-firewire-hard-drive/)
But I get stuck and am not able to actually get my imac to boot from the installer. Basically, I am able to use disk utility to create a copy of the disk image on my macbook. That resulting file ends in ".cdr" and it mounts when I double click it.
And I partitioned my firewire hard drive without problems.
I think I'm messing up when it comes to doing the restore. If I try to drag the .dmg mounted file in to the "source" it doesn't work (is greyed out). If I try to drag the mounted .dmg there than it works, but I get an error when I click "restore" (something about scans and images not being found). I tried physically copying the .dmg file onto the partition, but then when I plugged the HD into my imac, I wasn't able to get the imac to boot from the installer.
What am I doing wrong? If someone could walk me through these last steps I'd appreciate it!

Okay I finally got around to creating the bootable disk image of 10.5 using Carbon Copy Cloner. Still my iMac is not booting from the firewire drive!
Here's a recap of everything I've tried. I'm at a complete loss now!
- I partitioned the HD into 2 partitions-- a 10gig one for the 10.5 install, the then the rest for Time Machine. I make the partition in Disk Utility on my MacBook.
- I've partitioned the drive a few times-- always partitioning it in APM format (b/c it needs to boot my non-intel iMac).
- I've created the disk image using "restore" in disk utility. I've again tried this a few times.
- I am able to boot my MacBook from the disk image I create! So I know the FW drive is able to be used to boot from!
- Here's what I've tried in terms of getting the iMac to boot from the FW drive. It always just boots to my internal drive instead. Sometimes I briefly see a folder and question mark. I've tried all 3 FW ports. I've selected the install partition at start up in preferences. I've also held down the option key at start up (only my internal drive shows) and I've held down command-option-shift-delete and again I get the question mark and it boots to my internal drive.
- And I installed Carbon Copy Cloner and made the disk image that way on my macbook. Still, I tried everything and the iMac is not able to boot from the firewire drive!
Since my DVD drive is broken, this is the only way for me to install 10.5! Help!

Mounting Firewire drives

If I have two external Firewire drives connected in series, one to another, and eject the first drive, will the second drive stay mounted and show on the desktop?

This is the FW info, http://support.apple.com/kb/HT2952
Repeater function
The built-in repeater functionality on Apple computers with two or more ports allows FireWire data to pass between external devices through the computer. This repeater functionality is available even when the computer is in sleep mode or turned off, provided that it is connected to AC power. On a portable computer running on battery, in sleep mode, or powered off, the repeater functionality is provided if at least one FireWire device supplies power to the computer via the FireWire cable.

MacBook Pro 8,1 beeps 3 times on boot from FireWire drive: why?

Hi, all,
about the brand spanking new 13" I bought, I immediately wanted to boot the FireWire drive so I could install Snow Leopard. Install disk image was copied to a dedicated partition on the FW drive to speed up install process.
Holding the [alt] key during startup leads to 3 beeps that are indefinitely repeated. I also tried to select the relevant partition in the Control Panel Startup Disk. Same result
Why doesn't it want to start from this image? How can I solve this issue?

In fact, it is a late 2011, not an early 2011 "New Old Stock", so you're correct it shipped with Lion. But, aside from its weird ergonomics (Dynamically-attributed spaces and different gestures from the previous OS X versions), what turned me off was the official complete impossibility to get a physical copy of Lion at a reasonable price, when it is installed. I also wanted the mounted drives to appear at the top left corner in Finder windows, as they did in pre-Lion OS X, instead of the bottom left. I wanted to put back the Firefox profiles in their place... Turns out the Library folder isn't visible in Lion.
Simply put, anything I wanted to do to start on the good foot wasn't possible on Lion.
I went to the Genius Bar, and indeed their own external rescue drive also made the Mac beep. I told them about the Snow Leopard tethered downgrade. They were aware of the method, but there was no Snow Leopard Mac remaining in-store. And with the install DVD causing kernel panics, there was no way to at least try a dual-boot installation (Snow Leopard for mission-critical apps, Lion for playing around with).
To another Apple-approved place I went. The young tech here was willing to perform the downgrade (since it would have cost me $75/hr), and had both Snow Leopard and Lion machines. But I argued that I wouldn't be willing to pay twice since I intend to switch to SSD in a short while. He then tested when booted from a clone, and Snow Leo half-installed on the internal drive (needs one reboot during installation), but it ended up in kernel panic. Same went when he tried the physical Snow Leopard disk after formatting the internal drive, hypothesizing something detected on it may prevent Snow Leopard installer to boot. It immediately went into a kernel panic.
Both techs were actually surprised that this signal came out, instead of a message stating (official) incompatibility, as well as kernel panics.
My hypothesis is there's something in the Snow Leopard installer that accesses the hardware at a lower level during installation, but not during normal execution or Target Mode, hence causing kernel panics in the former.
What else can be tried, or what else didn't go through my mind?

Problems backing up then booting from a firewire drive on Intel Macs

Hi
I wanted to help a friend back up his Macbook and then install Bootcamp.
I took over my trusty external firewire drive (Makeytec MHD-25 Combo enclosure + Samsung 80Gb HDD).
So... I ran Disk Utility
Highlighted the firewire drive, clicked Partitions, named it "Backup". Clicked Options -> GUID -> Partition
I backed up his computer with SuperDuper onto Backup. SuperDuper automatically makes the drive bootable. At the end Backup was mounted on the desktop and all files are there.
But Backup wouldn't boot the computer. Instead I got a grey screen for a long time, then the Apple logo with the spinning cog, then after a few more minutes a circle with a bar through it (like a no smoking sign minus the cigarette)
Things I tried after this....
Partitioned the drive again, double checking that I had selected GUID
Erased the drive zeroing out all the data
Backing up using CCC (with make drive bootable option checked) instead of SuperDuper
Could not get this drive to boot his computer.
Then took the drive back home. Tried doing it with my MacMini (same problem)
Then plugged it into my Powerbook, Partitioned it as Apple Partition Map, ran SuperDuper, rebooted from it fine.
My conclusion: The drive will boot a G4 just fine, but not an Intel based Mac.
Does anyone have any suggestions?

A workaround:
The drive enclosure also has support for USB "1.1/2.0", including the ever important cable.
I reconnected it to the Macbook, partitioned the drive back to GUID, then I used super duper to back the Macbook drive (again!). I used firewire (only because it was much quicker - 6Mb/s vs 2.8Mb/s)
Once I did the backup, I ejected the external drive, disconnected it, then plugged it back in with USB, then selected it as the start up disk, then hit restart. Machine rebooted just fine although very slowly.
Still doesn't answer the question of why booting via the firewire port works fine with a G4 mac but not Intel.
Tim

FireWire Drives keep dying on me. . . (different systems, different brands)

If there is a better area to post this pls let me know and I'll move it there.
This problem has plagued me for years and through totally different Mac systems and completely different brands of drives. I use external firewire drives (I work in video so back years ago I had no choice). It starts with the drive not always showing up on the desktop (need to turn it on and off a few times). Then one day the drive dies. I have tried the basic diagnostic things to retrieve, in one case even sent the drive to the recovery place in Colorado. I never get anything back. Does anyone else have this issue or any idea why it might be happening?
Now with larger ATA drives I try to keep as much internally as I can and avoid FW drives, but then when Time Machine came along I needed some way to back up EVERYTHING, so I got a Terabyte FireWire Drive (MyBook, but I've used LaCie, Western Digital, every major name you could think of). Seemed to have issued showing up on the desktop after a restart (if I unplugged the power and put it back in the drive would restart and then show up on the desktop). But yesterday it died. It was soon enough that the store replaced but if it happens again I have to go to warranty.
Any ideas or references much appreciated.
thanks

Speed isn't the only issue if you are trying to determine why the drive failed. If it worked well with USB, then it's not the actual drive, but the Firewire chips that do the IDE or SATA conversion.
I use Firewire drives from OWC (with cooling fans) without any problems (none of the 8 drives have died in the last two years). Firewire is nice for speed, but in reality, USB is plenty fast for backup services. Unless you are having to backup many gigabytes every hour, USB will work fine.
On the other hand, I like my drives (and other devices) to connect directly to the machine instead of going through a hub. The current iMacs have two Firewire ports that are mostly unused by home users. Using one of these Firewire ports free's up one of the three USB ports for other devices (like the recommended UPS data cable).
It would be interesting to know if your WD drive actually died or just became corrupted due to bad Firewire firmware. In the last 6 months I've gotten these new WD drives in a state that they won't mount on Firewire and can't boot a Mac. The two drives I got like this were both repaired by the firmware updates from WD. Both of these drives worked fine with USB.
I've never cared for WD drives. Too run-of-the-mill and too many failed drives under intense use. But then, it took quite awhile for me to accept any non-SCSI drives. I can find anecdotal information on just about any brand that would suggest a brand is trash. For the present, I'm recommending the Hitachi (formerly IBM) Daystar and Travelstar drives for consumer machines.
Unfortunately, there have been failures with just about every manufacturer as the quality continues to degrade to get the prices down.

FireWire drives won't mount

Neither of my FireWire drives will mount on either my iMac 20" G5 or my iBook G4...I have a 500GB WD MyBook and a La Cie 80G. I've gone through all the suggested tips, and still nothing. I've reset the PRAM several times, reset the firewire bus by turning off the computer and unplugging it and the drives for a while, etc. I've tried different cables, too.
The drive shows up in the system profiler as an unknown device but not in the Finder. I have a USB hub with a card reader and 4G SD card that shows up just fine. I tried the MyBook in the USB port but it didn't show up there either.
The power supplies are working, as the indicator lights are on for both drives.
The MyBook was working fine until recently; not sure when it stopped working. I hadn't used the La Cie for a while but hooked it up to store iMovie files.
I plugged a Canopus ADVC-55 analog-to-digital convert into the FW port on both computers and it showed up as a named device in System Profiler. That tells me the port is OK and the problem is with the HDs--right?
Very frustrating! Hope someone can help.
Thanks in advance.

For what it's worth... I'm having the exact same issue and so are many others on the forums since 10.5.6.
See:
http://discussions.apple.com/thread.jspa?messageID=9206734
http://discussions.apple.com/thread.jspa?messageID=9206635
http://discussions.apple.com/thread.jspa?messageID=9043830
http://discussions.apple.com/thread.jspa?messageID=8917764
---cross posted---
I'm having a very similar issue as of the last few weeks at least. Periodically I'll turn my FW drive on and it won't mount and isn't visible in Disk Utility. This is usually after waking the computer from sleep.
The only way to get it back is to restart.
Also the console shows a long running list of errors that seem to occur non-stop when the drive is on, connected, but not mounting.
AppleFWOHCI_AsyncTransmit::waitForDMA
AppleFWOHCI_AsyncReceive::waitForDMA
I've also noticed that the system occasionally will not boot up and instead freezes on the Apple logo on startup. Not sure if this is related however.
---

Disappearing external Firewire drive.

Hi friends.
My wife's mini has a LaCie external firewire drive attached. She uses it with Backup and it just suddenly disappeared.
It appears to be on and working- but not showing up on her desktop. Is there a way on restart-- to force her mini to look for peripherals it's not seeing? I always get such great help on this forum. Thanks in advance. Dan

I'm curious if/how that link worked out for you. I have been observing problems with Firewire/USB for the past month or more that I allowed my clients to upgrade to 10.4.9 and 10.4.10.
I am finally starting to cross over into the belief that an update within 10.4.9/10.4.10 caused a failure with external Firewire drives -- now I will include USB drives in that belief. I was skeptical for a long while but the coincidences don't line up.
My guess is that Apple updated the Firewire/USB bridge -- perhaps they even made it more efficient. The cost may be that various external drive enclosure manufacturers who coexisted (or even accommodated) Apple's previous bridge, now fail. I don't know if you recall the 10.3.x update that took down Firewires for quite some time to come. The only solution that worked for me then was to boot into OS 9, mount the drive there, and then restart in OS X. A very round-about solution.
So far, I have observed the following failures in the past couple months:
Powerbook G4 1.4Ghz (or so): failed USB LaCie hard drive, no clicking/non-harddrive malfunction
Mac Pro -- Intel Core Duo: two failed Firewire enclosures (Nexstar Vantecs). The drives inside were perfect but the enclosures ceased functioning first on an iMac G5 and then continued to disappear on a Mac Pro tower.
One of these enclosures had also disappeared from a new iMac - Intel. I could get the thing to mount and then it would disappear overnight -- my thought is that perhaps the drives don't remount after sleep? I did not do extensive tests.
I have had another client on an as-of-yet-unknown machine (purchased in last couple years) lose a LaCie Firewire drive... no clicks or hardware failure indications. I will investigate this week.
I had yet another client lose two LaCie drives connected to a Dual 1.0 Ghz G4 Tower. One LaCie drive enclosure seemed to fail completely at Firewire 800 speed and transfer slowly but reliably when dumbed down to Firewire 400. The other LaCie was unreadable even when I transferred the drive to another enclosure. I am still investigating.
On a Mac Mini (Intel) new enclosures from PPA Galaxy Metal Gear would not daisy chain without disappearing.
I admit that I don't want to believe that the recent OS updates could have caused this -- especially after the debacle of 10.3.x. But it is definitely possible and not altogether unlikely. Consider this discussion about a LaCie firmware update tool meant to make them compatible: http://lovemac.org/2007/04/28/external-lacie-firewire-disappeared-from-the-deskh elp/
Not having attempted the Firmware update yet myself, I cannot vouch for it. Firmware updates are not to be taken lightly but they are just the sort of thing that might make the Firewire/USB bridge in the LaCie's compatible with Apple's updates/fixes. Of course, that leaves the other vendors' drives high-and-dry.
Usually, Apple or Apple defenders like to say that the vendors should be writing perfect code and it's not Apple's fault if they optimize or fix code which breaks the vendors' equipment. I think this is a ridiculous argument. Granted, in our legal system, Apple would not usually be obliged to accommodate "faulty" code (even if they might happen to have been the originators of it). But what is the true definition of faulty code? In the realm of technology and computers, there are likely countless kludges and fixes and patches. The whole idea and goal is FUNCTION (ideally). Optimizing or standardizing code is important of course. It means that future authors can rely on the accuracy of the previous authors. But the world -- especially the tech world -- stands to gain more from consistency... from the language of the vernacular. If all the equipment and all the operating systems up to a point have deigned to speak in a consistent kind of pidgin, then it doesn't make complete sense to "fix" it to be some more "accurate" or "refined" grammar. Language works because it's locally consistent, not because it's accurate to some holy grail of grammar.
Specifically: Apple can't switch code midstream and say "oh, I made the code 'accurate,' not my fault if your stuff was built on bad code." Up until that point THEIR stuff was built on "bad" code too! It's a ridiculous argument but what can you do.
At this point, I imagine that Apple attempted to fix something with 10.4.9 and 10.4.10 that it had tried to fix before with OS 10.3.X. Instead, I believe it created an intermittent failure in Firewire/USB drives that leaves the drives inoperable as often as unmountable. It's just a theory based on having seen enough updates and upgrades have a really bad effect. I think people think we live in some future where we can trust our technology and tech manufacturers to get things right (or at least get things right often enough). Surely they're doing the best they can...no doubt.
I'm a little frustrated I should ramp down my expectations. I know. It's not like this is 2020 or 2050. It's really only 2007.
Good luck to us all.

Sleeping firewire drive causes system crash

I have a 320 GB external firewire seagate drive connected to my Dual Ghz Quicksilver G4. At least twice a day, when I try to access that drive, I experience a system crash, what I believe to be a kernal panic. I get a message telling me I need to shut my computer down and restart it. I am thinking this is not so good for my computer.
So, either the hard drive is the problem or it's the third party firewire card i have installed in one of my PCI slots. But here's the thing, other drives are connected to that card.
Would keeping the Seagate drive awake stop this from happening? It goes to sleep all the time. Have others experienced problems with the seagate drives? Should I stop using it?

Hi, Aaron. Welcome to the Discussions.
If you are seeing this message, that indicates a kernel panic.
There could be a problem with the FireWire drive or the card. If disconnecting the drive for a few days results in no additional panics, then it is the drive. For that, I'd contact Seagate. If not, the card becomes suspect. An examination of the panic log might prove helpful.
You can also try running Step 1 of the process specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ against the Seagate FireWire drive.
Checking the FireWire cables, trying different cables or ports, checking that the card is installed correctly, checking that you assembled the Seagate drive and enclosure correctly (sounds like you built the FW drive) are some other troubleshooting steps to consider. The FireWire enclosure itself may be defective.
See also my "Resolving Kernel Panics" FAQ. This FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics, including tips like those above.
My FAQ is a roadmap: start at the beginning and work through to the end, following the instruction in the order specified, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein.
You maybe unable to prevent the FireWire drive from sleeping. Secondary hard drives (second internal, as well as external drives) may not respect the "Put the hard drive(s) to sleep when possible" option if de-selected. I discuss this particular issue in my "Spinning Beach Ball Of Death (SBBOD)" FAQ, specifically in the section entitled "SBBOD spins for 30-35 seconds. You may hear your hard drives spinning up."
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Booting from FireWire Drive

I have a LaCie 160MB (F A Porsche style) external firewire drive.
I have been able to create a bootable clone of my iBook HD using Disk Utility and the Restore function.
I have been able to create a bootable partition by installing the System Software onto it.
But I have not had success using SilverKeeper or SuperDuper! Does anybody know why? I would really like to use the features of one (or another if available) of these applications.
Thanks.
-Ted

Below is LaCie's Tech Support Reply. What is interesting is that they suggest Carbon Copy Cloner (instead of Silverkeeper). Also interesting is that it worked. I hope this helps some of you.
Ted
Hi Ted--
Thanks for contacting LaCie Technical Support. All of our firewire
drives can be used as boot volumes. Due to differences in operating
systems and Macs, we are unable to provide support for booting from
firewire drives other than the following information:
1. Make sure the Mac is bootable via firewire. All Macs with built-in
firewire can be booted from an external drive except:
-Blue and White G3s
-PCI-Graphics G4s. This can be determined by looking in the Apple
System Profiler. The PCI Graphics G4s use the same motherboard as the
B&W, except with a G4 processor shoehorned in.
2. The drive must be connected to a native port. It will not work if
the drive is connected to an add-on card.
3. The Mac must have the latest firmware installed. The proper updater
can be found and downloaded from here:
http://docs.info.apple.com/article.html?artnum=86117
Download and read the instructions carefully. It is possible to kill a
Mac if the update is interrupted. Then, perform the update. If the
firmware is already current, the updater will report this.
4. Format the drive fresh using either Apple's Disk Utility in OS X or
Silverlining in OS 9. Use the Mac OS Extended (HFS+) format only.
(Journaling may be enabled on OS 10.3.)
5. If making an OS 9 boot drive, you can just copy the System Folder
over to the root of the boot volume. To be bootable, the System Folder
must be blessed, i.e. has a happy Mac face on it. If it does not, you
can try to force it to bless by removing the Finder from the folder and
moving it to the root. Then, move the Finder back. The folder should
now be blessed. If not, then there is probably an issue with the System
Folder.
6. In making an OS X boot drive, the ONLY two recommended solutions
are:
--install from the OS X install disk, preferably the one which came with
the Mac. You will not be able to make a successful boot drive using an
older disk set. A newer disk set should also be fine.
--use a utility, such as Carbon Copy Cloner, to perform a copy of an
existing OS X install. It is not possible to do this manually. There
are issues with permissions, hidden files, and files in use that cannot
be manually overridden. If you are using a disk image, you will still
need to use a utility, such as Carbon Copy Cloner, to copy the files out
from the image to the root of the new boot volume. A simple drag and
drop will not include the necessary hidden files, such as the boot
loader and the kernel.
If the volume does not appear as a Start Up Disk, try booting with the
Option key held down and see if the drive shows in the boot drive
selection screen.
If the volume does not show, or the kernel panics on boot, chances are
the OS install was not performed properly.
In general, CD/DVD drives are not bootable via firewire, but will work
under certain circumstances, usually booting from OS X to OS X. They
should not be relied upon as such. To boot from one, hold down the
Option key while booting. If the boot CD shows on the screen, you may
select it and continue the boot.

Firewire drive no longer recognized after upgrade?

having an onset of problems the last 2 weeks.
first upgraded to 10.4.6 on mac mini 1.42 non-duo, worked a few days than acted weird with apps crashing. had to reinstall from 10.4 disk. seemed ok. repaired permissions, ect. after reinstall (and a subsequent power outage) a firewire drive attached at time was no longer recognized by mac mini or connected imacG3. reinstalled 10.4.2 on mac mini. installer unable to reinstall 10.4.6., I would like to have firewire drive recognized again. when attached to other firewire drive in daisy chain, says device unrecognized, other wise unable to get any info on drive. what to do?

I am having nearly the exact same issue as you are experiencing. My Western Digital Dual-Option Media Center 160 GB FW HD is going in and out big time. It seems to be there for a time but then conks out. I have to disconnect the power and now the drive seems to be malfunctioning.
Same story with my LaCie 52x CD Burner. I placed the Disk Warrior CD in there and the computer recognized the disc at first but then spinning beach balls galore!
This has to be one of the worst updates to an OS X system I can remember. I can only think PowerPC QA testing has gone through the toilet since the Intel move was completed.

Time Machine Data Transfer - From FireWire Drive to Time Capsule - HELP!

Time Machine Data Transfer - From FireWire Drive to Time Capsule - HELP!
I've been searching for weeks for a solution to my problem. Here's the story I've come across since I installed Leopard on Oct. 26, 2007.
I first installed Leopard on my Early 2006 MacBook and set up Time Machine with a 200GB external FireWire drive. Since then, things have been fine, until Time Machine started deleting the oldest backups. I'm a pack-rat and hated this feeling of losing data. So, I now have a few months worth of backups on my 200GB FireWire drive.
The Time Capsule is released, I finally talk myself into getting one and transferring my old data from the 200GB drive to my 1TB TC.
I did some researching through forums about how to move data from one Time Machine drive to another, so I took the concept and wanted to apply it to my Time Capsule. I made a DMG image of my 200GB drive, in order to move the data. I figured if I can make an image, copy it, and open it on the Time Capsule - all will go smoothly - just as some had mentioned they've done with external drives.
Now, I have a 164GB DMG image of my Time Machine, with no hope in sight of gaining it back. I've tried taking the image, using Disk Utility, and restoring my original 200GB external with the imaged Time Machine data, but whenever I do, I come across error messages.
In Disk Utility, I've done the following steps:
* Disk Image is found on Time Capsule
* I select the 200GB drive and select 'Restore'
* I drag and drop the Disk Image to the 'Image' field
* I drag and drop the 200GB drive into the the 'Restore' field
* Select 'Erase Destination'
* Select 'Restore'
* I get the warning message that I'll erase the drive - I proceed
* I enter my password
Error message pops up:
"Restore Failure: Could not find any scan information. The source image needs to be imagescanned/scanned for restore."
I select the image in Disk Utility, then proceed with the following steps:
* Click on "Image" then down to "Scan Image for Restore"
* I enter my password
After hours of waiting, I get another error message:
"Unable to scan. (Broken pipe)."
I'm going to see, after transferring the DMG to the Time Capsule, if I can drag-and-drop the files from the Time Capsule drive onto the 200GB hard drive.
IF anyone has any more suggestions, please let me know!

32 updates on this Mac since December 2007 - Hardware, software, OS...
They keep coming at about 6 or 7 a month. Some of them I don't care about, but several are essential. 10.5.3 has been seeded to the testers a couple of times and will probably show up in the next few weeks. Jaguar wasn't worth a d*mn until 10.2.6, Panther about 10.3.4, Tiger about 10.4.4 - I'd say we are ahead or on schedule Too bad I can't get Apple to fix Spaces. I wish they'd focus on what I want but I guess some take more time than others.
2007-12-18 00:32:39 -0800: Installed "GarageBand Update" (4.1.1)
2007-12-18 00:32:43 -0800: Installed "QuickTime Broadcaster" (1.5.2)
2007-12-18 00:33:07 -0800: Installed "Security Update 2007-009" (1.0)
2007-12-18 00:33:29 -0800: Installed "QuickTime" (7.3.1)
2007-12-19 09:32:03 -0800: Installed "MacBook MacBook Pro Software Update" (1.1)
2007-12-23 23:57:32 -0800: Installed "Security Update 2007-009" (1.1)
2008-01-16 09:18:07 -0800: Installed "iMovie Update" (7.1.1)
2008-01-16 09:18:14 -0800: Installed "Front Row Update" (2.1.2)
2008-01-16 09:18:45 -0800: Installed "iTunes" (7.6)
2008-01-16 09:19:31 -0800: Installed "QuickTime" (7.4)
2008-01-29 21:33:14 -0800: Installed "Keynote Update" (4.0.2)
2008-01-29 21:33:23 -0800: Installed "Pages Update" (3.0.2)
2008-01-29 21:33:31 -0800: Installed "Numbers Update" (1.0.2)
2008-02-02 01:18:43 -0800: Installed "iWeb Update" (2.0.3)
2008-02-05 20:12:17 -0800: Installed "iPhoto Update" (7.1.2)
2008-02-15 09:03:49 -0800: Installed "iLife Support" (8.2)
2008-02-15 09:04:17 -0800: Installed "QuickTime" (7.4.1)
2008-02-15 09:04:51 -0800: Installed "Leopard Graphics Update" (1.0)
2008-02-19 23:44:37 -0800: Installed "Keyboard Firmware Update" (1.0)
2008-02-25 19:24:33 -0800: Installed "iTunes" (7.6.1)
2008-03-03 17:14:18 -0800: Installed "GarageBand Update" (4.1.2)
2008-03-03 17:14:31 -0800: Installed "iPhoto Update" (7.1.3)
2008-03-12 18:11:36 -0700: Installed "AirPort Utility" (5.3.1)
2008-03-18 10:03:57 -0700: Installed "Safari" (3.1)
2008-03-20 13:00:58 -0700: Installed "Security Update 2008-002" (1.0)
2008-03-20 13:01:04 -0700: Installed "Time Machine and AirPort Updates" (1.0)
2008-03-21 22:49:16 -0700: Installed "Digital Camera RAW Compatibility Update" (2.0)
2008-04-03 00:50:22 -0700: Installed "Front Row Update" (2.1.3)
2008-04-03 00:50:50 -0700: Installed "QuickTime" (7.4.5)
2008-04-03 00:51:58 -0700: Installed "iTunes" (7.6.2)
2008-04-08 17:16:02 -0700: Installed "Keynote Update" (4.0.3)
2008-04-08 17:16:08 -0700: Installed "MacBook Pro EFI Firmware Update" (1.5)

Access Apple External drives through Windows

Core question:
How do I make external Firewire drives connected to my Mac accessible to my Windows computer?
I want to access files stored on external FireWire drives connected to my Mac on my Windows XP computer.
Background:
I can connect to my Mac from Windows, but only to the "boot" drive and only into the user folder I specify.
How do I access drives connected to the Mac through Windows?
TIA,
Paul

If you're using Mac OS 10.4 and older then install SharePoints from Hornware.com
If you're using 10.5, then just set up what files/folders/drive you want to share using the Sharing system preferences.

Firewire drives through Cardbus instead of built-in port

Similar Messages

Maybe you are looking for