From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc MERLIN Subject: Re: force remapping a pending sector in sw raid5 array Date: Sun, 11 Feb 2018 07:41:58 -0800 Message-ID: <20180211154158.qiddefzyhm7y2p42@merlins.org> References: <20180206181416.amo6geclrvc6ylrf@merlins.org> <20180209192928.vliiwkv6q76jf6jp@merlins.org> <1227ce39-31af-22f2-f4fa-de85466f05c7@turmel.org> <1934212.TzpEgCIeIR@matkor-lenovo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1934212.TzpEgCIeIR@matkor-lenovo> Sender: linux-raid-owner@vger.kernel.org To: Mateusz Korniak Cc: Phil Turmel , Kay Diederichs , Andreas Klauer , Adam Goryachev , Roger Heflin , linux-raid@vger.kernel.org List-Id: linux-raid.ids As a last update on those drives, sadly they seem to have real problems with SMART, which is why I was confused when using them. myth:~# badblocks -fsvn -b512 /dev/sdf /dev/sdf is apparently in use by the system; badblocks forced anyway. Checking for bad blocks in non-destructive read-write mode >From block 0 to 3131110575 Checking for bad blocks (non-destructive read-write test) Testing with random pattern: done Pass completed, 0 bad blocks found. (0/0/0 errors) That means a full read/write scan ran ok. Yet: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 7 7 sectors still marked as pending. This makes no sense... As far as I can tell, SMART is just broken on those drives, and they're going back to where I got them from. Thanks all for the replies and helping me confirm this. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08