Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26775 - Kernel 3.1 doesn't mount ext2 /boot partition (unknown filesystem type 'ext2')

Attached to Project: Arch Linux
Opened by Jonnathan Campos (jonnyxdoc) - Monday, 07 November 2011, 07:22 GMT
Last edited by Tom Gundersen (tomegun) - Sunday, 13 November 2011, 09:27 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I got this error when installed Linux kernel 3.1 (with /boot mounted) and tried to mount /boot manually after rebooting (because it doesn't automount at boot despite settings in /etc/fstab):

mount: unknown filesystem type 'ext2'

This error causes a 'uname -r' mismatch: no module loaded.

Because this, I downgraded to 3.0.7.

Additional info:
* package version(s): linux-3.1-3
* config and/or log files etc.

/etc/fstab:

/dev/sda1 none swap sw 0 0
/dev/sda3 / jfs noatime 0 1
/dev/sda2 /boot ext2 defaults 1 2
/dev/sr0 /media/cdrom auto noauto,user 0 0

Steps to reproduce:
-At installation, create a separated, ext2-formatted /boot partition. Mount all partitions.
-Activate testing in pacman.conf
-pacman -Suy after a fresh installation (installs linux-3.1-3 as an update, triggering mkinitcpio -p linux).
-pacman grub2-bios
-grub2-mkconfig -o /boot/grub/grub.cfg
-grub-install /dev/sda
-Reboot
This task depends upon

Closed by  Tom Gundersen (tomegun)
Sunday, 13 November 2011, 09:27 GMT
Reason for closing:  No response
Additional comments about closing:  Probably not a bug. Reopen otherwise.
Comment by Dave Reisner (falconindy) - Monday, 07 November 2011, 11:19 GMT
Cannot reproduce. I have multiple VMs with this configuration all running testing (and up to date).

If you're implying that a 'uname -r mismatch' means that uname still shows 3.0-ARCH and not 3.1.0-3-ARCH, then I cannot believe your claim that /boot wasn't mounted when you installed the new kernel.
Comment by Dave Reisner (falconindy) - Thursday, 10 November 2011, 00:58 GMT
ping?
Comment by Jonnathan Campos (jonnyxdoc) - Thursday, 10 November 2011, 12:28 GMT
I will update the kernel, if any problem occurs, it will be reported; if not, this thread can be closed.

Loading...