SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I compiled and installed kernel 2.6 and the modules according to all the readme's, but during the boot process I got the following message:
mount: mounting /dev/sda9 on /mnt failed: No such device or address
ERROR: mount returned error code 1. Trouble ahead.
mount: mounting /dev/sda9 on /mnt failed: Invalid argument
/boot/initrd.gz: exiting
I can't figure out what can cause this problem.
Filesystem support was compiled in the kernel (as well as Sata controller drivers). I didn't find any reference to (module) jbd in the menuconfig options which seems to be necessary for a ext3 filesystem, except for debugging support which I don't use. The file load_kernel_modules in the boot directory was empty except for some comment lines. Do I have to fill this file manually?
Here is a condensed version of my fstab:
/dev/hda5 /__NTFS_DATA ntfs
/dev/hda6 /__NTFS_GAMES ntfs
/dev/sda9 / ext3
/dev/sda10 /var ext3
/dev/sda11 /tmp ext3
/dev/sda12 /opt ext3
/dev/sda13 /home ext3
/dev/sda3 /boot ext3
I followed the README in the boot directory, which is the same as the mini howto.
This is my lilo.conf (and I ran lilo after making changes)
boot = /dev/sda
message = /boot/boot_message.txt
prompt
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x32k
vga = 790
other = /dev/sda1
label = Windows
table = /dev/sda
image = /boot/vmlinuz
initrd = /boot/initrd.gz
root = /dev/sda9
label = Linux
read-only
I didn't place lilo in the MBR, but in the root section. Could that make any difference? (sda1 is the first bootable NTFS partition, sda9 the root partition which is a logical partition).
As I also said that the file load_kernel_modules is empty, is that normal and if not how does it get filled with modules?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.