Summary: | gentoo-sources-2.6.31-r10 will not mount ext4 root rw on boot | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | mikopp |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | bug |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kernel config
output of lspci -v showing the kernel driver hdparm output, not sure if it helps dmesg of failed boot |
Description
mikopp
2010-02-26 19:40:16 UTC
Created attachment 221363 [details]
kernel config
Created attachment 221365 [details]
output of lspci -v showing the kernel driver
Created attachment 221367 [details]
hdparm output, not sure if it helps
for me this obviously makes this kernel version unusable. the Notebook is a Dell Latitude 520 This is from my r6 kernel where it does work EXT3-fs: sda4: couldn't mount because of unsupported optional features (240). EXT4-fs (sda4): barriers enabled EXT4-fs (sda4): delayed allocation enabled EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs (sda4): mounted filesystem with ordered data mode VFS: Mounted root (ext4 filesystem) readonly on device 8:4. Does it work with 2.6.32 or .33 kernel series? ( try the latest ~ ) What is set in kernel command line in boot loader? kernel /boot/vmlinuz root=/dev/sda4 I will try with 32 and 33 later this week to see if those work. Could you also test to add "rootfs=ext4" to kernel command line? I will. Can I see your fstab my fstab /dev/sda3 /mnt/portage ext3 noatime,user_xattr 0 1 /dev/sda4 / ext4 noatime,user_xattr 0 1 /dev/sda2 none swap sw 0 0 shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 I can only test your suggestions at the end of the week, so pls post what else I shall test if the suggestions until now fail. Post your full dmesg please. Created attachment 222177 [details]
dmesg of failed boot
rootfs=ext4 makes no difference. i attached the dmesg of the failed boot. I will now try with 32 and 33. In dmesg i found : Filesystem with huge files cannot be mounted RDWR without CONFIG_LBDAF (In reply to comment #16) > In dmesg i found : Filesystem with huge files cannot be mounted RDWR without > CONFIG_LBDAF > That's what I was looking for! Can you please enable that and test. I compared it to the one that works and I guess I found the problem: Working kernel: EXT4-fs (sda4): internal journal on sda4:8 Nonworking : EXT4-fs (sda4): Filesystem with huge files cannot be mounted RDWR without CONFIG_LBDAF the -r6 kernel does not have that set but it does work it seems. the -r10 kernel needs it to support this default ext4 feature I'm trying right now. should have seen that earlier I guess. Anyway this should be handled gracefully in an upgrade somehow. just saw your posts, yeah I saw it too, just wanted to try before I post, but couldn't wait for the compile to finish ;-). we'll know in a bit ok works now. I just checked again, the r6 kernel didn't need this flag and I wasn't even aware that I used the hugefile feature. I know that would be more a question for a forum, but is there a way to get rid of the hugefile option without reformating the filesystem? |