LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 07-07-2005, 01:15 PM   #16
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled

Okay, new info:


From /mnt/ I can use sbin/lilo, but then I get the error message: /etc/lilo.conf no such file or directory. If I am interpreting this right, the lilo program can't find the lilo.conf file, but it is clearly there... What on earth should I do? Thanks,

-Felix
 
Old 07-07-2005, 02:13 PM   #17
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,144

Rep: Reputation: 56
try this

# /mnt/sbin/lilo -C /mnt/etc/lilo.conf

See if it does the trick. -C option gives the location of config file.

Tux,
 
Old 07-07-2005, 02:32 PM   #18
TomAnderson
LQ Newbie
 
Registered: Jul 2005
Posts: 3

Rep: Reputation: 0
Space charcater in linux volume name

From one newbie to another...

You didnīt by chance have a space (ī ī) character in the name of the linux partition did you? I called mine "Fedora Core 4" and GRUB had a problem with it. I reformatted and renamed it to FC4 and re-installed, which worked fine after that...

Good luck

Tom
 
Old 07-07-2005, 02:36 PM   #19
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,144

Rep: Reputation: 56
Are you talking about empty space in the title field of grub config file?
 
Old 07-07-2005, 03:33 PM   #20
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled
Hi,

Thanks for that tip, I am about to go try it out. In the meantime, however, I figured that the reason it wasn't working was because LILO was looking for the config in /etc/lilo.conf, while under the rescue system it really is in /mnt/etc/lilo.conf. So I copied the file into /etc/, which for some surprising reason actually worked. When I tried running LILO, however, it said it could not write because it was read only. I may be completely off base here, but my explanation for this is that while running rescue, root is actually the CD, and the harddrive is under /mnt/, so LILO tried to write to root, which obviously it could not do since it is a CD-ROM. This explanation does not, however, match up with me being able to copy files onto what (if I am right) was the cd. Any ideas what happened there?

Either way, I will now go try your suggestion, and thanks!

-Felix


Edit/Update:

I tried and got the same error as I did with what I did:
Fatal: creat (sic) boot/map~ Read-only filesystem.

Any ideas?

Last edited by felixc; 07-07-2005 at 03:36 PM.
 
Old 07-07-2005, 06:11 PM   #21
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled
Hi everyone, once again,

Since no-one seems to know the answer to that, I will abandon that route for now. Instead, does anyone know what was wrong with my GRUB bootloader? I have given details about it above. This post is essentially just a summary of what I am having trouble with, namely:



1) Windows won't load. Says "booting from floppy is disabled" even when there is no floppy, and asks me to use a bootloader, says this even when using a bootloader.




2) GRUB will not load linux. I have

# boot Mandriva Linux from hda2
title Mandriva Linux
root (hd0,1)
kernel /boot/vmlinuz root=/dev/hda2

in my menu.lst file, and all I get is

VFS: Cannot open root device hda2 or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)



3) LILO won't run so that I can apply the updates to my lilo.conf file. I get:

Fatal: creat boot/map~ Read-only filesystem.




