Flaky firewire disks Fail Feisty but Do Dapper
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have an external Firewire/USB enclosure -- a MacAlly PHR-100AC enclosure containing a Maxtor DiamondMax Plus 9 200GB ATA/133 HDD. I have it formatted with three ext3 partitions (two large, and one small).
I copied my working data from my old PowerBook G3 Series (Wallstreet II/PDQ) running Dapper to this drive, then mounted it on an eMonster 550r running Feisty. This worked OK, though I would occasionally notice the FireWire drive wouldn't mount on the first try and I would have to power it down or log out and in before it would come up. I should have taken this as a warning!
This morning it didn't come up at all, and I examined dmesg and notice (among other error messages) it was complaining the drive had been mounted more than some number of times (50?) without a fsck. Like an idiot, I decided to run fsck manually, and of course it found some problems and corrected them. (Unfortunately I didn't keep the log of its corrections.)
After running fsck, the drive mounted in Feisty, but lots of data was missing and the logs were filling with all sorts of dire error messages. I tried various things but could not copy any of the data from the drive without encountering file errors.
For some reason I moved the drive back to the PowerBook and discovered the Dapper can read the drive perfectly. So I copied the data over the network to a new firewire drive on the Feisty box. I'm going to gather some of the relevant data and add that to this report, but I have to go at the moment....
information from Feisty system where firewire drive fails after being plugged in:
twt@emonster:~$ uname -a CRON[17508] : (root) CMD ( cd / && run-parts --report /etc/cron.hourly) 00080c]
Linux emonster 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
twt@emonster:~$ lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:0b.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
00:10.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
00:12.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:12.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:12.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:12.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)
00:12.4 FireWire (IEEE 1394): ALi Corporation M5253 P1394 OHCI 1.1 Controller
01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15)
twt@emonster:~$ tail -30 /var/log/syslog
Aug 23 20:49:09 emonster -- MARK --
Aug 23 21:09:09 emonster -- MARK --
Aug 23 21:17:01 emonster /USR/SBIN/
Aug 23 21:29:09 emonster -- MARK --
Aug 23 21:41:05 emonster kernel: [19979.040000] ieee1394: Error parsing configrom for node 0-00:1023
Aug 23 21:41:05 emonster kernel: [19979.040000] ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Aug 23 21:41:05 emonster kernel: [19979.040000] ieee1394: Node changed: 0-01:1023 -> 0-02:1023
Aug 23 21:41:05 emonster kernel: [19979.048000] ieee1394: sbp2: Reconnected to SBP-2 device
Aug 23 21:41:05 emonster kernel: [19979.048000] ieee1394: sbp2: Node 0-01:1023: Max speed [S400] - Max payload [2048]
Aug 23 21:41:19 emonster kernel: [19992.760000] ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[0010100540
Aug 23 21:41:19 emonster kernel: [19992.768000] ieee1394: sbp2: Reconnected to SBP-2 device
Aug 23 21:41:19 emonster kernel: [19992.768000] ieee1394: sbp2: Node 0-01:1023: Max speed [S400] - Max payload [2048]
Aug 23 21:41:19 emonster kernel: [19992.768000] scsi6 : SBP-2 IEEE-1394
Aug 23 21:41:19 emonster kernel: [19992.768000] ieee1394: sbp2: Workarounds for node 0-00:1023: 0x2 (firmware_revision 0x000265, vendor_id 0x001010, model_id 0x000201)
Aug 23 21:41:20 emonster kernel: [19993.772000] ieee1394: sbp2: Logged into SBP-2 device
Aug 23 21:41:20 emonster kernel: [19993.772000] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Aug 23 21:41:26 emonster kernel: [19999.272000] ieee1394: sbp2: aborting sbp2 command
Aug 23 21:41:26 emonster kernel: [19999.272000] scsi 6:0:0:0:
Aug 23 21:41:26 emonster kernel: [19999.272000] command: Inquiry: 12 00 00 00 24 00
Aug 23 21:41:36 emonster kernel: [20009.272000] ieee1394: sbp2: aborting sbp2 command
Aug 23 21:41:36 emonster kernel: [20009.27...