[Bug 230779] New: RAID detected but switched off in the BIOS
https://bugzilla.novell.com/show_bug.cgi?id=230779 Summary: RAID detected but switched off in the BIOS Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: neil@thump.org QAContact: jsrain@novell.com MSI K8 Neo4 with on board Sil 3114 RAID. 3x SATA drives. On installation SuSE loads the sil raid drivers, wrongly detecting RAID (not) enabled in the BIOS, and lists a non-existent RAID partition on over the 1st two SATA drives. There seems to be no way to pass kernel paramters at boot time to disable RAID completely (i.e 'linux nodmraid' that works in Redhat FC6 for example). Install fails at installation of boot manager with Error 23. I presume Grub is seeing a non-existent RAID partition ? I'll log a more detailed report shortly. The 'nodmraid' parameter seems to allow the partioner to see individual sata drives. There have been a few similar reports of this problem in the SuSE forums: http://www.suseforums.net/lofiversion/index.php/t28133.html And: http://www.suseforums.net/index.php?showtopic=28373 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical Status|NEW |NEEDINFO Info Provider| |neil@thump.org ------- Comment #1 from lmb@novell.com 2007-01-02 04:30 MST ------- Please attach installer and boot log messages. Downgrading to critical: We have already shipped 10.2, so we can hardly block it any longer. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 ------- Comment #2 from lmb@novell.com 2007-01-09 10:35 MST ------- Ping? Please provide the requested information, else we cannot help you. Also, does acpi=off, maxcpus=0 do anything for you? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 ------- Comment #3 from kay1234@gmx.de 2007-01-12 12:48 MST ------- Very similar issue here with a K9 Neo-F, nVidia nForce 550 chipset. I haven't tried to install yet since the partitioning tool displays raid partitions (like /dev/mapper/pdc_SOMETHING) instead of the correct device names (/dev/sdb2 in my case). If I continue with installing on that /dev/mapper partition I will always have to use that cryptic device names to mount my partitions. With Fedora Core you could use the nodmraid kernel option at boot time of the installation system and it won't detect those stupid /dev/mapper partitions and use /dev/sdxy instead. Will try to install on the /dev/mapper/pdc_... partition now and post the result here. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 kay1234@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kay1234@gmx.de ------- Comment #4 from kay1234@gmx.de 2007-01-12 14:10 MST ------- OK, here we go. Bootloader installation fails, too. Here is the error message: GNU Grub version 0.97 [...] setup --stage2=/boot/grub/stage2 (hd1,1) (hd1,1) checking if "/boot/grub/stage1" exists... yes checking if "/boot/grub/stage2" exists... yes Running "embed /boot/grub/e2fs-stage1-5 (hd1,1)"... failed (this is not fatal) Running "embed /boot/grub/e2fs-stage1-5 (hd1,1)"... failed (this is not fatal) Running "install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd1,1)/boot/grub/stage2 p /boot/grub/menu.lst... failed Error 22: no such partition Where do I find installer and boot log messages in order to attach them here? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 kay1234@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|neil@thump.org | ------- Comment #5 from kay1234@gmx.de 2007-01-21 10:22 MST ------- Workaround: Boot Resuce System, mount SUSE installation partition to /boot, copy /boot/boot/grub/* to /boot/grub/, do a grub-install --recheck /dev/sdb (change the device accordingly), copy /boot/grub/device.map to /boot/boot/grub/ restart Grub should install correctly with this procedure. However the original problem remains - how to disable dmraid at installation time to have SUSE install to /dev/sdb instead of /dev/mapper/pdc_something. And how to prevent the installed kernel from using dmraid, too, in order to boot the system with /dev/sdbx as / instead of /dev/mapper/pdc_something_partx. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 mkoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |kay1234@gmx.de ------- Comment #7 from mkoenig@novell.com 2007-01-23 03:55 MST ------- dmraid is a user space tool, it does not care about kernel configuration. The problem is that the only information dmraid has about potential RAIDs is the metaformat data on the disk. If there is metadata on disk dmraid tries to assemble a device mapper device even if it is disabled in the BIOS, this is a known issue. The only way to prevent dmraid detecting RAIDs is to delete the ondisk metadata. If you are sure you have no RAID configured and want to get rid of the metadata this can be done with dmraid -rE (it also dumps the metadata to files for backup). Please check if the dmraid partitions still appear after this step. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230779 kay1234@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|kay1234@gmx.de | Resolution| |FIXED ------- Comment #8 from kay1234@gmx.de 2007-01-23 15:41 MST ------- That did the trick, I have absolutely no idea why there were still RAID metaformat data on the disks - I wiped them completely with the manufacturer tool before installation. I never expected the disk itself to be the problem. Anyway, /dev/mapper/pdc_xxx is gone, I had to adjust /etc/fstab (of course) and /boot/grub/menu.lst and reinstall grub. I used the same method as described in comment 6 for that. Thanks a lot! -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com