Suspect I have a drive problem

English Hardware
1

I suspect I have a hard drive problem, here is what is happening:

  1. Very slow boot time > 5 to 8 minutes, if I am lucky
  2. Wait times on Applications is not immediate, sometimes they go into the background and a few minutes later they pop on the screen
  3. Ran Latencytop and some services are 2400 msec or greater; specifically on pagein or accessing applications

Is there a tool in the arsenal that I can use to help me isolate whether the problem is the hard drive.

Note ! I have already installed a “Fresh” 64bit Operating system with Formatting done before installation…

2

On Tue October 19 2010 09:36 pm, cherock1254 wrote:

>
> I suspect I have a hard drive problem, here is what is happening:
> 1. Very slow boot time > 5 to 8 minutes, if I am lucky
> 2. Wait times on Applications is not immediate, sometimes they go
> into the background and a few minutes later they pop on the screen
> 3. Ran Latencytop and some services are 2400 msec or greater;
> specifically on pagein or accessing applications
>
> Is there a tool in the arsenal that I can use to help me isolate
> whether the problem is the hard drive.
>
> Note ! I have already installed a “Fresh” 64bit Operating system with
> Formatting done before installation…
>
>
cherock1254;

Try enabling smartd. YaST->System->system services (Runlevel).

Smart will report disk diagnostics errors in:

var/log/messages

Most modern disk drives have S.M.A.R.T.

You should also check your cables. These can also go bad.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

3

Try this…

HARDLOCKLIMIT @256 11.3 install-default may cause Open Office issues

4

otto_oz, you should stop posting your HARDLOCKLIMIT-tutorial as a generic solution for performance problems as it will often be misleading.

5

IMHO HARDLOCKLIMIT has nothing to do with this either. If on a fresh, clean install disk actions are slow, a degrading condition of the disk may very well be the cause. Have been wrestling with this kind of problems a couple of years ago, it was “solved” when one of my HDD’s finally gave up. After replacement of the disk, restore of backups the same install did not have the issue anymore. From what’s written I suspect harm on the “/” partition.

6

Please, otto_oz, IMHO posting your HARDLOCKLIMIT-tutorial as a generic solution for performance problems can be misleading, especialy the the uninitiated.

7

On 2010-10-20 04:36, cherock1254 wrote:

> Is there a tool in the arsenal that I can use to help me isolate
> whether the problem is the hard drive.

There will be entries in the log.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

8

Results in WARN Log: (Does this mean what I think it means?)

Oct 20 17:03:20 linux-mnuu python: io/hpmud/musb.c 601: invalid usb_open: Permission denied
Oct 20 17:03:20 linux-mnuu python: io/hpmud/musb.c 601: invalid usb_open: Permission denied
Oct 20 17:26:56 linux-mnuu smartd[3240]: Device: /dev/sdb [SAT], 214 Currently unreadable (pending) sectors
Oct 20 17:26:56 linux-mnuu smartd[3240]: Device: /dev/sdb [SAT], 176 Offline uncorrectable sectors
Oct 20 17:28:50 linux-mnuu kdm[1258]: Cannot execute ‘grub-set-default’: not in $PATH.
Oct 20 17:28:58 linux-mnuu rpcbind: rpcbind terminating on signal. Restart with “rpcbind -w”
Oct 20 17:58:03 linux-mnuu kdm_config[1270]: Multiple occurrences of key ‘UseTheme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Oct 20 17:58:03 linux-mnuu kernel: 26.256276] nvidia: module license ‘NVIDIA’ taints kernel.
Oct 20 17:58:03 linux-mnuu kernel: 26.256282] Disabling lock debugging due to kernel taint
Oct 20 17:58:05 linux-mnuu kernel: 27.297416] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 20 17:58:05 linux-mnuu kernel: 27.445487] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 256.53 Fri Aug 27 20:27:48 PDT 2010
Oct 20 17:58:11 linux-mnuu dhcpcd[1936]: eth0: Failed to lookup hostname via DNS: Name or service not known
Oct 20 17:58:12 linux-mnuu audispd: No plugins found, exiting
Oct 20 17:58:13 linux-mnuu mcelog: failed to prefill DIMM database from DMI data
Oct 20 17:58:16 linux-mnuu smartd[3288]: Device: /dev/sdb [SAT], 214 Currently unreadable (pending) sectors
Oct 20 17:58:16 linux-mnuu smartd[3288]: Device: /dev/sdb [SAT], 176 Offline uncorrectable sectors
Oct 20 17:58:20 linux-mnuu python: hp-systray[3445]: error: option -s not recognized
Oct 20 18:28:16 linux-mnuu smartd[3296]: Device: /dev/sdb [SAT], 214 Currently unreadable (pending) sectors
Oct 20 18:28:16 linux-mnuu smartd[3296]: Device: /dev/sdb [SAT], 176 Offline uncorrectable sectors
Oct 20 18:49:34 linux-mnuu kdm[1269]: Cannot execute ‘grub-set-default’: not in $PATH.
Oct 20 18:50:11 linux-mnuu rpcbind: rpcbind terminating on signal. Restart with “rpcbind -w”
Oct 20 19:27:15 linux-mnuu kdm_config[1323]: Multiple occurrences of key ‘UseTheme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Oct 20 19:27:16 linux-mnuu kernel: 367.846193] nvidia: module license ‘NVIDIA’ taints kernel.
Oct 20 19:27:16 linux-mnuu kernel: 367.846199] Disabling lock debugging due to kernel taint
Oct 20 19:27:17 linux-mnuu kernel: 369.042880] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 256.53 Fri Aug 27 20:27:48 PDT 2010
Oct 20 19:27:17 linux-mnuu kernel: 369.143577] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 20 19:27:23 linux-mnuu dhcpcd[1993]: eth0: Failed to lookup hostname via DNS: Name or service not known
Oct 20 19:27:25 linux-mnuu audispd: No plugins found, exiting
Oct 20 19:27:26 linux-mnuu mcelog: failed to prefill DIMM database from DMI data
Oct 20 19:27:28 linux-mnuu smartd[3328]: Device: /dev/sdb [SAT], 214 Currently unreadable (pending) sectors
Oct 20 19:27:28 linux-mnuu smartd[3328]: Device: /dev/sdb [SAT], 176 Offline uncorrectable sectors
Oct 20 19:27:30 linux-mnuu python: hp-systray[3482]: error: option -s not recognized

