| 1 |
On Sat, Sep 07, 2013 at 09:53:28PM +0300, Alexander Kapshuk wrote: |
| 2 |
> <SNIP> |
| 3 |
> Based on the 'dmesg' output below, EXT2-fs attempted to mount the '/' |
| 4 |
> partition instead of the '/boot' one. |
| 5 |
> |
| 6 |
> box0 ~ # dmesg|grep 'EXT.*fs' |
| 7 |
> [ 2.444214] EXT2-fs (sda3): error: couldn't mount because of |
| 8 |
> unsupported optional features (240) |
| 9 |
> [ 2.444736] EXT4-fs (sda3): couldn't mount as ext3 due to feature |
| 10 |
> incompatibilities |
| 11 |
> [ 2.481412] EXT4-fs (sda3): mounted filesystem with ordered data |
| 12 |
> mode. Opts: (null) |
| 13 |
> [ 9.448819] EXT4-fs (sda3): re-mounted. Opts: (null) |
| 14 |
> [ 9.731383] EXT4-fs (sda5): mounted filesystem with ordered data |
| 15 |
> mode. Opts: (null) |
| 16 |
> |
| 17 |
> Would that suggest a corrupted /boot/grub/grub.conf file? |
| 18 |
> |
| 19 |
> How did the system boot then? |
| 20 |
|
| 21 |
Most likely your /boot partition is not ext2 as stated in fstab and it |
| 22 |
therefore fails to mount (the unsupported optional features hint in that |
| 23 |
direction). |
| 24 |
Simply try to mount it by hand (mount /boot). If that fails try to mount it |
| 25 |
with option -t <filesystem> (for filesystem try ext3 or ext4). |
| 26 |
|
| 27 |
Your system still boots because grub is able to read the filesystem (which |
| 28 |
makes corruption unlikely). grub doesn't use fstab or the drivers in the |
| 29 |
kernelimage (which isn't even loaded at that point of time). |
| 30 |
|
| 31 |
WKR |
| 32 |
Hinnerk |
Archives