Slower Reboot with FireWire Drive

Hi Guys,
I have noticed that whenever my WD My Book external drive is plugged in to my computer, my startup times are much slower. Unfortunately, I use BootCamp a lot, so it effects me very often. Do you know a way to make my computer boot up faster with an external drive plugged in?
Thanks.
C h r i s t o p h

You can reset the FW bus by unplugging all FW devices, shutting down & unplugging the computer for 5-10 minutes.
A G4 tower is getting long in the tooth
which is to say, it should be a sad day yet no surprise if a port or bus fails on the unit.

Similar Messages

10g RAC on SLES 9 with Firewire drive

Hello,
Is there documents/guides to setting up 10g RAC with firewire drive on SLES 9. Thank you.

Mike:
Yes! I resolved the problem by applying the 9.2.0.3 patch. However, ocfs is not working properly. Sometime I got I/O problem or used one node to create tablespace but the other node can not see it right away. May be is because I use version 1.0 of ocfs.o. I am trying to find newer version of ocfs.o. If you know where to get it please let me know.

Solaris 10 01/06 hard crash with firewire drive attached

I have Solaris 10 01/06 installed on a Sun W2100z workstation (BIOS is most recent available when last I checked in March). I have applied all publically available Solaris 10 patches that one can get without having a support contract.
I have an external firewire hard drive attached to the system but it's not powered on.
If I halt the workstation, power on the firewire drive, and then attempt to boot the workstation, Solaris will begin to load and then I get a kernel panic and crash dump. This happens every time.
My "mdb" skills are lacking, but if I issue:
cd /var/crash/hostname
mdb unix.1 vmcore.1
I get:
Loading modules: [ unix krtld genunix specfs ufs ip sctp usba uhci s1394 nca random fcp fctl emlxs lofs nfs audiosup sppp crypto ]
$cscsa1394_cmd_fill_cdb_rbc+0x332()
scsa1394_cmd_fill_cdb+0x6f()
scsa1394_scsi_start+0xe4()
scsi_transport+0x60()
scsi_watch_thread+0x2fa()
Anyone else having repeatable crashes on Solaris 10 01/06 x86_64 with firewire hardware attached?
Thanks,
Tim

Hi Asgorath,
Unfortunately I do not have an answer for you but I
am experiencing the identical problem on a HP
Proliant BL25p Blade Server. Here is my hardware
config:
CPU - Dual Opteron 2.6 Single Core
Memory - 16gb
Controller - HP Smart Array 6i
Logical drives - 1 (2x72gb RAID1+0)
I have tried the same things as you and I still get
intermittant boots. Power on and off does not always
work as the system still hangs. It's totally hit or
miss. Once it soes boot it seems to work fine. I have
also installed the latest Solaris 10 for x86 Patch
Cluster in hopes that some of the kernal patches
would fix the problem. So far no luck as the system
continues to hang...HARD!! HP was out to my site
today and the Eng. is going back to the group that
qualified Solaris10 on the HP Blades and see if they
have any input. If I receive anything back I will
post it here. I know this post is late and if you
have resolved please post your fix.Hi doc42755,
I have not come up with a solution as of yet, if I do come up with a solution i will most certainly post it here.
However, if you find the solution could you let us know in this thread aswell.
Thanks
Asgaroth

Error -36 when reading/writing with firewire drives (400 & 800)

This is only happening when I connect the drives to my G5, but the drives work fine on my MacBook Pro. I first thought I had a problem with my drives, but then when they worked on my laptop I figured it must be a problem with my G5. One of the drives is a smartdisk firelite drive connected via firewire to the front of my G5, the other is a G-Drive connected via FW 800 in the back of my machine.
Any ideas of what I need to do on my G5 to fix this issue?
Thanks!

Hi-
The error is an I/O error. One possible cause is low power on the firewire bus, or, the drives require more power than is available. Placing a powered hub between the G5 and the drive may be the solution.

10.5.2 TIme Machine with Firewire Drives

I have seen other people post that they have had problems with Time Machine and 10.5.2. I have had similar problems -- The backup would fail after about 6-8gb with mysterious system.log lines saying there were errors copying files to the volume. The most interesting lines in system.log were from backupd producing error -36 (io error) followed by a mysterious -8062 error.
I checked the disk, no errors. I verified that the files listed in the log file were not erroneous -- they were ok. I reformatted the time machine drive and got the same result. I bought a new external drive on the chance that the old external drive was failing and still got the messages. Prior to the 10.5.2 update, Time Machine worked as advertised with no issues.
In an attempt to figure this out, I switched the external drive from firewire 400 to USB. Now, the backup seems to progressing normally. Interestingly, when Aperture tried to backup a vault to the same firewire drives, it also got an I/O error.
I suspect there is a problem with the 10.5.2 firewire drivers and PowerMac G5 (and maybe others)

