Debugging FireWire HD issues

Hi,
I'm working heavily with big RAID systems (LaCie Biggest) attached to the Firewire port of my MacPro to store scientific simulation data and I'm having frequent issues with corrupted file systems without having the RAID reporting any error. Issues go as far as loosing the partition table and being unable to mount the external filesystem. I'm usually checking quite often the integrity of the file systems and also comparing checksums of files after I copied from one external disk to another.
I had this morning again a warning about a slightly corrupted file system of a RAID system I was sure it couldn't be corrupted. The file system is mounted r/o, was recently checked and wasn't reporting any problem. So, I tried a different cable, and at the end I tried with FW400 instead of FW800, and this mounted the file system correctly and no corruption was detected.
Now, has anybody an idea how I can debug this to find the problem on the FW. I have usually 2-3 big RAID attached at the same time. I now probably understand how I lost the file system on my Time Machine FW RAID, as I probably "repaired" a file system that wasn't corrupted. Is there anything I can do to avoid such problems. Are there firewire cards for the Mac, and are they safer? Would eSata be a better choice?
Any hint is welcome, thanks!
Thomas

Dump the LaCie and Firewire for RAID and important data or performance and invest in PCIe SATA controller that supports Port Multiplier and some 5-8 drive enclosures.
Don't rely on Apple Disk Utility First Aid, invest in Alsoft Disk Warrior - and if you need more than that, MicroMat TechTool Pro. Make some backups and clones with SuperDuper as well, "sparse disk images" are fine for keeping an image of your system/apps.
Yes, there are FW cards. Sonnet and Aaxeon are what I use. I also use OWC Oxford 934 for single drives.
http://eshop.macsales.com/item/Other%20World%20Computing/MEFW934AL1KS/
http://eshop.macsales.com/search/Aaxeon
http://eshop.macsales.com/shop/hard-drives/3.5-SerialATA/

Similar Messages

FIX: FireWire communication issue solved - What worked for me

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

FireWire Compatibility Issue

I have a '12 PowerBook G4 1.5 GHz with 1.25 GBs of RAM with Super Drive running 10.5.5 that I'm backing up to a OWC Neptune using Time Machine. It uses a Oxford 911+ chipset. My previous external hard drive used a Oxford 911 chipset.
Recently I've started getting Time Machine error messages related to some sort of chipset related FireWire compatibility issue. My OWC Neptune's firmware is up to date too. What could possibly be causing this to happen?

