|
Bugzilla – Full Text Bug Listing |
| Summary: | autoyast fails to create working grub boot config for md soft raid | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Boris Wesslowski <bw> |
| Component: | AutoYaST | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bw, ug |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
two xml parts (bootloader and partitioning) of autoyast control file
y2logs as requested autoyast control file used for the y2logs |
||
I added
<device_map_entry>
<firmware>hd1</firmware>
<linux>/dev/sdb</linux>
</device_map_entry>
to the device_map, now autoyast configures grub to boot from (hd0,7) which leads to "Error 22: no such partition".
BTW autoyast takes a remarkable amount of time for the "configuring bootloader" phase, but it is not evident from y2log what it is doing or why it chooses the wrong partition.
Several further attempts yield boot entries of the form (hd0,x) with x = random number (except the only working one up to now). Using the boot_mbr or boot_root options as suggested in #619837 does *not* help as workaround. Doesn't look like we can expect this to be fixed in openSUSE 11.3. Will this be fixed in 11.4? Please attach y2logs from installation so we can check what is wrong. http://en.opensuse.org/openSUSE:Bugreport_YaST (In reply to comment #2) > might be a duplicate of bug #629929 Uwe: you write this bug. Which one you mean as duplicate? Created attachment 392832 [details]
y2logs as requested
Attached y2logs as requested.
Logs are from a demo installation in VirtualBox.
To get a finished installation at all, grub was manually made to boot from partition 1, not from random partition 7632 as configured by autoyast.
Created attachment 392834 [details]
autoyast control file used for the y2logs
You should be able to reproduce the problem easily with the attached minimal control file, also used to produce the y2logs output.
(In reply to comment #7) > Created an attachment (id=392832) [details] > y2logs as requested > > Attached y2logs as requested. > > Logs are from a demo installation in VirtualBox. > > To get a finished installation at all, grub was manually made to boot from > partition 1, not from random partition 7632 as configured by autoyast. Thanks for logs. Now it is clear that it is not related to autoyast. It is general error when using 11.3, MD array and persistent device names. I already post update to update channel. So if you want to install with fix, you must enable update channel during installation and use the newest perl-Bootloader. *** This bug has been marked as a duplicate of bug 626132 *** Thanks for the fix. (Now I have to figure out how to get it into stage 1 of autoyast, I already have the updated perl-Bootloader in stage 2...) You might want to mark bug number 619837 as resolved too, since it seems to be a duplicate of this one. Yes, It looks same. To inject stage1 see dud argument - http://en.opensuse.org/SDB:Linuxrc#p_dud |
Created attachment 381923 [details] two xml parts (bootloader and partitioning) of autoyast control file User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 The relevant xml parts of the autoinstall control file (bootloader and partitioning) are attached. This works with previous openSUSE versions. Autoyast creates the partitions for the software raid and the md device correctly and is able to install, but when rebooting for second stage the kernel is not bootable because autoyast determined the wrong partition. The additionally installed custom kernel is configured as in the control file and is bootable (but not used for second stage). Editing the grub menu manually and booting leads to successful completion of the autoinstallation but the openSUSE and failsafe entries in grub.conf will still be wrong. The disk setup is: 2 swap partitions on sda1 and sdb1, md0 with raid1 on sda2 and sdb2. Result: Autoyast consistently configures grub to boot the default openSUSE kernel from (hd0,0) which leads grub to stop at "Error 17: Cannot mount selected partition" when looking for the kernel image. This bug may be related to #619837 Reproducible: Always Steps to Reproduce: 1. Use an autoyast control file with the attached xml parts included