I concur. Leopard's FireWire drivers still seem to be problematic. On my friend's computer, an iMac G4, using FireWire had consistently resulted in disk failures when running 10.5.1, so we had switched to USB as a workaround. After 10.5.2 arrived, we switched back, hoping Apple had fixed the problem. Unfortunately, that doesn't appear to be the case.
Soon after switching back to FireWire, Time Machine failed, and we ended up having to start from scratch. Time Machine got to about the 100-GB mark of the initial backup when it reported a disk error. Unlike your case, however, the volume was corrupted, and Disk Utility could not repair it. We're going back to USB for now.

Imac running 10.8.2 often does not start up with firewire drives connected

I have a mid 2007 imac running osx 10.8.2 and it will nit restart with two firewire drives connected if it has been running for sometime. If i disconnecr and restart and then connect the drives and then restart again it will restart.

a brody's guess is a good one. Please also look at what Apple says in Gray screen appears during startup

Why an I losing contact with Firewire drives and camera back?

One of my computers suddenly won't connect to a Phase One digital back via firewire.
Tried to plug in a external drive to check the port. No contact. (Tried various cables, etc.)
Tried camera on another computer. No contact. Tried firewire drives that had been running before on this same computer, and now it won't read these drives.
My PhaseOne dealer assures me that a digital back can't possible fry or disable a port. Still. there they are.
Took one of these drives to yet another computer that connects fine with yet another drive, tried the problem drive, and there was no connection. When I checked About This Mac there was a spinning wheel, as though it were looking for something.
Any thoughts, anyone? I don't want to test more drives if they are being damaged. And if they are, can they be recovered?
Many thanks
Sean Kernan

Hi, John.
1. I presume in Finder Preferences, in the General tab, you've selected "CDs, DVDs, and iPods" under "Show on desktop." Otherwise, FireWire drives won't display on the desktop, but they should still appear in the Finder's Sidebar.
2. If you did not Eject the drive before you disconnected it or powered it off, its partition map may be corrupted. That could explain the symptoms you are seeing. Your FireWire-based digital camera back may be seen as a FireWire drive.
Disconnecting a removable storage device — FireWire drive, USB drive, etc. — without first ejecting it can result in the drive's partition map being corrupted. Before disconnecting such a device, one must first Eject it by either:
- Dragging its icon to the Trash.
- Control-clicking the drive's icon and selecting Eject from its contextual menu.
- In Disk Utility, selecting the device, then selecting Eject in the Disk Utility toolbar.
If there's data on the drive you wish to recover, see my "Data Recovery" FAQ. Once you recover the data you want to save, if any, you will need to repartition and reformat the drive.
3. Before you panic w.r.t. item 2 above, Here is some general troubleshooting advice w.r.t. FireWire devices that may help:(1) Review the AppleCare Knowledge Base document "What to do if your computer won't recognize a FireWire device".
(2) If this problem occurred after installing a recent Mac OS X Update, and you are also unable to mount CDs, DVDs, or disk images perform the steps in this Mac OS X Hints article.
(3) The following additional steps will often help resolve problems with FireWire devices, particularly hard drives:(a) Power-on the FireWire drive before starting up (booting) your Mac.
(b) Reset PRAM and NVRAM.
(c) Reset the PMU or SMU: Select the appropriate knowledge base item for your model of Mac from this KB search. Follow the instructions on resetting the PMU or SMU carefully!
(d) Try a different FireWire port. James Wiebe, CEO of WiebeTech, has published FireWire Port Failures in Host Computers and Peripheral Devices, a white paper providing backgroud information and technical analysis concerning the causes of failure for FireWire ports. This may provide additional diagnostic information.
(e) Check with the manufacturer of your FireWire drive or enclosure to see if any firware updates are available for such.(4) Hopefully, the partition map on the FireWire drive is not damaged. If it still refuses to mount, you may need to employ data recovery tools or services: see my "Data Recovery" FAQ.Note that some of the information above is from the "FireWire Problems" chapter of my book, Troubleshooting Mac® OS X.
PS: You've not provided any info about the computer in question, i.e. Mac model, installed RAM, installed version of Mac OS X, etc. That's always important to include in a post, and I suggest you add it to your profile: click "My Settings" in the upper-right section of the sidebar on the right side of this page.
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.

