Re: Problems with external HD

On Tuesday 10 February 2004 21:31, Stefan Richter wrote:
> On 10 Feb, Alexej Davidov wrote:
> > I know about the scsi issue. But the ieee device itself is not
> > recognised, ie. does not show up in /proc/bus/ieee1394/devices. So I
> > don't even bother, yet, about sbp2.
> >
> > If I use gscanbus-0.7.1 and I plug in the HD, it says on stderr:
> > Error while reading from IEEE1394: : Unknown error 57005
> > 0/0x0000fffff0000400: read failed
> > 0/0x0000fffff0000400: wrong bus info block length
> >
> > This message is printed multiple times. The device is then shown as "S400
> > Unknown". The same message is printed if I try to do a bus reset with
> > gscanbus. No output is done to syslog when plugging/unplugging the
> > device.
>
> There seem to be problems specifically with this device (Prolofic
> PL3507) that show up as slightly different symptoms on different
> configurations:
> http://marc.theaimsgroup.com/?l=linux1394-user&m=107357814731517&w=2
> http://marc.theaimsgroup.com/?l=linux1394-user&m=107581288704098&w=2
>
> What is the content of /proc/bus/ieee1394/devices when the drive
> is *not* recognized as an SBP-2 capable device?
>
> What is shown in the "SelfID info" in gscanbus when the drive is
> not recognized, and what when it is recognized? (Left-click on
> the device symbol.)

It is not just not recognised as an sbp2 device, it is not recognised at all.
I.e., nothing shows up for that device in /proc/bus/ieee1394/devices.

For gscanbus, it shows an "Unknown" device in that case. As I can't reproduce
that case right now, I can't say for sure, what it says for SelfID info.
Although, if I remember right, it just shows 0s for all of the fields.

But now, I get more and more the impression, that the device really needs the
additional power supply through either USB or Firewire, even if the external
power supply is attached. Although it behaves really strange:

I've just unplugged the USB cable (which is, I suspect, needed as power
supply, as I'm using a 4 pin Firewire cable) and then did a modprobe
ohci1394. Strange enough, it worked this time, the device was recognised and
sbp2 autoloaded. Then I did "rescan-scsi-bus.sh" wich hung. As soon as I've
plugged in the USB cable again, it continued. Than I did a "cat <file> >/dev/
null" for a file on the Firewire device. As soon as I unplug the USB cable,
it stops. If I replug it, it continues.

After that I did "rmmod sbp2" and unplugged the USB cable again. gscanbus
still shows the device correctly as "Prolifio PL3507 Combo Device". If I do a
bus reset with gscanbus, this works and sbp2 is autoloaded again. But a mount
of the external drive hangs, until I plug in the USB cable again.

Btw.: I'm sure, I'm always using the ieee1394 device, and not the USB device,
by accident.

I hope this description was not too confusing, but it is really confusing for
me as well, as I havent worked out yet, under wich conditions exactly what
error occurs.

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user
Received on Wed Feb 11 02:27:05 2004