I already tried zapping the PRAM due to my ethernet not working on my '12 PowerBook G4 1.5 GHz & it didn't fix my FireWire issues either. I'm also still getting the "Unable to complete backup. An error occurred while copying files to the backup directory." error.
Here's my Carbon Copy Cloner log from when I tried to clone my hard drive earlier:
12:47:46 Launched Carbon Copy Cloner [3.1.1]
13:00:14 Launched Carbon Copy Cloner [3.1.3]
==================== Carbon Copy Cloner (v. 3.1.3): 2008-12-26 13:00:26 -0500 ====================
Operating System: Version 10.5.6 (Build 9G55)
Hardware:
hw.machine: Power Macintosh
hw.model: PowerBook6,8
hw.logicalcpu: 1
hw.physmem: 1342177280
vm.loadavg: { 0.81 0.94 0.92 }
Task: Disk-to-disk clone
Source: Macintosh HD (/dev/disk0s3, A5A956D7-D32B-3999-A802-9E670BF97CE5)
Mount point: /
Filesystem: hfs
Capacity: 148.93 GB
Used: 83.64 GB
Available: 65.28 GB
Mac OS X version: 10.5.6
Target: '12 PowerBook G4 Backup (/Volumes/'12 PowerBook G4 Backup/ [/dev/disk1s3, D184AB93-AAD8-3AC4-8134-AF5C30EE735B])
Mount point: /Volumes/'12 PowerBook G4 Backup
Filesystem: hfs
Capacity: 297.97 GB
Used: 132.79 MB
Available: 297.84 GB
Mac OS X version: Mac OS not installed
Bootability: This volume will be bootable.
Cloning method: Backup everything
Delete items on target that aren't on the source: No
13:00:27 The target volume has ownership enabled.
13:00:27 The target volume has Access Control Lists enabled.
13:00:27 Authenticating...
13:00:46 Initiating synchronization engine...
13:00:48 Cloning...
15:58:06 rsync: mknod "/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201120/private/var/samba/winbinddprivileged/pipe" failed: No such file or directory (2) (51)
15:58:06 rsync: mknod "/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201120/private/var/samba/winbinddpublic/pipe" failed: Address already in use (48) (51)
16:48:55 rsync: mknod "/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201330/private/var/samba/winbinddprivileged/pipe" failed: No such file or directory (2) (51)
16:48:55 rsync: mknod "/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201330/private/var/samba/winbinddpublic/pipe" failed: Address already in use (48) (51)
19:08:46 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at /Volumes/Home/Users/bombich/Development/Bombich_Software/rsync-3.0.5pre2/main.c (1047) [sender=3.0.5pre2] (51)
19:08:47 rsync: Some errors were encountered during the backup., Error code: 51
19:08:48 Sync Engine warnings: (
"rsync: mknod \"/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201120/private/var/samba/winbinddprivileged/pipe\" failed: No such file or directory (2)",
"rsync: mknod \"/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201120/private/var/samba/winbinddpublic/pipe\" failed: Address already in use (48)",
"rsync: mknod \"/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201330/private/var/samba/winbinddprivileged/pipe\" failed: No such file or directory (2)",
"rsync: mknod \"/Volumes/'12 PowerBook G4 Backup/Users/craigwd_2000/.Trash/Previous Systems.localized/2008-12-201330/private/var/samba/winbinddpublic/pipe\" failed: Address already in use (48)",
"rsync error: some files/attrs were not transferred (see previous errors) (code 23) at /Volumes/Home/Users/bombich/Development/Bombich_Software/rsync-3.0.5pre2/main.c (1047) [sender=3.0.5pre2]"
================================================================================

Original USB cable is missing something??? Not a firewire/usb issue!

This is what happens: can anyone explain?
I have two chargers with USB port (one in-car and one portable battery) that do not work with iphone 3g when the original white usb cable is attached; I don't get any message: they just do not charge the iphone. I even tried to use a different cable from my ipod but still... Then I tried to use the cable that came with the Proporta portable charger and guess what: _both of them now charge my iphone_!
So: what is exactly missing in the Apple cable?
And: where can I find another cable that works with 3rd part usb chargers?

Some USB power sources, even though they have the correct voltages, do not work. This is because they don't support USB negotiation, which allows devices to determine the precise capabilities of a host adapter. (this is unrelated to the USB vs FireWire charging issue.) Since the device doesn't respond to the iPhone's attempt to negotiate, the phone assumes it's not compatible.
Not sure how using that different cable could affect it, unless the cable itself has some circuitry in it to handle the negotiation.
PS
Here's some info from Wikipedia:
"There are also devices at the host end that do not support negotiation, such as battery packs that can power USB powered devices; some provide power, while others pass through the data lines to a host PC. Some of these devices can supply up to 1 A of current. Without negotiation, the powered USB device is unable to inquire if it is allowed to draw 100 mA, 500 mA, or 1 A."

X99S GAMING 9 AC Not booting - Debug 94 code - Issue with GTX 980 SLI in WoW

Hello, I bought the X99S GAMING 9 AC motherboard but have ran into some issues.
The computer won't boot when I put my second MSI GTX 980 Gaming 4 GB card in the last PCEI 3.0 port (PCIE port 5) and I get the debug LED message 94 on the motherboard. I have a SLI setup.
The first card I have in the second PCIE 3.0 port due to the Noctua U14S CPU fan takes up space for the first slot. So I have been running my grafic cards in PCIE slot 2 and 4 with some issues.
First the card in slot 2 gets really warm over 86 celsius. And second: SLI runs really poorly in World of Warcraft. I get a lot higher performance with just one card activated. I am not sure if it's cause I am not running my cards in the recommended PCIE 3.0 ports or because WoW has some issues with SLI, but I heard other people have no issues at all with WoW in SLI.
I got the same issue with 3Dmark firestrike, the cards perform really poor in SLI. I get higher score with SLI turned off..
Though SLI seems to run pretty well in 3dmark 11 and Diablo 3 Reaper of Souls.
But the main issue right now, is that the computer won't boot with the grafic cards in PCIE port 2 and 5. The solution to run them next to each other is not good, cause it gets really hot and I get bad performance in WoW and Firestrike.
Picture of my setup before I switched places with the grafic cards as you can see, it is really tight:
Any upcoming bios updates (got v1.3) that will solve this issue on the horization? Hopefully this get sorted out really soon..
My whole computer setup:
Intel i7 5820K | MSI X99S Gaming 9 AC (bios 1.3) | SLI MSI GTX 980 Gaming 4GB | Samsung 850 Pro 512 GB | WD Red 4TB | G.Skill Ripjaws DDR4 3000MHz 4x4GB | EVGA SuperNOVA P2 1000W | Noctua NH-U14S PnP | Fractal Design Define XL R2 | 5 Noctua NF-A14 PWM 140mm fans | Windows 7 Pro 64 bit

You must use the recommended PCIE slots as the manual says for your CPU type, PCIE #1 and PCIE #4 if I remember, just open the manual :P for optimal 2Way SLI, also your 5820k will limit to 28 pcie lanes only if you plan to add more vgas...the other problem is your giant CPU air cooler blocking PCIE#1, do a favor to yourself, buy a watercooler for your 5820k and your problems are gone, add some overclock in your system, low noise and better temps.
Here I use 3x980 in SLI with X99S Gaming 9 AC, going soon to WC the VGAs with EK blocks.....3way is far more temperature critical than 2way spaced one.
Cheers

IPod (with Dock Connector) 15GB firewire mounting issues with iTunes 7.0.2

Before I sent my iPod in for battery replacement I backed up my music and restored it under iTunes 7.0.2. I then disconnected it, put it in the box and sent it off. When I got it back, I charged it fully with the firewire cable and the wall charger then tried to mount it to refill it with music. It would not mount with the firewire cable. It is charging but will not show up in the finder or iTunes. I noticed that it would not turn off by pressing and holding the play/pause button. I figured it would eventually sleep so I put it into my laptop bag to bring with me to work.
I got to work and borrowed my buddies' USB cable and the iPod is completely dead. Dead like not even a boot screen. Apparently it can no longer sleep and completely discharged during the night. Additionally, the USB cable doesn't seem to be powering or charging it. I plugged it into my workstation using the firewire cable and although it will charge it still will not mount.
After about a half an hour of charging I disconnected the firewire cable and plugged in the USB cable. The iPod mounted into iTunes. I figured I would restore the iPod again to fix the firewire issue so I clicked Restore. I then got a message saying "You must connect using FireWire to restore the iPod." I cannot connect using Firewire.
To recap, I cannot charge over USB, I cannot update over USB and I cannot mount over Firewire.
I reconnected using USB, Quit iTunes without dismounting the iPod then tried to erase the iPod with Disk Utility, which failed. Next the iPod wouldn't even mount under USB so I went into iPod diagnostic mode and found a new line item labeled USB DISK which forced the iPod to become visible to Disk Utility again. I repaired the iPod disk and it will once again mount under USB but will not charge and will not restore.
I have scoured the apple.com site to try and find a way to downgrade my iPod to what it was before 7.0.2 but cannot find anything.
iTunes 7.0.2 has rendered my iPod totally useless. It was bad enough having a battery that was toasted and was glad to finally get that taken care of but now that I have a battery that works I have software that cannot mount via firewire and will not turn my iPod off and drains the battery. Plus with no way to go back to a previous version Apple has rendered my iPod useless.
Help!... please.

Hi Kenekeu
I just wanted to chime in and bump this thread. Although I've posted here several times about this exact problem, with no solution found yet, and no response from Apple. I tried rebooting into windows (via bootcamp) and reformatting my ipod from there. However when I downloaded the older version of the ipod updater, i was told that it was expired and a newer version was available (sigh). So I now have a windows formatted ipod that still won't connect via firewire.
I am still able to mount and transfer songs via USB in mac OSX. Luckily I had one of those dual usb/firewire cables, which plugs into the plug charger via firewire, and into the computer via USB at the same time, so my ipod doesn't lose charge.
Hopefully there'll be a fix soon, because this is really frustrating. I've had this ipod for a couple years, and was always proud that it lasted this long... and now this.

USB/FireWire Ports Issue

So before I go into the apple store and ask for this computer to be repaired/replaced, I would like to see if anyone knows if something can be done about this issue I have pinpointed..
Basically when I have more than a few USB/FireWire ports connected, one or more of the devices does not function properly. This has happened with two external hard drives - which should have no problem being connected simultaneously.. When I try to eject one of them, I receive a message stating that it cannot be ejected because one or more programs may be using it.. although all programs are closed, causing me to have to force eject..
Also, I plug in one drive and open the other in finder to back it up, and all of the folders in the drive are suddenly empty.. nothing inside. I go to Get Info.. Zero KB.. I try ejecting, but receive the same message, so I force eject, plug it back in, and wala, all the files are back in the right place..
This has also happened in the past when my cinema display and a printer were plugged in simultaneously.. the computer won't detect the USB of the cinema display -- which only means that the speakers of the display won't work + no brightness control from the keyboard.. so i let it slide.. but now with this external hard drive issue, i need to solve the problem..
Thank you for reading..

Same here. Since a few weeks, my MacPro ejects USB HDD's as soon as I write or read data on it.
(no I haven't installed something new at this time and all HUB's and HDD's have their own power supply, and yes they have been exchanged, so its not a broken cable or so !!!!!!!!)
After a reset of the NVRAM and PRAM its better for an hour or so, then starts to eject again. I've seen a lot of communities with exact the same question, but never a solution for it. There is also nothing in the support tab of apple.
Hope someone here can help me out or due to the fact that this is a AplleSupportCommunity, a Apple-Employee may starts to do his job and help this huge amount (I guess there are hundrets or tousand) of mac-user with exact the same problem....
btw: don't agree with MACATTACK2010 that this is a hardware problem, cause there are a lot of people in the
net that ask the same question with brandnew Hardware. I think it's an OS or an Update Bug, or may both.

Firewire Driver issue

Anyone using M-Audio Firewire 1814 still experiencing Driver issues with Snow Leopard and LP9? There was an update on 11/13 and 11/14 but my Firewire still isn't working. Anyone got any ideas? This is absolutely crazy that M-Audio hasn't got itself organized. Make me think twice about purchasing another one of their pieces of equipment. This is crap!!

Thanks guys for replying - I'm very grateful.
I have reset PRAM, bought a new FW cable, de-installed and reinstalled OS X and APOGEE user interface. I do not have any other FW devices unfortunately but I can try it on friends so will do that to rule out a hardware fault. The mini has only been in my possession since early jan and it was a completely clean unit - no apps or software etc.
The one suggestion I do not follow above is the Partition startup or Mavericks start up - sorry.,...what does that mean ? I do have 2 500gb drives plus 2 external HDD so storage is no problem. I will also try the SMC suggestion as I don't think I followed those steps clearly last time.
Again, thanks for your time. wish me luck - all I want to do is play and record my music !!!

Macbook Pro WD Firewire 800 issues possible work around

I have been having issues with my Western Digital My Passport Studio and the Firewire 800 connection. The drive would mount and was completly readable however copying to the drive would result in a stall. The USB connection worked perfect. I have found if I disabled the Wi-Fi connection I could then write as usuall without error.
I have read of people having issues with thier firewire connections and am curious to know if this helps anyone else. The most popular responses have been RMA the drive or the Macbook. I have also read peoples dealiings with Apple thus far have not been very helpful either. Hope it helps seems to be working for me thus far. Hopefully a fix is in the works 'cause I love my MacBook and the drive.
This is the current (late) 2011 MBpro with OsX Lion 10.7.2

I can only answer part of your question. Your SLR has mini HDMI and a mini USB out. Your MBP has three ways to connect: USB, FW 800 (9 pin) and Thunderbolt (which is ao far supported by a limited number of devices).
As far as I know, you will not be able to use On Location with the Canon. But I could be wtong. Good places to ask are the Adobe forums and Canon forums.
Good luck.
Russ

Firewire Bus Issue

I have a I Mac G5 with 10.3.9 installed and I have had the computer for about 1 and a half years. I have daisy chained three maxtor drives which I okayed with apple support--I wanted to make sure this computer could handle the three drives, and a video converter. About two months I bought the LaCie dvd burner and have to swap firewire ports with the Sony Converter when I want to burn discs.
Everything has worked just fine until about two weeks ago when i couldn't boot up the computer. I took it into an Apple Store thinking it might be related to a power problem I had about 9 months ago. After a two hour diagonostic was run twice on the machine the support people could find nothing wrong with the computer.
It also started up fine without the firewire ports being used and I didn't recognize that this must be the problem at that time.
The next morning, with the firewire cables plugged in directly to the back of the computer it wouldn't start, so I shut down, unplugged everything, waited a few moments and then plugged the processor back in. It started right up.
Now, I understand what's wrong, but don't know how to fix it. When the unit doesn't start up, as it didn't a few nights ago after I burned a dvd, I shut down and unplug the firewire cable and then reboot. I then can plug in the Maxtor drives, etc., and the processor works fine.
So, it seems to be a start up issue with the fire wire bus or whatever.
Does anyone know what I can do to fix this and get things back to the way they used to be?
I don't want to upgrade to Tiger because I have apps that won't work with Tiger and I don't want to upgrade them at present either.
Any help or advice would be greatly appreciated.
By the way, I use the external drives for my film shorts.
Lucin

This is Apple's article -
http://docs.info.apple.com/article.html?artnum=88338
FireWire ports can (or use to) get "fried" (99% of
the first FW Mac, Blue G3 users had to eventually
invest in PCI FW controller as ports would just stop
working).
I would invest in PCI FW800/400 rather than
daisy-chain and so you have two buses (all the FW
ports share one common bus).
A powered hub has its own a/c.
There use to be more talk about using "isolator FW
cables" to prevent hot-plugging from causing
electrical damage to FW ports.
I am not a fan of most of the vendor supplied FW
cases (Maxtor, WD, etc) and just go with a good
Oxford based unit (FW bridge type) which are more mac
friendly and work. Or even eSATA for hard drives
(SeriTek etc) which allows each drive to be on its
own channel.
Hi,
Thanks for the imput. What do you mean that the powered hub has it's own a/c? I'm confused.
Next time I get a drive I may go with the Oxford based, altho' I have to say that the Maxtor Drives have been very reliable so far.
As for the controller, I have to see if I can get one for the IMac. I got a PCI card for my G4 and that was a help.
I'll check out this article. Actually, I've already read this.
When I took the machine to the apple store they checked my firewire ports. They checked everything and they said when I called today that the ports were not fried, that they were okay.
My question is: why would the computer boot up when I unplug the fire wire cable and not boot up when I don't? this is a new development and I've been fine with this machine for over a year.

Firewire thunderbolt issues

So I'm trying to connect a PreSonus StudioLive AI to a 27 inch late 2013 iMac running 10.9.5. There have been people on the forums at PreSonus that say it that there is an issue with Mavericks. I've also seen a press release from PreSonus saying that they worked with the Firewire to Thunderbolt converters. The problem is that the system sees the converter but does not see the board. I have installed the recommended drivers and such.
The weird part is that it actually connects for a moment and I can use the software, but in less than 5 minutes, it will freeze and crash.
I can upload the saved system profile if necessary (just couldn't find an upload link/button).
Thanks for any and all assistance, this is driving me CRAZY!!!!!
Tyler

We would have no idea, my suggestion is to contact the developers of the PreSonus StudioLive and see if they support the device in
OS X Mavericks
via FW to Thunderbolt cable.
Good luck.

Does update 10.6.2 fix firewire HD issue?

Hi
I buy recently a firewire400 hard disk and it don't work with snow leopard (appear in finder but freeze when copying file, can't inizialize, etc...)
The drive works normally on Leopard 10.5.8.
So someone can tell me if with the 1o.6.2 update of snow leopard apple fix the problem of firewire?
my machine is a macBook Pro 15" santa rosa (late 2007) with 4gb ram
thank you and sorry for my bad english

I am experiencing similar problems and figured I would set the record strait here. I have two identical 2.8 GHz iMacs running the latest OS 10.6.2. One at home one at work. I extensively use both usb and firewire hard drives for data backup. Just bought a G-Raid Mini 1TB external. When I first plugged it into my Mac at work using the firewire 800 cable it mounted perfectly. I copied nearly 250 GB of data from that computer to it. Went home and accessed that data using the same firewire 800 connection and cable. Next time I came into work I went to mount the drive using the same cable and nothing would mount. Drive appeared to be working but nothing showed up on the desktop and disk utility shows no external drive. I switched to a usb cable and the drive mounted flawlessly. So I thought the cable was bad. But her is the kicker I mounted another drive using the same firewire 800 cable so the cable is not bad. The drive mounts perfectly at home via firewire and usb. Why a drive would only mount on some computers via firewire 800 and thumb it's nose at others I don't know but to me this sounds like a software glitch not a hardware or cable issue. I have had this same thing happen to me a while back with a friends hard drive from a different manufacturer but thought nothing of it because it wasn't my drive.

WCF debug Test-case issues.

This seems to be a weird issue, I had solution with a WCF Service and Unit Test Project.
In Unit test, I had some testcases which will step into WCF service. When I start the service, and go into Test-case (Test explorer) all test-cases are disabled, and in Test => all Debug / RunAll tests all options are disabled. So I am not able
to debug testcases when WCF Service is running this is the issue. I am using VS2013 Ultimate with Update3 installed.
I am rightclicking on WCF Service debug start new instance, then go into Test-case (Test-explorer) when I right click on test-case all options are disabled and so is in Test menu.
Thanks In Advance,
KSR

Hi KSR,
To debug the WCF Service from the Test project, one idea is that you could creates and opens the service host in test project code.
A similar thread about this issue, reference:
http://stackoverflow.com/questions/2790901/debugging-visual-studio-2010-unit-test-and-wcf-service-in-one-ide-instance
A blog also shared some suggestions here:
http://blogs.msdn.com/b/ploeh/archive/2006/12/04/integrationtestingwcfservices.aspx
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

FCE and FCE HD Firewire Connection Issues

Hello, I just recently cleaned out my hard drive and reinstalled Tiger 10.4.11. I reinstalled all my previous applications with out any problems, but I had an issue with both versions of FCE. For some reason it won't recognize my firewire port. I don't know if there was something else I had to do to get it to recognize. The cable is fine and the camera, because I got it to work with my Power Mac G4 last night, but it doesn't work for my laptop. Any ideas? Thanks, Matt

All HDV is MPEG-2 based. It's an HDV tape camera. The problem is QT7.4 and the older version of FCE. Some people have got this to work. I don't know how, but many others have had problems using that and older versions of FCE and newer versions of QuickTime, 7.3 and probably 7.4 as well.

Sudden FCP Firewire (?) Issue

I will preface by asking for no laughter regarding the age of my setup.
For the past eight (8) years we have been using a DVCPro deck (AJ-D230H) to capture video prior to uploading it to a scratch disk in a G4 Mac running OS 9.1.x (I think) using Firewire and FCP 1.2 (I think--I am typing this at a location other than the equipment in question).
Yesterday, I am told the computer "white screened". Bottom line is that it locked up and the computer had to be forcibly restarted.
Upon the restarting and opening FCP to continue editing, the user found there was no longer any sound.
What is actually happening is that it no longer plays over the FW to the DVCPro deck to the external broadcast monitor and speaker. When turning off External Video, the audio plays back just fine through the computer's speaker, as expected.
Something seems to be wrong with the Mac/FW interface and I am at a loss as to how to fix it.
Log and capture over the FW works (device control, playback, and capture).
Tried moving FW cable to different port on Mac.
Tried moving FW cable to different port on DVCPro deck FW card.
Tried replacing FW cable.
Tried Log & Capture using FW between PC & DVCPro deck (worked).
Found references to "trashing preferences", but wonder if this is possible in my old version.
Please, does anyone have any other suggestions?

I thought I would follow up on this thread just in case someone stumbles upon it in the future.
One of the people involved talked to the technician who last serviced our DVCPRO deck, and we were assured there was more than likely nothing wrong with the deck, nor with the Firewire card in the deck.
We were able to borrow a Mac running 10.4 and Final Cut Express HD. Once installed, we had none of the problems described in the original post. While repair might have been possible, we concluded that the eight-year-old Mac needed to be retired.
Therefore, this question was resolved by purchasing a new Mac Pro with dual quad core processors. I did not know FCP could Print to Video so quickly.
Thank you all who responded in an effort to help me resolve this issue.

Debugging FireWire HD issues

Similar Messages

Maybe you are looking for