-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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.
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.
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".
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 probably can work like this for years without problems, but watch it, and if they keep increasing, you should think oabout replacing the HD. 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.
P.S: Your mail program (Novell GroupWise Internet Agent 6.0.1) does not respect mail threads. I think that was a problem they already solved in another version or upgrade.
I mention this because it was only chance that I saw your answer.
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 :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGQFFgtTMYHG2NR9URAjJiAJ0dEWoeyM9LPzp5It34kHZEcthbpwCfe2P+ k0n4xoI8llOgK2CTOvapzz8= =ZqAs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org