Did a “zypper refresh” followed by “zypper update”. Finished successfully (I think), and then rebooted immediately. Now system only boots into grub (version 0.97) and stops with error 15: file not found. Running temporarily on Mint LiveCD.
# cat etc/SuSE-release
openSUSE 11.4 (i586)
VERSION = 11.4
CODENAME = Celadon
mint opensuse_root #
# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005095f
Device Boot Start End Blocks Id System
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c33e1
Device Boot Start End Blocks Id System
/dev/sdb1 1 10 71680 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2 * 10 1577 12587008 83 Linux
Partition 2 does not end on cylinder boundary.
/dev/sdb3 1577 1838 2096128 82 Linux swap / Solaris
Partition 3 does not end on cylinder boundary.
/dev/sdb4 1838 9730 63394904 8e Linux LVM
Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d461c
Device Boot Start End Blocks Id System
mint opensuse_root # df -h
Filesystem Size Used Avail Use% Mounted on
aufs 1007M 692M 315M 69% /
none 997M 644K 997M 1% /dev
/dev/sr0 4.0G 4.0G 0 100% /cdrom
/dev/loop0 642M 642M 0 100% /rofs
none 1007M 420K 1006M 1% /dev/shm
tmpfs 1007M 116K 1006M 1% /tmp
none 1007M 104K 1006M 1% /var/run
none 1007M 0 1007M 0% /var/lock
/dev/sdb2 12G 9.5G 1.8G 84% /mnt/opensuse_root
/dev/sdb1 68M 48M 17M 74% /mnt/opensuse_root/boot
mint opensuse_root #
Tried to figure out more about grub status on system
mint opensuse_root # chroot /mnt/opensuse_root /bin/bash
mint:/>
mint:/> grub
bash: grub: command not found
mint:/> grub2
bash: grub2: command not found
mint:/> rpm -qa|grep -i grub
grub2-1.98-12.1.i586
mint:/>
mint:/> ls -l /boot
total 41910
-rw------- 1 root root 512 Aug 17 2010 backup_mbr
lrwxrwxrwx 1 root root 1 Aug 17 2010 boot -> .
-rw-r--r-- 1 root root 1236 Feb 21 2011 boot.readme
-rw-r--r-- 1 root root 124871 Oct 29 18:20 config-2.6.37.6-24-default
-rw-r--r-- 1 root root 122382 Oct 29 18:21 config-2.6.37.6-24-desktop
drwxr-xr-x 2 root root 1024 Jan 15 20:02 grub
drwxr-xr-x 3 root root 5120 Jul 17 2012 grub2
lrwxrwxrwx 1 root root 26 Jan 10 17:58 initrd -> initrd-2.6.37.6-24-default
-rw-r--r-- 1 root root 6631424 Jan 10 17:59 initrd-2.6.37.6-24-default
-rw-r--r-- 1 root root 11120640 Jan 10 17:58 initrd-2.6.37.6-24-desktop
drwx------ 2 root root 12288 Aug 17 2010 lost+found
-rw-r--r-- 1 root root 548352 Jan 10 17:43 message
-rw-r--r-- 1 root root 563017 Oct 29 20:03 symtypes-2.6.37.6-24-default.gz
-rw-r--r-- 1 root root 558980 Oct 29 19:48 symtypes-2.6.37.6-24-desktop.gz
-rw-r--r-- 1 root root 199554 Oct 29 20:01 symvers-2.6.37.6-24-default.gz
-rw-r--r-- 1 root root 195437 Oct 29 19:44 symvers-2.6.37.6-24-desktop.gz
-rw-r--r-- 1 root root 1635590 Oct 29 19:48 System.map-2.6.37.6-24-default
-rw-r--r-- 1 root root 1783245 Oct 29 19:31 System.map-2.6.37.6-24-desktop
-rw-r--r-- 1 root root 5127710 Oct 29 20:01 vmlinux-2.6.37.6-24-default.gz
-rw-r--r-- 1 root root 5743535 Oct 29 19:44 vmlinux-2.6.37.6-24-desktop.gz
lrwxrwxrwx 1 root root 27 Jan 10 17:58 vmlinuz -> vmlinuz-2.6.37.6-24-default
-rw-r--r-- 1 root root 4020160 Oct 29 19:48 vmlinuz-2.6.37.6-24-default
-rw-r--r-- 1 root root 4512384 Oct 29 19:31 vmlinuz-2.6.37.6-24-desktop
mint:/>
Usually the first boot disk is /dev/sda, but in your case system appears to boot from /dev/sdb. What is disk boot order in BIOS? Could you show device.map from /boot/grub?
mint grub # pwd
/mnt/opensuse_root/boot/grub
mint grub # file dev*
device.map: ASCII text
device.map.old: ASCII text
mint grub # cat device.map
(hd0) /dev/disk/by-id/ata-ST380215A_5QZ0A66D
mint grub # cat device.map.old
(hd0) /dev/disk/by-id/ata-ST380215A_5QZ0A66D
and reboot. From what I see, that’s the disk which the system boots from, and it holds Legacy GRUB code, which should be replaced by the GRUB2 code. Please let know if this worked.
Bummer! Neither grub nor grub2 is available on the LiveCD.
mint root # cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=11
DISTRIB_CODENAME=katya
DISTRIB_DESCRIPTION="Linux Mint 11 Katya"
mint root # grub2
No command 'grub2' found, did you mean:
Command 'grub' from package 'grub' (main)
grub2: command not found
mint root # grub2-install /dev/sdb
No command 'grub2-install' found, did you mean:
Command 'grub-install' from package 'lupin-support' (main)
Command 'grub-install' from package 'grub-coreboot' (universe)
Command 'grub-install' from package 'grub' (main)
Command 'grub-install' from package 'grub-efi-ia32' (main)
Command 'grub-install' from package 'grub-ieee1275' (universe)
Command 'grub-install' from package 'grub-efi-amd64' (main)
Command 'grub-install' from package 'grub-pc' (main)
grub2-install: command not found
mint root #
On 2013-01-19 21:16, Knurpht wrote:
> and reboot. From what I see, that’s the disk which the system boots
> from, and it holds Legacy GRUB code, which should be replaced by the
> GRUB2 code. Please let know if this worked.
He is using openSUSE 11.4, only grub 1 is available there.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Thanks everyone for posting. I’m a bit confused now.
In reply to arvidjaar with respect to menu.lst
“Who created it? It looks exceptionally strange. Did you edit it manually?”
I’m quite sure I didn’t edit it myself. I presume the file was created upon install, however I wouldn’t know if the file was changed during “zypper update”.
I don’t know, but I wouldn’t be surprised since apparently grub legacy was (partlyu) switched to grub2 during the “update”.
Surely I can edit the menu.lst as you suggest, but I’m confused regarding whether that gives any effect if grub (legacy) vs. grub2 is the issue.
Please clarify?
In reply to Knurpht
Did you follow the instructions from the article? From what I see I get that the chroot to the installed system is no longer present.
I did read the article. I just got confused on the grub(legacy) grub2 issue. The article proposes grub2. As you self mentioned only grub (legacy) is available for my system (Open SuSE 11.4). This is what I get from asking about grub
Now I’m getting confused too. I admitted Carlos was right, you’re on 11.4 so you should have GRUB, and not GRUB2, now you’re posting output from the 11.4 install which says
i | grub2 | Bootloader with support for Linux, Multiboot and more | package
where the " i " means “installed”. So, one way or another you installed GRUB2 on the 11.4 install.
Another thing: 11.4 is at it’s end of life. Before we start spending a lot of time to get this working, could this be a good moment to move to 12.2?
On 2013-01-20 16:06, durque wrote:
> I’m quite sure I didn’t edit it myself. I presume the file was created
> upon install, however I wouldn’t know if the file was changed during
> “zypper update”.
> I don’t know, but I wouldn’t be surprised since apparently grub legacy
> was (partlyu) switched to grub2 during the “update”.
An upgrade of 11.4 to 12.1 keeps the same grub version 1 running, but
adds a section for grub2 so that you can try it.
An update of 11.4 means that you keep the same 11.4 with some updated
packages, and does not install any grub2.
Upgrade and Update have specific meanings here.
As you showed the output of “/etc/SuSE-release” to be for 11.4, then
that’s the version you have, and it is impossible you can have grub 2 -
unless you have done some very weird things there that you would have to
explain.l
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
On 2013-01-20 16:36, Knurpht wrote:
>
> Now I’m getting confused too. I admitted Carlos was right, you’re on
> 11.4 so you should have GRUB, and not GRUB2, now you’re posting output
> from the 11.4 install which says
>
> Code:
> --------------------
> i | grub2 | Bootloader with support for Linux, Multiboot and more | package
> --------------------
> where the " i " means “installed”. So, one way or another you installed
> GRUB2 on the 11.4 install.
This is very confusing indeed.
durque, what kind of update did you do?
Or is that output from mint and not openSUSE?
> Another thing: 11.4 is at it’s end of life. Before we start spending a
> lot of time to get this working, could this be a good moment to move to
> 12.2?
Unless switching to Evergreen…
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Don’t know how grub2 got in there. Grub2 must have followed in the “zypper update”-process. I had no plan to move to grub2.
Regarding move to 12.2:
A very good point and that’s the plan. In the “long” run. However, I hope to keep this running a couple of more weeks/months while I decide on new HW. I’m thinking of getting one of those build-yourself-kit’s, moving to 64bit and the works…
So, if it’s not too much hussle, getting the boot going on this “11.4-end-of-life” would be appreciated.
Followed the mentioned article. Here’s the output.
mint root # df -h
Filesystem Size Used Avail Use% Mounted on
aufs 1007M 744M 263M 74% /
none 997M 648K 997M 1% /dev
/dev/sr0 4.0G 4.0G 0 100% /cdrom
/dev/loop0 642M 642M 0 100% /rofs
none 1007M 208K 1006M 1% /dev/shm
tmpfs 1007M 12M 995M 2% /tmp
none 1007M 104K 1006M 1% /var/run
none 1007M 0 1007M 0% /var/lock
/dev/sdb2 12G 9.5G 1.8G 84% /mnt/opensuse_root
/dev/sdb1 68M 48M 17M 74% /mnt/opensuse_root/boot
mint root # mount --bind /dev/ /mnt/opensuse_root/dev
mint root # chroot /mnt/opensuse_root /bin/bash
mint:/ # mount /proc
mount: proc already mounted
mint:/ # mount /sys
mount: sysfs already mounted or /sys busy
mount: according to mtab, sysfs is already mounted on /sys
mint:/ #
On 01/20/2013 04:36 PM, Knurpht wrote:
> 11.4 is at it’s end of life. Before we start spending a
> lot of time to get this working, could this be a good moment to move to
> 12.2?
hmmmmm…i really wonder how grub2 got into this story…i’d like
‘durque’ run this command and return the in/output to here, using code
tags as described in http://goo.gl/i3wnr
grep "enabled=1" /etc/zypp/repos.d/*
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
On 2013-01-20 17:06, durque wrote:
> Don’t know how grub2 got in there. Grub2 must have followed in the
> “zypper update”-process. I had no plan to move to grub2.
Impossible. No update can have installed grub2 into an 11.4 system.
Please post the output of “zyper lr --details”.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
I wonder, is this discussion going in the direction of how grub2 got into this system or am I missing a crucial point on where to go next to get the system to actually successfully boot. Either in grub (legacy) or grub2?
