Hard drive failure when running realtime kernel
I recently compiled a realtime patch onto a kernel, and when restarting into the new kernel, I seem to get read errors on my hard drive.
I have 1 SATA drive with no RAID, and I have been running 2.6.26 for months now will no hardware problems. However, after recompiling the kernel with the real time patch found in http://www.kernel.org/pub/linux/kernel/projects/rt/, my system freezes up completely within the first few minutes. On one instant, I got an error from X, saying that my file system was read-only. Here is the relevant info from dmesg: Code:
Oct 12 22:31:43 debian kernel: [ 405.369226] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) This would seem to be a hardware problem, however it has never happened in the regular kernel. The drive is a year and a half old, and is a Seagate Barracuda 7200.10 Is it possible that something in the realtime kernel is writing more frequently to the hard drive, which is them coming upon a bad sector? Any help or suggestions are appreciated. |
Instead of wasting time trying to figure out what is wrong I would just reinstall the whole things, save you time and headaches.
|
Not quite sure what reinstalling would help. I've tried recompiling many versions of the real time kernel, all with the same result.
|
This sequence
Code:
Oct 12 22:31:44 debian kernel: [ 405.748884] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) I have to ask; Is RT necessary for your application, or even advantageous? Wouldn't you be better off just not using RT? |
I'm working with midi, so real time is pretty much mandatory. Any ideas why the errors would only occur with the new kernel? I couldn't find any additions in the new .config that deal with SATA
|
Anyone have any ideas?
Possibly something related to the speed of input/output to the drive? |
All times are GMT -5. The time now is 02:21 AM. |