OSX Retrospect unhappy with FireWire Drive?

Dear folks,
I have no idea if this is a hardware, software, and/or OS problem. But it's a real puzzle.
I have an external firewire drive I use with a PC Card firewire adapter. It works fine under both OS 9 and OS X. It also works fine with Retrospect under OS 9, performing backups and verifies at over 200 MB per minute.
But, with Retrospect 6.1.2 under OS X Panther, performance to firewire is abysmal. When backing up my Panther volume to the firewire drive, it takes more than eight minutes for Retrospect to do its prep and then the backup proceeds at only 70 MB per minute (no compression). It takes another eight minutes for Retrospect to close the backup and prepare for the verification pass. The verification pass runs at only 2 MB per minute! Yes, you read that right, about 30 kilobytes per second.
By comparison, if I back up the Panther volume to a different volume on the same internal hard drive, it takes Retrospect less than 1 minutes to do the setup (and to close the backup), it writes the backup at 100 MB per minute, and it runs the verification pass at 140 MB per minute.
For reference, copying files to and from the firewire drive runs at over 200 MB per minute in any other application under OS X.
Anyone here have any thoughts at all? I really like Retrospect, but 6.1.2 seems to be useless with my Firewire drive.
pax / Ctein
[[ Please excuse any word-salad. ViaVoice in training! ]]
=========================================
-- Ctein's Online Gallery http://www.ctein.com
-- Digital Restorations http://photo-repair.com
=========================================

"Repair Disk Permissions" from Disk Utility may help.
Also, cmd-opt-n-v (Clear NV RAM) may help as well.
Mihalis.

Weird Problem with Firewire Drive on 17" MBP

I have an external firewire drive that worked great on my 15" MBP and with any other computer I have never had any problems. The problem occurs when I plug the drive into my 17" MBP with the magsafe connected, it just wont mount, but as soon as I unplug the magsafe the drive mounts. Really weird. Anyone have a similar problem? I am going to the Apple Store and see if I can duplicate the problem.

I'd backup your files if you can. If the drive is failing then the advise you've gotten is good advise. You can try software recovery if you are unable to use the drive:
Basics of File Recovery
Files in Trash
If you simply put files in the Trash you can restore them by opening the Trash (left-click on the Trash icon) and drag the files from the Trash to your Desktop or other desired location. OS X also provides a short-cut to undo the last item moved to the Trash -press COMMAND-Z.
If you empty the Trash the files are gone. If a program does an immediate delete rather than moving files to the Trash, then the files are gone. Recovery is possible but you must not allow any additional writes to the hard drive - shut it down. When files are deleted only the directory entries, not the files themselves, is modified. The space occupied by the files has been returned to the system as available for storage, but the files are still on the drive. Writing to the drive will then eventually overwrite the space once occupied by the deleted files in which case the files are lost permanently. Also if you save a file over an existing file of the same name, then the old file is overwritten and cannot be recovered.
General File Recovery
If you stop using the drive it's possible to recover deleted files that have not been overwritten with 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.
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.
If the above is not possible then sending the drive to a data recovery service may be your only option, and they are very expensive.

Problems with firewire drive

Hi all.
Ive got a problem I need help with. Just installed Final Cut 3 on this older G3. Would like to do a little editing at home. Have a 240 gig Lacie firewire drive that I would like to use as a scratch drive. The drive was originally used on a pc so I initialized it on the mack Mac OS Extended (Journaled). I can capture video to the internal Mac harddrive but not the Lacie. Capture stops after a few seconds. I have tried transfering captured video from the internal drive to the Lacie but I get an error message and it wont transfer. Any ideas what I need to do to remedy this situation?
Thanks
Rocky
g3 Mac OS X (10.3) 256 mb ram

This seems wrong. I have two firewire drives daisy-chained and then plugged into my cube, and on the other firewire port I have my cinema display's hub which leads to my ipod mini and my belkin mac mini USB and firewire hub, where I connect my DV camera for import. I have had no problems importing footage to my FW drives. I'd say don't plug the camera into the computer through the FW drive, just straight into the computer. If that doesn't work, try what the other guy said about either reinitializing it or use disk utility to check the drive and maybe verify/repair something on it.
-Brian

