Using a Firewire HD with YDL 3.0.1

[Rich Simpson]

thanks, I can see my drive in dmesg now.
Can I mount an hfs+ or ufs partition on my firewire drive? or do I need 
to do something else to read my data on my mac partitions?


On Dec 15, 2003, at 10:38 AM, 
yellowdog-general-request@lists.terrasoftsolutions.com wrote:

> Message: 3
> Date: Mon, 15 Dec 2003 16:52:26 +1100
> From: Stephen.Harker@spme.monash.edu.au
> Subject: Re: Using a Firewire HD with YDL 3.0.1
> To: yellowdog-general@lists.terrasoftsolutions.com
> Reply-To: yellowdog-general@lists.terrasoftsolutions.com
>
> On Sun, Dec 14, 2003 at 08:26:11PM -0800, Rich Simpson wrote:
>> I tried to make my firewire drive work with YDL I loaded the ohci1394
>> and sbp2 modules as stated in the faq, now I can not find which device
>> my drive is assinged to
>>
>> plist -l /dev/sda give the following output
>>
>> pdisk: can't open file '/dev/sda' (no such device or address)
>>
>> I tried all the devices that I thought it could be, to no avail, where
>> should I look next?
>
> Your problem is that, with a 2.4 kernel, the change of the devices in
> the SCSI bus due to hotplugging of firewire (and to a lesser extent
> USB) devices is not well handled.  In effect you need to get the SCSI
> device list rescanned using rescan-scsi-bus.sh a shell script
> available from
>
>           http://www.garloff.de/kurt/linux/scsidev/
>
> or other locations.  There are a number of posts in the archive that
> discuss this which you can find with a google search.  However, to
> illustrate:
>
> If I plug in a firewire drive then dmesg shows something like:
>
> scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices
> blk: queue d69fea14, I/O limit 4095Mb (mask 0xffffffff)
> ieee1394: sbp2: Logged into SBP-2 device
> ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
> ieee1394: Node added: ID:BUS[0-00:1023]  GUID[0030e000000002f0]
>
> but I have no SCSI device in the list:
>
> [~] cat /proc/scsi/scsi
> Attached devices: none
>
> Now if I run the rescan-scsi-bus.sh script then:
>
> [~] sudo sh ~/bin/rescan-scsi-bus.sh
> Password:
> Host adapter 0 (ide-scsi) found.
> Host adapter 1 (sbp2_0) found.
> Scanning for device 1 0 0 0 ...
> NEW: Host: scsi1 Channel: 00 Id: 00 Lun: 00
>       Vendor: IC25N030 Model: ATCS04-0         Rev:
>       Type:   Direct-Access                    ANSI SCSI revision: 06
> 1 new device(s) found.
> 0 device(s) removed.
>
> and
>
> [~] cat /proc/scsi/scsi
> Attached devices:
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
>   Vendor: IC25N030 Model: ATCS04-0         Rev:
>   Type:   Direct-Access                    ANSI SCSI revision: 06
>
> while dmesg now gives:
>
>   Vendor: IC25N030  Model: ATCS04-0          Rev:
>   Type:   Direct-Access                      ANSI SCSI revision: 06
> blk: queue c9cf5e14, I/O limit 4095Mb (mask 0xffffffff)
> Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
> SCSI device sda: 58605120 512-byte hdwr sectors (30006 MB)
>  sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
>
> So I can mount the device at /dev/sda or use pdisk to examine the
> device.  For my drive the command `sudo mount -t ext3 /dev/sda10 
> /mnt/fw'
> will mount the linux partition to the mount point /mnt/fw which I
> created for this purpose.
>
> I understand that this process won't be required with the 2.6 series
> kernel when they are released.
>
> -- 
> Stephen Harker                           
> Stephen.Harker@spme.monash.edu.au
> School of Physics & Materials Engineering
> Monash University                       
> http://www.ph.adfa.edu.au/s-harker/
>                                  Baloney Baffles brains: Eric Frank 
> Russell