Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 have a disk with several partitions (two with Windows XP, one for data only, and one for Linux Red Hat 8). I don't want Linux to mess up my MBR, so I executed grub to install on the partition where Linux is; /dev/hda7. I get errors however when I boot to my Linux partition with grub:
mounting root file system
EXT2-fs: unable to read superblock
mount: error 22 mounting ext2
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
kernel panic: no init found
I tried to put init=/bin/bash, init=/sbin/init, and init=bin/sh on the kernel command, without any success. I used Red Hat 2.4.18-14.
Now, when I boot from my startup floppy disk, everything works smoothly! So I presume it's not really a problem with the filesystem, but with the configuration. Does anyone have an idea?
well i always use lilo because it's easier. first of all, lilo will not screw up your MBR. lilo is a better bootloader than windows uses. hell NTloader doesn't even recognize linux! i would suggest putting lilo in your MBR. if you have problems, you can always fdisk mbr and lilo is gone. its that simple.
but since you used grub, lets see what we can do. i'm no expert on grub but if you look at your file, you said you installed linux on /dev/hda7 yet you are telling grub root is on /dev/hd06??? so my guess is you are getting errors because grub is looking for root on /dev/hd06 when it's really on /dev/hda7.
also, if your system boots properly from your bootdisk, take a look at the config files on the bootdisk and see where it's telling the loader to look for root.
Last edited by TheWalkingDead; 08-02-2003 at 12:25 PM.
Ok, it works now. I just stopped trying doing it manually, and created the grub.conf file, which I customized as follows:
default=0
timeout=0
splashimage=(hd0,6) /boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.18-14)
root (hd0,6)
kernel /boot/vmlinuz-2.4.18-14 ro root=LABEL=/ hdd=ide-scsi
initrd /boot/initrd-2.4.18-14.img
Everything works now, and the MBR was not touched - all's done on the hda7 partition only.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.