Bug 462578 - Installing openSUSE11.1 -GRUB - .Error 22 No such partition
Summary: Installing openSUSE11.1 -GRUB - .Error 22 No such partition
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: Final
Hardware: i686 openSUSE 11.1
: P2 - High : Major (vote)
Target Milestone: ---
Assignee: Torsten Duwe
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-26 12:42 UTC by Frans Leerink
Modified: 2010-03-11 13:54 UTC (History)
5 users (show)

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Requested y2logs (1.11 MB, application/x-gzip)
2009-01-12 15:25 UTC, Frans Leerink
Details
archive with files concerning GRUB (1022 bytes, application/x-bzip)
2009-01-22 20:00 UTC, Martin Konopka
Details
archived /var/log/YaST2 directory (530.25 KB, application/x-bzip)
2009-01-22 20:02 UTC, Martin Konopka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frans Leerink 2008-12-26 12:42:51 UTC
Hello,

I have installed openSUSE 11.1 from a 8 GB USB-Stick, made according to URL

   http://en.opensuse.org/SuSE_install_from_USB_drive

from the openSUSE 11.1 dvd iso.  The Netbook is a MEDION AKOYA-E1210,
MD97160 with Windows XP. This netbook is basically a cloon of the MSI Wind.

The dual-boot install went oke until the last moment - installing GRUB.
At that moment the system says that installing Grub went not oke and gave me
the possibility to change the grub configuration settings. I changed the
location for Grub from "logical partition (hd0,3) to MBR" but this change
resulted in the following displayed error message.

Error while installing GRUB

GNU GRUB version 0.97 (640k lower/3072k upper memory)

[Minimal BASH-like line editing is supported. For the first word, TAB lists
possible command completions. Anywhere else TAB lists the possible
completion of the device/file name]

grub>setup --stage2=/boot/grub/stage2 --force-lba (hd0,2),(hd0,6)
   Checking if "/boot/grub/stage1" exists ...  yes
   Checking if "/boot/grub/stage2" exists ...  yes
   Checking if "/boot/grub/e2fs_stage1_5" exists ...  yes
Running"embedded /boot/grub/e2fs_stage1_5 (hd0,2) failed. Not fatal
Running"embedded /boot/grub/e2fs_stage1_5 (hd0,6) failed. Not fatal

Running "install--force-lba--stage2=/boot/grub/stage2 /boot/grub/stage
(hd0,2) /boot/grub/stage2 p /boot/grub/menu.lst" ... Failed

Error  22 No such partition

Grub > quit


The partion setup was
hd01  Windows
hd02  Recover
hd03  Logical     (created by openSUSE 11.0 install)

hd05  swap        (created by openSUSE 11.0 install)
hd06  /           (created by openSUSE 11.0 install)
hd07  /home       (created by openSUSE 11.0 install)


Regards / Groeten,
                        Frans
