| View previous topic :: View next topic |
| Author |
Message |
Lowyn
n00b
Joined: 07 Jan 2006
Posts: 6
|
 Posted: Sat Jan 07, 2006 8:27 pm Post subject: [Suspend-to-Ram] HD errors after wake up |
 |
|
Hello,
Whenever i try to wake up from suspend to ram from my laptop, i get a bunch of these messages on my logs. After that, my partitions are not reachable anymore, and i have to reboot, the hard way.
| Code: | hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=113795039, sector=113795039
ide: failed opcode was: unknown
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=113795039, sector=113795039
ide: failed opcode was: unknown
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=113795039, sector=113795039
ide: failed opcode was: unknown
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=113795039, sector=113795039
ide: failed opcode was: unknown
ide0: reset: success
hda: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=113795039, sector=113795039
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 113795039
|
I don't think it is a HD weakness as i never, ever, get any hda error when i do anything else on my laptop. Furthermore, i've checked every sector without problem with the tools provided by the laptop manufacturer. And sleep under WinXP wakes up cleanly. I must admint i am quite puzzled here.
I suppose this is somehow connected, so i add what i've got during boot up process. Needless to say, i already booted on gentoo install disk to ext3.efsck'ed (sp ?) every partition and their friends with no luck.
| Code: | EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
|
So, if anyone here has an idea, please let me know. Btw, suspend to ram used to work on this laptop, not so long ago. I must have done something terribly wrong *shivers*.
Lowyn. |
|
| Back to top |
|
 |
