Bug 42914 - disk is offset 8 bytes on firewire
Summary: disk is offset 8 bytes on firewire
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: IEEE1394 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_ieee1394
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-12 22:28 UTC by Tormod Volden
Modified: 2012-03-12 23:35 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.2
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg including blkid triggering BUG (25.46 KB, text/plain)
2012-03-12 22:28 UTC, Tormod Volden 		Details
dmesg on 3.3-rc7 i386 (72.10 KB, text/plain)
2012-03-12 22:49 UTC, Tormod Volden 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Tormod Volden 2012-03-12 22:28:31 UTC 
Created attachment 72570 [details]
dmesg including blkid triggering BUG

I have an external drive with both USB and firewire. When using the firewire connection I can not mount the partitions (or identify them with blkid). I dd'ed the disk and partitions both via usb and via firewire and compared the results, and it seems like everything is shifted 8 bytes on firewire. If I use "blkid -p -O 8" I can successfully identify the partitions via firewire. I have tested this both on my PowerBook G4 (powerpc) and Acer TravelMate 8100 (i386).

Under MacOSX 10.4 both firewire and USB work fine.
Comment 1 Stefan Richter 2012-03-12 22:37:14 UTC 
You obviously have a PL3507 based disk enclosure, and the udev helper scsi_id triggers a firmware bug.  See thread "Unable to access firewire hard drive" at linux1394-user, http://marc.info/?t=132975440900001
Comment 2 Tormod Volden 2012-03-12 22:49:55 UTC 
Created attachment 72571 [details]
dmesg on 3.3-rc7 i386
Comment 3 Tormod Volden 2012-03-12 22:53:55 UTC 
Thanks! Disabling scsi_id worked.
Comment 4 Stefan Richter 2012-03-12 23:35:52 UTC 
OK, so it is indeed the same issue, and not a kernel problem.  But let's keep this ticket open as a reminder until I have a proposal for a fix (in udev rules or scsi_id or wherever).
Note You need to log in before you can comment on or make changes to this bug.