From: robin_listas@es.invalid   
      
   On 23/10/2020 05.25, bad sector wrote:   
   >   
   > I ran into a complex problem (discussed on alt.comp.hardware)   
   > and while TS-ing it came face-to-face with something I had   
   > never seen before, except in suse. It cought my eye because it   
   > was the SECOND time within in a few weeks. I have a Leap-15.2   
   > and a Tumbleweed installation (among others). Just as I was   
   > isolating the problem otherwise unrelated to any OS  the Leap-15.2   
   > failed to boot, I mean totally failed.  Looking into it from another   
   > booted partition I saw an fstab file that is completely EMPTY.  I   
   > have no idea how this could happen but like I said it's happened   
   > TWICE now within a month.  Seems like there might be a hole in   
   > some script dealing with fstabs, I certainly have never emptied an   
   > fstab file or saved one that's empty :)   
      
      
   I don't remember having heard of anybody complaining of a similar   
   problem in the places I read.   
      
   The timestamps of the fstab file would aid you to correlate with the   
   journal or syslog and perhaps find out what caused this.   
      
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)