LinuxQuestions.org - Second firewire external hdd enclosure fails to appear as a scsi device;

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Second firewire external hdd enclosure fails to appear as a scsi device; (https://www.linuxquestions.org/questions/linux-newbie-8/second-firewire-external-hdd-enclosure-fails-to-appear-as-a-scsi-device%3B-364635/)

Second firewire external hdd enclosure fails to appear as a scsi device;

looks like I'm having the same problem as /questions/showthread.php?s=&threadid=187792
to which nobody had an answer...

Essentially I have two near identical, pretty generic USB 2.0 & Firewire external HDD boxes, both with 80gb NTFS drives in them. If I plug either one into the (single) firewire port on my computer, it appears as /dev/sda without a problem. If I plug one into USB and one into firewire they're both there as /dev/sda and /dev/sdb - the problem arises with daisy chaining; both these enclosures have 2 firewire ports on for daisychaining, however, while the second drive will generate a load of spaff in dmesg, it refuses to get recognised as a hdd.

Sequence of events follows:

Plug 1st enclosure into firewire on pc, power on drive,
it appears as /dev/sda, and the following spaff in dmesg:

Code:

[root@jericho /]# dmesg -c

ieee1394: Error parsing configrom for node 0-01:1023

ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...

ieee1394: Error parsing configrom for node 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: Node resumed: ID:BUS[0-00:1023]  GUID[0050770e00071002]

ieee1394: unsolicited response packet received - no tlabel match

scsi7 : SCSI emulation for IEEE-1394 SBP-2 Devices

ieee1394: sbp2: Logged into SBP-2 device

ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]

  Vendor: WDC WD80  Model: 0JB-00CRA1        Rev:

  Type:  Direct-Access                      ANSI SCSI revision: 06

SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write through

SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write through

 sda: sda1

Attached scsi disk sda at scsi7, channel 0, id 0, lun 0

[root@jericho /]#

At this point it can be mounted no problem.

The second enclosure is plugged into the spare firewire port on the first enclosure (currently connected one) and powered on restulting in the following spaff from dmesg and an utter lack of /dev/sdb:

Code:

[root@jericho /]# dmesg -c

ieee1394: Error parsing configrom for node 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: Node changed: 0-01:1023 -> 0-02:1023

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: Reconnected to SBP-2 device

ieee1394: Node 0-01:1023: Max speed [S400] - Max payload [2048]

ieee1394: Node changed: 0-01:1023 -> 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: Reconnected to SBP-2 device

ieee1394: Node 0-01:1023: Max speed [S400] - Max payload [2048]

[root@jericho /]#

My thinking here is that my firewire controller is either crap, or unsupported. It *is* quite a recent motherboard (Via EPIA MII 12000) So I'm more enclined to think it's unsupported in some way. I, however, know nothing of these things :) If it helps at all;

Code:

[root@jericho /]# uname -a

Linux jericho.oneiria.co.uk 2.6.11-1.1369_FC4 #1 Thu Jun 2 22:55:56 EDT 2005 i686 i686 i386 GNU/Linux

I can't find anything on the net and nobody on irc seems to have any clues other than "it might be a driver problem". I'm pretty new to any serious use of linux, and while the post above seems to be having exactly the same problem as me (albeit quite a while ago)... I am completely and utterly stumped.

Help very much appreciated
Ta
David

Does which hard drive you plug in first impact the results you see? Do you have any non-drive firewire devices that can verify that the daisy-chaining works at all?

I'm not sure if this is relevant, but you may also wish to look at this thread online: http://forums.whirlpool.net.au/forum...fm/387670.html

Doesn't appear to make any difference what order they're in

Code:

First one,



[root@jericho /]# dmesg -c

ieee1394: Error parsing configrom for node 0-01:1023

ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...

ieee1394: Error parsing configrom for node 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: Node resumed: ID:BUS[0-00:1023]  GUID[0050770e00071002]

ieee1394: unsolicited response packet received - no tlabel match

scsi8 : SCSI emulation for IEEE-1394 SBP-2 Devices

ieee1394: sbp2: Logged into SBP-2 device

ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]

  Vendor: WDC WD80  Model: 0JB-00CRA1        Rev:

  Type:  Direct-Access                      ANSI SCSI revision: 06

SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write through

SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write through

 sda: sda1

Attached scsi disk sda at scsi8, channel 0, id 0, lun 0

ieee1394: Error parsing configrom for node 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: Node changed: 0-01:1023 -> 0-02:1023

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: Reconnected to SBP-2 device

ieee1394: Node 0-01:1023: Max speed [S400] - Max payload [2048]

ieee1394: Node changed: 0-01:1023 -> 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: Reconnected to SBP-2 device

ieee1394: Node 0-01:1023: Max speed [S400] - Max payload [2048]



Powered down, swapped wires round



[root@jericho /]# dmesg -c

ieee1394: Node changed: 0-01:1023 -> 0-00:1023

ieee1394: Node changed: 0-02:1023 -> 0-01:1023

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: Reconnected to SBP-2 device

ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]

ieee1394: Node changed: 0-01:1023 -> 0-00:1023

ieee1394: Node suspended: ID:BUS[0-00:1023]  GUID[0050770e00071002]



Second one,



[root@jericho /]# dmesg -c

ieee1394: Error parsing configrom for node 0-01:1023

ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...

ieee1394: Error parsing configrom for node 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: Node resumed: ID:BUS[0-00:1023]  GUID[0050770e00071002]

ieee1394: unsolicited response packet received - no tlabel match

scsi9 : SCSI emulation for IEEE-1394 SBP-2 Devices

ieee1394: sbp2: Logged into SBP-2 device

ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]

  Vendor: ST380011  Model: A                Rev:

  Type:  Direct-Access                      ANSI SCSI revision: 06

SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write through

SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)

SCSI device sda: drive cache: write through

 sda: sda1

Attached scsi disk sda at scsi9, channel 0, id 0, lun 0

ieee1394: Error parsing configrom for node 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: Node changed: 0-01:1023 -> 0-02:1023

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: Reconnected to SBP-2 device

ieee1394: Node 0-01:1023: Max speed [S400] - Max payload [2048]

ieee1394: Node changed: 0-01:1023 -> 0-00:1023

ieee1394: Node changed: 0-00:1023 -> 0-01:1023

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: unsolicited response packet received - no tlabel match

ieee1394: Reconnected to SBP-2 device

ieee1394: Node 0-01:1023: Max speed [S400] - Max payload [2048]

[root@jericho /]#

I don't own any other firewire devices to verify that daisy chaining is working, I'm just unsure if this is a driver problem I can fix, or a problem with the chipset of the external hdd boxes, if they have the extra port *to* daisychain, and they're identical, so I'm thinking its more likely to be the former.

you have a duplicate GUID

google for 0050770e00071002 ... and see:

http: // sandeen.net/ fwfix/ index.html

silly linuxq won't let me post urls...