https://bugzilla.novell.com/show_bug.cgi?id=682779 https://bugzilla.novell.com/show_bug.cgi?id=682779#c0 Summary: IEEE 1394b harddisk offlines unexpectedly Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: TLingk@vdsvossk.de QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=421491) --> (http://bugzilla.novell.com/attachment.cgi?id=421491) Kernel messages reporting the drive offlined User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 I have a Western Digital WDH1Q10000E MyBook Studio eSATA/USB/FireW harddisk connected to my machine using the drive's IEEE 1394b port and a IEEE1394b firewire adapter. The disk is of 1TB size and there is one ext3 partition on it. I put the drive into /etc/fstab, so it gets mounted automatically on boot which in principle seems to work. But if I open KDE's System Workspace, the whole machine locks up. Only a hard reset recovers from this state. After reboot, I found some spurious messages in the kernel log, saying, that some sectors could not be read. I supposed a corrupted file system causing this error, so I removed the fstab entry, and rebooted so the disk remains unmounted. Then I executed e2fsck on the first partition of the drive to check it for errors. After a while, e2fsck aborted with an error. I realized, that the disk was not accessible any more at all. The device node /dev/sdh was still present and also KDE did not detect a drive removal. Nevertheless, all accesses to the drive fail. I tried fdisk /dev/sdh, but fdisk exits with an error. Switching the drive off and on again does not change anything. Only rebooting the whole system makes it accessible again. I found some error messages in the kernel log, saying that the drive offlined. I'll append them to this report. I didn't see this behaviour on OpenSuse 11.0 so I'm rather sure that this is not caused by a hardware defect. Reproducible: Always Steps to Reproduce: 1. Connect IEEE1394b disk to machine 2. Execute e2fsck to the first ext3 partition Actual Results: e2fsck aborts with an error message, the drive is not accessible any more Expected Results: e2fsck should complete successfully and the disk should remain accessible -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.