9

On 2010-10-21 03:36, cherock1254 wrote:
>
> Results in WARN Log: (Does this mean what I think it means?)

> Oct 20 17:26:56 linux-mnuu smartd[3240]: Device: /dev/sdb [SAT], 214
> Currently unreadable (pending) sectors

> Oct 20 17:26:56 linux-mnuu smartd[3240]: Device: /dev/sdb [SAT], 176
> Offline uncorrectable sectors

Ok, paste the output of “smartctl -a /dev/sda”. Put it as code in the forum, not as plain text. Quick.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

10

Oops, sorry, that should be “/dev/sdb”.

Anyway, I’m off to bed now, it is 4 AM here. I want to have a clearer view of the smartd log. I suspect the spare sectors reserved in your disk for remapping bad sectors has been spent, which means “replace the disk ASAP”, and that is really ASAP, like now. Power off till you replace the disk.

You will have to rescue your data later with dd_rescue.

11

otto_oz, you should stop posting your HARDLOCKLIMIT-tutorial as a generic solution for performance problems as it will often be misleading.

Please, otto_oz, IMHO posting your HARDLOCKLIMIT-tutorial as a generic solution for performance problems can be misleading, especialy the the uninitiated.

Understood ! No Problem !

Cheers Otto;)

12

Here is the output of smartctl:

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Black family
Device Model: WDC WD7501AALS-00E3A0
Serial Number: WD-WCATR0367812
Firmware Version: 05.01D05
User Capacity: 750,156,374,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Thu Oct 21 15:48:04 2010 CDT
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: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: (11400) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 133) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3037) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

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 0x002f 200 200 051 Pre-fail Always - 2486
3 Spin_Up_Time 0x0027 175 173 021 Pre-fail Always - 4225
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 833
5 Reallocated_Sector_Ct 0x0033 198 198 140 Pre-fail Always - 12
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1724
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 561
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 37
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 795
194 Temperature_Celsius 0x0022 098 089 000 Old_age Always - 49
196 Reallocated_Event_Count 0x0032 189 189 000 Old_age Always - 11
197 Current_Pending_Sector 0x0032 199 199 000 Old_age Always - 214
198 Offline_Uncorrectable 0x0030 199 199 000 Old_age Offline - 176
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 197 197 000 Old_age Offline - 701

