After upgrading to the latest major -current changes, my system fails to boot with my old custom kernel (not changed). It does however, boot just fine with the huge-kernel supplied with -current.

So my question is - what's changed on the userlevel side related to e2fs that makes a custom kernel report the following:
The filesystem in question is ext4, and my custom kernel is also 2.6.33, upgraded from 2.6.32.6 which ran just fine before the latest -current upgrade. ext4 is built into the kernel. It seems like the kernel cannot even see the harddisk at all, since entering rescue mode shows cfdisk claiming there is no /dev/sda ...

Disclaimer: Yes - I know custom kernels are not supported "out of the box" - but since I am curious as to what has changed to cause this, I'm still asking, since there definitely is a change somewhere.
The -current-upgrade in question ran fine without warnings, interruptions or any problems.

Thanks in advance for any insight!

-y1

Hi,

Do you have any /dev/sdaX devices?
If not check that you have disable the deprecated sysfs in your custom kernel:
Regards

2 members found this post helpful.

Thanks much - that did the trick - system now works perfectly again!!