4) Loadlin needs vmlinuz to be copied to windows root partition, how do I do this? (irrelevant if I can't fix problem 1)



Thank you to everyone who has tried to help so far, and in advance to whoever can solve these riddles,

-Felix
 
Old 07-07-2005, 07:25 PM   #22
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,144

Rep: Reputation: 56
Hey Felix,
As I've already mentioned, I'm not good with Lilo but I know quite a bit about grub. I've actually written a how-to on grub since I like to document what I do.

Here's the tutorial I wrote. Please read it through and you would understand a few things about grub.

As far as your grub problem is concerned, I posted the problem with your grub config file in one of my previous post.

Tux,
 
Old 07-07-2005, 07:35 PM   #23
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled
Hi,

Thanks for the link, I am reading through it right now. I fixed what you said was wrong and now have a different problem with GRUB, as outlined in the above post. Thanks,

-Felix
 
Old 07-07-2005, 08:44 PM   #24
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled
Latest info:

GRUB - Still no progress. I updated it like tuxrules suggested, and took a look at his file. Everything looks like it should, this is it

# boot Mandriva Linux from hda2
title Mandriva Linux
root (hd0,1)
kernel (hd0,1)/boot/vmlinuz root=/dev/hda2

but it does not work and I get

VFS: Cannot open root device hda2 or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


-----


LILO- I managed to circumvert my previous problem with chroot, and ran lilo to update its config. However, no luck, same error message

Mounting root filesystem with flags noatime
mount: error 6 mounting ext3 flags noatime
well, retrying without the option flags
mount: error 6 mounting ext3
well, retrying read-only without any flag
mount: error 6 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/sys failed: 2
umount /initrd/proc failed: 2
Initrd finished
Freeing unused kernel memory: 240k freed
Kernel panic - not syncing: no init found. Try passing init= option to kernel.


-------


Windows - Still refusing to boot.



Thanks in advance,

-Felix
 
Old 07-07-2005, 10:16 PM   #25
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,144

Rep: Reputation: 56
try adding 'ro' option before the root=/dev/hda2 in the grub config file like i've shown below...its a guess and might work

Code:
kernel (hd0,1)/boot/vmlinuz ro root=/dev/hda2
Also are you sure the kernel is called vmlinuz since I doubt with that...

Edit: Also if you have initrd file, which i think you do, include that line below the kernel line.

initrd (hd0,1)/boot/name of initrd file

The error message that you get is most likely related to missing initrd or improper naming.

Tux,

Last edited by tuxrules; 07-07-2005 at 10:20 PM.
 
Old 07-08-2005, 10:12 AM   #26
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled
Thanks again, making progress once more;

I added the ro where you suggested, and also added the initrd line just after it. Now GRUB gives me the same error message as LILO, namely

Mounting root filesystem with flags noatime
mount: error 6 mounting ext3 flags noatime
well, retrying without the option flags
mount: error 6 mounting ext3
well, retrying read-only without any flag
mount: error 6 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/sys failed: 2
umount /initrd/proc failed: 2
Initrd finished
Freeing unused kernel memory: 240k freed
Kernel panic - not syncing: no init found. Try passing init= option to kernel.

This looks like there is a problem with the initrd part, but I have checked and rechecked the filename, and I am definitely specifying the right one. Maybe my file is incomplete or damaged? How would I fix that?

My menu.lst file for the floppy disk GRUB now reads:

# boot Mandriva Linux from hda2
title Mandriva Linux
root (hd0,1)
kernel (hd0,1)/boot/vmlinuz ro root=/dev/hda2
initrd (hd0,1)/boot/initrd-2.6.11-6mdk-i586-up-1GB.img

As for the kernel name, in the boot dir I have one file called vmlinuz and one called vmlinuz-2.6.11-6mdk-i586-up-1GB, which seems to match up nicely with the initrd's filename. I will try changing the kernel name to that, and see what happens. However, as I said, I think the problem is with the initrd file. Thanks again,

-Felix

Edit: Changed kernel name, menu.lst now reads

# boot Mandriva Linux from hda2
title Mandriva Linux
root (hd0,1)
kernel (hd0,1)/boot/vmlinuz-2.6.11-6mdk-i586-up-1GB ro root=/dev/hda2
initrd (hd0,1)/boot/initrd-2.6.11-6mdk-i586-up-1GB.img

Receiving same error

Last edited by felixc; 07-08-2005 at 10:16 AM.
 
Old 07-08-2005, 10:42 AM   #27
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,144

Rep: Reputation: 56
you dont have a seperate boot partition do you??? Post your output of the command

# fdisk -l (it is lowercase "L")

Tux,
 
Old 07-08-2005, 10:52 AM   #28
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled
Well, I certainly didn't create a separate partition for it, but fdisk reports that there is a mysterious partition that I did not create, and that is overlapping with the swap partition. Anyway, this is what it gives me (I have excluded the Blocks since they were a pain to copy and I dont think they're necessary - If they are I'll post them:


Code:
Device Boot         Start        End       Blocks      Id             System
/dev/hda1           1              3                   c              W95 FAT32 (LBA)
/dev/hda2           338          516                   83             Linux
/dev/hda3           517          526                   5              Extended
/dev/hda5           517          526                   82             Linux swap
I hope this bears some resemblance to a table in your browser


This may not be exact, some of the numbers may be a bit off, I produced this by running back and forth between two rooms, however it should give you a general idea. Thanks,

-Felix

Last edited by felixc; 07-08-2005 at 10:55 AM.
 
Old 07-08-2005, 10:59 AM   #29
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,144

Rep: Reputation: 56
thats not a mysterious partition. Its an extended partition within which your swap is contained. It just happens so that swap takes up entire extended partition. Nothing abnormal there.

I'm stumped man! You could google with the error you get and you'll get some leads.

Good luck
Tux,
 
Old 07-08-2005, 11:17 AM   #30
felixc
Member
 
Registered: Jul 2005
Distribution: Debian
Posts: 94

Original Poster
Rep: Reputation: Disabled
Thanks for trying, anyway...

A google search for that error was what led me here in the first place, but I just did another one, and it seems like the error may have something to do with technical language I don't understand. Other people have mentioned something about the ext3 filesystem not being built into the kernel but loaded as a module (or something similar), and have "rebuilt" their kernel with support for this. I don't know if this makes any sense, I may just have misinterpreted some things. Either way, does anyone have any suggestions? Thanks,

-Felix
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
GRUB LILO boot floppy idris1388 Linux - Software 2 04-12-2005 07:53 AM
LILO did not overwrite GRUB- can't boot riemann_noodles Linux - General 2 03-03-2005 08:48 PM
lilo and grub won't boot winXP mshahwan Linux - Software 2 10-21-2004 08:57 PM
no LILO, no GRUB, NO BOOT !!! mioche Linux - Newbie 4 08-25-2003 06:55 AM
can linux boot without lilo or grub? murshed Linux - General 13 06-01-2002 06:39 AM


All times are GMT -5. The time now is 05:32 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration