View previous topic :: View next topic |
Author |
Message |
cookie n00b
Joined: 26 Feb 2003 Posts: 36 Location: Manchester England
|
Posted: Wed May 21, 2003 1:21 pm Post subject: Problems with SILO |
|
|
Ive installed everything on my sun ultra 5, its taken days, but I cannot for the life of me get silo to work.
I get an error Cannot find /boot/vmlinuz-2.4.20 (Unknown ext2 error)
Ive got the following partition structure
hda1 /boot ext2
hda2 swap swap
hda3 sun whole disk
hda4 / ext3
I read elsewhere that creating a seperate boot partition was a bad idea on suns although this is after going through the install, I really dont want to have to go through all that again.
Any help much appricated
John |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Wed May 21, 2003 2:41 pm Post subject: |
|
|
Hi John,
Typically unknown ext2 errors are caused by SILO not being able to find the kernel specified in your config. One of two possibilities comes to mind;
1) There's a typo in your silo.conf
2) Since you have a seperate boot partition, you may need to put your silo.conf in /boot/etc and then run silo -C /boot/etc/silo.conf to get things to correctly work.
What you can do to try and boot in the meantime is to do this at the silo prompt;
1/vmlinuz-2.4.20 root=/dev/hda4
you can also append any additional kernel arguments to the end of that string.
Let me know how it goes. |
|
Back to top |
|
|
cookie n00b
Joined: 26 Feb 2003 Posts: 36 Location: Manchester England
|
Posted: Thu May 22, 2003 3:40 pm Post subject: Success! |
|
|
Moving silo.conf to /boot/etc/silo.conf and running silo -C seems to have worked I can now boot
Thanks for your help |
|
Back to top |
|
|
Gecklord Apprentice
Joined: 17 Mar 2004 Posts: 174
|
Posted: Tue Mar 23, 2004 2:10 pm Post subject: |
|
|
actually I got the same, at least similar, problem with my silo
I've already tried the tipps - named in this thread, but nothing seems to help (my machine is a ultra80) |
|
Back to top |
|
|
linuxbum Tux's lil' helper
Joined: 20 Dec 2003 Posts: 131 Location: USA
|
Posted: Tue Mar 30, 2004 4:08 pm Post subject: |
|
|
Gecklord
Post your silo.conf for us.
Did you mount /boot then run silo -C MOUNTPOINTOF/boot/silo.conf -f ?
Remember that every time you emerge and there is a new SILO version you will need to do this before you reboot. Or you will get error again. |
|
Back to top |
|
|
Gecklord Apprentice
Joined: 17 Mar 2004 Posts: 174
|
Posted: Tue Mar 30, 2004 4:57 pm Post subject: |
|
|
I finally managed silo to boot from /boot but the kernel image was too big, according to silo
after "modularizing" nearly everthing, silo was still unwilling to boot the kernel, so I copied my vmlinux to /, changed the silo.conf and it's working!
|
|
Back to top |
|
|
linuxbum Tux's lil' helper
Joined: 20 Dec 2003 Posts: 131 Location: USA
|
Posted: Fri Apr 02, 2004 9:51 pm Post subject: |
|
|
Gecklord
After Kernel compile make sure you vmlinux is less than 3.7
Try
Code: | strip -R .comment -R .note vmlinux |
To strip out some of the extra STUFF
ls -lah vmlinux. |
|
Back to top |
|
|
|