From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id DBBEE1381F3 for ; Mon, 9 Sep 2013 11:45:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 10F20E0ACF; Mon, 9 Sep 2013 11:45:24 +0000 (UTC) Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 14AF4E0AA5 for ; Mon, 9 Sep 2013 11:45:22 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id m6so6226225oag.4 for ; Mon, 09 Sep 2013 04:45:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=fi88Uwa71IQaY92vemQEIfZV6VfCiAXJs5EeJo1xTSw=; b=Z3ab9oDMNFIaNkLmzlft9CQK0arQJby9ik4UJOErBpjBlD2SQ4e3qc7Drm174IRFOq PuiC6Avv4u+Il67mdoCrTUBsLqEHtEvVdnOfjMsG2MbIc9YspNNXycQyBP+jHgs9BKrp jzVQUuJWcfb021sxal45d09vJUeqsZWD8mcWFMQ2bWIQbL5Qqkxdw+34PGitzU1XNbxO 0FatiyAxybL62CFuIkxImieAOXXPN7vPBU4RKIr0OfElEEzYl15mhxSCBL61uYe4yCLE xb6TJlHbbsuHd8YxZeze6fFI9hjCwr6+3EiHX8GkT9FQ33xHhSLgJiQe4iHnjX+/YUQ9 hQDw== X-Received: by 10.60.58.10 with SMTP id m10mr106882oeq.61.1378727122185; Mon, 09 Sep 2013 04:45:22 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.60.52.79 with HTTP; Mon, 9 Sep 2013 04:44:41 -0700 (PDT) In-Reply-To: <20130909095931.GA9720@bifrost.zedat.fu-berlin.de> References: <522B6B12.2040903@gmail.com> <522B6F69.1060104@gmail.com> <522B7628.3000303@gmail.com> <20130909095931.GA9720@bifrost.zedat.fu-berlin.de> From: Francisco Ares Date: Mon, 9 Sep 2013 08:44:41 -0300 Message-ID: Subject: Re: [gentoo-user] re: can't find /boot/grub/grub.conf after kernel upgrade [3.10.7] To: gentoo-user Content-Type: multipart/alternative; boundary=089e01538bc45c335504e5f1ec21 X-Archives-Salt: 8986cf5d-a8a2-48a8-9c77-0bae712de7d5 X-Archives-Hash: ecf7628fe3cdd846dd6fabb288851c34 --089e01538bc45c335504e5f1ec21 Content-Type: text/plain; charset=UTF-8 2013/9/9 Hinnerk van Bruinehsen > On Sat, Sep 07, 2013 at 09:53:28PM +0300, Alexander Kapshuk wrote: > > > > 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 (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 > Could it be that the partition was formated using EXT2 extended properties from a previous kernel built with those options, and now this new kernel that has just been built, has those extended options missing? Just my 2 cents. Francisco --089e01538bc45c335504e5f1ec21 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= 2013/9/9 Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de= >
On Sat, Sep 07, 2013 at 09:53:28PM +0300, Al= exander 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'
> [ =C2=A0 =C2=A02.444214] EXT2-fs (sda3): error: couldn't mount bec= ause of
> unsupported optional features (240)
> [ =C2=A0 =C2=A02.444736] EXT4-fs (sda3): couldn't mount as ext3 du= e to feature
> incompatibilities
> [ =C2=A0 =C2=A02.481412] EXT4-fs (sda3): mounted filesystem with order= ed data
> mode. Opts: (null)
> [ =C2=A0 =C2=A09.448819] EXT4-fs (sda3): re-mounted. Opts: (null)
> [ =C2=A0 =C2=A09.731383] EXT4-fs (sda5): mounted filesystem with order= ed 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<= br> makes corruption unlikely). grub doesn't use fstab or the drivers in th= e
kernelimage (which isn't even loaded at that point of time).

WKR
Hinnerk

Could= it be that the partition was formated using EXT2 extended properties from = a previous kernel built with those options, and now this new kernel that ha= s just been built, has those extended options missing?

Just my 2 cents.

Francisco
--089e01538bc45c335504e5f1ec21--