Re: lacie BIGGEST FW800

[Stefan R. <st...@s5...>]

Hugh Dixon wrote:
> Thing is, under OSX or Windows, it doesn't show as much besides an 
> "Texas Instruments OHCI compliant ieee1394 Controller" (or words to that 
> effect - didn't install anything Lacie-specific at all).

If you have the OS X or Windows box with the LaCie card and a Linux box 
with another FireWire card in the same room, you could hook them 
together via FireWire and look up the LaCie card's GUID in Linux' sysfs. 
But...

> I'll have a go when I'm back in the office - have just compiled and 
> installed 2.6.13-rc3 to try ... and indeed, no joy.  I did notice that 
> it seemed to report 2 GUID's yesterday - will look in output again. One 
> that nonsensey 55aa55aa55aa55aa and one more "random/genuine" semingly 
> reported by "the other host" (0-00:1023 vs 0-01:1023) - can't find it 
> now.  grrr.

...if you find it in an old log, the simpler. *However*, the only thing 
we learn from this is that the LaCie card is indeed not correctly set up 
under Linux (if it can have a proper GUID under the other OSs). What we 
still don't know is if this is actually the source of the problems to 
talk to the disk (I tend to blame the card indeed). And more 
importantly, we still don't learn how to cure that.

OK, there _is_ a quite simple cure with a certain chance for success: 
Replace the card by a different one, preferably one that someone else 
reported working under Linux.

> Maybe I'll just hang the RAID box of OSX and set up rsync and samba and 
> the like as I currently have the old setup under linux ...

Seems to be an even better solution, since that OS is supported by LaCie.
-- 
Stefan Richter
-=====-=-=-= -=== =-==-
http://arcgraph.de/sr/