Due Kernel I/O error, system does not boot sometimes
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
gaurish@gaurish-desktop:~$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0a.0 Modem: PCTel Inc HSP56 MicroModem (rev 04)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6200] (rev a2)
:~$ sudo smartctl -a /dev/sda
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST380815AS
Serial Number: 6RA6TP00
Firmware Version: 3.AAD
User Capacity: 80,026,361,856 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Apr 21 22:58:26 2008 IST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 27) minutes.
SMART Error Log Version: 1
ATA Error Count: 276 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 276 occurred at disk power-on lifetime: 339 hours (14 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 24 0d 60 e0 Error: UNC at LBA = 0x00600d24 = 6294820
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 08 1f 0d 60 e0 00 00:25:54.949 READ DMA EXT
25 03 01 00 00 00 e0 00 00:25:54.948 READ DMA EXT
24 03 01 af f8 50 e0 00 00:25:54.947 READ SECTOR(S) EXT
c6 03 10 af f8 50 a0 00 00:25:54.946 SET MULTIPLE MODE
91 03 3f af f8 50 af 00 00:25:54.936 INITIALIZE DEVICE PARAMETERS [OBS-6]
Error 275 occurred at disk power-on lifetime: 339 hours (14 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 24 0d 60 e0 Error: UNC at LBA = 0x00600d24 = 6294820
Error 274 occurred at disk power-on lifetime: 339 hours (14 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 24 0d 60 e0 Error: UNC at LBA = 0x00600d24 = 6294820
Error 273 occurred at disk power-on lifetime: 339 hours (14 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 24 0d 60 e0 Error: UNC at LBA = 0x00600d24 = 6294820
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 0f 0d 60 e0 00 00:25:33.053 READ DMA EXT
24 03 01 af f8 50 e0 00 00:25:33.040 READ SECTOR(S) EXT
c6 03 10 af f8 50 a0 00 00:25:33.037 SET MULTIPLE MODE
91 03 3f af f8 50 af 00 00:25:33.027 INITIALIZE DEVICE PARAMETERS [OBS-6]
ef 03 0c af f8 50 a0 00 00:25:32.995 SET FEATURES [Set transfer mode]
Error 272 occurred at disk power-on lifetime: 339 hours (14 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 24 0d 60 e0 Error: UNC at LBA = 0x00600d24 = 6294820
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 0f 0d 60 e0 00 00:25:26.876 READ DMA EXT
24 03 01 af f8 50 e0 00 00:25:26.792 READ SECTOR(S) EXT
c6 03 10 af f8 50 a0 00 00:25:20.816 SET MULTIPLE MODE
91 03 3f af f8 50 af 00 00:25:20.816 INITIALIZE DEVICE PARAMETERS [OBS-6]
ef 03 0c af f8 50 a0 00 00:25:20.806 SET FEATURES [Set transfer mode]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 3 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
gaurish@gaurish-desktop:~$
I would suggest that you run a memory test first. You could use memtest86 to check the memory. If you have a KNOPPIX Livecd, it has the memtest86 you can run.
If the memory checks out then you could use the diagnostics for the HDD that is provided by the manufacture.
I had the exact same problem with a AMD64 3400+ Motherboard. Turned out that my memory timings were too tight. lengthened my CAS latency time. Been running now for a year
with no issues. Mayhap I lost a few nanoseconds here or there but have never really
noticed any slowness. I think AMD64's are quite intolerant of memory timing problems.
If you need the sights were I got info on changing BIOS memory settings, shoot me an email.
I dont at the moment remember them off hand. But they really helped me.
It also seemed I had a problem when the system was
cold. After warming up it would work fine even with the aggressive timings I had set,
Hardware is weird no ?
I had the exact same problem with a AMD64 3400+ Motherboard. Turned out that my memory timings were too tight. lengthened my CAS latency time. Been running now for a year
with no issues. Mayhap I lost a few nanoseconds here or there but have never really
noticed any slowness. I think AMD64's are quite intolerant of memory timing problems.
<snip>
Hardware is weird no ?
How do you come to the conclusion that the AMD64 are intolerant to memory timing problems?
Hardware is not weird if you have a understanding of it.
How do you come to the conclusion that the AMD64 are intolerant to memory timing problems?
Hardware is not weird if you have a understanding of it.
Hyper transport on AMD64 processors really stress the
chipsets. I have had 3 AMD64 motherboards that have
had problems of this nature. All from different
manufacturers. More conservative timings has always
been the key for for me . In particular CAS latency
timing. Some memory is advertised to do CAS-L of 2
clocks. Many dont seem to do it right. 3 or 4 and
I have no problems. I suppose you could go with more
expensive Dram but it's a simple thing to drop back
timing and see if you get stable operation of the
box. It wont hurt the CPU to go slower. I have no
trouble understanding the hardware, but I still think
it can be wierd at times.
I guess I'm spoiled. I tend to match the hardware so as not too create a problem. Sure it costs more but you do get what you pay for. Thus you get what you expect for your specifications.
I really don't OC that much anymore because I can buy what I want. Don't get me wrong, I don't throw good money away. I make sure that the hardware I want meets my specifications therefore the systems are around for awhile. I didn't jump on the 64 bit bandwagon because there were a lot of problems at first. I've always relied on certain manufactures for my MBs and memory. I still use AMD over Intel because of the $ verse the performance.
As for sub-sytems, the commercial market(s) are fairly equal for performance dollars.
I guess I'm spoiled. I tend to match the hardware so as not too create a problem. Sure it costs more but you do get what you pay for. Thus you get what you expect for your specifications.
I really don't OC that much anymore because I can buy what I want. Don't get me wrong, I don't throw good money away. I make sure that the hardware I want meets my specifications therefore the systems are around for awhile. I didn't jump on the 64 bit bandwagon because there were a lot of problems at first. I've always relied on certain manufactures for my MBs and memory. I still use AMD over Intel because of the $ verse the performance.
As for sub-sytems, the commercial market(s) are fairly equal for performance dollars.
---
I have no argument to your statement. If I am putting a network
access control system or file server, I don't muck around being
cheap. However a box for me to monkey with as a hobby, does not
have to be top notch. I dont think there will be a major deal
if the Kids cant get to the net for a day because the Linux
router box is down. Hell if it catches on fire, I just get
another one. Computers these days are pretty affordable.
Especially if you put them together yourself. Again it's
just a hobby for me. At work, things are quite a bit different.
Producing a unreliable system can invite a boot to your rear.
So I do understand the difference between Hobby stuff and
real mission critical systems. I just am crazy enough to like
to mess with the hardware. I gravitate to AMD for the reasons
you state along with the reason that they run cooler than the
Intel chips. Less fan noise needed .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.