You are not logged in.
I am having issues booting after upgrade from Linux 4.5.4-1 -> 4.6.2-1
When I boot I get a garbled message which is something to do with "dirent pino" and the dumped to rootfs# [EDIT] The last entry in dmesg is "F2FS-fs (sda2) Cannot load crc32 driver"
I am able to boot into Linux-lts (this was upgraded from 4.4.12-1 -> 4.4.13-1 at the same time). It gives me a similar message during boot but goes ahead and finishes a normal boot into KDE.
A Google search shows some patch was made to f2fs-dev in March, but I can't see that any update to the f2fs or crc32 packages in Arch has been done lately, so I am assuming this is linked to the linux update.
Any ideas?
Last edited by Aitch (2016-06-17 17:47:34)
Offline
Update: CAN SOMEONE PLEASE HELP ME?
I found on the F2FS filesystem page this note:
The driver included in the kernel 4.6 or higher uses Crypto API for computing CRC32. Add crc32_generic and crc32-pclmul to the MODULES array in /etc/mkinitpcio.conf and regenerate the initramfs if the driver fails to load a CRC32 module at boot.
As I can boot into 4.4.13-1-lts I tried running chroot (from the wiki instructions here) but when I regenerate initramfs it says
==> ERROR: module not found: `crc_generic'
==> ERROR: module not found: `crc-pclmul'
modprobe gives
modprobe: FATAL: Module crc_generic not found in directory /lib/modules/4.4.13-1-lts
In my chroot environment how do I get modprobe to look in /lib/modules/4.6.2-1-ARCH?
Offline
Offline
Duh
Thanks slithery, when will I learn to double check the simple things???
Initramfs regenerated and I'm able to boot again. I am still getting the message above but I can look at that in my own time.
NOTE: I would have thought a change that breaks booting from any drive using F2FS for the root partition would have deserved a news item on the Home page! Or am I the only Archlinux instance doing this?
Offline
Or am I the only Archlinux instance doing this?
Nope, searching the forums before posting would have led you to this solved thread.
Offline
Ah yes, hindsight is a wonderful thing. Afraid I was focused on the "dirent pino" portion of the boot error message. Searching on that produced nothing.
Thanks again for your help slithery, but I still think there should be a message to make all users aware of this issue before upgrading to the 4.6.2 kernel.
Offline