| View previous topic :: View next topic |
| Author |
Message |
sheriff-jms
Tux's lil' helper
Joined: 28 May 2004
Posts: 79
Location: Pittsburgh, PA, USA
|
 Posted: Tue Jun 30, 2009 5:51 am Post subject: [SOLVED] - unable to mount external Firewire hard drive |
 |
|
I have an external hard drive (Western Digital MyBook 250 GB) with both USB 2.0 and Firewire 400 ports.
I can see the drive from my laptop (Dell Latitude D820) and mount partitions from it with no problems,
using the USB port, but when I try the Firewire port, the system sees a drive there, and recognizes it as a
SCSI device, but the sd block devices are never created.
Looking at the dmesg output, something isn't happy.
| Code: |
ieee1394: Node added: ID:BUS[0-00:1023] GUID[0090a991e0110cdf]
scsi2 : SBP-2 IEEE-1394
ieee1394: raw1394: /dev/raw1394 device initialized
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
ieee1394: sbp2: aborting sbp2 command
scsi 2:0:1:0: CDB: cdb[0]=0x12: 12 00 00 00 24 00
ieee1394: sbp2: aborting sbp2 command
scsi 2:0:1:0: CDB: cdb[0]=0x0: 00 00 00 00 00 00
ieee1394: sbp2: reset requested
ieee1394: sbp2: generating sbp2 fetch agent reset
ieee1394: sbp2: aborting sbp2 command
scsi 2:0:1:0: CDB: cdb[0]=0x0: 00 00 00 00 00 00
scsi 2:0:1:0: Device offlined - not ready after error recovery
ieee1394: sbp2: scsi_add_device failed
|
This is on a machine running a 2.6.25-r8 kernel. The Firewire specific pieces of the
config look like this:
| Code: | # IEEE 1394 (FireWire) support
CONFIG_IEEE1394=y
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_OHCI1394=m
# CONFIG_IEEE1394_VIDEO1394 is not set
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394_ROM_ENTRY is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
CONFIG_IEEE1394_RAWIO=m
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
|
The Firewire drivers are loaded... (ohci1394, raw1394, sbp2), and the kernel is
configured with SCSI device support. The udev rules should be ok, since the same
drive is properly seen as a SCSI device and the sd block devices are created if I
connect to the drive using USB.
I'm trying to figure out what the kernel doesn't like on the Firewire side.
I can roll a new kernel with the 1394 verbose debugging enabled, if it will help get
to the bottom of this.
Thoughts?
Thanks
jms
Last edited by sheriff-jms on Wed Jul 15, 2009 3:30 am; edited 1 time in total |
|
| Back to top |
|
 |
pappy_mcfae
Watchman
Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.
|
| Posted: Tue Jun 30, 2009 6:57 am Post subject: |
|
|
Compile support into the kernel instead of using modules and retry.\
Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols. |
|
| Back to top |
|
|
sheriff-jms
Tux's lil' helper
Joined: 28 May 2004
Posts: 79
Location: Pittsburgh, PA, USA
|
| Posted: Wed Jul 15, 2009 3:30 am Post subject: |
|
|
Sorry for the delay in the thread. As it turns out, the issue wasn't so much a problem with the kernel as far as I could tell, but the external drive itself decided to die after not being used for a few months. I confirmed this by plugging the drive in using the USB port and it still did not fire up. I picked up another drive that has both USB and Firewire ports (WD MyBook, 1TB), and the new drive fires up perfectly on both the USB and Firewire ports now.
Thanks for the assist!
jms |
|
| Back to top |
|
|
pappy_mcfae
Watchman
Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.
|
| Posted: Wed Jul 15, 2009 5:20 am Post subject: |
|
|
Ah, the old broken drive trick. Happy Gentooing.
Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
