YDL 2.3 and Ext FW Drive

Scott Burch yellowdog-newbie@lists.terrasoftsolutions.com
Fri, 28 Feb 2003 16:02:43 +0000


I solved my problem. I was reading the HOW-TO in YDL support about Firewire:

<http://www.yellowdoglinux.com/support/solutions/ydl_general/firewire_disks.shtml>

and the author left out the section about rescanning the SCSI bus to 
find a new drive. All I needed to do was rescan the bus. I did it with 
this utility:

<http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh>

After download, I ran it as root  and found that it would not only 
rescan the SCSI bus, but also add the Firewire drive as a device. That's 
what I needed. I created a mount point by creating a directory, and 
followed the rest of the instructions in the  HOW-TO.

thanks  ##  scott


Scott Burch wrote:

> I read Jeroen's great note about mounting a Firewire drive, but I have 
> a problem: I cannot see the drive or its partition table using pdisk; 
> but I can see the other two SCSI drives I am using. I am using an IBM 
> 15GB DTLA-series drive in an external Coolmax Firewire enclosure. It 
> partitioned fine under Mac OS9 using FWB's Hard Disk Tools -- a story 
> about that follows -- and I created a Mac 1GB partition  and a 10 GB 
> Apple_Unix_SVR2 partition . I reproduced the dmesg below so you can 
> see the results. I plugged and unplugged the device and you can see 
> that in the notes.
>
> Another question: I set the jumpers on the IDE drive to slave under a 
> "16 head" configuration. Is that correct?
>
> The FWB story: when I first booted the Firewire drive, the OS 9 on the 
> 9500 I am using wanted to initialize the drive. I elected to do that 
> -- I should selected "eject" -- and was stuck with a 2 GB partition 
> that I could not remove with Hard Disk Tools [HDT] v.4, Apple's Drive 
> Set-up, or even Atto Express RAID. HDT has a utility called Firewire 
> Loader that was supposed to blow away the stock Apple driver and 
> replace it with an FWB driver. It would not. I wrote a note to the 
> tech support at FWB. They replied later that same day -- a very cool 
> tech guy! -- by sending v.4.5 of Firewire Loader. It replaced the 
> Apple driver and the drive behaves the way it should.
>
> Hardware notes: Mac 9500, 300 MB RAM, YDL 2.3., Macally PCI Firewire 
> card in the uppermost slot, two internal SCSI drives that report as 
> /dev/sda and /dev/sdb.  The root folder is on /dev/sdb [4 GB Seagate]  
> and /dev/sda [ 350 MB Quantum] strictly holds only Mac OS 9 for booting.
>
> thanks  ##  scott
>
> ----------------------------
> ohci1394: $Revision: 1.101 $ Ben Collins <bcollins@debian.org>
> ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[23]  MMIO=[80800000-80800800]  
> Max Packet=[2048]
> scsi3 : 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
> ohci1394_0: Received OHCI evt_* error 0x3
> ieee1394: Host added: Node[01:1023]  GUID[0000000000007657]  [Linux 
> OHCI-1394]
> ieee1394: Node 01:1023 changed to 00:1023
> ohci1394_0: Error in reception of SelfID packets 
> [0x80030004/0x00039d6d] (count: 0)
> 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[00000000000007b2]  [Oxford 
> Semiconductor Lt
> d.   ]
> ieee1394: Device removed: Node[01:1023]  GUID[00000000000007b2]  
> [Oxford Semiconductor
> Ltd.   ]
> ieee1394: sbp2: Logged out of SBP-2 device
> ohci1394_0: Error in reception of SelfID packets 
> [0x80080004/0x00089528] (count: 0)
> 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[00000000000007b2]  [Oxford 
> Semiconductor Lt
> d.   ]
> [END]
>
> Jeroen Diederen wrote:
>
>> look if the firewire HD is recognised, if not try unplugging and 
>> plugging and do a dmesg again
>>
>> then, and only if it showed up:
>>
>> modprobe sbp2
>>
>
>
> _______________________________________________
> yellowdog-newbie mailing list
> yellowdog-newbie@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie
>