Slow to mount firewire drive.

I just bought a 200 gig firewire harddrive off of ebay and it takes about 2 minutes for it to mount. I plug it in and the activity light blinks for a while before it finally shows up. It doesn't take as long when it is connected with USB but I would rather use FireWire because it's better. Does anyone have any ideas why this would take so long.

My friend I had the exact problem.
I had the maxtor One touch II I used it like one year after warranty expires the contoller chip gone.
probablly thats the problem you have or some thing different than mine.
Somethimes system cant recognize the external drive for a moment. Unplug the Firewire cable or USB cable and re-plug it. That could working for me.

Freezes when waking up with Firewire drive connected??

When you put your mac to sleep are you supposed to unmount your external drives(firewire)? is this different for firewire vs. usb?
I have a Dual 2GHz G5 and an Iomega "black" 250Gig external hard drive connected through firewire and many times (not always) when i put the computer to sleep or it goes to sleep by itself when it wakes up the computer freezes (spinning ball) but un-freezes if i pull the firewire cable.
what am i doing wrong?

There could be a problem with the FW drive's firmware. Older, non-standards-complying versions have been known to do stuff like this, especially with newer Macs that are more stringent in what they tolerate. Check with the manufacturer for updates.

Need Help with Firewire drive

I got a Seagate HDD in a Vantec Firewire enclosure. Every so often when my IMAC awake from sleep, the External Drive look like still in sleep mode. It is not responding at all. I cannot hear the HDD spinning.
The only way I can get the drive to work again is by turning it off, then unplug and plug the firewire cable back. If I just turn the power on and off on the external enclosure, the HDD wont spin at all.
I know the external enclosure and the HDD work fine because I tested it on My PC and it work fine without any issue.
Is there a way to turn off the power management for the IMAC firewire port or any solution to resolve the drive stop responding after wake up from sleep? This could happen 2-3 times a week.

Not going to hi-jack this thread with my issue but I'm experiencing some very odd (and not too far off) behavior like this with a Seagate drive (However it's a FreeAgent Desk | Mac).
YOU ARE NOT ALONE! Something must be going on. I'll edit this post with a link to my post once I'm through searching (Came across yours, wanted to see if I could find an existing Seagate / Firewire issue.

Dreamweaver CC opening files very slow iMac with Fusion drive

I am working on a small website based off on Bootstrap 3. Now that I am almost done with the project opening files take a few seconds to open them (in code view). I have tried the various fixes like resolveremoteurltoipaddress=FALSE but still the files load very slow. On my Windows Machine it loads very fast and that machine is 4 years old. The iMac I am using at work is the latest version with decked out specs and only Dreamweaver CC and Edge Code have very slow opening of files. Creating new documents inside Dreamweaver CC is fast. Is there a way to make Dreamweaver open files faster? How to make it load faster, open documents faster, especially in code view. My initial thought is maybe its because I am linking to a few JS library like TypeKit and jQuery but I have not experience these problems on my Windows PC. Any help would be appreciated.

I am working on a small website based off on Bootstrap 3. Now that I am almost done with the project opening files take a few seconds to open them (in code view). I have tried the various fixes like resolveremoteurltoipaddress=FALSE but still the files load very slow. On my Windows Machine it loads very fast and that machine is 4 years old. The iMac I am using at work is the latest version with decked out specs and only Dreamweaver CC and Edge Code have very slow opening of files. Creating new documents inside Dreamweaver CC is fast. Is there a way to make Dreamweaver open files faster? How to make it load faster, open documents faster, especially in code view. My initial thought is maybe its because I am linking to a few JS library like TypeKit and jQuery but I have not experience these problems on my Windows PC. Any help would be appreciated.

Mini won't start with firewire drives connected

to all,
please ignore the specs below. the computer i am talking about is the 1.66 Intel Core Duo, 1 GB RAM OS X 10.4.7.
as per the title, the mini will not start up if there is a FW drive connected. my wifes amacom flip 2 disk, the Iomega drive specially deisgned for the mini, or my lacie pocket drive. the screen shows the apple but the cog does not appear. it immediately appears after the drives are removed or powered down.
is there a solution for this? or do we have to live with it? or am i alone in experiencing this? there are no other operating systems alive on any of the FW drives to start from.

Hold down Apple-V right after you hit the power button. That will put you in verbose mode, so you should be able to see whatever is keeping the kernel from loading.

Slower Reboot with FireWire Drive

Similar Messages

Maybe you are looking for