public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] re: can't find /boot/grub/grub.conf after kernel upgrade [3.10.7]
Date: Mon, 9 Sep 2013 11:59:31 +0200	[thread overview]
Message-ID: <20130909095931.GA9720@bifrost.zedat.fu-berlin.de> (raw)
In-Reply-To: <522B7628.3000303@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]

On Sat, Sep 07, 2013 at 09:53:28PM +0300, Alexander Kapshuk wrote:
> <SNIP>
> Based on the 'dmesg' output below, EXT2-fs attempted to mount the '/'
> partition instead of the '/boot' one.
>
> box0 ~ # dmesg|grep 'EXT.*fs'
> [    2.444214] EXT2-fs (sda3): error: couldn't mount because of
> unsupported optional features (240)
> [    2.444736] EXT4-fs (sda3): couldn't mount as ext3 due to feature
> incompatibilities
> [    2.481412] EXT4-fs (sda3): mounted filesystem with ordered data
> mode. Opts: (null)
> [    9.448819] EXT4-fs (sda3): re-mounted. Opts: (null)
> [    9.731383] EXT4-fs (sda5): mounted filesystem with ordered data
> mode. Opts: (null)
>
> Would that suggest a corrupted /boot/grub/grub.conf file?
>
> How did the system boot then?

Most likely your /boot partition is not ext2 as stated in fstab and it
therefore fails to mount (the unsupported optional features hint in that
direction).
Simply try to mount it by hand (mount /boot). If that fails try to mount it
with option -t <filesystem> (for filesystem try ext3 or ext4).

Your system still boots because grub is able to read the filesystem (which
makes corruption unlikely). grub doesn't use fstab or the drivers in the
kernelimage (which isn't even loaded at that point of time).

WKR
Hinnerk

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2013-09-09  9:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 18:06 [gentoo-user] re: can't find /boot/grub/grub.conf after kernel upgrade [3.10.7] Alexander Kapshuk
2013-09-07 18:11 ` Canek Peláez Valdés
2013-09-07 18:24   ` Alexander Kapshuk
2013-09-07 18:35     ` Canek Peláez Valdés
2013-09-07 18:53       ` Alexander Kapshuk
2013-09-07 19:25         ` Canek Peláez Valdés
2013-09-07 19:30           ` Alexander Kapshuk
2013-09-07 19:35             ` Canek Peláez Valdés
2013-09-07 19:41               ` Alexander Kapshuk
2013-09-07 20:11                 ` Canek Peláez Valdés
2013-09-07 20:15                   ` Alexander Kapshuk
2013-09-07 21:31                     ` meino.cramer
2013-09-08 15:20                       ` Bruce Hill
2013-09-08 16:09                         ` [gentoo-user] re: can't find /boot/grub/grub.conf after kernel upgrade [3.10.7] [SOLVED] Alexander Kapshuk
2013-09-07 21:43                   ` [gentoo-user] re: can't find /boot/grub/grub.conf after kernel upgrade [3.10.7] gottlieb
2013-09-09  9:59         ` Hinnerk van Bruinehsen [this message]
2013-09-09 11:44           ` Francisco Ares

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130909095931.GA9720@bifrost.zedat.fu-berlin.de \
    --to=h.v.bruinehsen@fu-berlin.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox