From: Sebastian N. <seb...@ar...> - 2011-06-30 10:45:18
|
Hi everyone in my syslogs I have following error: Device: /dev/sdb, 4 Currently unreadable (pending) sectors Device: /dev/sdb, 4 Offline uncorrectable sectors these messages repeat every 30 minutes /dev/sdb is a seagate baracuda disk. /dev/sdb is part of a linux software raid1, so it was possible to extract the disk and check it in another machine using seatools dos cd (as FAQ said) without rebooting the computer. But seatools did not find any errors (tried short and long test which should repair bad sectors)! I inserted the disk again and still get the errors from smartd in syslog. Why does smartd repeat the message? I guess it always means the same 4 sectors. Does it save the status of the disk and just repeats the old message? Can I tell smartd that the disk is checked? Is there any other way to get rid of the problem. Thanks for your help Sebastian |
From: Justin P. <jp...@lu...> - 2011-06-30 10:47:37
|
On Thu, 30 Jun 2011, Sebastian Neustein wrote: > Hi everyone > > in my syslogs I have following error: > Device: /dev/sdb, 4 Currently unreadable (pending) sectors > Device: /dev/sdb, 4 Offline uncorrectable sectors > these messages repeat every 30 minutes > > /dev/sdb is a seagate baracuda disk. > > /dev/sdb is part of a linux software raid1, so it was possible to extract the > disk and check it in another machine using seatools dos cd (as FAQ said) without > rebooting the computer. > > But seatools did not find any errors (tried short and long test which should > repair bad sectors)! I inserted the disk again and still get the errors from > smartd in syslog. > > Why does smartd repeat the message? I guess it always means the same 4 sectors. > Does it save the status of the disk and just repeats the old message? Can I tell > smartd that the disk is checked? > > Is there any other way to get rid of the problem. > > Thanks for your help > Sebastian Hi, Is the disk under warranty? If it is, you may want to RMA it. Justin. |
From: Sebastian N. <seb...@ar...> - 2011-06-30 11:09:02
|
Am 30.06.2011 12:47, schrieb Justin Piszcz: > > > On Thu, 30 Jun 2011, Sebastian Neustein wrote: > >> Hi everyone >> >> in my syslogs I have following error: >> Device: /dev/sdb, 4 Currently unreadable (pending) sectors >> Device: /dev/sdb, 4 Offline uncorrectable sectors >> these messages repeat every 30 minutes >> >> /dev/sdb is a seagate baracuda disk. >> >> /dev/sdb is part of a linux software raid1, so it was possible to >> extract the >> disk and check it in another machine using seatools dos cd (as FAQ >> said) without >> rebooting the computer. >> >> But seatools did not find any errors (tried short and long test which >> should >> repair bad sectors)! I inserted the disk again and still get the >> errors from >> smartd in syslog. >> >> Why does smartd repeat the message? I guess it always means the same >> 4 sectors. >> Does it save the status of the disk and just repeats the old message? >> Can I tell >> smartd that the disk is checked? >> >> Is there any other way to get rid of the problem. >> >> Thanks for your help >> Sebastian > > Hi, > > Is the disk under warranty? > If it is, you may want to RMA it. > > Justin. > > Hi Justin, no, it's about three years old. Sebastian -- Sebastian Neustein (geb. Scholz) Airport Research Center GmbH Bismarckstraße 61 52066 Aachen Germany Phone: +49 241 16843-23 Fax: +49 241 16843-19 e-mail: seb...@ar... Website: http://www.airport-consultants.com Register Court: Amtsgericht Aachen HRB 7313 Ust-Id-No.: DE196450052 Managing Director: Dipl.-Ing. Tom Alexander Heuer |
From: Justin P. <jp...@lu...> - 2011-06-30 10:57:39
|
On Thu, 30 Jun 2011, Sebastian Neustein wrote: > > > Am 30.06.2011 12:47, schrieb Justin Piszcz: >> >> >> On Thu, 30 Jun 2011, Sebastian Neustein wrote: >> >>> Hi everyone >>> >>> in my syslogs I have following error: >>> Device: /dev/sdb, 4 Currently unreadable (pending) sectors >>> Device: /dev/sdb, 4 Offline uncorrectable sectors >>> these messages repeat every 30 minutes >>> >>> /dev/sdb is a seagate baracuda disk. >>> >>> /dev/sdb is part of a linux software raid1, so it was possible to extract >>> the >>> disk and check it in another machine using seatools dos cd (as FAQ said) >>> without >>> rebooting the computer. >>> >>> But seatools did not find any errors (tried short and long test which >>> should >>> repair bad sectors)! I inserted the disk again and still get the errors >>> from >>> smartd in syslog. >>> >>> Why does smartd repeat the message? I guess it always means the same 4 >>> sectors. >>> Does it save the status of the disk and just repeats the old message? Can >>> I tell >>> smartd that the disk is checked? >>> >>> Is there any other way to get rid of the problem. >>> >>> Thanks for your help >>> Sebastian >> >> Hi, >> >> Is the disk under warranty? >> If it is, you may want to RMA it. >> >> Justin. >> >> > Hi Justin, > > no, it's about three years old. > > Sebastian Have you looked at the ignore options? -i ID [ATA only] Ignore device Attribute number ID when checking for failure of Usage Attributes. ID must be a decimal integer in the range from 1 to 255. This Directive modifies the behavior of the ´-f´ Directive and has no effect without it. This is useful, for example, if you have a very old disk and don´t want to keep getting messages about the hours-on-lifetime Attribute (usually Attribute 9) failing. This Directive may appear multiple times for a single device, if you want to ignore multiple Attributes. -I ID [ATA only] Ignore device Attribute ID when tracking changes in the Attribute values. ID must be a decimal integer in the range from 1 to 255. This Directive modifies the behavior of the ´-p´, ´-u´, and ´-t´ tracking Directives and has no effect with- out one of them. This is useful, for example, if one of the device Attributes is the disk temperature (usually Attribute 194 or 231). It´s annoy- ing to get reports each time the temperature changes. This Directive may appear multiple times for a single device, if you want to ignore multiple Attributes. -r ID[!] [ATA only] When tracking, report the Raw value of Attribute ID along with its (normally reported) Normalized value. ID must be a decimal integer in the range from 1 to 255. This Directive modifies the behavior of the ´-p´, ´-u´, and ´-t´ tracking Directives and has no effect without one of them. This Direc- tive may be given multiple times. A common use of this Directive is to track the device Tempera- ture (often ID=194 or 231). If the optional flag ´!´ is appended, a change of the Normalized value is considered critical. The report will be logged as LOG_CRIT and a warning email will be sent if ´-m´ is specified. Justin. |
From: Sebastian N. <seb...@ar...> - 2011-06-30 11:19:22
|
Justin Piszcz <jpiszcz <at> lucidpixels.com> writes: > On Thu, 30 Jun 2011, Sebastian Neustein wrote: > > On 30.06.2011 12:47, schrieb Justin Piszcz: > >> On Thu, 30 Jun 2011, Sebastian Neustein wrote: > >>> Hi everyone [..snip..] > >>> Why does smartd repeat the message? I guess it always means the same 4 > >>> sectors. > >>> Does it save the status of the disk and just repeats the old message? Can > >>> I tell > >>> smartd that the disk is checked? > Have you looked at the ignore options? > > -i ID > -I ID > -r ID[!] Okay, I could ignore the messages - but is this save? As I understand the parameters above, they won't ignore my error message since they all need an Attribute ID but the error message has not such an ID. Regards Sebastian |
From: Justin P. <jp...@lu...> - 2011-06-30 11:21:24
|
On Thu, 30 Jun 2011, Sebastian Neustein wrote: > Justin Piszcz <jpiszcz <at> lucidpixels.com> writes: > >> On Thu, 30 Jun 2011, Sebastian Neustein wrote: >>> On 30.06.2011 12:47, schrieb Justin Piszcz: >>>> On Thu, 30 Jun 2011, Sebastian Neustein wrote: >>>>> Hi everyone > [..snip..] >>>>> Why does smartd repeat the message? I guess it always means the same 4 >>>>> sectors. >>>>> Does it save the status of the disk and just repeats the old message? Can >>>>> I tell >>>>> smartd that the disk is checked? >> Have you looked at the ignore options? >> >> -i ID >> -I ID >> -r ID[!] > > Okay, I could ignore the messages - but is this save? > > As I understand the parameters above, they won't ignore my error message since > they all need an Attribute ID but the error message has not such an ID. > > Regards > Sebastian Hi, It should have an ID: # smartctl -a /dev/sda | egrep '(Current_Pending_Sector|Offline_Uncorrectable)' 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 Add whichever are alarming to the smartd.conf -i / ignore options perhaps? Justin. |
From: Sebastian N. <seb...@ar...> - 2011-07-01 13:02:22
|
Justin Piszcz <jpiszcz <at> lucidpixels.com> writes: > > > On Thu, 30 Jun 2011, Sebastian Neustein wrote: > > > Justin Piszcz <jpiszcz <at> lucidpixels.com> writes: > > > >> On Thu, 30 Jun 2011, Sebastian Neustein wrote: > >>> On 30.06.2011 12:47, schrieb Justin Piszcz: > >>>> On Thu, 30 Jun 2011, Sebastian Neustein wrote: > >>>>> Hi everyone > > [..snip..] > >>>>> Why does smartd repeat the message? I guess it always means the same 4 > >>>>> sectors. > >>>>> Does it save the status of the disk and just repeats the old message? > >>>>> Can I tell smartd that the disk is checked? > >> Have you looked at the ignore options? > >> > >> -i ID > >> -I ID > >> -r ID[!] > > > > Okay, I could ignore the messages - but is this save? > > > > As I understand the parameters above, they won't ignore my error message > > since they all need an Attribute ID but the error message has not such an > > ID. > > Hi, > > It should have an ID: > > # smartctl -a /dev/sda | egrep '(Current_Pending_Sector|Offline_Uncorrectable)' > 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 > 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 > > Add whichever are alarming to the smartd.conf -i / ignore options perhaps? > > Justin. > Hi Justin thanks for all your help. Meanwhile I tried to update the firmware which did not succeed. Even SeaTools for Windows could not find the harddisc. Therefore I called support and they were even more frightening: "Don't switch of the server if you have another hd of the same type in there bought on the same day - it might not be possible to reboot again. There is a severe firmware bug!". So they will pick up the disk... Anyway, it did not work to use the -i 197 -i 198 option in smartd.conf. The errors were still reported (I checked the IDs). But I for now it does not matter anymore. Again thanks for your help Sebastian |