Weird firewire error: no valid selfIDs

Question

Level 1

75 points

Weird firewire error: no valid selfIDs

We are having an issue with firewire on two different macs. One is mac pro running 10.5.5 and the other g5 running 10.4.11 ( i am not on my home machine). We were shooting tethered to a hasselblad h3d via firewire 800 this morning when we first encountered the problem, although subsequently all firewire devices (externals, various manufacturers Lacie, iomega) drives were affected. The camera, and the the hardrives were not recognised. We have followed all steps appart from step 9 in this document http://www.thexlab.com/faqs/firewiretroubleshooting.html . We have also ran permissions repairs and subsequently applejack http://applejack.sourceforge.net/ Reseting the PRAM resulted in sucessful remounting of the external hardrives but when we started the camera it was not recognised. I subsequently noted the external hardrives that had remounted after the pram reset were no longer mounted although i am not sure when this happened.
This message shows up repeatedly in the system events log, even when no firewire devices are physically connected.:
Jan 19 15:55:02 Mac-Pro kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.

A similar message repeatedly shows up in 10.4.11. I would have said that the fact it was not working on two different machines would isolate it to the camera (changed firewire cables too) but these messages on both systems is just weird =. Help very appreciated!!!

mac pro, Mac OS X (10.5.6)

Posted on Jan 19, 2009 8:37 AM

Reply

Answer 1

tmx3 Author

Level 1

75 points

Jan 19, 2009 8:55 AM in response to tmx3

here are a few bits of the log from the g5

Jan 19 12:46:30 Studio-G5 configd[35]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jan 19 12:46:30 Studio-G5 configd[35]: posting notification com.apple.system.config.network_change
Jan 19 12:46:30 Studio-G5 lookupd[85]: lookupd (version 369.8) starting - Mon Jan 19 12:46:30 2009
Jan 19 12:46:32 Studio-G5 configd[35]: target=enable-network: disabled
Jan 19 12:47:40 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:47:49 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:47:51 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:48:02 Studio-G5 kernel[0]: Bad SelfID packet 3: 0x0 != 0xffffffff!
Jan 19 12:49:22 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: 274 bus resets in last minute.
Jan 19 12:50:26 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: no valid selfIDs for more than 2 minutes after bus reset.

and

Jan 19 13:19:14 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: no valid selfIDs for more than 2 minutes after bus reset.
Jan 19 13:22:26 Studio-G5 kernel[0]: FireWire (OHCI) Apple ID 52 built-in: no valid selfIDs for more than 2 minutes after bus reset.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.
Jan 19 15:09:24 Studio-G5 kernel[0]: disk1s1: media is not present.

there

Reply

Answer 2

Jan 21, 2009 4:04 AM in response to tmx3

I've got a similar problems with two mac and three different FireWire Drives.

1/21/09 6:50:44 AM kernel FireWire (OHCI) Lucent ID 5811 built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 6:53:56 AM kernel FireWire (OHCI) Lucent ID 5811 built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 6:57:08 AM kernel FireWire (OHCI) Lucent ID 5811 built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 6:57:08 AM kernel FireWire (OHCI) Lucent ID 5811 built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 7:00:20 AM kernel FireWire (OHCI) Lucent ID 5811 built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 7:00:20 AM kernel FireWire (OHCI) Lucent ID 5811 built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 7:03:32 AM kernel FireWire (OHCI) Lucent ID 5811 built-in: no valid selfIDs for more than 3 minutes after bus reset.

Reply

Answer 3

Jan 21, 2009 7:50 AM in response to Khurt Williams

Hi, I too am having this problem and my isight camera is not working. I don't have any other firewire devices plugged into the machine (log below).

When I unplugged my monitors firewire connection, the problem went away. I have a mac pro that I bought in the last two weeks. It has 2 30 inch cinema displays. In the working configuration, I have nothing plugged into the firewire port on the back of the machine and the isight camera plugged into the one on the front.

1/21/09 8:03:24 AM kernel FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 8:06:36 AM kernel FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 8:09:48 AM kernel FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 8:13:00 AM kernel FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
1/21/09 8:16:12 AM kernel FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.

Reply

Answer 4

Jan 23, 2009 4:06 PM in response to Hsing-Huei

I took the 3 FireWire drives and plugged them into my friends MacBooks. No mount. Apple tech thinks the FireWire port on my Macs are hosed since very unlikely that three FireWire drives ( one is brand new ) could have bad FireWire ports. However I think it is unlikely that FireWire ports on all my Macs have problems.

Reply

Answer 5

tmx3 Author

Level 1

75 points

Jan 24, 2009 2:41 AM in response to Khurt Williams

it would be interesting to see what order you plug them in - if that made a difference - whether it is one drive that triggers it or all drives are affected. We hired a new camera to isolate the probelm and that worked fine. We've got a suspision that the firewire port on the camera has become damaged as the port is recessed and very difficult to get in (e.g. constant wigling that would loosen the board. bad design, though we'll see when we get the report from the manufacturer). Could it be a problem with the way your machine writes to the drives? were they formatted on different machines or the same one? Just grasping at straws really! keep yu posted.

Reply

Answer 6

Feb 3, 2009 7:43 AM in response to tmx3

I had the same problem 3 weeks ago at my office (Macmini 10.5.6 intel). I tried several things to find out why my 4 external firewire drives did not mount. I never had this problem at home (Macmini 10.5.6 PPC, with 3 external firewire drives). During the weekend, I plugged an audio cable that I use few times a year to listen to the iTunes music in the basement. Later in the day, I restarted the computer and all firewire drives did not mount. Same problem that I have at the office. I asked myself what have I changed since last restart and I noticed that I had plugged the audio cable. I removed the audio cable, restarted and the problem is solved.

So I wanted to see if this is the solution because at the office, I also have an audio cable plugged in the external audio. On monday morning, I removed the audio cable from my office Macmini and all the external firewire drives mounted.

I do not know if it is the solution for others firewire issues. I personnaly think that is is hardware/software related because it happened after recent Apple updates.

I hope it can help.

Reply