Unable to access firewire hard drive
Brought to you by:
aeb,
bencollins
From: Peter C. <ch...@at...> - 2012-02-20 16:11:31
|
System: Slackware64-13.37 Kernel: 3.2.2 Libraw1394 2.0.7 # lspci | grep FireWire 01:06.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 04) # lsmod | grep firewire firewire_sbp2 10977 0 firewire_ohci 26284 0 firewire_core 41461 2 firewire_sbp2,firewire_ohci crc_itu_t 1185 2 udf,firewire_core #dmesg firewire_core: created device fw1: GUID 0050770e00071002, S400, 3 config ROM retries firewire_core: phy config: card 0, new root=ffc0, gap_count=5 scsi5 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.0: 0x20 (firmware_revision 0x012804, model_id 0x000001) firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries) scsi 5:0:0:0: Direct-Access-RBC ST316002 2ACE PQ: 0 ANSI: 4 sd 5:0:0:0: Attached scsi generic sg4 type 14 sd 5:0:0:0: [sdd] 312558593 512-byte logical blocks: (160 GB/149 GiB) sd 5:0:0:0: [sdd] Write Protect is off sd 5:0:0:0: [sdd] Mode Sense: 11 00 00 00 sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdd: sdd1 sd 5:0:0:0: [sdd] Attached SCSI disk The device is a hard drive caddy with both USB and FireWire ports, and contains an NTFS formatted drive. Under Windoze, the drive functions perfectly as either USB or FireWire (ie this is not a hardware fault!) Under Slackware, when connected as USB, the drive is immediately recognised, and a prompt appears on the desktop asking if I want to mount it. If I accept, it is mounted as /media/Video (the partition label). If I connect it as Firewire, although the kernel appears to recognise it (see demsg above), no prompt to mount it appears. Attempting to mount it manually creates an eror message saying it can't identify the filing system. Specifying ntfs-3g produces a "wrong super-block" error. Examining the disk with GParted indicates that the disk contains only "unallocated" space, when attached via FireWire! In other words, although the disk works fine under Windows, and under Linux as USB, it doesn't work under FireWire, as the system is unable to identify the partition, although it knows it exists! I haven't used this caddy for a while, but it used to work perfectly under the old FireWire stack. (I was unaware that there was a new stack until I started trying to debug this problem!) I am not a programmer, though I would claim to be "computer literate". This may be an error on my part, but if so it is not obvious to me. Googling for solutions to this issue has produced a number of hits for Ubuntu users with the same problem, but no apparent solution! Is anyone here able to offer advice or enlightenment, please? Cheers, -- Pete ch...@at... |