https://bugzilla.novell.com/show_bug.cgi?id=377529 Summary: Dual boot configuration with WINXP on a RAID1 fails Product: openSUSE 10.3 Version: Final Platform: i386 OS/Version: openSUSE 10.3 Status: NEW Severity: Blocker Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: gemocker@aol.com QAContact: jsrain@novell.com Found By: Customer 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.