Comment 1 Josef Reidinger 2009-01-05 08:05:25 UTC
Please attach yast logs(http://en.opensuse.org/Bugs/YaST) and also try look, how looks your device map (first must be disk not, usb stick) - it is under bootloader installation details.
Comment 2 Frans Leerink 2009-01-12 15:25:39 UTC
Created attachment 264554 [details]
Requested y2logs

In the comment Josef Reidinger also ask a question about the device map, but where do i find that on the harddisk?

Just some more information. Finally I managed to get it corrected, but do not ask how.

Regards,  Frans
Comment 3 Josef Reidinger 2009-01-12 15:30:09 UTC
device map you can find in yast2 bootloader -> bootloader installation details
or written result in /boot/grub/device.map.
Comment 4 Frans Leerink 2009-01-12 15:47:24 UTC
Hello Josef,

Currently it say:

Grub
Boot from Master Boot Record

The hard disk is currently the first device. I don't know how it was at the time of the problem.

Regards,   Frans
Comment 5 Josef Reidinger 2009-01-13 14:30:03 UTC
OK, I found interesting think from logs. It says that sda7 is '/' and sda6 is mounted as '/home'. That is different from what you wrote in first comment, can you say what is correct?
Comment 6 Frans Leerink 2009-01-13 18:15:16 UTC
Hello Josef,

If I look currently in Yast/System/Partitioner sda6 is indeed /home and sda7 is indeed /.

Looking back in my paper notes (saying 5 swap, 6 /home, 7 /) I most probally has reported it incorrectly.

Sorry

Regards,  Frans
Comment 7 Martin Konopka 2009-01-20 16:02:33 UTC
I also hit similar problem, installing final openSUSE 11.1 from DVD (plus AddOn media).
My machine: a notebook Fujitsu-Siemens AMILO Pro V3205  (a 32-bit PC)
My partitions:
/dev/sda1 - an NTFS partition with Windows XP
/dev/sda5 - formatted to be swap area
/dev/sda6 - formatted to be ext3 mounted on /
/dev/sda7 - formatted to be ext3 mounted on /home

After performing bulk of the installation, while doing grub setup, I got a message:
Error 22: No such partition.

It's pretty awkward situation for me since my machine would not boot now. Can anybody give me some advice? Thanks.

PS I changed severity of this bug to blocker because it really is. My machine is simply unusable now. With openSUSE 11.0 there was no such an issue.
Comment 8 Jiri Srain 2009-01-21 06:36:18 UTC
Martin, could you, please, attach your logs as well as created bootloader configuration files (/etc/grub.conf, /boot/grub/menu.lst, /boot/grub/device.map)? 

You can boot the installation DVD, switch to 2nd console (ctrl+alt+F2) and mount the system to grab the /var/log/YaST2 directory as well as the files I mentioned above.

Hopefully they help finding any lead to the root of this problem.
Comment 9 Martin Konopka 2009-01-22 20:00:03 UTC
Created attachment 267015 [details]
archive with files concerning  GRUB

Please find attached my files concerning grub. I must say that after the failure of grub installation I was trying to do something manually. I do not remember all details but the original files (e.g. menu.lst) were overwritten unfortunately due to my manual trials. But perhaps the original files (or files closer to them) are those with suffixes .old .

few remarks:
* The problem with grub first appeared for me in openSUSE 11.1 RC1. The older releases (11.1 Beta4,Beta3) as well as final 11.0 installed grub perfectly (and the partitioning was identical as I tried now).

* Perhaps the long name  /dev/disk/by-id/ata-FUJITSU_MHW2120BH_NZ2TT7329S80
causes problems. At least I read something like this after I reported this bug for RC1.

* NO directory will be created after uncompressing the attached grub_files.tar.bz2 archive. Just files.

In next attachment I will send archived /var/log/Yast2 directory.
Comment 10 Martin Konopka 2009-01-22 20:02:33 UTC
Created attachment 267017 [details]
archived /var/log/YaST2 directory

Please let me know if you need more files. In worst case I can repeat the unsuccessful installation.
Martin.
Comment 11 Jiri Srain 2009-01-26 11:33:59 UTC
Torsten, this looks like the bug with long names (Martin, thanks for the hint) which I hope has been already fixed. What do you think? Any other hint what can be the problem? I do not see anything else that could cause this error...
Comment 12 Forgotten User 43GIiIuyBL 2009-01-26 21:37:16 UTC
Hi all

i ran in the same problem. So i finish to install OpenSuSE 11.1 in my T61p.

Then i boot and run the setup again but select the rescue mode system.

I mount my root partition and found that the device.map had:
(hd0)   /dev/disk/by-id/ata-ST9160823AS_5NK0FW4J

i changed to 
(hd0)   /dev/sda

And run root and setup again and it works perfectly well.

I am not sure what is the error creating the device map, but it has something to do.
Comment 13 Vitaly Merenkov 2009-01-29 13:07:32 UTC
I have the same problem... I have ASUS X51L notebook, and if I do not changed where grub should be installed it trying to install not to a local drive in the boot sector but to removable disck (I have no it), so if I do not change this parameter my notebook dose not load after installation.
Comment 14 Forgotten User zSppWjup9E 2009-01-30 08:24:51 UTC
Hello,

I've had this problem three times:
-with the KDE live CD on the RC of 11.1, but it worked with DVD
-with the KDE Four live CD (with KDE 4.2)
-with the openSUSE 11.1 official DVD.

The problem occurs everytime when installing a second system (I've got always my stable system on sda1 and another root partition sda7 with a testing system).

When rebooting it says Error 22 or No system found, as described above. It doesn't find the new or the old GRUB.

I fixed it with the "Recover installed system" from the DVD. It reinstalls GRUB on the first system (sda1), I make a direct entry for the second system (sda7) and it works.

I'll send you my yast log if you wish to.
Comment 15 Torsten Duwe 2009-02-04 15:09:47 UTC
This (the original problem reported) is most likely yast calling parted.

This setup _is_ fragile. Use a primary partition, on the first disk if by any means possible.
Comment 16 Jiri Srain 2009-02-09 10:58:34 UTC
Does not sound to me like the known parted issue (parted wiping out the GRUB's stage1 code form the boot sector of extended partition). This bug is about GRUB failing to install at all, not about its (successful) installation being destroyed later. (the parted issue which I'm aware is that YaST calls parted, but not GRUB at all afterwares).

If you refer to different issue of parted, I think that this bug may become a duplicate. But I think it is more likely related to the problem with long names (see comment #12).

On the other hand, I agree with you that having dedicated primary partition for GRUB is much more than desirable.
Comment 17 Stephan Binner 2009-02-14 19:58:12 UTC
Please read http://en.opensuse.org/Bugs/Definitions
Comment 18 Frans Leerink 2009-02-25 00:39:00 UTC
Hello, I did a new install on my Netbook MEDION AKOYA-E1210/MD97160 in exactly the same way as in my original bug report. The same error occured and the system gave me also the opportunity to change in Yast the bootloader settings.

The only thing that I have changed is the root device in section management from an abbreviated textual device description to /dev/sda7 and than it installed grub correctly. The harddisk was the 1st device in bootloader installation details.

Regards, Frans
Comment 20 Torsten Duwe 2010-03-11 13:54:26 UTC
Problems with long device names should have been fixed a while ago.