smartctl -A /dev/hda

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   060    Pre-fail
Always      -       0
2 Throughput_Performance    0x0005   155   155   050    Pre-fail
Offline     -       225
3 Spin_Up_Time              0x0007   097   097   024    Pre-fail
Always      -       293 (Average 270)
4 Start_Stop_Count          0x0012   100   100   000    Old_age
Always      -       10
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   125   125   020    Pre-fail
Offline     -       36
9 Power_On_Hours            0x0012   100   100   000    Old_age
Always      -       3548
10 Spin_Retry_Count         0x0013   100   100   060    Pre-fail
Always      -       0
12 Power_Cycle_Count        0x0032   100   100   000    Old_age
Always      -       10
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age
Always      -       158
193 Load_Cycle_Count        0x0012   100   100   050    Old_age
Always      -       158
194 Temperature_Celsius     0x0002   189   189   000    Old_age
Always      -       29 (Lifetime Min/Max 23/33)
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


Check the "Power_On_Hours" figure. If this is more than say 25K (3
years continuous uptime) it's time to replace.

On Jan 14, 2008 2:48 PM, Gideon Guillen <[EMAIL PROTECTED]> wrote:
> On 1/14/08, Nelson Serafica <[EMAIL PROTECTED]> wrote:
> > I experience this problem in my samba server last year November cause one of
> > the files can't be open. What I did is do a inside vacuum (cause its dirty
> > already) and replace ide cable. After several times, it did bootup. And now,
> > I'm experiencing it again. I check message and found the ff:
> [snipped]
> > This is also the problem before. Did anyone experience the same problem?
> > Would you think  its time to upgrade/reinstall and used another hard disk?
>
> Have you check all the ables to see if they're properly connected?
> Have you tried replacing the IDE cable with another one, or even the
> old one? Could be just a cable problem.
>
> If that still doesn't work, try connecting the hard disk to another
> computer. If you still get the same error, it's time to back up all
> important data that you can still access and replace the hard disk. If
> you don't get the error message anymore, maybe you damaged something
> in the built-in HDD controller on your motherboard while you were
> removing the dusts or something else like power fluctuations.
>
> > Is there an application in Linux where it is possible to bypass a certain
> > sector?
>
> fsck for some file systems (e2fsck for ext2, for example) can use the
> "-c" parameter to run badblocks to check for bad sectors. But if I
> were you, you should replace the hard disk immediately.
>
> --
> Gideon N. Guillen
> [EMAIL PROTECTED]
> _________________________________________________
> Philippine Linux Users' Group (PLUG) Mailing List
> [email protected] (#PLUG @ irc.free.net.ph)
> Read the Guidelines: http://linux.org.ph/lists
> Searchable Archives: http://archives.free.net.ph
>



-- 
Orlando Andico
+63.2.976.8659 | +63.920.903.0335

"I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure
out how to use my telephone."
  -- Bjarne Stroustrup
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to