From: Dieter S. <st...@co...> - 2004-10-18 15:43:22
|
My weekly "badblock" reported a bad sector this night and an extended test "-t long" confirmed this. I was able to track it down to the affected file and did some tests on it until the error suddenly disappeared! The file is readable again, and an other extended self test does not report any errors any more. I noticed bad sectors to disappear earlier, but I always believed they have been rewritten by new data written to that disk. This time however I am sure, the disk was mounted read-only! Interestingly the Reallocated_Sector_Ct jumped to 1 while the error was there but dropped back to 0 after it disappeared. I would expect this for "Current_Pending_Sector", but not for "Reallocated_Sector_Ct". The disk was a 300Gb Maxtor 5A300J0. strange... -- Dieter Stüken, con terra GmbH, Münster st...@co... http://www.conterra.de/ (0)251-7474-501 |
From: Bruce A. <ba...@gr...> - 2004-10-19 00:59:23
|
Hi Dieter, > My weekly "badblock" reported a bad sector this night and an extended > test "-t long" confirmed this. I was able to track it down to the > affected file and did some tests on it until the error suddenly > disappeared! The file is readable again, and an other extended self > test does not report any errors any more. I noticed bad sectors to > disappear earlier, but I always believed they have been rewritten > by new data written to that disk. This time however I am sure, the > disk was mounted read-only! > > Interestingly the Reallocated_Sector_Ct jumped to 1 while the error > was there but dropped back to 0 after it disappeared. I would expect > this for "Current_Pending_Sector", but not for "Reallocated_Sector_Ct". > > The disk was a 300Gb Maxtor 5A300J0. > > strange... Actually I think that this is NOT so strange. The things you were doing (badblocks, tracking down the affected file, etc) kept asking the disk to read this bad block. Suddenly, instead of failing, one of the reads was SUCCESSFUL. So the disk firmware did what some smart engineer programmed it to do: it reallocated the bad sector right then and there. Does this make sense to you? The reallocated sector count might have gone back to zero because perhaps the disk decided that after all the trouble this sector was OK, and decided to re-use it. Cheers, Bruce |