[opensuse] GRUB error - can anyone help please?
Suddenly I cannot boot into 10.1 with GRUB coming up with, "Error 18" as soon as it starts to execute on bootup. Does anyone know what this error means and how to get grub working correctly again? I suppose I could recreate grub (through Yast2) but I don't want to do this in case I do more damage than I already have. The only way I am currently booting into 10.1 is the Installation route and booting into an existing system (but because I also dual-boot doing it this way doesn't get me into Windows [if I need to, that is]). Any help appreciated. Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-11-25 at 20:47 +1100, Basil Chupin wrote:
Suddenly I cannot boot into 10.1 with GRUB coming up with, "Error 18" as soon as it starts to execute on bootup.
Does anyone know what this error means and how to get grub working correctly again?
info grub, Troubleshooting, Stage2 errors: | 18 : Selected cylinder exceeds maximum supported by BIOS | This error is returned when a read is attempted at a linear block | address beyond the end of the BIOS translated area. This generally | happens if your disk is larger than the BIOS can handle (512MB for | (E)IDE disks on older machines or larger than 8GB in general). Create a separate /boot partition somewhere near the begingining of your hard disk. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFaCdBtTMYHG2NR9URAgaPAJ47+ByueUuinMieBrm3yERlDUo9lACfZAQz zK72UtMAtq5jwf36TqA13Ms= =JRHn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-11-25 at 20:47 +1100, Basil Chupin wrote:
Suddenly I cannot boot into 10.1 with GRUB coming up with, "Error 18" as soon as it starts to execute on bootup.
Does anyone know what this error means and how to get grub working correctly again?
info grub, Troubleshooting, Stage2 errors:
| 18 : Selected cylinder exceeds maximum supported by BIOS | This error is returned when a read is attempted at a linear block | address beyond the end of the BIOS translated area. This generally | happens if your disk is larger than the BIOS can handle (512MB for | (E)IDE disks on older machines or larger than 8GB in general).
Create a separate /boot partition somewhere near the begingining of your hard disk.
Thanks for the response but, eh, I have been dual-booting for years now and therefore already have a 300MB boot partition at the start of the HD, and have been running 10.1 without any problems since it came out until this morning when the error message suddenly came up. (Just checked with cfdisk and all the partitions are there as they are supposed to be.) Checked in the BIOS and all drives are correctly recognised. Any other suggestions, please? Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 25 November 2006 05:03, Basil Chupin wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-11-25 at 20:47 +1100, Basil Chupin wrote:
Suddenly I cannot boot into 10.1 with GRUB coming up with, "Error 18" as soon as it starts to execute on bootup.
Does anyone know what this error means and how to get grub working correctly again?
info grub, Troubleshooting, Stage2 errors: | 18 : Selected cylinder exceeds maximum supported by BIOS | This error is returned when a read is attempted at a linear block | address beyond the end of the BIOS translated area. This generally | happens if your disk is larger than the BIOS can handle (512MB for | (E)IDE disks on older machines or larger than 8GB in general).
Create a separate /boot partition somewhere near the begingining of your hard disk.
Thanks for the response but, eh, I have been dual-booting for years now and therefore already have a 300MB boot partition at the start of the HD, and have been running 10.1 without any problems since it came out until this morning when the error message suddenly came up. (Just checked with cfdisk and all the partitions are there as they are supposed to be.)
Checked in the BIOS and all drives are correctly recognised.
Any other suggestions, please?
Can you view the menu.lst file at the grub prompt(grub>) and do the entries match your current partitioning setup? grub> cat (hd0,0)/boot/grub/menu.lst where (hd0,0) represents (drive#,partition#) with numbering starting at zero and pointing to the partition holding menu.lst which should be your separate boot partition assuming grub was installed there originally and not to the root partition. (hd0,0) would point to the 1st partition on the 1st drive. (hd1,3) would point to the 4th partition on the second drive, etc... grub> geometry (hdx) will show existing partitions(x=0,1,2 etc.) . Can you boot from the grub prompt manually? ie. grub> root (hdx,x) grub> kernel /vmlinuz root=/dev/hdx <other options> grub> initrd /initrd grub> boot with appropriate modifications if you altered the default installation image names. where x points to appropriate partition. Note that unlike (hdx,x)mentioned above, root=/dev/hdx, numbering starts at 1 and points to root partition, not the boot partition. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
rmyster@gmail.com wrote:
On Saturday 25 November 2006 05:03, Basil Chupin wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-11-25 at 20:47 +1100, Basil Chupin wrote:
Suddenly I cannot boot into 10.1 with GRUB coming up with, "Error 18" as soon as it starts to execute on bootup.
Does anyone know what this error means and how to get grub working correctly again? info grub, Troubleshooting, Stage2 errors: | 18 : Selected cylinder exceeds maximum supported by BIOS | This error is returned when a read is attempted at a linear block | address beyond the end of the BIOS translated area. This generally | happens if your disk is larger than the BIOS can handle (512MB for | (E)IDE disks on older machines or larger than 8GB in general).
Create a separate /boot partition somewhere near the begingining of your hard disk. Thanks for the response but, eh, I have been dual-booting for years now and therefore already have a 300MB boot partition at the start of the HD, and have been running 10.1 without any problems since it came out until this morning when the error message suddenly came up. (Just checked with cfdisk and all the partitions are there as they are supposed to be.)
Checked in the BIOS and all drives are correctly recognised.
Any other suggestions, please?
Thanks for your help. The results:
Can you view the menu.lst file at the grub prompt(grub>) and do the entries match your current partitioning setup?
grub> cat (hd0,0)/boot/grub/menu.lst
Yes.
where (hd0,0) represents (drive#,partition#) with numbering starting at zero and pointing to the partition holding menu.lst which should be your separate boot partition assuming grub was installed there originally and not to the root partition. (hd0,0) would point to the 1st partition on the 1st drive. (hd1,3) would point to the 4th partition on the second drive, etc...
grub> geometry (hdx)
will show existing partitions(x=0,1,2 etc.) .
Geometry OK. All partitions correctly shown (both HDs, btw).
Can you boot from the grub prompt manually?
ie. grub> root (hdx,x)
This is OK.
grub> kernel /vmlinuz root=/dev/hdx <other options>
This is OK.
grub> initrd /initrd
This comes up with an error, "Error 28: Selected item cannot fit into memory" which is a bit strange as I have 1.5GB of RAM and even right at the moment I have 58.5MB free.
grub> boot
Of course this does not happen :-) . What does all of the above mean? Do I need a grease and oil change or a new set of spark plugs? :-) Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-11-26 at 02:11 +1100, Basil Chupin wrote:
grub>initrd /initrd
This comes up with an error, "Error 28: Selected item cannot fit into memory" which is a bit strange as I have 1.5GB of RAM and even right at the moment I have 58.5MB free.
|28 : Selected item cannot fit into memory | This error is returned if a kernel, module, or raw file load | command is either trying to load its data such that it won't fit | into memory or it is simply too big. Check that file, perhaps it is broken somehow. Usually, "/boot/initrd" is a symlink, so check the link and the destination. Also, you can try to expand it on a temporary dir, it is gzipped. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFaGchtTMYHG2NR9URAjR9AJ4nDFT915eJ/JsQBLpk66psVkFUhwCeNxVH Iy3IS5zufAv5Aq/oYdHD7hA= =KG2B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2006-11-26 at 02:11 +1100, Basil Chupin wrote:
grub>initrd /initrd This comes up with an error, "Error 28: Selected item cannot fit into memory" which is a bit strange as I have 1.5GB of RAM and even right at the moment I have 58.5MB free.
|28 : Selected item cannot fit into memory | This error is returned if a kernel, module, or raw file load | command is either trying to load its data such that it won't fit | into memory or it is simply too big.
Check that file, perhaps it is broken somehow. Usually, "/boot/initrd" is a symlink, so check the link and the destination. Also, you can try to expand it on a temporary dir, it is gzipped.
Well, if it[1] was broken then I wouldn't be able to boot into the installed system from the Installation CD/DVD, and if it couldn't fit into memory then, again, it wouldn't fit when booting from the Installation CD. Something very weird going on here and I cannot figure it out. I used the Repair System from the Installation CD and when the automatic repair did nothing to fix the problem I used the Expert Mode and tried to Repair the Boot Loader. The interesting -- if you call this error message "interesting"! -- thing here is I got the following error message: grub> setup --stage2=/boot/grub/stage2 (hd0,8) (hd0,8) Error 21 Selected disk does not exist but, of course, the disc does exist. Grub is reading something from somewhere which has been corrupted but the Installation CD is not reading the same info and therefore boots into the existing system correctly. But what is grub reading and, more importantly, how to fix this is the 64,000 dollar question :-) (which I cannot answer :-( ). ([1] BTW, where is this gzipped copy located" I couldn't find it :-( .) Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
grub> setup --stage2=/boot/grub/stage2 (hd0,8) (hd0,8) Error 21 Selected disk does not exist I believe the second one should only be the disk, i.e. (hd0)
-- Joe Morris Registered Linux user 231871 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
Basil Chupin wrote:
grub> setup --stage2=/boot/grub/stage2 (hd0,8) (hd0,8) Error 21 Selected disk does not exist
I believe the second one should only be the disk, i.e. (hd0) I just checked my /etc/grub.conf, and looks basically the same as yours above, and mine works, so I may be way off. I assume you have doubled checked everything, that it is supposed to be hda9 in OS speak. Have you tried to boot with the rescue system, mount hda9, chroot, then install grub again via the grub command line? It would be basically grub, then root (hd0,8), then setup (hd0), which should find everything and install it, the quit to leave grub, exit to leave the chroot, then shutdown -r now to reboot and check. HTH.
-- Joe Morris Registered Linux user 231871 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
It would be basically grub, then root (hd0,8), then setup (hd0), which should find everything and install it, the quit to leave grub, exit to leave the chroot, then shutdown -r now to reboot and check. HTH.
One more idea, since at least once it appeared you had a problem with the initrd, while you are in the chroot, you could rerun the mkinitrd command and make sure it finishes without error. HTH. -- Joe Morris Registered Linux user 231871 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-11-26 at 14:01 +1100, Basil Chupin wrote:
Check that file, perhaps it is broken somehow. Usually, "/boot/initrd" is a symlink, so check the link and the destination. Also, you can try to expand it on a temporary dir, it is gzipped.
Well, if it[1] was broken then I wouldn't be able to boot into the installed system from the Installation CD/DVD, and if it couldn't fit into memory then, again, it wouldn't fit when booting from the Installation CD.
I'm not sure of that.
Something very weird going on here and I cannot figure it out.
I used the Repair System from the Installation CD and when the automatic repair did nothing to fix the problem I used the Expert Mode and tried to Repair the Boot Loader. The interesting -- if you call this error message "interesting"! -- thing here is I got the following error message:
grub> setup --stage2=/boot/grub/stage2 (hd0,8) (hd0,8) Error 21 Selected disk does not exist
but, of course, the disc does exist.
Have a look at the "/boot/grub/device.map" file. Mine has: (hd1) /dev/hdb (fd0) /dev/fd0 (hd3) /dev/hdd (hd0) /dev/hda
Grub is reading something from somewhere which has been corrupted but the Installation CD is not reading the same info and therefore boots into the existing system correctly. But what is grub reading and, more importantly, how to fix this is the 64,000 dollar question :-) (which I cannot answer :-( ).
([1] BTW, where is this gzipped copy located" I couldn't find it :-( .)
Copy? I don't understand. But: nimrodel:/boot # l initrd* lrwxrwxrwx 1 root root 29 Sep 28 02:06 initrd -> initrd-2.6.16.21-0.25-default -rw-r--r-- 1 root root 2440205 Oct 5 21:42 initrd-2.6.16.21-0.25-cer -rw-r--r-- 1 root root 2438012 Sep 28 02:06 initrd-2.6.16.21-0.25-default lrwxrwxrwx 1 root root 25 Oct 5 21:50 initrd-cer -> initrd-2.6.16.21-0.25-cer initrd is a symlink, and you should check it is pointing correctly. Also: nimrodel:/boot # file initrd-2.6.16.21-0.25-default initrd-2.6.16.21-0.25-default: gzip compressed data, from Unix, max compression it is a gziped file, so probably it can be checked. Or even easier, rebuilt wit the command "mkinitrd". Do it, it won't hurt. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFaYUctTMYHG2NR9URAq12AKCE5TCduoQIiw8+mhudUUqKUqW7IgCfUthQ +4/MIFPXimaPDiWU8p9f/U4= =mvyI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-11-25 09:11, Basil Chupin wrote:
<snip>
ie. grub> root (hdx,x)
This is OK.
That should be the location of /boot, not the root system (/). These are of course the same location if you do not have a separate boot partition.
grub> kernel /vmlinuz root=/dev/hdx <other options>
This is OK. /dev/hdx is the root system, eg /dev/hda2
grub> initrd /initrd This is only correct if you have a separate boot partition; otherwise, it should be /boot/initrd.
From subsequent messages: this is my /etc/grub.conf:
setup --stage2=/boot/grub/stage2 (hd0) (hd0,0) -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The Saturday 2006-11-25 at 20:47 +1100, Basil Chupin wrote:
Suddenly I cannot boot into 10.1 with GRUB coming up with, "Error 18" as soon as it starts to execute on bootup.
Does anyone know what this error means and how to get grub working correctly again?
info grub, Troubleshooting, Stage2 errors: | 18 : Selected cylinder exceeds maximum supported by BIOS | This error is returned when a read is attempted at a linear | block address beyond the end of the BIOS translated area. This | generally happens if your disk is larger than the BIOS can handle | (512MB for (E)IDE disks on older machines or larger than 8GB in | general).
Can you view the menu.lst file at the grub prompt(grub>) and do the entries match your current partitioning setup?
grub> cat (hd0,0)/boot/grub/menu.lst
Yes.
where (hd0,0) represents (drive#,partition#) with numbering starting at zero and pointing to the partition holding menu.lst which should be your separate boot partition assuming grub was installed there originally and not to the root partition. (hd0,0) would point to the 1st partition on the 1st drive. (hd1,3) would point to the 4th partition on the second drive, etc...
grub> geometry (hdx)
will show existing partitions(x=0,1,2 etc.) .
Geometry OK. All partitions correctly shown (both HDs, btw).
Can you boot from the grub prompt manually?
ie. grub> root (hdx,x)
This is OK.
grub> kernel /vmlinuz root=/dev/hdx <other options>
This is OK.
grub> initrd /initrd
This comes up with an error, "Error 28: Selected item cannot fit into memory" which is a bit strange as I have 1.5GB of RAM and even right at the moment I have 58.5MB free.
grub> boot
Of course this does not happen :-) .
What does all of the above mean? Do I need a grease and oil change or a new set of spark plugs? :-)
On Saturday 25 November 2006 21:33, Joe Morris (NTM) wrote:
Joe Morris (NTM) wrote:
It would be basically grub, then root (hd0,8), then setup (hd0), which should find everything and install it, the quit to leave grub, exit to leave the chroot, then shutdown -r now to reboot and check. HTH.
One more idea, since at least once it appeared you had a problem with the initrd, while you are in the chroot, you could rerun the mkinitrd command and make sure it finishes without error. HTH.
As Joe suggests, rerunning mkinitrd is worth a try based on what you see. After the upgrade to beta1, I ran into a case where the upgrade somehow removed the initrd image completely and had to recreate it. Using the installation disk allowed me to boot the system even with this image missing. If you haven't already done something else that would render this next portion nonapplicable, try the following after booting into the system w/ the installation disk to create a new initrd image: cd /boot mv initrd-2.6.18.2-4-default initrd-2.6.18.2-4-default.notworking.old Modify "2.6.18.2-4-default" above(10.2 beta2 version) to match your current version which you can view with the output of "uname -a". rm initrd (or mv initrd initrd.notworking.old) mkinitrd -k vmlinuz-2.6.18.2-4-default -i initrd-2.6.18.2-4-default (your new initd-2.6.18.2-4 image should now be present) and/or for the xen image mkinitrd -k vmlinuz-2.6.18.2-4-xen -i initrd-2.6.18.2-4-xen Note that running just 'mkinitrd' with no options will create the default image that matches your current kernel vmlinuz image. recreate symbolic link(s) ln -s /boot/initrd-2.6.18.x-y /boot/initrd where "2.6.18.x-y" above is the version number you just created Verify that the symbolic links named /boot/initrd & /boot/vmlinuz point to matching version numbers . # ll initrd initrd -> initrd-2.6.18.2-4-default and confirm that this version matches the vmlinuz image version # ll vmlinuz vmlinuz -> vmlinuz-2.6.18.2-4-default You could also check for matching versions this before rerunning mkinitrd and if they don't match, it might be the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
rmyster@gmail.com wrote:
The Saturday 2006-11-25 at 20:47 +1100, Basil Chupin wrote:
[pruned]
On Saturday 25 November 2006 21:33, Joe Morris (NTM) wrote:
It would be basically grub, then root (hd0,8), then setup (hd0), which should find everything and install it, the quit to leave grub, exit to leave the chroot, then shutdown -r now to reboot and check. HTH. One more idea, since at least once it appeared you had a problem with
Joe Morris (NTM) wrote: the initrd, while you are in the chroot, you could rerun the mkinitrd command and make sure it finishes without error. HTH.
As Joe suggests, rerunning mkinitrd is worth a try based on what you see. After the upgrade to beta1, I ran into a case where the upgrade somehow removed the initrd image completely and had to recreate it. Using the installation disk allowed me to boot the system even with this image missing. If you haven't already done something else that would render this next portion nonapplicable, try the following after booting into the system w/ the installation disk to create a new initrd image:
cd /boot mv initrd-2.6.18.2-4-default initrd-2.6.18.2-4-default.notworking.old Modify "2.6.18.2-4-default" above(10.2 beta2 version) to match your current version which you can view with the output of "uname -a".
rm initrd (or mv initrd initrd.notworking.old)
mkinitrd -k vmlinuz-2.6.18.2-4-default -i initrd-2.6.18.2-4-default (your new initd-2.6.18.2-4 image should now be present)
and/or for the xen image mkinitrd -k vmlinuz-2.6.18.2-4-xen -i initrd-2.6.18.2-4-xen
Note that running just 'mkinitrd' with no options will create the default image that matches your current kernel vmlinuz image.
recreate symbolic link(s) ln -s /boot/initrd-2.6.18.x-y /boot/initrd where "2.6.18.x-y" above is the version number you just created
Verify that the symbolic links named /boot/initrd & /boot/vmlinuz point to matching version numbers .
# ll initrd initrd -> initrd-2.6.18.2-4-default
and confirm that this version matches the vmlinuz image version # ll vmlinuz vmlinuz -> vmlinuz-2.6.18.2-4-default
You could also check for matching versions this before rerunning mkinitrd and if they don't match, it might be the problem.
Thanks to you, Joe and to Darryl for your assistance and I ask for some time to digest all that has been suggested because I am finding it just a tad hard going trying to get it all into perspective. I am finding that what I expect to find I am not finding and what I read (eg in the Suse manual) is not as explicit as I would like so it is kinda confusing me. For example, above you state that doing "uname -a" will give me the current version of the kernel I am using. After a bit of puzzlement I realised (I think!) that when one boots into a 'broken' system using the installation DVD the uname -a command shows the version of the kernel used by the installation DVD to boot into the OS and *not* the actual kernel installed in the OS. For example, after booting using the 10.1 Installation DVD uname -a shows that the kernel is 2.6.16.13-4 but the kernel now actually in place is 2.6.16.21-0.25 and, of course, initrd etc also have this same (latter) number. It took a "few" minutes to work out why you said that not using any parameters with the mkinitrd command will create a default image which will match the current kernel - in this case being the old ...16.13-4 kernel which is not what I need. This of course would explain why booting from the DVD works even though there is a corruption in,say, initird because it is the kernel etc which is on the DVD which is used and until the damage is repaired the OS continues to run on the old kernel etc. At least this is what I make of it :-) . I'll recreate the initrd as described later today after rereading all that has been stated 'cause I don't want to mess things up even more and have to reinstall not only 10.1 but XP as well even though I only use it once in a blue moon. Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-11-27 at 01:09 +1100, Basil Chupin wrote: ...
For example, after booting using the 10.1 Installation DVD uname -a shows that the kernel is 2.6.16.13-4 but the kernel now actually in place is 2.6.16.21-0.25 and, of course, initrd etc also have this same (latter) number.
It took a "few" minutes to work out why you said that not using any parameters with the mkinitrd command will create a default image which will match the current kernel - in this case being the old ...16.13-4 kernel which is not what I need.
Did you try that, or is it a guess? :-? If it is a guess, as I think, then try it and don't waste more time :-p If you get an initrd for the old version then I'll tell you how to solve that. But I don't think you will.
This of course would explain why booting from the DVD works even though there is a corruption in,say, initird because it is the kernel etc which is on the DVD which is used and until the damage is repaired the OS continues to run on the old kernel etc. At least this is what I make of it :-) .
Correct.
I'll recreate the initrd as described later today after rereading all that has been stated 'cause I don't want to mess things up even more and have to reinstall not only 10.1 but XP as well even though I only use it once in a blue moon.
I have run the mkinitrd dozens or hundreds of times, and it never broke my install, that I can remember. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFabuJtTMYHG2NR9URAkl7AJ9dDxY3AQpy65M6HLJXX6GG91QeOwCgkfww rb4o3bjzfl8TM7Lle2vHtyA= =F06F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-11-27 at 01:09 +1100, Basil Chupin wrote:
...
For example, after booting using the 10.1 Installation DVD uname -a shows that the kernel is 2.6.16.13-4 but the kernel now actually in place is 2.6.16.21-0.25 and, of course, initrd etc also have this same (latter) number.
It took a "few" minutes to work out why you said that not using any parameters with the mkinitrd command will create a default image which will match the current kernel - in this case being the old ...16.13-4 kernel which is not what I need.
Did you try that, or is it a guess? :-?
If it is a guess, as I think, then try it and don't waste more time :-p
If you get an initrd for the old version then I'll tell you how to solve that. But I don't think you will.
[pruned] Well, I ran mkinitrd (with specifying the latest kernel by its full number) and created a new initrd to match which was slightly larger than the 'old' one and this showed that the 'old' one was corrupted. However, this has not helped at all :-( . When booting, the error message 18 still comes up :-( . So the problem appears to be elsewhere and possibly in more than one location. I ran the Repair System from the Installation CD/DVD and it keeps crashing always at the same spot but it doesn't show what the error is! (what a great repair system- it not only doesn't repair but is doesn't even show what the error is :-) ). The Repair System module goes thru and finds that all partitions are there as specified, the root etc are all OK, the file systems are OK and then it gets to the point of Check Package Database - Searching for package database and is executing- /usr/bin/test -f /mnt/var/lib/rpm/Triggername when it quietly crashes, simply shows "Error encountered" (or something like this) "OK" -- and waits for you to click on the OK after which you have a choice of doing all sorts of things including chucking the computer out of the window. To save time in booting from the Installation DVD I thought I would create a boot CD but it doesn't seem to be doing what I think it should be doing. I posted a question about this last night and now await an answer. I'll use the boot CD while trying to figure out what is causing my present problem with grub. Fortunately at the moment I don't need to boot into Windows but unless I get this grub going - or find another way to boot into Windows - I am going to be in a pickle when I do have to boot into XP. Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-11-28 at 21:02 +1100, Basil Chupin wrote:
Well, I ran mkinitrd (with specifying the latest kernel by its full number) and created a new initrd to match which was slightly larger than the 'old' one and this showed that the 'old' one was corrupted.
I don't think you need to specify the version, or any parameters at all. However... try this: - boot the rescue system (prompt, not the automatd thing). - mount your normal root partition somewhere, probably /mnt - mount your boot partition to /mnt/boot - same for separate /usr if you use it, ec. - do chroot /mnt - and "mkinitrd" with no parameters.
However, this has not helped at all :-( . When booting, the error message 18 still comes up :-( . So the problem appears to be elsewhere and possibly in more than one location.
I also have a problem when booting my test partition, which resides in a disk bigger than what my bios can handle. But I haven't studied the problem yet, although I'm starting to think that it is similar to your problem, or perhaps even the same one. I wonder.
I ran the Repair System from the Installation CD/DVD and it keeps crashing always at the same spot but it doesn't show what the error is! (what a great repair system- it not only doesn't repair but is doesn't even show what the error is :-) ).
I don't know if you can switch to a text console at the moment and see the logs, there will be in the ramdisk, but they might say something.
To save time in booting from the Installation DVD I thought I would create a boot CD but it doesn't seem to be doing what I think it should be doing. I posted a question about this last night and now await an answer.
I saw it, but I don't know about that.
I'll use the boot CD while trying to figure out what is causing my present problem with grub. Fortunately at the moment I don't need to boot into Windows but unless I get this grub going - or find another way to boot into Windows - I am going to be in a pickle when I do have to boot into XP.
I think the install cd can boot any installed system. And... you grub halts when loading suse, you get to the grub menu, no? There you can choose XP and it should not have the same problem - I hope. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFbBaKtTMYHG2NR9URAuEhAJ4nt9rIMN9NeC3v5DE/07h7BFe8UACggdop f38cyMo1xCspXL5VlkHV36s= =iKy+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote: [pruned]
I also have a problem when booting my test partition, which resides in a disk bigger than what my bios can handle. But I haven't studied the problem yet, although I'm starting to think that it is similar to your problem, or perhaps even the same one. I wonder.
[pruned]
And... you grub halts when loading suse, you get to the grub menu, no? There you can choose XP and it should not have the same problem - I hope.
No. I don't get to the grub menu. If I did I wouldn't be too worried (well :-) ) because I would be able to at least boot into Windows but I cannot because the grub menu does not come up. All that happens is I get the Error #18 message as soon as grub kicks in on boot and all I see is the grub> prompt followed by the error #18 statement. Let me go over the situation, just to clear all the stuff which may be muddying the waters. I have XP installed and I then installed 10.1 - and everything was working fine until a few days ago when suddenly on startup I got the grub> Error #18 message and the only way I can now boot into Suse is using the installation DVD and using the Boot Into Existing System. I have no access to XP. Because all my HD are in removable cradles, I installed 10.2 RC1 on this same computer (my "main" one, the one I am now using to type this message with 10.1) using one of my other HDs. I have no problems with booting into 10.2 RC1 on this computer- grub doesn't come up with any error messages. Knowing that there is the option on the Installation DVD/CD to do a Repair on an existing system I tried doing this repair and after finding that all the partitions are in place with their correct file systems, Repair crashes at the stage called Check Package Database - Searching for package database where it is executing the following command: /usr/bin/test -f /mnt/var/lib/rpm/Triggername when the whole Repair process just dies and I am faced with a red screen with an error message of Error Encountered (or similar) - no explanation of what caused the error. Now, in summary I guess, I can boot into 10.1 using the Installation DVD/CD and the system appears to be going OK except that I have noticed a couple of "funnies" - eg, suddenly I cannot access any CD or DVD either as a user or root because KDE gives out with an error message that Permission is Denied (or similar); also booting from the Installation CD uses the original version of the kernel as it is on the DVD/CD and not the one which is now installed on the HD after the kernel has been upgraded several times in the past months. So, here we are :-) . Something suddenly zapped this system but what it was which caused this I don't know except to note that some upgrades were done during the day a few days ago and the next morning when I went to start the system I wasn't able to do a normal bootup. I now feel that unless something miraculous happens and someone can come up and say, "This is where the problem is!" I will need to reinstall 10.1 -- which I am loath to do because of all the mucking around with installing the video apps to be able to watch DVD :-( . And, of course, having to install smart and then downloading all over again all the upgrades to 10.1 :-( . But.... "that's show biz" :-) . Maybe, just maybe, I'll wake up in the morning and find that all this has been simply a bad dream and in fact there is no problem with the system :-) . Or maybe the elves will fix the system while I am asleep :-) . Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 29 Nov 2006, Basil Chupin wrote:
[pruned] No. I don't get to the grub menu. If I did I wouldn't be too worried (well :-) ) because I would be able to at least boot into Windows but I cannot because the grub menu does not come up.
I do not know if this will assist you or not, but I thought I should share two experiences I had a similar problem once when grub got corupted. I had to boot using the install CD. I choose repair existing system. After logging in as root I mounted the root filesystem to /mnt I am going to use what I had as an example # mount /dev/hda5 /mnt # cd /mnt # chroot /mnt # mount /dev/hda4 /boot # mkinitrd # yast2 I then choose grub install and installed grub to /dev/hda4 and copied the old boot to the new boot change menu.lst. I also boot into XP with the systems. I was then able to reboot the system. On an other system where the BIOS does not support > 1024 I had to use the partitioner to delete swap create a boot partition of about 50 MB and use the rest for swap. I have a 200-300 MB Dos partition as /dev/hda1, NTFS as /dev/hda2, a linux swap on /dev/hda3 that became boot, change to extended partition to include the extra space that was in swap and made /dev/hda4 a linux swap. Just becareful and have a backup of your critical stuff.
All that happens is I get the Error #18 message as soon as grub kicks in on boot and all I see is the grub> prompt followed by the error #18 statement.
After the above I was able to use the auto repair of the system. Good Luck, -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 28 November 2006 16:32, Basil Chupin wrote:
I have XP installed and I then installed 10.1 - and everything was working fine until a few days ago when suddenly on startup I got the grub> Error #18 message and the only way I can now boot into Suse is using the installation DVD and using the Boot Into Existing System. I have no access to XP.
If you didn't do anything manually, 10.1 installed grub to the 10.1 partition, and set the "active" flag to that partition. You should be able to boot XP by running the partitioner and setting the XP partition to active instead. Error 18 means "trying to read beyond the capacity of the BIOS". Did you change something in the hard drive settings in the BIOS recently? LBA mode, or such? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-11-29 at 02:32 +1100, Basil Chupin wrote: ...
And... you grub halts when loading suse, you get to the grub menu, no? There you can choose XP and it should not have the same problem - I hope.
No. I don't get to the grub menu. If I did I wouldn't be too worried (well :-) ) because I would be able to at least boot into Windows but I cannot because the grub menu does not come up.
All that happens is I get the Error #18 message as soon as grub kicks in on boot and all I see is the grub> prompt followed by the error #18 statement.
Then your problem is not the initrd file! It can't be, it is not read till after you choose to boot into linux. It's got to be a problem with grub own files, those in /boot/grub, or the copy near the mbr - I don't fully understand that part. Maybe you need to rerun grub-install or whatever.
Let me go over the situation, just to clear all the stuff which may be muddying the waters.
Ok :-)
Because all my HD are in removable cradles, I installed 10.2 RC1 on this same computer (my "main" one, the one I am now using to type this message with 10.1) using one of my other HDs. I have no problems with booting into 10.2 RC1 on this computer- grub doesn't come up with any error messages.
I don't know if that is relevant... something changes and it crashes :-? A change in LBA numbering :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFbI9TtTMYHG2NR9URAmhvAJ0dsR388MeKo/mzVVhwBX1ZLvhkRwCfdJuI uwRqTPYP1mgz2W9lvih9oIw= =LiU4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 26 November 2006 07:09, Basil Chupin wrote:
rmyster@gmail.com wrote:
mkinitrd -k vmlinuz-2.6.18.2-4-default -i initrd-2.6.18.2-4-default (your new initd-2.6.18.2-4 image should now be present)
and/or for the xen image mkinitrd -k vmlinuz-2.6.18.2-4-xen -i initrd-2.6.18.2-4-xen
Note that running just 'mkinitrd' with no options will create the default image that matches your current kernel vmlinuz image.
recreate symbolic link(s) ln -s /boot/initrd-2.6.18.x-y /boot/initrd where "2.6.18.x-y" above is the version number you just created
Thanks to you, Joe and to Darryl for your assistance and I ask for some time to digest all that has been suggested because I am finding it just a tad hard going trying to get it all into perspective. I am finding that what I expect to find I am not finding and what I read (eg in the Suse manual) is not as explicit as I would like so it is kinda confusing me.
For example, above you state that doing "uname -a" will give me the current version of the kernel I am using. After a bit of puzzlement I realised (I think!) that when one boots into a 'broken' system using the installation DVD the uname -a command shows the version of the kernel used by the installation DVD to boot into the OS and *not* the actual kernel installed in the OS.
That didn't occur to me but did you boot with your system's installation cd/dvd or were you using an earlier version? Booting with the 10.2 RC1 dvd on my end shows the kernel as 2.6.18.2-23-default which matches the kernel when booting directly into 10.2 RC1.
For example, after booting using the 10.1 Installation DVD uname -a shows that the kernel is 2.6.16.13-4 but the kernel now actually in place is 2.6.16.21-0.25 and, of course, initrd etc also have this same (latter) number.
It took a "few" minutes to work out why you said that not using any parameters with the mkinitrd command will create a default image which will match the current kernel - in this case being the old ...16.13-4 kernel which is not what I need.
If vmlinux-2.6.16.21-0.25-default is your latest available version in your /boot dir, then use those numbers and use mkinitrd with the -k & -i options mentioned previously. Looking at where the /boot/vmliuz symbolic link points to at the moment should tell you what the latest version is on your system and just match that one. As of 10.2 RC1, the latest version is 2.6.18.2-23-default and my earlier examples used the 10.2 beta2 kernel version.
This of course would explain why booting from the DVD works even though there is a corruption in,say, initird because it is the kernel etc which is on the DVD which is used and until the damage is repaired the OS continues to run on the old kernel etc. At least this is what I make of it :-) .
or the install disk just creates the initrd ramdisk on the fly from the existing vmlinuz image.
I'll recreate the initrd as described later today after rereading all that has been stated 'cause I don't want to mess things up even more and have to reinstall not only 10.1 but XP as well even though I only use it once in a blue moon.
If your latest kernel vmlinuz image is 2.6.18.2-23-default, then after renaming the existing files (initrd and initrd-2.6.18.2-23-default), you can use mkinitrd -k /boot/vmlinuz-2.6.18.2-23-default -i /boot/initrd-2.6.18.2-23-default followed by ln -s /boot/initrd-2.6.18.2-23-default /boot/initrd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
rmyster@gmail.com wrote:
On Sunday 26 November 2006 07:09, Basil Chupin wrote:
[pruned]
Thanks to you, Joe and to Darryl for your assistance and I ask for some time to digest all that has been suggested because I am finding it just a tad hard going trying to get it all into perspective. I am finding that what I expect to find I am not finding and what I read (eg in the Suse manual) is not as explicit as I would like so it is kinda confusing me.
For example, above you state that doing "uname -a" will give me the current version of the kernel I am using. After a bit of puzzlement I realised (I think!) that when one boots into a 'broken' system using the installation DVD the uname -a command shows the version of the kernel used by the installation DVD to boot into the OS and *not* the actual kernel installed in the OS.
That didn't occur to me but did you boot with your system's installation cd/dvd or were you using an earlier version? Booting with the 10.2 RC1 dvd on my end shows the kernel as 2.6.18.2-23-default which matches the kernel when booting directly into 10.2 RC1.
Which is what is to expected since the kernel for 10.2 RC1 hasn't been upgraded (yet). Re the rest: see my reply to Carlos. I created a new initrd to match the latest kernel (on 10.1) but it didn't help- the error #18 message still comes up :-( . Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/11/28 21:07 (GMT+1100) Basil Chupin apparently typed: I did a FTP install from the beta2 mirror state IIRC. Shortly after I did some partition rearranging, moving the factory from hda21 to hda10. After editing the appropriate files and running grub-install, it would not boot when hda10 selected from IBM Boot Manager or when hda10 chainloaded from grub on another partition. Loading the kernel and initrd from grub elsewhere worked fine. After updating to the rc1 mirror state I reran grub-install once again, and now it boots from BM, and presumably also from chainload. The rc1 graphical grub boot menu is way cool! -- "Rejoice and be glad, because great is your reward in heaven." Matthew 5:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-11-28 at 07:30 -0500, Felix Miata wrote:
I did a FTP install from the beta2 mirror state IIRC. Shortly after I did some partition rearranging, moving the factory from hda21 to hda10. After editing the appropriate files and running grub-install, it would not boot when hda10 selected from IBM Boot Manager or when hda10 chainloaded from grub on another partition. Loading the kernel and initrd from grub elsewhere worked fine.
The documentation for grub-install is incomplete, at least in 10.1. There is only the man page, with this mention: | The full documentation for grub-install is maintained as a Texinfo | manual. If the info and grub-install programs are properly | installed at your site, the command | | info grub-install but "info grub-install" gives the exact same info, there is no "info" page. Thus, I have an "/etc/grub.conf" file which I can not understand, and I think it has a mistake: install --stage2=/boot/grub/stage2 (hd3,1)/grub/stage1 d (hd0) (hd3,1)/grub/stage2 0x8000 (hd3,1)/grub/menu.lst root (hd1,1) install --stage2=/boot/grub/stage2 /grub/stage1 d (hd1,1) /grub/stage2 0x8000 (hd1,1)/grub/menu.lst quit - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFbDectTMYHG2NR9URAmN3AJ0bs4NR7H841AxmHc89aqW5Y04XUgCdHiz2 FMvhu4hRJdelqqKsR7KstBU= =p9pb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/11/28 14:20 (GMT+0100) Carlos E. R. apparently typed:
Thus, I have an "/etc/grub.conf" file which I can not understand, and I think it has a mistake:
install --stage2=/boot/grub/stage2 (hd3,1)/grub/stage1 d (hd0) (hd3,1)/grub/stage2 0x8000 (hd3,1)/grub/menu.lst root (hd1,1) install --stage2=/boot/grub/stage2 /grub/stage1 d (hd1,1) /grub/stage2 0x8000 (hd1,1)/grub/menu.lst quit
Not sure how you figured it has a mistake and not be able to tell what it is. Mine's considerably simpler: root (hd0,4) install --stage2=/boot/grub/stage2 /grub/stage1 (hd0,4) /grub/stage2 0x8000 (hd0,4)/grub/menu.lst quit -- "Rejoice and be glad, because great is your reward in heaven." Matthew 5:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-11-28 at 08:37 -0500, Felix Miata wrote:
Not sure how you figured it has a mistake and not be able to tell what it is. Mine's considerably simpler:
Because last time I let Yast touch grub, when I updated to 10.1, my system would not boot. I had to overwrite the MBR from a backup using 'dd'. Now, when I boot, it says the message file has a format error and to press a key, throwing me into the text screen boot menu instead of the nice graphical one. I have tried replacing that message file from another install to no avail. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFbEo9tTMYHG2NR9URAlTtAJ9Si6bBFboacWZg3U6Tdk/mMmB8MwCfQ/jW LMaD2wNNH9FLb4EEjbmvodw= =eq4J -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/11/28 15:39 (GMT+0100) Carlos E. R. apparently typed:
The Tuesday 2006-11-28 at 08:37 -0500, Felix Miata wrote:
Not sure how you figured it has a mistake and not be able to tell what it is. Mine's considerably simpler:
Because last time I let Yast touch grub, when I updated to 10.1, my system would not boot. I had to overwrite the MBR from a backup using 'dd'. Now, when I boot, it says the message file has a format error and to press a key, throwing me into the text screen boot menu instead of the nice graphical one. I have tried replacing that message file from another install to no avail.
NAICT, /etc/grub.conf is nothing but configuration information for grub-install, not for using grub to boot. Grub's menu configuration lives in /boot/grub/menu.lst, unless you're using Fedora or RedHat. -- "Rejoice and be glad, because great is your reward in heaven." Matthew 5:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-11-28 at 10:02 -0500, Felix Miata wrote:
Because last time I let Yast touch grub, when I updated to 10.1, my system would not boot. I had to overwrite the MBR from a backup using 'dd'. Now, when I boot, it says the message file has a format error and to press a key, throwing me into the text screen boot menu instead of the nice graphical one. I have tried replacing that message file from another install to no avail.
NAICT,
cer@nimrodel:~> wtf NAICT Gee... I don't know what NAICT means...
/etc/grub.conf is nothing but configuration information for grub-install, not for using grub to boot. Grub's menu configuration lives in /boot/grub/menu.lst, unless you're using Fedora or RedHat.
Precisely. If /etc/grub.conf is bad, Yast intalls grubs incorrectly. I said that I had to repair that install overwriting the MBR using dd to copy my backup of the MBR over what Yast/grub module had broken. I did not have to repair the menu, that was correct. If I knew how to correct that file yast will not break it again next time (when I update to 10.2) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFbFFftTMYHG2NR9URAoCiAKCLlm062cIKVXVhxoTnvReC0fftdgCgg5Cx 9zAUtyH9E/pzx/4hVe/y3Mg= =IxQW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/11/28 16:10 (GMT+0100) Carlos E. R. apparently typed:
NAICT,
cer@nimrodel:~> wtf NAICT Gee... I don't know what NAICT means...
http://www.acronymfinder.com/acronym.aspx?rec={CBE8AE0D-29FD-4960-AC27-B5F5DC1C2346} http://www.stands4.com/NAICT http://acronyms.thefreedictionary.com/NAICT -- "Rejoice and be glad, because great is your reward in heaven." Matthew 5:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
If /etc/grub.conf is bad, Yast intalls grubs incorrectly. I said that I had to repair that install overwriting the MBR using dd to copy my backup of the MBR over what Yast/grub module had broken.
I did not have to repair the menu, that was correct.
If I knew how to correct that file yast will not break it again next time (when I update to 10.2)
For what it's worth, I had all kinds of problems with 10.1's grub, and manually installed grub many times. I assumed it was because my root was raid1 (/dev/md0). Anyway, 10.2 Beta 1 and 2 left me needing to install grub manually still, but much to my surprise and delight, RC 1 worked straight away. Here is my present /etc/grub.conf. jmorris:/home/joe # cat /etc/grub.conf setup --stage2=/boot/grub/stage2 (hd0,4) (hd0,4) quit Quite a bit shorter than in 9.3, but it has worked flawlessly now through a change (silent to verbose option) and 2 kernel updates (which shouldn't mess with grub but used to). So, at least RC1's bootloader looks very promising. -- Joe Morris Registered Linux user 231871 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/11/28 14:20 (GMT+0100) Carlos E. R. apparently typed:
The documentation for grub-install is incomplete, at least in 10.1. There is only the man page
Try this: http://www.gnu.org/software/grub/manual/grub.html -- "Rejoice and be glad, because great is your reward in heaven." Matthew 5:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-11-25 at 23:03 +1100, Basil Chupin wrote:
info grub, Troubleshooting, Stage2 errors:
| 18 : Selected cylinder exceeds maximum supported by BIOS | This error is returned when a read is attempted at a linear block | address beyond the end of the BIOS translated area. This generally | happens if your disk is larger than the BIOS can handle (512MB for | (E)IDE disks on older machines or larger than 8GB in general).
Create a separate /boot partition somewhere near the begingining of your hard disk.
Thanks for the response but, eh, I have been dual-booting for years now and therefore already have a 300MB boot partition at the start of the HD, and have been running 10.1 without any problems since it came out until this morning when the error message suddenly came up. (Just checked with cfdisk and all the partitions are there as they are supposed to be.)
Ugh. Seems to be correct...
Checked in the BIOS and all drives are correctly recognised.
Any other suggestions, please?
No... sorry. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFaD+YtTMYHG2NR9URAvySAJ967FEf1MWV6R0XbkXuv7EFslWrgQCeIKfA kO9drIwXJwAuVrPgqeGaCsk= =XLdh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2006-11-25 at 23:03 +1100, Basil Chupin wrote:
info grub, Troubleshooting, Stage2 errors:
| 18 : Selected cylinder exceeds maximum supported by BIOS | This error is returned when a read is attempted at a linear block | address beyond the end of the BIOS translated area. This generally | happens if your disk is larger than the BIOS can handle (512MB for | (E)IDE disks on older machines or larger than 8GB in general).
Create a separate /boot partition somewhere near the begingining of your hard disk. Thanks for the response but, eh, I have been dual-booting for years now and therefore already have a 300MB boot partition at the start of the HD, and have been running 10.1 without any problems since it came out until this morning when the error message suddenly came up. (Just checked with cfdisk and all the partitions are there as they are supposed to be.)
Ugh. Seems to be correct...
Checked in the BIOS and all drives are correctly recognised.
Any other suggestions, please?
No... sorry.
Thanks, Carlos. If the worse comes to the worst I'll just breakdown and cry..... Cheers. -- "I do not feel obliged to believe that the same God who has endowed us with sense, reason and intellect has intended us to forgo their use." Galileo Galilei -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Anders Johansson -
Basil Chupin -
Boyd Lynn Gerber -
Carlos E. R. -
Darryl Gregorash -
Felix Miata -
Joe Morris (NTM) -
rmyster＠gmail.com