Drive errors

[Emanoil Kotsev]

Mark Fraser wrote:

> On Saturday 18 October 2008 10:13:48 Emanoil Kotsev wrote:
>> Mark Fraser wrote:
>> > On Friday 17 October 2008 22:16:44 Emanoil Kotsev wrote:
>> >> Mark Fraser wrote:
>> >> > Emanoil, I haven't run badblocks yet, but I loaded up a live CD this
>> >> > morning and ran fsck.ext3 which didn't find anything wrong.
>> >> >
>> >> > Also, I have done a backup of the majority of the drive, but if I
>> >> > was to copy everything to a new drive how do I make a bootable
>> >> > partition?
>> >>
>> >> fsck checks the file system not the drive integrity
>> >
>> > Ran badblocks this morning and it completed without errors. Will see if
>> > I get any more errors in the logs today and then I'll have to use
>> > another drive.
>>
>> If the drive is ok, then it might be another issue. You can check what
>> chipset you have and google about issues with your specific chipset, or
>> may be with your specific drive model.
>>
>> May be contact the kernel people, who will tell you to install the recent
>> kernel and try again.
>>
>> regards
> 
> As an update, my computer locked up again this morning (nothing worked and
> something was constantly accessing one of my drives). When I rebooted and
> check smartctrl again I did see some errors:
> 
> Error 176 occurred at disk power-on lifetime: 2959 hours (123 days + 7
> 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 51 01 6e f0 50 e9
> 
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   37 ff 01 6e f0 50 e9 00      03:35:52.602  SET MAX ADDRESS EXT
>   27 ff 00 6e f0 50 e0 00      03:35:52.378  READ NATIVE MAX ADDRESS EXT
>   37 ff 00 6e f0 50 e9 00      03:35:52.313  SET MAX ADDRESS EXT
>   27 ff 01 6e f0 50 e0 00      03:35:50.233  READ NATIVE MAX ADDRES
> 
> and:
> 
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   37 ff 01 6e f0 50 e9 00      01:48:28.144  SET MAX ADDRESS EXT
>   27 ff 00 6e f0 50 e0 00      01:48:28.093  READ NATIVE MAX ADDRESS EXT
>   37 ff 00 6e f0 50 e9 00      01:48:28.092  SET MAX ADDRESS EXT
>   27 ff 01 6e f0 50 e0 00      01:48:28.092  READ NATIVE MAX ADDRESS EXT
>   37 ff 01 6e f0 50 e9 00      01:48:28.092  SET MAX ADDRESS EXT
> 
> 
> Also ran Hard Disk Sentinel which came back with:
> 
> HDD Device  0: /dev/sda
> HDD Model ID : ST380815AS
> HDD Serial No: 6RA4P3CL
> HDD Revision : 3.AAD
> HDD Size     : 76319 MB
> Interface    : S-ATA II
> Temperature  : 40 °C
> Health       : 100 %
> Performance  : 100 %
> Power on time: 123 days, 9 hours
> Est. lifetime: more than 1000 days
> 
> Still think I might have to replace the drive sooner than later.

As I suggested the only one who can help you take the right decision are the
kernel people, or a linux hard drive expert.
I fully trust the badblocks program. It didn't show any errors, so my bet
would be that some hardware component is not working properly.
But I can not help you further.

Post the message to the kernel harddisk (sata) list.

regards