Lowyn
n00b
Joined: 07 Jan 2006
Posts: 6
|
| Posted: Sun Jan 08, 2006 4:58 pm Post subject: [HD] Failure after wake up fom S3 |
|
|
Btw, my kernel is 2.6.14-suspend2-r7, if it may help.
Bumping.
L. |
|
| Back to top |
|
|
toralf
Developer
Joined: 01 Feb 2004
Posts: 3942
Location: Hamburg
|
| Posted: Sun Jan 08, 2006 5:05 pm Post subject: |
|
|
| Code: | | $> zgrep IDEDISK_MULTI_MODE /proc/config.gz |
? |
|
| Back to top |
|
|
Lowyn
n00b
Joined: 07 Jan 2006
Posts: 6
|
| Posted: Sun Jan 08, 2006 5:29 pm Post subject: |
|
|
CONFIG_IDEDISK_MULTI_MODE=y
I remember having enabled this option in kernel config a while ago, "just in case" bit it changed nothing =/
L. |
|
| Back to top |
|
|
Lowyn
n00b
Joined: 07 Jan 2006
Posts: 6
|
| Posted: Thu Jan 12, 2006 4:48 pm Post subject: |
|
|
I found something suspicious when checking my SMART report. So i paste it here :
| Code: | smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: HTS726060M9AT00
Serial Number: MRH401M4G6148B
Firmware Version: MH4OA6BA
User Capacity: 56,448,705,536 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a
Local Time is: Thu Jan 12 17:36:57 2006 CET
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: ( 645) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 39) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 115 115 040 Pre-fail Offline - 3433
3 Spin_Up_Time 0x0007 207 207 033 Pre-fail Always - 2
4 Start_Stop_Count 0x0012 082 082 000 Old_age Always - 29124
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 118 118 040 Pre-fail Offline - 37
9 Power_On_Hours 0x0012 088 088 000 Old_age Always - 5664
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1735
191 G-Sense_Error_Rate 0x000a 099 099 000 Old_age Always - 65537
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 89
193 Load_Cycle_Count 0x0012 081 081 000 Old_age Always - 191139
194 Temperature_Celsius 0x0002 144 144 000 Old_age Always - 38 (Lifetime Min/Max 9/50)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
Warning: ATA error count 65535 inconsistent with error log pointer 4
ATA Error Count: 65535 (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 65535 occurred at disk power-on lifetime: 5664 hours (236 days + 0 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
-- -- -- -- -- -- --
10 59 08 27 41 c6 e6 Error: IDNF at LBA = 0x06c64127 = 113656103
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 27 41 c6 e6 00 00:01:01.800 READ SECTOR(S)
10 00 3f 00 00 00 e0 00 00:01:01.700 RECALIBRATE [OBS-4]
91 00 3f 3f ff 3f ef 00 00:01:01.700 INITIALIZE DEVICE PARAMETERS [OBS-6]
20 00 08 27 41 c6 e6 04 00:01:01.700 READ SECTOR(S)
20 00 08 27 41 c6 e6 00 00:01:01.600 READ SECTOR(S)
Error 65534 occurred at disk power-on lifetime: 5664 hours (236 days + 0 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
-- -- -- -- -- -- --
10 59 08 27 41 c6 e6 Error: IDNF at LBA = 0x06c64127 = 113656103
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 27 41 c6 e6 00 00:01:01.600 READ SECTOR(S)
20 00 08 27 41 c6 e6 00 00:01:01.600 READ SECTOR(S)
10 00 3f 00 00 00 e0 00 00:01:01.600 RECALIBRATE [OBS-4]
20 00 08 27 41 c6 e6 00 00:01:01.500 READ SECTOR(S)
20 00 08 27 41 c6 e6 00 00:01:01.500 READ SECTOR(S)
Error 65533 occurred at disk power-on lifetime: 5664 hours (236 days + 0 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
-- -- -- -- -- -- --
10 59 08 27 41 c6 e6 Error: IDNF at LBA = 0x06c64127 = 113656103
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 27 41 c6 e6 00 00:01:01.600 READ SECTOR(S)
10 00 3f 00 00 00 e0 00 00:01:01.600 RECALIBRATE [OBS-4]
20 00 08 27 41 c6 e6 00 00:01:01.500 READ SECTOR(S)
20 00 08 27 41 c6 e6 00 00:01:01.500 READ SECTOR(S)
10 00 3f 00 00 00 e0 00 00:01:01.500 RECALIBRATE [OBS-4]
Error 65532 occurred at disk power-on lifetime: 5664 hours (236 days + 0 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
-- -- -- -- -- -- --
10 59 08 27 41 c6 e6 Error: IDNF at LBA = 0x06c64127 = 113656103
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 27 41 c6 e6 00 00:01:01.500 READ SECTOR(S)
20 00 08 27 41 c6 e6 00 00:01:01.500 READ SECTOR(S)
10 00 3f 00 00 00 e0 00 00:01:01.500 RECALIBRATE [OBS-4]
91 00 3f 3f ff 3f ef 00 00:01:01.500 INITIALIZE DEVICE PARAMETERS [OBS-6]
20 00 08 27 41 c6 e6 04 00:01:01.400 READ SECTOR(S)
Error 65531 occurred at disk power-on lifetime: 5664 hours (236 days + 0 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
-- -- -- -- -- -- --
10 59 08 27 41 c6 e6 Error: IDNF at LBA = 0x06c64127 = 113656103
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
20 00 08 27 41 c6 e6 00 00:01:01.500 READ SECTOR(S)
10 00 3f 00 00 00 e0 00 00:01:01.500 RECALIBRATE [OBS-4]
91 00 3f 3f ff 3f ef 00 00:01:01.500 INITIALIZE DEVICE PARAMETERS [OBS-6]
20 00 08 27 41 c6 e6 04 00:01:01.400 READ SECTOR(S)
20 00 08 27 41 c6 e6 00 00:01:01.300 READ SECTOR(S)
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% 5664 -
# 2 Extended offline Completed without error 00% 5480 -
# 3 Short offline Completed without error 00% 5480 -
Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
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. |
Maybe someone could understand what it does mean and have an idea about what to do to correct that.
Thanks,
L. |
|
| Back to top |
|
|
Private_X
n00b
Joined: 30 May 2003
Posts: 34
Location: Germany
|
| Posted: Mon Jan 23, 2006 12:41 pm Post subject: |
|
|
I had the same Problem twice with my IBM Thinkpad. The first time I got this error I did a fsck from a live cd and corrected some errors. The second time I got no live cd and bootet with a lot of errors into single user mode. No command was found (I tried to force an fsck after reboot). After another reboot with a live cd and running fsck serveral thousand errors got corrected! After that the filesystem was partly corrupted. e.g. /etc was a file and /var/log was a dead symlink. My smartmantools show only an ATA Error Count of 2. The hitachi drive fitness test showed no errors.
I think we have the same harddrive
| Quote: | | Device Model: HTS726060M9AT00 |
Maybe it is a drive problem. But I'm not an expert.
Anyone an idea? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
