From: nospam@needed.invalid   
      
   On 7/1/2024 12:02 AM, Mike Easter wrote:   
   > philo wrote:   
   >> Just curious as to why someone would want to do that.   
   >   
   > It is hard to say all of what man hdparm has to say about --make-bad-sector   
   in just a few words, but if you are curious you should read that, incl the   
   EXCEPTIONALLY  DANGEROUS. DO NOT USE THIS OPTION!! part.  I think it isn't a   
   good idea for us    
   novices to mess around w/ things like low level hdd 'treachery'.  However, I   
   do think that hdparm might be something you could try to use to fix your   
   current bad sector problem if you are so inclined.  I don't think I would   
   bother w/ the idea of    
   creating your own bad sector for the 'fun' (or experience) of it.   
   >   
   >   
      
   It's possible it would show up in a bad block scan.   
   As a CRC error.   
      
   The error might be resolved by writing to the sector.   
   If you know the sector number, using "dd", using seek and skip,   
   using bs=512 and so on, you should be able to target the   
   bad block and write it. If the write succeeds, it won't get   
   spared out. If the write fails, it might substitute a good   
   sector for the "fake bad" one.   
      
   Naturally, you would not "aim" at a sector containing valued data.   
   You'd also have to be careful of not hitting metadata in the   
   file system. In some cases, on a "hot" file system, it can be   
   difficult to be sure you're parked on white space if you are   
   trying to do this.   
      
   But where is the fun if the drive does not have data on it :-)   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)