1 |
2013/9/9 Hinnerk van Bruinehsen <h.v.bruinehsen@×××××××××.de> |
2 |
|
3 |
> On Sat, Sep 07, 2013 at 09:53:28PM +0300, Alexander Kapshuk wrote: |
4 |
> > <SNIP> |
5 |
> > Based on the 'dmesg' output below, EXT2-fs attempted to mount the '/' |
6 |
> > partition instead of the '/boot' one. |
7 |
> > |
8 |
> > box0 ~ # dmesg|grep 'EXT.*fs' |
9 |
> > [ 2.444214] EXT2-fs (sda3): error: couldn't mount because of |
10 |
> > unsupported optional features (240) |
11 |
> > [ 2.444736] EXT4-fs (sda3): couldn't mount as ext3 due to feature |
12 |
> > incompatibilities |
13 |
> > [ 2.481412] EXT4-fs (sda3): mounted filesystem with ordered data |
14 |
> > mode. Opts: (null) |
15 |
> > [ 9.448819] EXT4-fs (sda3): re-mounted. Opts: (null) |
16 |
> > [ 9.731383] EXT4-fs (sda5): mounted filesystem with ordered data |
17 |
> > mode. Opts: (null) |
18 |
> > |
19 |
> > Would that suggest a corrupted /boot/grub/grub.conf file? |
20 |
> > |
21 |
> > How did the system boot then? |
22 |
> |
23 |
> Most likely your /boot partition is not ext2 as stated in fstab and it |
24 |
> therefore fails to mount (the unsupported optional features hint in that |
25 |
> direction). |
26 |
> Simply try to mount it by hand (mount /boot). If that fails try to mount it |
27 |
> with option -t <filesystem> (for filesystem try ext3 or ext4). |
28 |
> |
29 |
> Your system still boots because grub is able to read the filesystem (which |
30 |
> makes corruption unlikely). grub doesn't use fstab or the drivers in the |
31 |
> kernelimage (which isn't even loaded at that point of time). |
32 |
> |
33 |
> WKR |
34 |
> Hinnerk |
35 |
> |
36 |
|
37 |
Could it be that the partition was formated using EXT2 extended properties |
38 |
from a previous kernel built with those options, and now this new kernel |
39 |
that has just been built, has those extended options missing? |
40 |
|
41 |
Just my 2 cents. |
42 |
|
43 |
Francisco |