Re: lacie BIGGEST FW800 - SUCCESS!!
Brought to you by:
aeb,
bencollins
|
From: Hugh D. <hu...@zo...> - 2005-07-26 13:19:26
|
Well..!! I feel a bit dumb for not trying this earlier .. Swtiched the Lacie Biggest box off (much bleeping ensued), switched it back on and let it settle. Result: Detected successfully....! This was prompted by the fact that it wasn't being recognised at all via USB either, whereas that was definitely working before (though it was giving a range of horrible errors if I tried to actually mount a partition). I have grabbed a huge stack of dmesg output (the ieee1394/ohci1394 module was compiled with full-verbosity, since switched back off). Key bits: ieee1394 disable_irm=1 appears to be an absolute requirement. noteably it's showing both the nonsense GUID and a 'real' one. this is in a 33Mhz/32bit PCI slot - any suggestions on what to use to test the data transfer rates in the current setup? here's the "transcript" - # = my commandline, > = dmesg output (this is all after I recompiled ieee1394 support without the full-verbosity option - Stefan would you like me to send you the more verbose output? #modprobe ieee1394 (plain) > ieee1394: Initialized config rom entry `ip1394' > ohci1394: $Rev: 1313 $ Ben Collins <bco...@de...> > ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 9 (level, low) -> IRQ > 9 > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[9] MMIO=[fe1ff800-fe1fffff] Max > Packet=[4096] > ieee1394: Host added: ID:BUS[0-00:1023] GUID[55aa55aa55aa55aa] > ieee1394: Node added: ID:BUS[0-01:1023] GUID[00d04b5609081e85] > ieee1394: The root node is not cycle master capable; selecting a new root node a > nd resetting... > ieee1394: Node changed: 0-01:1023 -> 0-00:1023 > ieee1394: Node changed: 0-00:1023 -> 0-01:1023 #modprobe -r sbp2, ohci1394,ieee1394 > ieee1394: Node removed: ID:BUS[0-01:1023] GUID[55aa55aa55aa55aa] > ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00d04b5609081e85] #modprobe ieee1394 disable_irm=1 > ieee1394: Initialized config rom entry `ip1394' > ieee1394: IRM functionality disabled #modprobe ohci1394 > ohci1394: $Rev: 1313 $ Ben Collins <bco...@de...> > ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 9 (level, low) -> IRQ > 9 > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[9] MMIO=[fe1ff800-fe1fffff] Max > Packet=[4096] > ieee1394: Host added: ID:BUS[0-00:1023] GUID[55aa55aa55aa55aa] > ieee1394: Node added: ID:BUS[0-01:1023] GUID[00d04b5609081e85] > sbp2: $Rev: 1316 $ Ben Collins <bco...@de...> > scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices > ieee1394: sbp2: Logged into SBP-2 device > ieee1394: Node 0-01:1023: Max speed [S800] - Max payload [4096] > Vendor: LaCie Model: Biggest F800 Rev: 1.32 > Type: Direct-Access ANSI SCSI revision: 06 > SCSI device sda: 976790016 512-byte hdwr sectors (500116 MB) > sda: asking for cache data failed > sda: assuming drive cache: write through > SCSI device sda: 976790016 512-byte hdwr sectors (500116 MB) > sda: asking for cache data failed > sda: assuming drive cache: write through > sda: sda1 sda2 sda3 > Attached scsi disk sda at scsi1, channel 0, id 0, lun 0 > Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0 Bingo! - partitions mounted, rsyncing across from the main server now. H It all makes a bit more sense now, as I had to power the disks down before I could try them in the various other platforms that I reported successul detection from!! Question to ask is whether Lacie should really be able to fix whatever freeze-up is happening I suppose? |