GekkoGeck0 Posted November 23, 2009 Report Share Posted November 23, 2009 I just built a new system and have been using Mandriva (2009.1 Spring 64-bit) on it for about two or three months. About a month ago I started getting I/O errors across the board. I immediately rebooted into Windows and checked the drive. No problems with it and I spent the next week in Windows because I didn't have the time to go back and diagnose the issue in Linux. It seems to happen over time or whenever I'm doing intense downloading with BitTorrent. I can't shut down the system from within KDE when they happen and reboots result in having to run fsck manually (Inodes that were part of a corrupted orphan were found). I can't use the system when the I/O errors start appearing, either. I have no problems whatsoever with the drives in Windows and checking the system logs within Windows reveal no errors. Here's what I'm seeing within the logs in Linux: Oct 5 13:36:58 localhost klogd: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 5 13:36:58 localhost klogd: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Oct 5 13:36:58 localhost klogd: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 5 13:36:58 localhost klogd: ata2.00: status: { DRDY } Oct 5 13:36:58 localhost klogd: ata2.00: hard resetting link Oct 5 13:36:58 localhost klogd: ata2.01: hard resetting link Oct 5 13:37:04 localhost klogd: ata2.00: link is slow to respond, please be patient (ready=0) Oct 5 13:37:08 localhost klogd: ata2.00: SRST failed (errno=-16) Oct 5 13:37:08 localhost klogd: ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 5 13:37:08 localhost klogd: ata2.01: SATA link down (SStatus 0 SControl 300) Oct 5 13:37:08 localhost klogd: ata2.00: link online but device misclassified, retrying Oct 5 13:37:08 localhost klogd: ata2.00: hard resetting link Oct 5 13:37:08 localhost klogd: ata2.01: hard resetting link Oct 5 13:37:14 localhost klogd: ata2.00: link is slow to respond, please be patient (ready=0) Oct 5 13:37:18 localhost klogd: ata2.00: SRST failed (errno=-16) Oct 5 13:37:18 localhost klogd: ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 5 13:37:18 localhost klogd: ata2.01: SATA link down (SStatus 0 SControl 300) Oct 5 13:37:18 localhost klogd: ata2.00: link online but device misclassified, retrying Oct 5 13:37:18 localhost klogd: ata2.00: hard resetting link Oct 5 13:37:18 localhost klogd: ata2.01: hard resetting link Oct 5 13:37:24 localhost klogd: ata2.00: link is slow to respond, please be patient (ready=0) Oct 5 13:37:30 localhost klogd: npviewer.bin[13854]: segfault at f6a45470 ip 00000000f6a45470 sp 00000000e9e1803c error 14 Oct 5 13:37:53 localhost klogd: ata2.00: SRST failed (errno=-16) Oct 5 13:37:53 localhost klogd: ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 5 13:37:53 localhost klogd: ata2.01: SATA link down (SStatus 0 SControl 300) Oct 5 13:37:53 localhost klogd: ata2.00: link online but device misclassified, retrying Oct 5 13:37:53 localhost klogd: ata2.00: limiting SATA link speed to 1.5 Gbps Oct 5 13:37:53 localhost klogd: ata2.01: limiting SATA link speed to 1.5 Gbps Oct 5 13:37:53 localhost klogd: ata2.00: hard resetting link Oct 5 13:37:53 localhost klogd: ata2.01: hard resetting link Oct 5 13:37:58 localhost klogd: ata2.00: SRST failed (errno=-16) Oct 5 13:37:58 localhost klogd: ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 5 13:37:58 localhost klogd: ata2.01: SATA link down (SStatus 0 SControl 310) Oct 5 13:37:58 localhost klogd: ata2.00: link online but device misclassified, device detection might fail Oct 5 13:37:59 localhost klogd: ata2.00: revalidation failed (errno=-2) Oct 5 13:38:03 localhost klogd: ata2.00: hard resetting link Oct 5 13:38:03 localhost klogd: ata2.01: hard resetting link Oct 5 13:38:04 localhost klogd: ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 5 13:38:04 localhost klogd: ata2.01: SATA link down (SStatus 0 SControl 310) Oct 5 13:38:04 localhost klogd: ata2.00: configured for UDMA/133 Oct 5 13:38:04 localhost klogd: ata2: EH complete Oct 5 13:38:04 localhost klogd: sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) Oct 5 13:38:04 localhost klogd: end_request: I/O error, dev sdb, sector 17247991 Oct 5 13:38:04 localhost klogd: Aborting journal on device sdb1:8. Oct 5 13:38:04 localhost klogd: sd 1:0:0:0: [sdb] Write Protect is off Oct 5 13:38:04 localhost klogd: ext4_abort called. Oct 5 13:38:04 localhost klogd: EXT4-fs error (device sdb1): ext4_journal_start_sb: Detected aborted journal Oct 5 13:38:04 localhost klogd: Remounting filesystem read-only Oct 5 13:38:04 localhost klogd: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 5 13:38:04 localhost klogd: journal commit I/O error Here's my fstab: # Entry for /dev/sda5 : UUID=b4d5c598-4cb1-4555-be9d-869cf0da9a78 / ext4 relatime 1 1 # Entry for /dev/sdb1 : UUID=28e1570a-c15a-4cc3-ace4-60271d9299af /home ext4 relatime 1 2 /dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 # Entry for /dev/sda1 : UUID=3ED03D08D03CC843 /mnt/win_c ntfs-3g defaults,umask=000 0 0 # Entry for /dev/sdb5 : UUID=94F00622F0060B66 /mnt/win_c2 ntfs-3g defaults,umask=000 0 0 # Entry for /dev/sdc1 : UUID=1234-5678 /mnt/win_c3 vfat umask=000,iocharset=utf8 0 0 none /proc proc defaults 0 0 # Entry for /dev/sda6 : UUID=b0ca92e5-68d6-4330-9fa0-f1668b17fe1e swap swap defaults 0 0 Any ideas on how to stop this from occurring? Quote Link to comment Share on other sites More sharing options...
tux99 Posted November 24, 2009 Report Share Posted November 24, 2009 (edited) Can you post the output of 'lspci' (run as root in a terminal) so we can see the type of Sata controller you have? Also it could be worth running a disk surface check to see if it is a disk problem, it could well be that there are defective sectors on the Linux partition but not on the Windows partition (yet). To do that boot off a bootable Linux CD (for example Mandriva One) and run this command in a terminal: badblocks -sv /dev/sdX (replace X with the sd device letter, it should be 'b' but double-check first with 'fdisk -l' as it might be different when booting off CD) Edited November 24, 2009 by tux99 Quote Link to comment Share on other sites More sharing options...
GekkoGeck0 Posted November 24, 2009 Author Report Share Posted November 24, 2009 Output of lspci: 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1 00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 5 00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 6 00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller 00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller 01:00.0 VGA compatible controller: nVidia Corporation GT200 [GTX260-216] (rev a1) 02:00.0 Ethernet controller: Attansic Technology Corp. L1e Gigabit Ethernet Adapter (rev b0) 03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b2) 05:03.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) I was going to run SpinRite on the drive but hadn't yet. I'll run badblocks tomorrow. Quote Link to comment Share on other sites More sharing options...
tux99 Posted November 24, 2009 Report Share Posted November 24, 2009 I see you have 2 physical disk controller chips, do you know to which one sdb is connected? 00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller 00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller (these two should be both part of the same physical chip, the Intel ICH10 southbridge, first one is probably 4 sata ports while the second one is the IDE connector) 03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b2) (this should be a separate chip that provides you with additional sata ports) Quote Link to comment Share on other sites More sharing options...
scarecrow Posted November 24, 2009 Report Share Posted November 24, 2009 The ext4 filesystem had massive issues on the 2.6.29.x series kernels. I would upgrade the kernel to 2.6.30 series, at least. You can get 2.6.31 for 2009.1 from the backports official repo. Quote Link to comment Share on other sites More sharing options...
tux99 Posted November 24, 2009 Report Share Posted November 24, 2009 The ext4 filesystem had massive issues on the 2.6.29.x series kernels. I would upgrade the kernel to 2.6.30 series, at least. You can get 2.6.31 for 2009.1 from the backports official repo. While that might well be the case, the errors shown in this case are clearly not filesystem errors, they are either controller (or driver) errors, or physical disk errors. Quote Link to comment Share on other sites More sharing options...
scarecrow Posted November 25, 2009 Report Share Posted November 25, 2009 (edited) There used to be problems with that particular controller, but AFAIK they were fixed quite some time ago (since 2.6.24.1). On the other hand, I don't have used that hardware, but I did experience some horror stories with ext4 and 2.6.28/29. And, 2.6.31 will certainly fix the ext4 issues, and (hopefully) any outstanding issue with the sata driver. Edited November 25, 2009 by scarecrow Quote Link to comment Share on other sites More sharing options...
GekkoGeck0 Posted November 30, 2009 Author Report Share Posted November 30, 2009 The SATA drives are all on the 4 port controller, if I remember correctly. The Marvell one deals with my IDE DVD/CD-ROM drives and is a non-issue. I'll try the kernel upgrade and see if that fixes the issue. If it doesn't, I'll have to stop using Linux until I find a solution. :( Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.