W dniu 06.02.2015 o 20:31, Ben Hutchings pisze:
Control: retitle -1 Boot fails due to missing ext4 module
On Fri, 2015-02-06 at 18:48 +0100, Rafał Pietrak wrote:
W dniu 04.02.2015 23:07, Ben Hutchings pisze:
[...]
Severity: grave
Tags: newcomer
Justification: renders package unusable
I've upgraded my LG notebook (X-note: LS50a) from wheezy to jessie and:
1. the upgrade have installed kernel "version-i585" in addition to my earlier
(automatically installed during an upgrade to wheezy) "version-i486".
2. when booting "i486", it fails to modprobe "ext4-fs" during the boot. It
breaks boot sequence, but manual (from shell prompt) modprobe ext4 does not
load the module into the kernel.
Can you clarify how far the system boots? Does it stop at a shell with
the prompt '(initramfs)'?
Stops at: "maintenance mode. Give root password or control-D"
And I think, it does that because /srv/pgdat is ext4 and cannot be
mounted because of missing ext4.ko within the kernel.
I vagually remember the boot stopping at "(initramfs)", but after I've
moved /usr to jfs it is mounted during the boot and the process stops
somewhat farther.
Please send a copy of the /etc/fstab file.
=========/etc/fstab===============
proc /proc proc defaults 0 0
/dev/mapper/vg0-root / xfs defaults 0 1
[...]
So is the root filesystem type really xfs, or is it ext4?
Yes, it's XFS. I didn't bother to change that after "my experimentation
time was done" (I don't mind since my /usr is on a separate partition).
So, at this point only /srv/pgdat is ext4 .... and it looks like it only
rises a problem of missing ext4.ko module when booting kernel
3.2.xxx-486, which was the kernel *number* I used before the upgrade (it
was upgraded by apt-get since); Yet, ext4 are modprobed correctly only
when I boot from 3.16.x-586 kernel, which jessie have installed on this
machine.
One additional info regarding keyboard:
1. currently, after the upgrade I have six entries in my grub.menu: 1)
linux-586, 2) linux-586 (sysvinit), 3) linux-586 (recover), 4)
linux-486, 5) linux-486 (sysvinit), and 6) linux-486 (recover)
2. when I boot (5) (e.g.: linux-486/sysvinit) I get the notebook
keyboard working correctly. No other boot does that.
-R
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54d538c2.4030...@ztk-rp.eu
