LacCie FireWire ext.HD

[Bill Fink]

On Fri May 3 2002, kcross wrote:

> I'm trying to mount my mac LaCie fireWire drive by following YDL's 
> 'howto_firewire'.
> I'm able to load the ieee1394,ohci1294 & sbp2 drivers.
> But I'm unable to find the correct sda (or is it hfs?) device to mount.
> Whenever I try to mount anything other than sda(like sda1 or sda 8,etc),which 
> is the macintosh HD,I'm told the device isn't valid or doen't exist.
> 
> I ran pdisk and got my partition map:
> 
> pdisk: No valid block 1 on '/dev/sda'     (worrying, what does this mean?)

Hi Keith,

Make sure everything works fine at each stage by doing a dmesg.

After:

	modprobe ieee1394
	modprobe ohci1394

If all goes well, dmesg should report something similar to the following:

ohci1394: $Revision: 1.98 $ Ben Collins <bcollins@debian.org>
PCI: Enabling device 02:0a.0 (0010 -> 0012)
ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[63]  MMIO=[80080000-80080800]  Max Packet=[2048]
ieee1394: NodeMgr: hotplug policy returned -2
ieee1394: Device added: Node[00:1023]  GUID[00000000204027a1]  [LaCie Group SA  ]
ieee1394: Host added: Node[01:1023]  GUID[00000000feeb324a]  [Linux OHCI-1394]

If you instead see something like this:

ohci1394_0: Received OHCI evt_* error 0x3
ieee1394: ConfigROM quadlet transaction error (-16) for 00:1023
ohci1394_0: Received OHCI evt_* error 0x3
ieee1394: ConfigROM quadlet transaction error (-16) for 00:1023
ohci1394_0: Received OHCI evt_* error 0x3
ieee1394: ConfigROM quadlet transaction error (-16) for 00:1023
ieee1394: Giving up on node 00:1023 for ConfigROM probe, too many errors

You can then try unplugging/plugging your firewire hard drive, and/or
rmmod'ing ohci1394/ieee1394 and redoing the modprobe ieee1394/ohci1394,
until the dmesg output indicates all is well.  I have always been able
to get my LaCie 80 GB firewire hard drive to be properly recognized by
this procedure (usually it just works but sometimes it's finicky,
especially after a cold boot).

Once ieee1394 and ohci1394 are happy with your firewire hard drive,
you can then do the:

	modprobe sbp2

If this is successful, dmesg should display something like:

ieee1394: sbp2: Logged into SBP-2 device
ieee1394: sbp2: Node[00:1023]: Max speed [S400] - Max payload [2048]
scsi1 : IEEE-1394 SBP-2 protocol driver (host: ohci1394)
SBP-2 module load options:
- Max speed supported: S400
- Max sectors per I/O supported: 255
- Max outstanding commands supported: 8
- Max outstanding commands per lun supported: 1
- Serialized I/O (debug): no
  Vendor: ST380021  Model: A                 Rev: 3.05
  Type:   Direct-Access                      ANSI SCSI revision: 06
Attached scsi disk sdd at scsi1, channel 0, id 0, lun 0
SCSI device sdd: 156301488 512-byte hdwr sectors (80026 MB)
 /dev/scsi/host1/bus0/target0/lun0: [mac] p1 p2 p3 p4 p5 p6 p7 p8 p9 p10

As you can see, my firewire disk drive is sdd.

If all the above looks good, the only other reason I can think of that
pdisk would complain is if the disk had never been formatted and partitioned
under MacOS.

> Partition map (with 512 byte blocks) on '/dev/hda'

[internal hard drive partitioning info deleted]

> pdisk: can't open file '/dev/hde'  (No medium found)     (what is hde for?)

I assume this is your internal CDROM or DVDROM drive.

						-Hope this helps

						-Bill

P.S.  You have to have SCSI and SCSI disk support either built into your
      kernel or loaded as modules (I believe the modules are scsi_mod.o
      and sd.o but I'm not sure since I have the SCSI support built into
      the kernel).

P.P.S.  I'm using the 2.4.18-ben0 kernel (2.4.18 is a highly recommended
        kernel for firewire support at the moment).