Re: Boot stops at fsck
On Sun, May 17, 2015 at 12:51:01PM -0700, Patrick Bartek wrote:
> On Sun, 17 May 2015, Victor Munoz wrote:
>
> > On Sun, May 17, 2015 at 01:08:31PM -0400, Victor Munoz wrote:
> > > Hi, everyone. Last night I updated a lot of files in my sid system,
> > > and today morning I cannot boot. Actually, it hangs after announcing
> > > it will run fsck. I know that the partition was scheduled to a
> > > routine check after 32 times (I receive a message before shutdown
> > > when that is about to occur), however today the system says that it
> > > will run fsck because the system was not cleanly mounted (which I
> > > do not understand, because I shutdown the system from the command
> > > line last night, no power failure or similar abnormal situation).
> > > Could this inconsistency be related to my problem?
> > >
> > > Anyway, is it possible to bypass the fsck at boot time? I am able to
> > > reach the boot prompt by typing "c" at the boot menu, but beyond
> > > that I don't know what to do. Googling has not helped me as it
> > > leads me to other issues with grub and fsck which do not seem to
> > > give me ideas I can apply to my problem.
> > >
> > > I think that if I can at least skip the check, I could do some work,
> > > check the filesystem manually and try to go ahead somehow.
> >
> > Hi again. Now I've been able to skip the check, after learning that
> > adding the fastboot option at the boot command works. Of course, I do
> > not intend to avoid checks forever, so now the problem is that fsck
> > does not do anything (or doesn't seem to). Some issue with fsck? With
> > my filesystem? Any suggestion as to how to diagnose this?
>
> Did you let fsck complete its check? Sometimes, it takes a while.
> Depends on how big your partitions are. I'm guessing you stopped it
> thinking the boot had frozen. Do the check manually. Use the -V
> (verbose) option, so you can see what's happening.
I realized there was a problem because I turned it on, then forgot
about it, and then looked at the screen about 15-20 minutes later.
There it was, hanging after announcing it would do the check. And
after several trials I convinced myself that it was not doing the
test. Thanks for the suggestion.
I am now doing a long check with smartctl, and see what happens before
attempting new things (a short check on the disk reported no
problems).
Victor
Reply to: