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.
check the lilo configuration (assuming that lilo is the boot loader); use the installation cd as a rescue cd (type "rescue" to boot the cd into rescue mode)
Are you booting the graphical interface. It's not very informative, however, hitting the F2 or F3 (I can't remember right now), will put you in Verbose mode and you'll be able to see where it's hanging or you can do a step through process.
It may also be checking the partitions which awhile, however, I beleive it that was the case it would automatically dump you in verbose mode.
As "mike33" said, could be that LiLo is just pointing to the wrong drive or partition...
Here, the issue is that I cannot boot to complete
the full installation. That is, near the end of install
phase, the system would auto-reboot for some kind of
post-installation configurations, right? It's here where
I'm always stuck no matter how many installs and reinstalls
I do.
As stated in my previous reply-post, I'd checked the lilo
configuration for the correct kernel image, and this looked
just right.
So, if anyone has any idea what I should be looking for
when I use my rescue CD, I'll be much thankful.
With a rescue CD you can access the files on your drive for reading and writing, using the kernel on the cd. Assuming that you get a root command prompt via the cd, you can mount the partition that you installed linux on, and for example modify the lilo configuration file, which should be at /etc/lilo.conf, (but then you should rerun lilo by chrooting to the directory where you mounted the partition). From the rescue cd prompt you can run the command
Code:
fdisk -l
to list the partitions available.
It would help if you gave us more information though, such as: the type and number of hard drives, whether this is a dual boot system or not, how the drives were partitioned, and so on. You can find out much of this with a rescue cd. For example, if you have an ext3 filesystem on the partition /dev/hda7, then from the rescue cd you can mount it say at /mnt with the command
I've put aside Mandrake for now as SuSE 9.3 Pro
replaced its place on my dual boot system. I will
certainly look into your options when I return to
Mandrake sooner or later.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.