/sbin/e2fsck: No such file or directory while trying to open /dev/sda2
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: Quote:
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? Code:
ls -l /dev/sda* Code:
grep SYSFS /usr/src/linux/.config |
Thanks much - that did the trick - system now works perfectly again!!
|
All times are GMT -5. The time now is 07:02 PM. |