|
Bugzilla – Full Text Bug Listing |
| Summary: | Dual boot configuration with WINXP on a RAID1 fails | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Gerhard Mocker <gemocker> |
| Component: | YaST2 | Assignee: | Jozef Uhliarik <juhliarik> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | chrubis, duwe |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Yast2 log files with grub error 23 | ||
For the grub installation error please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks! CCing grub maintainer to help how to setup the chain loader. Created attachment 207622 [details] Yast2 log files with grub error 23 entries from 2008-04-12 show what happens when doing the following with SATA, RAID1 drives connected: YAST2, Boot : start from scratch, propose configuration, finish .. Resulting in grub Error 23 Please check the description in point 1.1 of the referenced document: http://en.opensuse.org/Bugs/YaST. It is not up to date. Manually and again after quite some trial and error, guessing, sorting out different information from different forums, we found, that grub can also boot Windows with the following configuration files contents (Grub was installed before with the SATA, RAID1 drives disconnected): device.map: (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb menu.lst: # Modified by YaST2. Last modification on Sun Apr 6 10:23:40 CEST 2008 default 1 timeout 12 gfxmenu (hd0,1)/boot/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd0,1) kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/scsi-SATA_ST320413A_5ED0576T-part2 resume=/dev/sda1 splash=silent showopts initrd /boot/initrd-2.6.22.17-0.1-default ###Don't change this comment - YaST2 identifier: Original name: windows### title WindowsXP Professional rootnoverify (hd1,0) makeactive chainloader (hd1)+1 map (hd0) (hd1) map (hd1) (hd0) boot ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,1) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 root (hd0,1) kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/scsi-SATA_ST320413A_5ED0576T-part2 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /boot/initrd-2.6.22.17-0.1-default ###Don't change this comment - YaST2 identifier: Original name: Kernel-2.6.22.17-0.1-default### title Kernel-2.6.22.17-0.1-default root (hd0,1) kernel /boot/vmlinuz-2.6.22.17-0.1-default root=/dev/disk/by-id/scsi-SATA_ST320413A_5ED0576T-part2 resume=/dev/sda1 splash=silent showopts initrd /boot/initrd-2.6.22.17-0.1-default .. I hope this helps Please do not mix different problems in one bugreport, it would be better to open new one for outdated wiki. Sending this report to yast2-bootloader maintainer. GRUB Error 23 means that GRUB does't found partion for any boot section. In this case: grub> setup --stage2=/boot/grub/stage2 (hd0) (/dev/sdc2,1) Error 23: Error while parsing number The problem is that your device.map doesn't include info about /dev/sdc original device.map included just info about DM-RAID and floppy. Device /dev/sdc was not added. It will be fixed in 11.0 yast2-storage and hwinfo support "bios_id" for DM-RAID now. (openSUSE 11.0) bios_id is number indicated ordering of disks by BIOS. openSUSE 10.3 doesn't support bios_id in DM-RAID. It was added by heuristic in yast2-storage. The heuristic works wrong if there was any disk out of DM-RAID and with bios_id same than yast2-bootloader added to DM-RAID by heuristic. :( I am sorry but it should work OK in openSUSE 11.0. |
Main Hardware Configuration: Mainboard Type ASROCK 4Core1600P35-WiFi+ Processor: Intel Pentium Dual Core Hardisk: 2 SATA Harddisk, Seagate, configured as RAID1 using onboard chipset 1 IDE Harddisk, Seagate CD-ROM: SATA Drive The first plan was to install Windows XP Prof and SuseLinux10.3 in different partions opf the RAID1 system. Fortunately this was dropped early as considered to be too critical. This would have to be verified still whether it can be made operational, as it would be the preferred solution. Then first only WINXP Prof was installed on the RAID1 system. The installation worked smoothly. After this the IDE Harddisk was added and configured as boot harddisk in BIOS, and the installation of openSUSE 10.3 was started on this additional harddisk, after configuring a Swap partion, a root partition (EXT3), a home partition (EXT3) and another FAT32 partition. The installation worked so far smoothly until the GRUB installation terminated with Error 23. It was only possible to access Linux again using the installation CD, selecting: installation, .. , boot of installed systems. We spent quite some time trying different ways of bootmanager configuration: To use the windows bootmanager following a procedure described by Suselinux failed, having YAST propose a new configuration for GRUB, guessing manually the correct parameters for the GRUP configuration files through YAST2 or by terminal failed, starting GRUB through YAST or by terminal, altogether using the GRUB boot manager for Linux and Windows failed. Finally we disconnected the SATA drives temporarily, had to boot gain through the installation CD, had YAST2 propose a configuration and did run GRUB again and succceded at least to achieve a boot configuration for Linux only. After reconnecting the SATA drives booting to LINUX fortunately also still did work. The attempt to guess the correct configuation for the GRUB menu file in order to add a chainload to the windows MBR on the RAID1 system did fail, also after a lot of reading. The workaround for now is to change the Boot Disk in BIOS to be either the IDE harddisk or the RAID system in order to either boot LINUX or WindowsXP. As newcomer on Linux I consider such problems as really critical to be fixed, as installing systems in this way is not all productive. Maybe somebody can inform me, if a solid solution for YAST and GRUB is available. Also after an update of SuseLinux through internet the problem with YAST and GRUP with SATA harddisks as RAID1 connected was rechecked and had not improved. I am also missing clear, reliable procedure descriptions in a lot of respects on LINUX issues.