"Error 22: No Such Partition" from GRUB after openSUSE 11.3 install
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"Error 22: No Such Partition" from GRUB after openSUSE 11.3 install
I tried to install openSUSE 11.3 from the Gnome live CD. I had four partitions set already for /boot, /, /home (ext4 all) and swap from a previous failed Linux Mint installation. I installed into them, and formatted them. The /boot partition is primary and pretty well into the disk. The other partitions are logical and at the end of an extended partition which has several partitions before them. There's also an inactive Windows primary partition at the start, and a second disk with a Windows installation and a lot of logical partitions.
After install, it looks like booting into grub works fine, and I get "Error 22: No Such Partition". I then get to the GRUB menu. If I choose openSUSE from there I get:
Booting 'openSUSE 11.3'
root (hd1,2)
Error 22: No Such Partition
Booting from the live CD it looks like /boot, / and /home contain data, so they must be formatted fine.
Could you provide that actual drive and partition details.
Boot with a live disk and get fdisk -l. Also the GRUB configuration would be helpful.
GRUB numbers disks/partitions starting from 0.
Here it's looking for the partition with /boot on it. This is pointing to the 3 partition on the 2nd disk:
Code:
Booting 'openSUSE 11.3'
root (hd1,2)
Error 22: No Such Partition
If thats not where your boot partition is you need to change the GRUB config. How you do that depends on the version of GRUB. Not sure which openSUSE is using right now.
GRUB provides the ability to modify the entries and an excellent command line interface.
You can change that root line and see if it boots correctly.
No, that's actually where '/boot' is. '/' is on the 13th partition, IIRC. I'm confused now, thought, because if I understand jasohl correctly, that should be '/boot' (and it is), but your version makes more sense, since '/' is the OS itself.
I've since installed Fedora, the only distro so far that installed without problem, but if this really should point to '/' then it's probably an easy fix, and I might try openSUSE again, since I think it's friendlier.
I made a new install, cleared up 20GB of space at the start of the disk and put '/' there (and booting is from there). Wasn't easy, since that partition manager in the installer is pretty awful, but it's done. Still doesn't work, but the error looks more informative.
Here's the menu.lst for GRUB:
Code:
# Modified by YaST2. Last modification on Wed Aug 4 07:20:01 IDT 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
gfxmenu (hd1,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.3
root (hd1,0)
kernel /boot/vmlinuz-2.6.34-12-desktop root=/dev/disk/by-id/ata-ST3500418AS_5VM49NQK-part1 resume=/dev/disk/by-id/ata-ST3500418AS_5VM49NQK-part12 splash=silent quiet showopts vga=0x375
initrd /boot/initrd-2.6.34-12-desktop
###Don't change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
rootnoverify (hd0,0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
map (hd1) (hd0)
map (hd0) (hd1)
rootnoverify (hd1,1)
makeactive
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.3
root (hd1,0)
kernel /boot/vmlinuz-2.6.34-12-desktop root=/dev/disk/by-id/ata-ST3500418AS_5VM49NQK-part1 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x375
initrd /boot/initrd-2.6.34-12-desktop
The error is:
Filesystem type unknown, partition type 0x7
kernel /boot/... (i.e., the command from menu.lst for linux)
Error 17: Cannot mount selection partition
More or less what I expected - the BIOS is enumerating the disks differently to the Linux initscripts. Try this - at the boot menu, highlight the openSuse option, then hit the "e" key (for edit). Then highlight the "root (hd1,0)" and hit "e"again. Change the line to "root (hd0,0)" and hit enter. Then "b" to boot.
This is a temporary change only, just for a test.
Last edited by syg00; 08-04-2010 at 04:17 AM.
Reason: d'oh
Thanks! I also got this response at the openSUSE forums, though I only saw the response after posting the above. I changed from hd1 to hd0 in menu.lst and got a working openSUSE desktop.
syg00,
Just curious, how did you figure that "BIOS is enumerating the disks differently to the Linux initscripts."
fdisk shows the bootable Linux partition is on /dev/sdb1.
My first thought was
/dev/sda > primary master
/dev/sdb > primary slave.
But if root(hd0,0) cause is it to boot correctly then /dev/sdb must be as primary drive designated by BIOS. If I'm understanding you correctly.
How did you catch that?
That's NTFS - so the stage1 loader code is looking at the "wrong" disk. The "fdisk -l" is from a Linux system (i.e. after initscripts have run) - grub install would have (likely) been run from this same environment.
Recent Ubuntus (for example) got around this by hacking (classic) grub to use uuid instead of root. Grub2 has that option as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.