>>> "Carlos E. R." <[EMAIL PROTECTED]> 2007-05-08 12:30:55 >>> > > The Tuesday 2007-05-08 at 10:22 +0200, Wilfred van Velzen wrote: > > > I started the test at about 18:00 (local time), and now at 10:15, it > > says: > > > > Self-test execution status: ( 243) Self-test routine in > > progress... > > 30% of test remaining. > > Uau, that's a large disk. Or busy. Usually, it's about two hours or so.
It's big: 750GB Not too busy, but busy enough during work hours, because the 30% hasn't moved yet... > > The performance of the server seems to be ok, so I let it run for > > now... > > Mine crawls while doing the surface test part. On my older disks I can > continue working almost transparently. None of the users are complaining, so it's fast enough! ;-) > > > You can also look at the smart log of the disk. If there was an > > > uncorrectable error and there was a write attempt to that sector, it will > > > already be remapped, and thus it will not show again on tests. > > > > There is nothing in the logs. > > Not the system log, but the smart log that resides in the disk; you can > dig it out with "smartctl -a device". Yes, that was what I meant. I checked with: smartctl -l error /dev/sdb and: smartctl -l selftest /dev/sdb But that shows the same output as the -a option... > > > Only the remap counter should show it (Reallocated_Sector_Ct). > > > > For /dev/sdb: > > > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE > > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 4 > > > > /dev/sda: > > > > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 > > > > The RAW_VALUE is different on the disk that has the "problem", so is > > this the value that you should look at? > > Right. If I interpret it correctly, your sda has four sectors remapped. It sdb! > probably can work like this for years without problems, but watch it, and > if they keep increasing, you should think about replacing the HD. I'll keep a close eye on it! > Disks are designed so they survive bad sectors, it's a normal ocurrence, > and they are prepared for that. But if they keep growing, then it becomes > a problem or a symptom of failure. I'll advice the one who controls the money to order a spare one in advance, so we can replace it if necessary. It's one of the disks in a raid 1 configuration, so it shouldn't be an immediate problem if one disk fails... > > This isn't something that can be fixed on short notice ;), so I hope > > you will see this message! > > Yep, I noticed, because you sent also a CC to me: in those cases Pine > shows a yellow mark :-) I will keep doing this, then... ;) Met vriendelijke groet / Best regards, Wilfred van Velzen -- SERCOM Regeltechniek b.v. Heereweg 9 2161 AB Lisse Nederland +31 (0)252 416530 (voice) +31 (0)252 419481 (fax) <http://www.sercom.nl/> Op al onze offertes, op alle opdrachten aan ons en op alle met ons gesloten overeenkomsten zijn toepasselijk de METAALUNIEVOORWAARDEN, gedeponeerd ter Griffie van de Rechtbank te Rotterdam, zoals deze luiden volgens de laatstelijk aldaar neergelegde tekst. De leveringsvoorwaarden worden u op verzoek toegezonden. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
