Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.suse    |    Suse is actually not that bad    |    138,051 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 137,095 of 138,051    |
|    Carlos E.R. to bad sector    |
|    Re: Empty fstab?    |
|    24 Oct 20 19:42:29    |
      From: robin_listas@es.invalid              On 24/10/2020 16.18, bad sector wrote:       > On 2020-10-23 21:59, Carlos E.R. wrote:       >> On 24/10/2020 03.07, bad sector wrote:       >>> On 2020-10-23 07:47, Carlos E.R. wrote:       >>>> 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.       >>>       >>> too late cause the first thing I did of course was write another one       >>       >> Pity.       >>       >> Well, make a backup of the file.       >>       >>       >>> but I do remember at times using Yast>Partitioner just to edit a       >>> Volume-Label to a partition       >>       >> Good.       >       > As in, that's when Yast or partitioner might have       > wrote an empty fstab, just a hunch. I certainly haven't       > emptied or saved an emty fstab in my life.              It never happened to me, and I use labels on all my partitions.       YaST does other things, like changing your tabs to spaces and other wise       wrecking a beautifully edited fstab, but empty it, never.              So to protect about changes in the formatting of fstab, I make a backup       copy before doing changes:              /etc/fstab       /etc/fstab.20201024                     --       Cheers, Carlos.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca