From: robin_listas@es.invalid   
      
   On 07/09/2019 21.48, bad sector wrote:   
   > On 9/7/19 2:20 PM, Carlos E.R. wrote:   
   >> On 07/09/2019 14.21, bad sector wrote:   
      
   ...   
      
   >   
   >>> The last several attempts to update had bombed for assorted reasons, the   
   >>> last 2 or 3 with the cited fs issue, each time the installation had been   
   >>> recovered from an image file made with dd.   
   >>   
   >> Was the partition mounted when you did the dd? That means you have to   
   >> fsck each time you use it.   
   >   
   > I have always done my dd from another installation, the source and/or   
   > taget being strictly unmounted.  But I WOULD like to do a backup dd from   
   > the active partition itself and if an fsck is the only condition i'll   
   > probably go for it.   
   >   
   > As for the image in question I still have it. It's a simple matter to   
   > revert to it and do the fsck to find out if the image carries the prob.   
   > I want to know how this mess came about. I should vave adopted the   
   > practice as procedure anyway ie. fsck before each backup as well as   
   > after recovery.   
      
   You can probably loop-mount the image and find out, even repair it, as   
   long as it is rw.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)