You are not logged in.
Hi,
I have custom compiled kernel, that was working very well so far. Recently there must been some upgrades I didn't noticed, because I cannot boot my kernel any more.
Here's what happens with my kernel:
- Root is /dev/sda2 with ext4
- Boot starts off well, /dev/sda2 is mounted according to the log
- when checking file systems, boot stops saying that the partition has some problems, log in as root and fix it
- when I log in, check /etc/mtab, /dev/sda2 listed just as there should be, I can see the whole filesystem, and everything. But /dev/ is missing all the sda entries ....
When I boot the official kernel:
- Everything is mounted, filesystem check passed, boots well....
The reason I think it's a recent change not my kernel is wrong, because downgrading my self-compiled kernel to a version that I used successfully before, that has the same issue as well....
Any ideas?
Offline
Add it into fstab. Should fix it.
Registered User number: 496613. Show your Tux Pride!
http://counter.li.org
Offline
Sure, my mount options are listed in fstab...
But this does not explain why is the entry missing from /dev and then how can I still see the contents but not boot...
Offline
Fu..! I´ve got the same problem. I just made a update and now i am out...
I am missing my sda* entries with my custom kernel! The update broke my system!!!!
Is there a nice broken glibc or something like that?
Last edited by naitsabesn (2010-02-06 01:06:50)
Offline
Fu..! I´ve got the same problem. I just made a update and now i am out...
I am missing my sda* entries with my custom kernel! The update broke my system!!!!
Is there a nice broken glibc or something like that?
Check this other thread: http://bbs.archlinux.org/viewtopic.php?id=90129
Posted a possible solution there.
Offline
Yes, that solved my problem & makes sense...
Thank you very much!!!!!
Offline