On Tue, 20 Feb 2024 at 17:51, Default User <hunguponcont...@gmail.com> wrote: > > Hi guys!
Hi to all readers, > Now it "works", BUT . . . I ran: > > sudo smartctl --test=long /dev/sdb on it, > > and it reports a Current_Pending_Sector error, at LBA 325904690. [...] > According to sudo smartctl --test=long /dev/sdb, > there is one Current_Pending_Sector error. > > I have done some research online, which seems to say that the error > will remain until there is an an attempt to write to the bad sector > (block). Then it will be "re-mapped", and presumably taken out of > service. > > But since the sector already can not be read, How can it be re-written > to a "good" sector? > > If I knew which file (if any) is using the bad sector, I could try just > deleting that file from the "bad" drive, then copy the same file over > from the "Good" drive, at which time the bad sector "should" be > retired, and replaced by a good sector. > > Or, as a more "brute force" solution, I could either simply format the > bad drive, or do: [...] > Any suggestions? Maybe this document will guide you to a preferred solution: https://www.smartmontools.org/wiki/BadBlockHowto
