Date: Thu, 29 Oct 2009 07:12:45 +1100 From: David N <davidn04@gmail.com> To: =?ISO-8859-1?Q?Micha=EBl_Gr=FCnewald?= <michaelgrunewald@yahoo.fr> Cc: Polytropon <freebsd@edvax.de>, freebsd questions general <freebsd-questions@freebsd.org> Subject: Re: Bad sectors: how bad can it be Message-ID: <4d7dd86f0910281312u54015538sb492db1ebc51fe59@mail.gmail.com> In-Reply-To: <4AE8A1B3.2070503@yahoo.fr> References: <FAF67E79-922C-4F54-8BE1-2C3ED88FD3CD@yahoo.fr> <20091027150519.dcee178a.freebsd@edvax.de> <4AE75293.5020603@yahoo.fr> <20091028125215.55ad3801.freebsd@edvax.de> <4AE8A1B3.2070503@yahoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/10/29 Micha=EBl Gr=FCnewald <michaelgrunewald@yahoo.fr>: > Polytropon wrote: >> >> On Tue, 27 Oct 2009 21:05:39 +0100, Micha=EBl Gr=FCnewald >> <michaelgrunewald@yahoo.fr> wrote: >>> >>> I have however a question: How do I verify that a hard-drive is >>> accurately working if its firmware will hide the bad sectors as long as >>> possible? >> >> I think the smartctl program from ports/smartmontools is a good tool for >> such verification. As far as I understood, >> it can read internal error logs from the firmware. > > Hi, following your suggestion I used smartmon to get access to the SMART > data. I have run an extended offline test (with-t offline I think). The t= est > reported no error (!) and the bad sectors are now read/writeable (!!). Is= it > safe to think the problem is gone? > > # smartctl -l selftest /dev/ad10 > > =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D > SMART Self-test log structure revision number 1 > Num =A0Test_Description =A0 =A0Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= Remaining LifeTime(hours) > =A0LBA_of_first_error > # 1 =A0Extended offline =A0 =A0Completed without error =A0 =A0 =A0 00% = =A0 =A0 =A0 458 =A0 =A0 - > # 2 =A0Extended offline =A0 =A0Aborted by host =A0 =A0 =A0 =A0 =A0 =A0 = =A0 70% =A0 =A0 =A0 456 > -- > Best regards, > Micha=EBl > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" > I've had this problem before on consumer grade HDD. * The drive tries to read/write to a sector, it can't, then marks the sector as bad and preps for remapping * Remapping may take upto 10 minutes on consumer grade HDD, enterprise ones usually remap within seconds. so this 10 minute lagg time will timeout the read/write of the OS. * Usually a remap is done on reboot or when its done internally and data is copied (if it can). If your smartctl says it has used up a spare block (Reallocated_Sector_Ct), replace the drive ASAP. The drives will tend to get more and more bad blocks after the the first one is found, usually because the head is damaging the disks or the head itself is damaged, or other reasons. If its under warranty they usually replace is, talk to the manufacturer before hand. Regards David N
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d7dd86f0910281312u54015538sb492db1ebc51fe59>