SMART Error Log Version: 1
ATA Error Count: 237 (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 237 occurred at disk power-on lifetime: 1703 hours (70 days + 23 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 45 05 86 e7 Error: UNC at LBA = 0x07860545 = 126223685

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

c8 00 00 40 05 86 e7 08 11:02:34.792 READ DMA
c8 00 20 20 05 86 e7 08 11:02:34.789 READ DMA
c8 00 08 70 06 86 e7 08 11:02:34.785 READ DMA
c8 00 18 38 a5 85 e6 08 11:02:34.770 READ DMA
c8 00 20 a0 31 85 e6 08 11:02:34.734 READ DMA

Error 236 occurred at disk power-on lifetime: 1660 hours (69 days + 4 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 c5 22 15 e8 Error: UNC at LBA = 0x081522c5 = 135602885

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

c8 00 00 e0 21 15 e8 08 10:44:03.274 READ DMA
c8 00 00 e0 20 15 e8 08 10:44:03.273 READ DMA
c8 00 00 e0 1f 15 e8 08 10:44:03.264 READ DMA
c8 00 00 e0 1e 15 e8 08 10:44:03.263 READ DMA
c8 00 00 e0 1d 15 e8 08 10:44:03.262 READ DMA

Error 235 occurred at disk power-on lifetime: 1637 hours (68 days + 5 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 08 fa 6a a7 e2 Error: UNC 8 sectors at LBA = 0x02a76afa = 44526330

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

c8 00 08 f8 6a a7 e2 08 00:58:43.561 READ DMA
c8 00 08 f0 6a a7 e2 08 00:58:43.561 READ DMA
c8 00 08 e8 6a a7 e2 08 00:58:43.561 READ DMA
c8 00 08 e0 6a a7 e2 08 00:58:43.561 READ DMA
c8 00 08 d8 6a a7 e2 08 00:58:43.560 READ DMA

Error 234 occurred at disk power-on lifetime: 1637 hours (68 days + 5 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 ff 6a a7 e2 Error: UNC at LBA = 0x02a76aff = 44526335

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

c8 00 00 30 6a a7 e2 08 00:58:37.082 READ DMA
ec 00 00 00 00 00 a0 08 00:58:37.079 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 00:58:37.079 SET FEATURES [Set transfer mode]

Error 233 occurred at disk power-on lifetime: 1637 hours (68 days + 5 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 39 6a a7 e2 Error: UNC at LBA = 0x02a76a39 = 44526137

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

c8 00 00 30 6a a7 e2 08 00:58:34.176 READ DMA
ec 00 00 00 00 00 a0 08 00:58:34.173 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 00:58:34.172 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 captive Completed: read failure 90% 1511 16652676

2 Short captive Completed without error 00% 485 -

3 Short captive Completed without error 00% 485 -

4 Short captive Completed without error 00% 485 -

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

13

On 2010-10-21 23:06, cherock1254 wrote:
>
> Here is the output of smartctl:

Lines wrapped around, I had to edit.


> 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     0x002f   200   200   051    Pre-fail  Always       -       2486
>   3 Spin_Up_Time            0x0027   175   173   021    Pre-fail  Always       -       4225
>   4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       833
>   5 Reallocated_Sector_Ct   0x0033   198   198   140    Pre-fail  Always       -       12

Not expent. I think it means it has reallocated 12 sectors.


>   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
>   9 Power_On_Hours          0x0032   098   098   000    Old_age   Always       -       1724

The disk is young.


>  10 Spin_Retry_Count        0x0032   100   100   000    Old_age  Always        -       0
>  11 Calibration_Retry_Count 0x0032   100   100   000    Old_age  Always        -       0
>  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       561
> 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age  Always        -       37
> 193 Load_Cycle_Count        0x0032   200   200   000    Old_age  Always        -       795
> 194 Temperature_Celsius     0x0022   098   089   000    Old_age   Always       -       49
> 196 Reallocated_Event_Count 0x0032   189   189   000    Old_age   Always       -       11
> 197 Current_Pending_Sector  0x0032   199   199   000    Old_age   Always       -       214
> 198 Offline_Uncorrectable   0x0030   199   199   000    Old_age   Offline      -       176

That is the problem.


> 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
> 200 Multi_Zone_Error_Rate   0x0008   197   197   000    Old_age   Offline      -       701



> Error 237 occurred at disk power-on lifetime: 1703 hours (70 days + 23 hours)

Errors happened recently.


> SMART Self-test log structure revision number 1
> Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
> # 1  Short captive       Completed: read failure       90%      1511    16652676
> # 2  Short captive       Completed without error       00%       485    -
> # 3  Short captive       Completed without error       00%       485    -
> # 4  Short captive       Completed without error       00%       485    -

If my understanding is correct, you have to write to the bad sectors in order to force a remap. In
any case, you should make a backup of all your data as soon as possible. After that, I would rewrite
the entire disk with zeroes, then with 0xFF, then run a long smart test. Probably wait and repeat
tests over several days to see if more bad sectors appear, by writing over it again each time.
Depending on that, the disk might be usable, or you should think of returning to the manufacturer
for replacement, if it is still under guaranty.

The problem is serious.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

14

Carlos, based on what I was seeing with errors and bad sectors, this is exactly what I was thinking … This drive is about 90 to 120 days old. I had another exact same drive crash with Windows 7 less than a month after I purchased. I was sent a green drive to replace it, now this one appears to be bad. Not a very good track record for Western Digital “Black Caviar”… I appreciate your help and all who have had input into this problem, so if I haven’t identified you by name or user name, a Thank You goes out to you… I will send this Hard Drive back, it is still under-warranty. Sincerely, Clois

15

Hi
Yet looking at the smart figures it’s power-on hours vs power cycle
count shows an event around every three hours (12 Power Cycle
Count is Quantity of full HDD power on/off cycles).

Sure your power supply is OK? If that’s the second drive to fail I
would also be looking at the rest of the system hardware.

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.23-0.3-default
up 13:05, 4 users, load average: 0.03, 0.07, 0.06
GPU GeForce 8600 GTS Silent - Driver Version: 260.19.12

16

You should also mind the temperature of your hard drives, what do you have a laptop? High temperature can screw even a good drive very quickly, so take care, good luck!

17

Bad sectors are possible, but I also second malcolmlewis’ idea about malfunctioning power supply, as I had the exact same errors when I was using bad SATA-to-IDE-adapters once. It got solved when I was switching my motherboard (which did not need any adapters).