Firewire HDs

[Stefan Bruda]

At 21:07 -0400 on 2003-5-18 Ben Hall wrote:
 >
 >  ieee1394: Node 01:1023 has non-standard ROM format (0 quads), cannot parse
 > ieee1394: sbp2: Logged into SBP-2 device
 > ieee1394: sbp2: Node[01:1023]: Max speed [S400] - Max payload [2048]
 > ieee1394: Device added: Node[01:1023]  GUID[0030e001e0005bcc]  [Oxford 
 > Semiconductor Ltd.   ]
 > 
 > I still, however, cannot see the device from any programs.  I'm assuming 
 > it would use /dev/sda, at least that's what happened in RH9.

Well, I did not have a chance to try Firewire drives, but you should
probably mount some /dev/sdaX (where X is a partition number of the
partition you are interested in) instead of /dev/sda.

>From what I understand from the logs (keep in mind though that I am
not familiar with those messages so this is just an educated guess)
the Firewire driver does see and adds a device (is your drive made by
Oxford Semiconductor?), although it is a bit strange that it does not
tell you to which /dev entry it belongs.  It is however consistent to
assume that the first available SCSI device will be used (which would
be /dev/sda if no other SCSI devices are attached).

One other (stupid) question would be: do you have (generic) SCSI
support compiled into the kernel?  Maybe the Firewire module works (as
is apparent from the logs) but has no place to pass the result (i.e.,
the new SCSI drive) to.

You could also try to run pdisk or fdisk (depending on how the
Firewire drive has been formatted) on the thing to see whether you see
at lest the partition table.  (If the drive is not formatted in any
way, you may want to use pdisk/fdisk to set it up anyway.)

Hope my $0.02 help a bit,
Stefan

-- 
If it was so, it might be; and if it were so, it would be; but as
it isn't, it ain't. That's logic.
    --Lewis Carroll, Through the Looking-Glass