I ran sudo e2fsck -f /dev/sda1 . Up to this point, the system failed as I described more severely when first starting, i.e., when it had been powered off for a while. So I waited 'till this AM to power on after being off overnight. I have detected no failures so far.
This novice's reading of man e2fsck makes me think that the command e2fsck -f /dev/sda1 does not do anything, unless "checking a file system" means "fixing a file system". In fact, if e2fsck -f does fix things what is the purpose of the -p option? So I am left with the mystery: Why does my system seem OK? It certainly gave me major failures the last two days. What am I missing? -Denis On Sat, Jul 4, 2015 at 4:33 PM, Denis Heidtmann <denis.heidtm...@gmail.com> wrote: > I am running sudo e2fsck -f /dev/sda1 I suppose I could interrupt it (if > I knew how) and add the v and p options. Certainly the -v is a no-brainer. > > -Denis > > On Sat, Jul 4, 2015 at 4:20 PM, Rich Shepard <rshep...@appl-ecosys.com> > wrote: > >> On Sat, 4 Jul 2015, Denis Heidtmann wrote: >> >> > As I said, "I booted from a live CD and attempted to run fsck. It spends >> > zero time to respond that /dev/sda1 is clean." >> > >> > Are there some options I should use when running fsck? I know when >> Ubuntu >> > runs automatically every so often on boot that it takes a few minutes >> to >> > complete. Yet when I run fsck from the live CD it completes >> immediately, >> > with no errors. >> >> Denis, >> >> After booting with the live CD and running 'mount' what devices are >> shown? >> >> What specific command did you give e2fsck? Notice that there are >> different >> options for fsck and e2fsck. The latter works on ext2, ext3, and ext4 file >> systems. I believe the options that Slackware suggested I use include: >> >> -f (force checking/repairing even if the initial report is a clean >> device), >> -p (automatically 'preen' -- repair -- the filesystem), >> -v (verbose mode) >> >> So, to fix /dev/sda1/ write >> e2fsck -fpv /dev/sda1 >> >> Look at man e2fsck to check whether you want these options, too. >> >> Rich >> >> _______________________________________________ >> PLUG mailing list >> PLUG@lists.pdxlinux.org >> http://lists.pdxlinux.org/mailman/listinfo/plug >> > > _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
