[opensuse] LILO/Grub Problem
Hello SUSE people. Just installed 10.2 on a brand new hard drive. Installed just fine. Already was booting to Win98 and SUSE 10.0, each on their own hard drives My 10.0 is my normal everyday system and 10.2 was to be my experimenting/test bed. I was using LILO to boot Win 98 and SuSE 10.0 on the MBR of hda. (the win98 drive) When I installed 10.2 I let it use Grub which also installed on hda, thinking it would pick up 10.0 and if not I would be able to add it. No good. I can boot Win98 and my new 10.2 but not my old 10.0. Not in the menu. Can't even boot it from the DVD. Of course all of my tips and procedures I have gleaned from this list are safely tucked away in 10.0 that I can't get at. Hope someone is kind enough to point me in the right direction so that I can boot 10.0 again. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 01 February 2007 22:39, Bob S wrote:
Hope someone is kind enough to point me in the right direction so that I can boot 10.0 again. Use your 10.0 boot CD, or boot DVD...
... and (like you are going to install the system) don't install but take the other option and bring up the utilities. You will find a utility which will allow you to restore the mbr (should restore the lilo mbr from your Suse10 /windoze install). Once you get the system back (10.0) then install the grub boot-loader. Get the machine booting windoze and Suse10.0 with grub... then add the menu.lst option for the Suse 10.2 system. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
No good. I can boot Win98 and my new 10.2 but not my old 10.0. Not a big problem probably. Not in the menu. Just mount your 10.0 boot directory (if on it own partition or if in /) so you can compare the 10.0 grub device map and menu.lst, and add the correct entry to the menu.lst in the 10.2 grub, where it already boots from and already has an entry for win98 and 10.2. Can't even boot it from the DVD. What do you mean here? Hope someone is kind enough to point me in the right direction so that I can boot 10.0 again.
This appears to be a fairly easy fix. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
look at your file: /boot/grub/menu.lst and compare between 10.0 and 10.2. I recommend you to dump LILO. Modify that file on 10.2, so that it will load 10.0 as well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 02 February 2007 05:08, Joe Morris (NTM) wrote:
Bob S wrote:
No good. I can boot Win98 and my new 10.2 but not my old 10.0.
Not a big problem probably.
Not in the menu.
Hi Joe, thanks for replying. Hope you can bail me out yet another time.
Just mount your 10.0 boot directory (if on it own partition or if in /) so you can compare the 10.0 grub device map and menu.lst, and add the correct entry to the menu.lst in the 10.2 grub, where it already boots from and already has an entry for win98 and 10.2.
Well that is the problem. I can't mount 10.0. It is on a completely separate hard drive. Even if I find out how to do that, I don't have a 10.0 grub device map. I was using LILO to mount 10.0
Can't even boot it from the DVD.
What do you mean here?
When I put the 10.0 DVD into the machine and boot the installed system it boots 10.2 and I have not figured out how to mount 10.0 Figured I could use Yast to fix it. Think I could fix it from within 10.2 ?? Trouble is, I know absolutely nothing about grub. Been using lilo all of these years. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 02 February 2007 16:25, Bob S wrote:
When I put the 10.0 DVD into the machine and boot the installed system it boots 10.2 and I have not figured out how to mount 10.0 Figured I could use Yast to fix it.
Think I could fix it from within 10.2 ?? Trouble is, I know absolutely nothing about grub. Been using lilo all of these years.
Yes, you most likely can fix it from 10.2 but we would need to see (from the
10.2 install)
/etc/fstab
/boot/grub/menu.lst
and also
fdisk -l /dev/
On Friday 02 February 2007 17:02, Bruce Marshall wrote:
On Friday 02 February 2007 16:25, Bob S wrote:
When I put the 10.0 DVD into the machine and boot the installed system it boots 10.2 and I have not figured out how to mount 10.0 Figured I could use Yast to fix it.
Think I could fix it from within 10.2 ?? Trouble is, I know absolutely nothing about grub. Been using lilo all of these years.
Hello Bruce, Thanks for replying
Yes, you most likely can fix it from 10.2 but we would need to see (from the 10.2 install)
/etc/fstab
/boot/grub/menu.lst
and also
fdisk -l /dev/
> 10-0parts the 10-0parts file from the above command.
In short, you will/may have to change the 10.0 /etc/fstab and the menu.lst if you have changed the order of the partitions for 10.0
Did not touch the hdb (10.0) drive
Having the 10.2 files for the above wouldn't hurt either.
OK, some of what you requested to assist me: -------------------------------------------------------------------------------------- (10.2 fstab) /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda5 /home ext3 acl,user_xattr 1 2 /dev/sda6 /usr ext3 acl,user_xattr 1 2 /dev/hdb2 swap swap defaults 0 0 /dev/sda2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 ---------------------------------------------------------------------------------- (10.2 /boot/grub/menu.1st) # Modified by YaST2. Last modification on Thu Feb 1 22:04:23 EST 2007 default 0 timeout 8 gfxmenu (hd2,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=0x31a resume=/dev/sda2 splash=silent showopts initrd /boot/initrd-2.6.18.2-34-default ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.18.2-34-default ------------------------------------------------------------------------------------------- My comments: OK, when I tried to do the fdisk-l /dev/hdb > 10-oparts (as root in a console from within 10.2) I got no output. Nothing. (Is it the number 10 or the capitalized IO, and is oparts capitalized?) Had to drop back to level 3 before I could get any output from the command. I don't know how to save and paste the output from there but this is what I found: fdisk -l /dev/hdb gives me 3 partitions. A 1G boot partition, a 1G swap partition, and a 28G LVM (which I have my home and all other partions on as LVM's) If I then do an fdisk -l on hdb1 (the boot partition) it tells me that hdb1 doesn't have a valid partition table ?? Seeing that, I do and fsck on /dev/hdb. Output is that the device is busy and failed (status 0x0) Then I do an fsck on hdb1 - says it is clean Then I do an fsck on hdb2 - says swap not found (error2) Then I do an fsck on hdb3 - says LVM2 member: not found (errror2) I really can't believe there is a partition table problem. The command > 10-Opart never produces any results. (Tried in every variation I could think of, as above) Sooooo...I guess that I am not understanding this. Mind you now, I did not TOUCH any of the partitions on hdb. To remind you, I have 3 drives. The first is hda which is an ide device that has Win98 and several Linux partitions (where I keep my backups, workspace and some not so important data) The second is hdb, another ide, where 10.0 is installed and most of my important personal data is stored, and the new drive a SATA, sda, where I installed 10.2 I can go into the Yast partioner and see that everything is there. I just cannot access hdb (10.0) I have to access hdb. That is where everything that is important resides. Maybe if I unplug the new Sata drive I will be able to mount that drive with the DVD? Thanks again and Please help. I'm sure it has something to do with changing from LILO to Grub. but then Win98 was picked up by Grub but 10.0 was not. Very frustrating. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Did not touch the hdb (10.0) drive Good, there is hope.
Having the 10.2 files for the above wouldn't hurt either.
OK, some of what you requested to assist me: -------------------------------------------------------------------------------------- (10.2 fstab)
/dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda5 /home ext3 acl,user_xattr 1 2 /dev/sda6 /usr ext3 acl,user_xattr 1 2 /dev/hdb2 swap swap defaults 0 0
So it was able to find the swap.
/dev/sda2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 ---------------------------------------------------------------------------------- (10.2 /boot/grub/menu.1st)
# Modified by YaST2. Last modification on Thu Feb 1 22:04:23 EST 2007 default 0 timeout 8 gfxmenu (hd2,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=0x31a resume=/dev/sda2 splash=silent showopts initrd /boot/initrd-2.6.18.2-34-default
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1
###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.18.2-34-default
Add this to this file. ________________________________________________________________________________ ### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /vmlinuz root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /initrd ___________________________________________________________________________________ This assumes the following which I cannot be sure of with the supplied info. I assume: The initrd on that drive has the modules for the lvm in it. The vmlinuz and initrd symlinks are setup properly the lvm root partition is hdb3 Also, to make this the default boot, change default from 0 to 4
------------------------------------------------------------------------------------------- My comments:
OK, when I tried to do the fdisk-l /dev/hdb > 10-oparts (as root in a console from within 10.2) I got no output. Nothing. (Is it the number 10 or the capitalized IO, and is oparts capitalized?)
You are creating a file, nothing comes back to your screen.
Had to drop back to level 3 before I could get any output from the command. I don't know how to save and paste the output from there but this is what I found:
fdisk -l /dev/hdb gives me 3 partitions. A 1G boot partition, a 1G swap partition, and a 28G LVM (which I have my home and all other partions on as LVM's)
Is that one hdb3? or did you have any extended partitions?
If I then do an fdisk -l on hdb1 (the boot partition) it tells me that hdb1 doesn't have a valid partition table ??
Correct, that belongs to hdb. hdb1 IS a partition, it wouldn't need a partition table.
Seeing that, I do and fsck on /dev/hdb. Output is that the device is busy and failed (status 0x0) Then I do an fsck on hdb1 - says it is clean Then I do an fsck on hdb2 - says swap not found (error2) Then I do an fsck on hdb3 - says LVM2 member: not found (errror2) I really can't believe there is a partition table problem.
LVM makes this much harder than normal.
The command > 10-Opart never produces any results. (Tried in every variation I could think of, as above)
You are just overwriting the file over and over.
Sooooo...I guess that I am not understanding this.
Mind you now, I did not TOUCH any of the partitions on hdb.
Good.
To remind you, I have 3 drives. The first is hda which is an ide device that has Win98 and several Linux partitions (where I keep my backups, workspace and some not so important data) The second is hdb, another ide, where 10.0 is installed and most of my important personal data is stored, and the new drive a SATA, sda, where I installed 10.2
I can go into the Yast partioner and see that everything is there. What is the partition with the lvm called there? hdb3? I just cannot access hdb (10.0) I have to access hdb. That is where everything that is important resides. Maybe if I unplug the new Sata drive I will be able to mount that drive with the DVD?
Doubt it. Sorry, I am not that familiar with lvm disk notation.
Thanks again and Please help. I'm sure it has something to do with changing from LILO to Grub. No, actually it has to do with the lvm volumes. but then Win98 was picked up by Grub but 10.0 was not. Very frustrating.
IIRC, there was something about this in the release notes. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 03 February 2007 02:27, Joe Morris (NTM) wrote: Hi Joe, ............<snip a bunch>................
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.18.2-34-default
Add this to this file. ___________________________________________________________________________ _____ ### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /vmlinuz root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /initrd ___________________________________________________________________________ ________ This assumes the following which I cannot be sure of with the supplied info. I assume: The initrd on that drive has the modules for the lvm in it. The vmlinuz and initrd symlinks are setup properly the lvm root partition is hdb3 Also, to make this the default boot, change default from 0 to 4
OK, did as instructed. Sadly it did not work. Does it matter where it is placed in the file?
------------------ My comments:
<more snip>
fdisk -l /dev/hdb gives me 3 partitions. A 1G boot partition, a 1G swap partition, and a 28G LVM (which I have my home and all other partions on as LVM's)
Is that one hdb3? or did you have any extended partitions?
Yes that LVM is hdb3
<more snip>
Sooooo...I guess that I am not understanding this.
Mind you now, I did not TOUCH any of the partitions on hdb.
Good.
To remind you, I have 3 drives. The first is hda which is an ide device that has Win98 and several Linux partitions (where I keep my backups, workspace and some not so important data) The second is hdb, another ide, where 10.0 is installed and most of my important personal data is stored, and the new drive a SATA, sda, where I installed 10.2
I can go into the Yast partioner and see that everything is there.
What is the partition with the lvm called there? hdb3?
Yes. Are you thinking that the boot parameters are inside the LVM? That's why you called root=/dev/hdb3 in the script? When that didn't work I went ahead and changed it to root=/dev/hdb1. That didn't work either.
I just cannot access hdb (10.0) I have to access hdb. That is where everything that is important resides. Maybe if I unplug the new Sata drive I will be able to mount that drive with the DVD?
Doubt it. Sorry, I am not that familiar with lvm disk notation.
Thanks again and Please help. I'm sure it has something to do with changing from LILO to Grub.
No, actually it has to do with the lvm volumes.
but then Win98 was picked up by Grub but 10.0 was not. Very frustrating.
IIRC, there was something about this in the release notes.
The release notes for 10.2? How can I get at them again? Please do not give up on me until you are totally out of ideas. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 03 February 2007 02:27, Joe Morris (NTM) wrote:
Add this to this file.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
Sorry, watch the wrapping. Perhaps some explanation of the above will help. [Note, i changed a few items above from original try]. root is for grub to find the root of the OS (I originally thought it needed to be the boot partition). I forgot since I have not had a separate boot for some years. Kernel like is to load the kernel image. Here I added
Bob S wrote: the grub notation to find vmlinuz on the boot partition in the root of that partition. My root line above appears to be wrong from a few pages I have seen searching online, but I have no way of determining what it would be for your system. Check out http://www.rocklinux.org/wiki/Root_on_LVM and http://www.linuxforums.org/forum/redhat-fedora-linux-help/61630-grub-lvm-mul... it appears from these it may be something like (hd1,2)/dev/VolGroup00/LogVol00 or something like it. BTW, according to the release notes, Yasts partition tool can handle LVMs and might at least allow you to get to your data while we get this working. It might also help figure out what the root= line should be.
OK, did as instructed. Sadly it did not work. Does it matter where it is placed in the file?
Yes, I assumed you would add it after the last entry, but it would only change the number for which is the default choice if you do not choose.
fdisk -l /dev/hdb gives me 3 partitions. A 1G boot partition, a 1G swap partition, and a 28G LVM (which I have my home and all other partions on as LVM's)
Is that one hdb3? or did you have any extended partitions?
Yes that LVM is hdb3
Sorry, like I said, not that familiar with lvm. Is it called /dev/hdb3 like normal, or what is it called? For example, I run a raid 1, so mine is /dev/md0.
Yes. Are you thinking that the boot parameters are inside the LVM? No, your root partition is in there. That's why you called root=/dev/hdb3 in the script? No, that is because that is where your root partition is (i.e. /). When that didn't work I went ahead and changed it to root=/dev/hdb1. That didn't work either.
That is your boot partition. You need a separate boot (I checked the release notes) if you use a lvm. Inside your boot partition (hdb1) is your kernel and most importantly your initrd, which I would assume is fine since you haven't messed with hdb. Your initrd will have the necessary modules to recognize your lvm volume. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 03 February 2007 19:31, Joe Morris (NTM) wrote:
Bob S wrote:
On Saturday 03 February 2007 02:27, Joe Morris (NTM) wrote:
Add this to this file.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
Sorry, watch the wrapping.
OK. I checked the wrapping. and made your script follow the format of what was there. Worked and showed in the menu. Would not boot however with an Error 19. Linux kernel must be loaded before initrd. Are we any closer?
OK don't know if SuSE uses that Rock LVM. Was all CLI though and when I installed 10.0 I used the Yast partitioner (all graphic) to set it up.
andhttp://www.linuxforums.org/forum/redhat-fedora-linux-help/61630-grub-lvm-mu
lti-boot-problem.html
That URL is not working.
it appears from these it may be something like (hd1,2)/dev/VolGroup00/LogVol00 or something like it. BTW, according to the release notes, Yasts partition tool can handle LVMs and might at least allow you to get to your data while we get this working. It might also help figure out what the root= line should be.
Hmmmm maybe we are past that now?
Yes, I assumed you would add it after the last entry, but it would only change the number for which is the default choice if you do not choose.
Yep that is what I did. and 10.0 comes up as the default.
......<snip more>.................
Sorry, like I said, not that familiar with lvm. Is it called /dev/hdb3 like normal, or what is it called? For example, I run a raid 1, so mine is /dev/md0.
Yes it is called dev/hdb3 like normal and is designated Linux LVM. FYI There is another entry further down in the table that is the exact same size and is identified as /dev/system and is designated LVM2 System. Back to above. Did a Google on the Error19 in grub and came up with the same kernel must be loaded before initrd message. Got one promising hit but alas is in french, which I cannot undedrstand. Maybe jdd could interpret for us. Hope we're closer. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Worked and showed in the menu. Would not boot however with an Error 19. Linux kernel must be loaded before initrd. Are we any closer?
I believe so. Could you mount your boot partition and verify you have a vmlinuz and initrd symlinks to their respective kernel and initrd? Should be as easy as, in a console as root, mount /dev/hdb1 /mnt, then go to /mnt in Konqueror.
OK don't know if SuSE uses that Rock LVM. I know they don't, but I was seeing there is different notation for a lvm drive. Was all CLI though and when I installed 10.0 I used the Yast partitioner (all graphic) to set it up.
Would love to see the fstab in your 10.0 system. You could probably mkdir /data1, then use Yast Partitioner to mount the old 10.0 root lvm partition to /data1 to get to it.
Yes it is called dev/hdb3 like normal and is designated Linux LVM. Where are you seeing this? FYI There is another entry further down in the table that is the exact same size and is identified as /dev/system and is designated LVM2 System.
That might be it. You could try changing the root=/dev/hdb3 to root=(hd1,2)/dev/system.
Back to above. Did a Google on the Error19 in grub and came up with the same kernel must be loaded before initrd message. Got one promising hit but alas is in french, which I cannot undedrstand. Maybe jdd could interpret for us.
Sounds like it is finding the boot partition, and thus the kernel image and the initrd, but the kernel's module tree, located on your lvm root, are not being located. We are close. If you can mount your lvm drive and get to it, could you send the 10.0 fstab and lilo.conf? -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 03 February 2007 23:43, Joe Morris (NTM) wrote:
I believe so. Could you mount your boot partition and verify you have a vmlinuz and initrd symlinks to their respective kernel and initrd? Should be as easy as, in a console as root, mount /dev/hdb1 /mnt, then go to /mnt in Konqueror.
Would love to see the fstab in your 10.0 system.
OK, was able to mount the drive. Here is the fstab
/dev/hda2 /workspace ext3 acl,user_xattr 1 2 /dev/hda3 /datastorage ext3 acl,user_xattr 1 2 /dev/hda5 /backup ext3 acl,user_xattr 1 2 /dev/hdb1 / ext3 acl,user_xattr 1 1 LABEL=data /data ext3 acl,user_xattr 1 2 LABEL=home /home ext3 acl,user_xattr 1 2 LABEL=local /local ext3 acl,user_xattr 1 2 LABEL=opt /opt ext3 acl,user_xattr 1 2 LABEL=usr /usr ext3 acl,user_xattr 1 2 LABEL=var /var ext3 acl,user_xattr 1 2 /dev/hda1 /c vfat users,rw,gid=users,umask=0000 0 0 /dev/hdb2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/dvdrecorder /media/ subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/cdrecorder /media/ subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0 none /subdomain subdomainfs noauto 0 0 --------------------------------------------------------------------------------------------- As you can see, I was able to mount my ext3 partitions which are on /dev/hda also. Here is LILO config -------------------------------------------------------------------------------------------- # Modified by YaST2. Last modification on Sat Dec 31 02:10:21 UTC 2005 menu-scheme = Wb:kw:Wb:Wb timeout = 80 lba32 change-rules reset read-only prompt default = Linux message = /boot/message boot = /dev/hda image = /boot/vmlinuz ###Don't change this comment - YaST2 identifier: Original name: linux### label = Linux append = "selinux=0 resume=/dev/hdb2 splash=silent showopts" vga = 0x31a initrd = /boot/initrd root = /dev/hdb1 other = /dev/hda1 ###Don't change this comment - YaST2 identifier: Original name: windows### label = Windows image = /boot/vmlinuz ###Don't change this comment - YaST2 identifier: Original name: failsafe### label = Failsafe append = "showopts ide=nodma apm=off acpi=off noresume selinux=0 edd=off 3" vga = normal initrd = /boot/initrd root = /dev/hdb1 ----------------------------------------------------------------------------------
You could probably mkdir /data1, then use Yast Partitioner to mount the old 10.0 root lvm partition to /data1 to get to it.
I'm afraid I don't understand. I don't know what you mean by using the partitioner to mount the LVM partition.
Yes it is called dev/hdb3 like normal and is designated Linux LVM.
Where are you seeing this?
By looking directly at the partition table in Yast Partioner.
FYI There is another entry further down in the table that is the exact same size and is identified as /dev/system and is designated LVM2 System.
That might be it. You could try changing the root=/dev/hdb3 to root=(hd1,2)/dev/system.
No, tried it. (hd1,2)?? (Why that?) Anyway, I still get the error19 message about kernel before initrd. Bless you Joe, and I can't thank you enough for helping me. I am sure we are close now. Stick with me and I will check back tomorrow night. (after the Superbowl, priorities you know) Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
OK, was able to mount the drive. Here is the fstab
-------------------------------------------------------------------------------- /dev/hda2 /workspace ext3 acl,user_xattr 1 2 /dev/hda3 /datastorage ext3 acl,user_xattr 1 2 /dev/hda5 /backup ext3 acl,user_xattr 1 2 /dev/hdb1 / ext3 acl,user_xattr 1 1 LABEL=data /data ext3 acl,user_xattr 1 2 LABEL=home /home ext3 acl,user_xattr 1 2 LABEL=local /local ext3 acl,user_xattr 1 2 LABEL=opt /opt ext3 acl,user_xattr 1 2 LABEL=usr /usr ext3 acl,user_xattr 1 2 LABEL=var /var ext3 acl,user_xattr 1 2 /dev/hda1 /c vfat users,rw,gid=users,umask=0000 0 0 /dev/hdb2 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/dvdrecorder /media/ subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/cdrecorder /media/ subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0 none /subdomain subdomainfs noauto 0 0
Now we have all the pieces of the puzzle. Try making the following changes and I think you will be set. ### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 February 2007 01:05, Joe Morris (NTM) wrote:
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
I use my /dev/hda1 installation for the same purpose as it is used separate boot partition in Bob's. It has complete /boot directory that is used completely only for version that is installed on /dev/hda1 (stable version). For all other versions, installed on other partitions, are used the grub related entries in /boot/grub and /boot/message file while kernel stuff for each version is located on coresponding partition in /boot directory. This way I have no problems to update kernel using YaST, and I don't try my luck by overwriting MBR on each installation. I have good base for repairs of installations on other partitions. Even if I move new version that deserves attribute stable to /dev/hda1 everything still works if I keep same /boot/grub/menu.lst. The only quirk is that I have to use Advanced tab in Instalation proposal to tell SUSE installer not to install grub. Than later to edit manually section for particular partition in /boot?grub/menu.lst on /dev/hda1. With new SUSE versions that is mostly change in line title SUSE <version> the rest is generic. BTW, have anybody tested how is handled resume option on systems with few installations. Is it possible to happen that you request suspend to disk in one installation and resume in another that is default? -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 February 2007 02:05, Joe Morris (NTM) wrote:
Bob S wrote:
OK, was able to mount the drive. Here is the fstab
------------------------------------------------------------------------- ------- /dev/hda2 /workspace ext3 acl,user_xattr 1 2 /dev/hda3 /datastorage ext3 acl,user_xattr 1 2 /dev/hda5 /backup ext3 acl,user_xattr 1 2 /dev/hdb1 / ext3 acl,user_xattr 1 1 LABEL=data /data ext3 acl,user_xattr 1 2 LABEL=home /home ext3 acl,user_xattr 1 2 LABEL=local /local ext3 acl,user_xattr 1 2 LABEL=opt /opt ext3 acl,user_xattr 1 2 LABEL=usr ......<snip some fstab>.............
Now we have all the pieces of the puzzle. Try making the following changes and I think you will be set.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
Nope, using that removes 10.0 from the menu. GRrrrrrrrr!! Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
On Sunday 04 February 2007 02:05, Joe Morris (NTM) wrote:
Now we have all the pieces of the puzzle. Try making the following changes and I think you will be set.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
Nope, using that removes 10.0 from the menu. GRrrrrrrrr!!
Bob S.
It is the wrapping again. I sent you an attached file via pm. Lines under title should all start with root, kernel, and initrd. Wrapping has messed it up, but after seeing your fstab and lilo.conf, i am pretty confident this will work. My problem before was you mentioned fdisk told you hdb1 was a boot partition, but it was actually root (/). HTH. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 February 2007 18:21, Joe Morris (NTM) wrote:
Bob S wrote:
On Sunday 04 February 2007 02:05, Joe Morris (NTM) wrote:
Now we have all the pieces of the puzzle. Try making the following changes and I think you will be set.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
Nope, using that removes 10.0 from the menu. GRrrrrrrrr!!
Bob S.
It is the wrapping again. I sent you an attached file via pm. Lines under title should all start with root, kernel, and initrd. Wrapping has messed it up, but after seeing your fstab and lilo.conf, i am pretty confident this will work. My problem before was you mentioned fdisk told you hdb1 was a boot partition, but it was actually root (/). HTH.
Hi Joe thanks for sticking with this. No, I was very careful to make sure it didn't wrap. Nevertheless I then copied and pasted the text file you sent me. Same result. On reboot 10.0 does not show up on the menu. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
No, I was very careful to make sure it didn't wrap. Nevertheless I then copied and pasted the text file you sent me. Same result. On reboot 10.0 does not show up on the menu.
Could you please post your menu.lst file in your 10.2. That doesn't sound right. Not showing up at all sounds like there is something wrong with that file. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 05 February 2007 05:07, Joe Morris (NTM) wrote:
Bob S wrote:
No, I was very careful to make sure it didn't wrap. Nevertheless I then copied and pasted the text file you sent me. Same result. On reboot 10.0 does not show up on the menu.
Could you please post your menu.lst file in your 10.2. That doesn't sound right. Not showing up at all sounds like there is something wrong with that file.
OK Joe, Following: ------------------------------------------------------------------------------------------- # Modified by YaST2. Last modification on Thu Feb 1 22:04:23 EST 2007 default 4 timeout 8 gfxmenu (hd2,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=0x31a resume=/dev/sda2 splash=silent showopts initrd /boot/initrd-2.6.18.2-34-default ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.18.2-34-default ### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd ---------------------------------------------------------------------------------------------------------------- The following was that which brought up 10.0 in the boot menu. (But also produced the kernel initrd error 19 ) when executed. ### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz-2.6-15.13-default root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-02-05 16:51, Bob S wrote:
<snip>
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
This is correct as per your /etc/fstab for 10.0 (from your message of Sunday, 0145 EST.)
---------------------------------------------------------------------------------------------------------------- The following was that which brought up 10.0 in the boot menu. (But also produced the kernel initrd error 19 ) when executed.
Are you sure it was a kernel error, or was it a grub error? (Grub error 19 results when the kernel is not loaded prior to attempting to load initrd.)
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz-2.6-15.13-default root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
This is certainly wrong. For 10.0, your root partition is /dev/hdb1 == (hd1,0), and there is no separate /boot partition. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 05 February 2007 18:03, Darryl Gregorash wrote:
On 2007-02-05 16:51, Bob S wrote:
<snip>
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
This is correct as per your /etc/fstab for 10.0 (from your message of Sunday, 0145 EST.)
Hi Darryl, Stick with Joe and I on this. Glad you are following this. The more input and ideas, the better. OK, may be correct but is not bringing up the menu with 10.0 on it. Thus I cannot boot 10,0 (BTW the wrapping is from the email. I assure you that the lines are displayed properly in menu.1st)
------------------------------------------------------------------------- The following was that which brought up 10.0 in the boot menu. (But also produced the kernel initrd error 19 ) when executed.
Are you sure it was a kernel error, or was it a grub error? (Grub error 19 results when the kernel is not loaded prior to attempting to load initrd.)
No, it was a grub error. It did state that the kernel is not loaded prior to attempting to load initrd.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz-2.6-15.13-default root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
This is certainly wrong. For 10.0, your root partition is /dev/hdb1 == (hd1,0), and there is no separate /boot partition.
Well yes, you are probably correct. I was only pointing out to Joe that that was the only iteration that showed 10.0 in the boot menu. (also line wrapped in the email)
Stick with us. I have to be able to mount 10.0 Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
OK Joe, Following: ------------------------------------------------------------------------------------------- # Modified by YaST2. Last modification on Thu Feb 1 22:04:23 EST 2007 default 4
BTW, I would reset this back to 0 til 10.0 is booting OK. Just less work for you.
<snip>
Rest looked good.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd ---------------------------------------------------------------------------------------------------------------- The following was that which brought up 10.0 in the boot menu. (But also produced the kernel initrd error 19 ) when executed.
Are you saying the above (hoping the wrapping is the email programs and not in your file, i.e. you have 5 lines there, one commented, next title next 3 indented, starting with root, then kernel, then initrd.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz-2.6-15.13-default root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
This one should be deleted. This was before I saw your fstab and lilo.conf. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 05 February 2007 18:40, Joe Morris (NTM) wrote:
Bob S wrote:
OK Joe, Following: ------------------------------------------------------------------------- ------------------ # Modified by YaST2. Last modification on Thu Feb 1 22:04:23 EST 2007 default 4
BTW, I would reset this back to 0 til 10.0 is booting OK. Just less work for you.
Yes, OK. But at this point I am not concerned about the work. Just want 10.0 to show up and boot.
<snip>
Rest looked good.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
Was wrapped in your reply to me. I assure you it is not wrapped in Menu.1st. May look good, but does not work. 10.0 does not show up in the boot menu with that statement.
------------------------------------------------------------------------- The following was that which brought up 10.0 in the boot menu. (But also produced the kernel initrd error 19 ) when executed.
Are you saying the above (hoping the wrapping is the email programs and not in your file, i.e. you have 5 lines there, one commented, next title next 3 indented, starting with root, then kernel, then initrd.
Again, I assure you that the wrapping is from the email. The menu.1st file is formatted properly. And what was it you were going to ask?
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz-2.6-15.13-default root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
This one should be deleted. This was before I saw your fstab and lilo.conf.
OK, It has already been removed from Menu.1st, back 3 or 4 emails ago.. I am pointing out/reminding you that it is the only iteration that produces 10.0 in the boot menu. (but then fails with the grub error 19 message)
Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
On Monday 05 February 2007 18:40, Joe Morris (NTM) wrote:
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd
I am pointing out/reminding you that it is the only iteration that produces 10.0 in the boot menu. (but then fails with the grub error 19 message)
OK the only way for it to not show up as a choice is for there to be a problem with your menu.lst file (which I asked you to post). Alternatively, does it show up as a choice in Yast, System< Bootloader? If so, go ahead and try to edit it there, making sure it has the lines as shown above. The first commented out line is not necessary. If Yast sees it and it looks good there but still does not show up in the grub menu, then please post your menu.lst file. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 06 February 2007 06:17, Joe Morris (NTM) wrote:
I am pointing out/reminding you that it is the only iteration that produces 10.0 in the boot menu. (but then fails with the grub error 19 message)
OK the only way for it to not show up as a choice is for there to be a problem with your menu.lst file (which I asked you to post). Alternatively, does it show up as a choice in Yast, System< Bootloader? If so, go ahead and try to edit it there, making sure it has the lines as shown above. The first commented out line is not necessary. If Yast sees it and it looks good there but still does not show up in the grub menu, then please post your menu.lst file.
Just a thought here.... Since it didn't show up, it makes me think he's adding it to the wrong menu.lst file. He has 10.0 and 10.2 each with their own /boot/grub/menu.lst I would assume. Perhaps he's dealing with the wrong one? Since he installed 10.2, I would assume that the MBR is pointing to the 10.2 /boot/grub I've never heard of a menu item not showing up without some error being shown. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bruce Marshall wrote:
Just a thought here.... Since it didn't show up, it makes me think he's adding it to the wrong menu.lst file. He has 10.0 and 10.2 each with their own /boot/grub/menu.lst I would assume. Perhaps he's dealing with the wrong one?
No, the 10.0 used lilo.
Since he installed 10.2, I would assume that the MBR is pointing to the 10.2 /boot/grub
I've never heard of a menu item not showing up without some error being shown.
Same here. Since he used to use lilo, his 10.2 should be the only grub and menu.lst. And I agree, I don't understand how it doesn't even show up either. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-02-06 16:38, Joe Morris (NTM) wrote:
Bruce Marshall wrote:
Just a thought here.... Since it didn't show up, it makes me think he's adding it to the wrong menu.lst file. He has 10.0 and 10.2 each with their own /boot/grub/menu.lst I would assume. Perhaps he's dealing with the wrong one?
No, the 10.0 used lilo.
Since he installed 10.2, I would assume that the MBR is pointing to the 10.2 /boot/grub
I've never heard of a menu item not showing up without some error being shown.
Same here. Since he used to use lilo, his 10.2 should be the only grub and menu.lst. And I agree, I don't understand how it doesn't even show up either.
This is becoming almost beyond comprehension. I agree with your suggestion that Bob should see if the 10.0 menu selection shows up in the Yast bootloader configuration. If not, he should edit it into the menu, then check with a reboot. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 06 February 2007 17:38, Joe Morris (NTM) wrote:
Bruce Marshall wrote:
Just a thought here.... Since it didn't show up, it makes me think he's adding it to the wrong menu.lst file. He has 10.0 and 10.2 each with their own /boot/grub/menu.lst I would assume. Perhaps he's dealing with the wrong one?
No, the 10.0 used lilo.
Since he installed 10.2, I would assume that the MBR is pointing to the 10.2 /boot/grub
I've never heard of a menu item not showing up without some error being shown.
Same here. Since he used to use lilo, his 10.2 should be the only grub and menu.lst. And I agree, I don't understand how it doesn't even show up either.
OK Gentlemen, Stick with me .....Please??? I checked Yast - Bootloader and 10.0 was there. But there was practically nothing describing/pertaining to it. No /dev/root - no nothing. So I edited the file extensively and saved it. Rebooted, and 10.0 showed up in the boot menu. Some success I guess. But now it fails with an Error 15 File not found. Grrrr......Did some Googling on the grub error 15 but didn't find anything that I thought would pertain to this. Here is the present version of my menu.1st: ------------------------------------------------------------- # Modified by YaST2. Last modification on Tue Feb 6 22:12:27 EST 2007 default 4 timeout 15 gfxmenu (hd2,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=0x31a resume=/dev/sda2 splash=silent showopts initrd /boot/initrd-2.6.18.2-34-default ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,0) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.18.2-34-default ### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz-2.6-15.13-default root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd-2.6-15.13-default -------------------------------------------------------------------------------------------- It does wrap in this outgoing e-mail at "resume" for 10.0.It is all one line in my Menu.1st. I also attached a text file. Thanks for your patience Bob S
On 2007-02-06 22:55, Bob S wrote:
<snip>
Rebooted, and 10.0 showed up in the boot menu. Some success I guess. But now it fails with an Error 15 File not found. Grrrr......Did some Googling on the grub error 15 but didn't find anything that I thought would pertain to this.
All the grub errors are in the grub info files, in the "troubleshooting" section for stage 2. Make sure you have the "info" package installed, then run "info grub". Basically, the error means all the syntax for disk/partition info is correct, but a file cannot be found. Did the error message specify which file it could not find?
<snip>
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz-2.6-15.13-default root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd-2.6-15.13-default Boot to 10.2, then mount /dev/hdb1, and check for the presence of the correct kernel and initrd files. One or both of them is not present for error 15 to occur.
You should not even have to specify the exact versions of the files. There should be symlinks, kernel and initrd respectively, pointing to the current files. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 07 February 2007 00:11, Darryl Gregorash wrote:
On 2007-02-06 22:55, Bob S wrote: <snip>
All the grub errors are in the grub info files, in the "troubleshooting" section for stage 2. Make sure you have the "info" package installed, then run "info grub". Basically, the error means all the syntax for disk/partition info is correct, but a file cannot be found. Did the error message specify which file it could not find?
No, did not specify the file. And the grub info file is installed. Could not bring up the troubleshooting section though. Probably because I have never dealt with grub before.
<snip> .........<more snip>.....................
Boot to 10.2, then mount /dev/hdb1, and check for the presence of the correct kernel and initrd files. One or both of them is not present for error 15 to occur.
Did that. Both the vmlinuz and the initrd files are present in the /boot file of hdb1. That is where they should be, right???
You should not even have to specify the exact versions of the files. There should be symlinks, kernel and initrd respectively, pointing to the current files.
Yeah, I know, and they are there. But I am getting so frustrated that I am trying to leave nothing to chance.
Stick with me, everybody, please. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz-2.6-15.13-default root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd-2.6-15.13-default -------------------------------------------------------------------------------------------- It does wrap in this outgoing e-mail at "resume" for 10.0.It is all one line in my Menu.1st.
Try dropping the version info, i.e. vmlinuz instead of vmlinuz-2.6.-15.13-default, and that is your problem, it is actually 2.6.15.13, no dash between 6 and 15. But use vmlinuz and initrd without the version, which will use the symlinks (which BTW was what your lilo used). -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 7 Feb 2007, Joe Morris (NTM) wrote:
Bob S wrote:
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz-2.6-15.13-default root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd-2.6-15.13-default -------------------------------------------------------------------------------------------- It does wrap in this outgoing e-mail at "resume" for 10.0.It is all one line in my Menu.1st.
Try dropping the version info, i.e. vmlinuz instead of vmlinuz-2.6.-15.13-default, and that is your problem, it is actually 2.6.15.13, no dash between 6 and 15. But use vmlinuz and initrd without the version, which will use the symlinks (which BTW was what your lilo used).
To be really clear use
### Added 10.0 Boot ###
title openSUSE 10.0
root (hd1,0)
kernel /boot/vmlinuz root=/dev/hdb1 vga=0x31aresume=/dev/hdb2 splash=silent showopts
initrd /boot/initrd
All one line as you have noted before.
--
Boyd Gerber
On Wednesday 07 February 2007 06:00, Joe Morris (NTM) wrote:
Bob S wrote:
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,0) kernel /boot/vmlinuz-2.6-15.13-default root=/dev/hdb1 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd /boot/initrd-2.6-15.13-default ------------------------------------------------------------------------- ------------------- It does wrap in this outgoing e-mail at "resume" for 10.0.It is all one line in my Menu.1st.
Try dropping the version info, i.e. vmlinuz instead of vmlinuz-2.6.-15.13-default, and that is your problem, it is actually 2.6.15.13, no dash between 6 and 15. But use vmlinuz and initrd without the version, which will use the symlinks (which BTW was what your lilo used).
Joe, especially you, and Darryl, and all the others who contributed and tried to help. Thank You, Thank You, Thank You. That worked! I can now boot into 10.0 where all of my important stuff is. You cannot imagine how happy I am ! Soooo, the problem finally and basically boils down to the Yast Bootloader which I had to edit. (aside from my dumb assumptions and mistakes) Sooo....now if I understand this correctly my 10.0 and windows hard drives are booting from Grub instead of LILO. Am going to abandon any further work on 10.2 for at least a week. I was only setting it up as a test bed anyway. Many more problems than just this booting thing. ie. sound settings don't work from boot to boot, can't see linux partitions on the other drives, hal doesn't work properly, etc. etc. But they will be all separate questions in the future when I am ready to tackle this again. Thanks again guys. This is the greatest list in all of Linux world Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Soooo, the problem finally and basically boils down to the Yast Bootloader which I had to edit. Actually, it just correctly edited your menu.lst. There was something wrong with your edits. Sooo....now if I understand this correctly my 10.0 and windows hard drives are booting from Grub instead of LILO.
Correct. The nice thing about grub is to change things you only need to edit your menu.lst file (with an appropriate editor ;-) ) and you are done. No need to run lilo nor grub. No changes need to be made in the mbr.
Thanks again guys. This is the greatest list in all of Linux world
Glad to finally see the [Solved]. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 08 February 2007 04:58, Joe Morris (NTM) wrote:
Bob S wrote:
Sooo....now if I understand this correctly my 10.0 and windows hard drives are booting from Grub instead of LILO.
Correct. The nice thing about grub is to change things you only need to edit your menu.lst file (with an appropriate editor ;-) ) and you are done. No need to run lilo nor grub. No changes need to be made in the mbr.
Joe, and/or others, To clarify my understanding. One of the reasons I did not use Grub in the past was that I didn't understand how it worked. When using Lilo it edited the MBR, correct? What is happening now when using Grub? What is in the MBR now? It doesn't change? Does the MBR now refer the boot process to Menu.1st? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
One of the reasons I did not use Grub in the past was that I didn't understand how it worked. That is usually the main reason most new things are left untried... the
On Friday 09 February 2007 22:13, Bob S wrote: positive way to put it is that most of us use what we know and are comfortable with...
When using Lilo it edited the MBR, correct? What is happening now when using Grub? What is in the MBR now? It doesn't change? Does the MBR now refer the boot process to Menu.1st? Phase #1 resides in the MBR, and contains just enough to load phase #2.
The cool thing is that grub knows how to read the file system(s) before the system is booted... so it can find all of phase #2 on the drive under /boot. The menu is built on-the-fly from the /boot/grub/menu.lst file (located on the filesystem) and not written to the MBR. (lilo configuration is contained on the mbr... so lilo.conf is used when the mbr is written) Because the config for grub is *not* written to the mbr it can be changed dynamically on bootup (from the grub command menu). Also, changes to the menu configuration (menu.lst) are read at bootup from /boot/grub/menu.lst so the mbr does not have to be written when changes are made to the menu.lst file. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 09 February 2007 23:56, M Harris wrote:
On Friday 09 February 2007 22:13, Bob S wrote:
One of the reasons I did not use Grub in the past was that I didn't understand how it worked.
That is usually the main reason most new things are left untried... the positive way to put it is that most of us use what we know and are comfortable with...
When using Lilo it edited the MBR, correct? What is happening now when using Grub? What is in the MBR now? It doesn't change? Does the MBR now refer the boot process to Menu.1st?
Phase #1 resides in the MBR, and contains just enough to load phase #2.
The cool thing is that grub knows how to read the file system(s) before the system is booted... so it can find all of phase #2 on the drive under /boot. The menu is built on-the-fly from the /boot/grub/menu.lst file (located on the filesystem) and not written to the MBR. (lilo configuration is contained on the mbr... so lilo.conf is used when the mbr is written) Because the config for grub is *not* written to the mbr it can be changed dynamically on bootup (from the grub command menu). Also, changes to the menu configuration (menu.lst) are read at bootup from /boot/grub/menu.lst so the mbr does not have to be written when changes are made to the menu.lst file.
That answers my question. Thanks Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 06 February 2007 23:55, Bob S wrote:
On Tuesday 06 February 2007 17:38, Joe Morris (NTM) wrote:
Bruce Marshall wrote:
Just a thought here.... Since it didn't show up, it makes me think he's adding it to the wrong menu.lst file. He has 10.0 and 10.2 each with their own /boot/grub/menu.lst I would assume. Perhaps he's dealing with the wrong one?
No, the 10.0 used lilo.
Since he installed 10.2, I would assume that the MBR is pointing to the 10.2 /boot/grub
I've never heard of a menu item not showing up without some error being shown.
Same here. Since he used to use lilo, his 10.2 should be the only grub and menu.lst. And I agree, I don't understand how it doesn't even show up either.
OK Gentlemen,
Stick with me .....Please???
I checked Yast - Bootloader and 10.0 was there. But there was practically nothing describing/pertaining to it. No /dev/root - no nothing. So I edited the file extensively and saved it.
Rebooted, and 10.0 showed up in the boot menu. Some success I guess. But now it fails with an Error 15 File not found. Grrrr......Did some Googling on the grub error 15 but didn't find anything that I thought would pertain to this.
Here is the present version of my menu.1st: ------------------------------------------------------------- # Modified by YaST2. Last modification on Tue Feb 6 22:12:27 EST 2007 default 4 timeout 15 gfxmenu (hd2,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda1 vga=0x31a resume=/dev/sda2 splash=silent showopts initrd /boot/initrd-2.6.18.2-34-default
Something here doesn't look right. I assume that on 10.0 you have your /boot contained on the root partition since you have grub-root as (hd1,0) and system root as /dev/hdb1 which would be the same. Now for 10.2, I'm seeing grub-root as (hd2,0) which would be hdc or sdc unless you have things mapped differently and your system root is sda1 Didn't know you had three drives... ???????? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
--- "Joe Morris (NTM)"
I've never heard of a menu item not showing up without some error being shown.
Same here. Since he used to use lilo, his 10.2 should be the only grub and menu.lst. And I agree, I don't understand how it doesn't even show up either.
Most likely, it does show up, but being at the bottom of the list he has to scroll the menu to see it. It would also help if he moved the SUSE 10.0 stanza to be the second entry, right after the SUSE 10.2 entry. ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-02-03 18:31, Joe Morris (NTM) wrote:
Bob S wrote:
On Saturday 03 February 2007 02:27, Joe Morris (NTM) wrote:
Add this to this file.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
Sorry, watch the wrapping. Perhaps some explanation of the above will help. [Note, i changed a few items above from original try]. root is for grub to find the root of the OS (I originally thought it needed to be the boot partition). I forgot since I have not had a separate boot for some years. Kernel like is to load the kernel image. Here I added
"Root" in grub most certainly is the location of the kernel, ie. of /boot. I assume the (hd1,0) is correct. Using that method to specify the kernel and initrd locations, the "root" command is quite unnecessary. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 February 2007 02:00, Darryl Gregorash wrote:
On 2007-02-03 18:31, Joe Morris (NTM) wrote:
Bob S wrote:
On Saturday 03 February 2007 02:27, Joe Morris (NTM) wrote:
Add this to this file.
### Added 10.0 Boot ### title openSUSE 10.0 root (hd1,2) kernel (hd1,0)/vmlinuz root=/dev/hdb3 vga=0x31a resume=/dev/hdb2 splash=silent showopts initrd (hd1,0)/initrd
Sorry, watch the wrapping. Perhaps some explanation of the above will help. [Note, i changed a few items above from original try]. root is for grub to find the root of the OS (I originally thought it needed to be the boot partition). I forgot since I have not had a separate boot for some years. Kernel like is to load the kernel image. Here I added
"Root" in grub most certainly is the location of the kernel, ie. of /boot. I assume the (hd1,0) is correct. Using that method to specify the kernel and initrd locations, the "root" command is quite unnecessary.
Ummmm...Don't quite understand what you are saying. Would you please explain more? Thanks Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 February 2007 02:00, Darryl Gregorash wrote:
<snip> "Root" in grub most certainly is the location of the kernel, ie. of /boot. I assume the (hd1,0) is correct. Using that method to specify the kernel and initrd locations, the "root" command is quite unnecessary.
Ummmm...Don't quite understand what you are saying. Would you please explain more? Thanks What is specified in the "root" command of a grub menu item has nothing to do with what gets mounted as /. It is the location of /boot. The
On 2007-02-04 16:19, Bob S wrote: partition that gets mounted as / goes into the kernel "root=" parameter. Thus, if you have /dev/hdb2 (in grub, that becomes (hd1,1)) mounted as /boot and /dev/hdb1 mounted as /, the proper grub commands are: root (hd1,1) kernel /vmlinuz root=/dev/hdb1 .... initrd /initrd In essence, the grub "root" command is saying, "this is the default device for unresolved device references." You may dispense with the root command, at least in some versions of grub (such as the one distributed with 9.3), provided that all device references are fully resolved: kernel (hd1,1)/vmlinuz root=/dev/hda1 ... initrd (hd1,1)/initrd Suppose now that /boot is not on a separate partition, but resides on the root partition, /dev/hdb1. Then your menu item looks like this: root (hd1,0) kernel /boot/vmlinuz root=/dev/hdb1 .... initrd /boot/initrd Here we need to preface the paths with "/boot" because it is now a directory on (hd1,0), rather than a separate device. Again, the "root" command may be left out, with proper device referencing: kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 .... initrd (hd1,0)/boot/initrd -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
On Friday 02 February 2007 05:08, Joe Morris (NTM) wrote:
Just mount your 10.0 boot directory (if on it own partition or if in /) so you can compare the 10.0 grub device map and menu.lst, and add the correct entry to the menu.lst in the 10.2 grub, where it already boots from and already has an entry for win98 and 10.2.
Well that is the problem. I can't mount 10.0. It is on a completely separate hard drive. Even if I find out how to do that, I don't have a 10.0 grub device map. I was using LILO to mount 10.0
OK, sorry I forgot (looks again at subject). In that case, you can still mount it. as root, you can access it via mount /dev/xxxx /mnt, with xxxx corresponding to the drive and partition, like hdb2. This would allow you access to the files.
When I put the 10.0 DVD into the machine and boot the installed system it boots 10.2 and I have not figured out how to mount 10.0 Figured I could use Yast to fix it.
You do not have to boot to it to fix it. We will get it booting from within a 10.2 boot.
Think I could fix it from within 10.2 ?? Definitely. It isn't broke. Grub just needs the info given it to boot it. Trouble is, I know absolutely nothing about grub. Been using lilo all of these years.
It is different and takes some getting used to. but, it is not that bad since you have 2 systems already booting. You only need to give it a correct entry in your 10.2 menu.lst, perhaps something in device.map, and hopefully that is it. To know what to put, unless you know it, could you send to the list your 10.2 /boot/grub/menu.lst, /boot/grub/device.map, and the output of fdisk -l (all copied and pasted into your email, no attachments). We should get you booting into 10.0 in a few minutes. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Alexey Eremenko -
Bob S -
Boyd Lynn Gerber -
Bruce Marshall -
Darryl Gregorash -
frank nelson -
Joe Morris (NTM) -
M Harris -
Rajko M.