https://bugzilla.novell.com/show_bug.cgi?id=328388#c1 --- Comment #1 from Tiago Freitas 2007-09-25 17:53:03 MST --- https://www.redhat.com/archives/ataraid-list/2007-September/msg00019.html I'm trying to contact the dmraid author in the ataraid-list to help me fix the raid volumes, but I don't have much hope... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c3 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cthiel@novell.com |hare@novell.com Priority|P0 - Crit Sit |P3 - Medium --- Comment #3 from Stephan Kulow 2007-09-26 00:19:25 MST --- what means "entered the live installer"? You only looked it at, right? You didn't reformat all your hard drive? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c5 --- Comment #5 from Thomas Fehr 2007-09-26 02:22:26 MST --- I just got a report about 10.3 RC1 not supporting Intel ICH9 any more (#290918) while alpha5 did supported it. I just tried 10.3 RC2 on my Promise MBFastTrak133 Lite (PDC20276) and this still worked fine so it seems to be either something special with ICH9 support. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c7 --- Comment #7 from Thomas Fehr 2007-09-26 04:53:15 MST --- But this behavior is consistent with bug report #290918 where lacking dmraid support for ICH9 in RC1 is reported and where the live installer is not involved at all. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c10 --- Comment #10 from Tiago Freitas 2007-09-26 07:41:02 MST --- Stephan Kulow: "And then you overwrote your meta data." I did not give any instructions to alter anything on my system. I simply launched the live installer and chose "custom partitioning". I saw immediately that it did not activate the raid volumes (two separated disks), so I aborted the install without touching anything. I then simply did "dmraid -ay" and saw they were broken. I didn't even try to mount them. I thing something is very wrong with your device-mapper because the version is "unknown". You use the same dmraid version as mandriva, but probably altered the device-mapper. If that's true I don't think that's a good thing to do in a RC. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c13 --- Comment #13 from Stephan Kulow 2007-09-26 08:51:41 MST --- the bug is that boot.device-mapper and boot.dmraid isn't started. So it's natural that you don't see them or see "unknown". But that isn't destroying your tables -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c15 --- Comment #15 from Tiago Freitas 2007-09-26 11:39:51 MST --- I say it once more, I DID NOT do any partitioning whatsoever. It destroyed the metadata by itself (maybe the live installer modifies the partition tables when it's supposedly only reading them). Hannes: I had a matrix raid, do you have one? To reproduce it, make one raid0 and one raid1 volumes on two disks. Boot the livecd, enter install, go to custom partitioning and abort. Then do "dmraid -ay". I don't think the problem is in dmraid, because "dmraid -ay" only activates the arrays and gives the information to device-mapper I think. Also, mandriva 2008 has the same dmraid version and works. It might be related to this bug report: https://bugs.launchpad.net/ubuntu/+bug/141435 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c19 --- Comment #19 from Stephan Kulow 2007-10-08 10:03:33 MST --- there is no final livecd. If you have a problem with 10.3 final and dmraid, please report it differently from here. The live CD is not supporting dmraid and we'll add an error there. The sata CD-Rom problem is known and is a different bug -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c22 Radoslav Rangelov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |creator@dir.bg --- Comment #22 from Radoslav Rangelov 2007-10-09 04:57:02 MST --- Hi! I have 2 computers. The first has Asus P5K Deluxe mainboard and the second has Gigabyte P35-DQ6. The both of mainboards have ICH9R RAID controller. The final version of OpenSuSE 10.3 works only on my Asus P5K Deluxe system. The SuSE breaks my RAID0 configuration on Gigabyte P35-DQ6. It makes my RAID controller to not work till full shutdown (power off). Just reboot doesn’t work (The boot BIOS screen shows that my RAID0 is broken). The OpenSuSE 10.3 beta3 works fine on both of my mainboards. I think that some SuSE changes in kernel patches are responsible for issue. The final SuSE works fine with old patched kernel from beta3. All newer patched kernels don’t work. On the other hand all vanilla kernels (including the newest) work fine. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c28 Tiago Freitas changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|cthiel@novell.com | --- Comment #28 from Tiago Freitas 2007-10-09 08:37:59 MST --- Radoslav thank's so much for finding this. I think it's better that you or me open a new bug report for this to be fixed. Are you using the ICH9R in the asus? It can have two raid controllers. To fix the broken raid, first disconnect one of the disks. Power on and it will still say one of the disks is offline. Then power off and connect it again, it will recognize it and work again. Raid0 will be ok and raid1 will be degraded, you can fix it in the intel manager in windows. You will not lose your data. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c31 --- Comment #31 from Radoslav Rangelov 2007-10-10 03:18:15 MST --- (In reply to comment #28 from Tiago Freitas)

Radoslav thank's so much for finding this. I think it's better that you or me open a new bug report for this to be fixed. Are you using the ICH9R in the asus? It can have two raid controllers. To fix the broken raid, first disconnect one of the disks. Power on and it will still say one of the disks is offline. Then power off and connect it again, it will recognize it and work again. Raid0 will be ok and raid1 will be degraded, you can fix it in the intel manager in windows. You will not lose your data.

Yes I am sure that I use the Intel Matrix Storage controller. I have RAID0 configuration on both of my computers. To fix the raid configuration after trying to install OpenSuSE 10.3, I don't need to disconnect any devices. It needs only the computer to be switched off completely (with power off), not just restarted. I made workaround for the issue just changing "static int ata_ignore_hpa = 1" to "static int ata_ignore_hpa = 0" in linux-source/drivers/ata/libata-core.c file. It works. I found this in another forum: https://bugs.launchpad.net/ubuntu/+bug/141435 I found another bug but it is in YaST probably. If the raid configuration name has space sign in the name, the installer of SuSE can't see the raid partitions. It's detects only the raid devices but not the partitions on them. I had to create my RAID0 configuration again (without spaces in the name) to install successfully. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c33 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #33 from Jiri Srain 2007-10-10 05:47:18 MST --- I've just submitted version, which checks for presence of unsupported DMRAID and in such case issues a warning about possible data loss. Fixing the driver is different issue not related to the live installer. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c35 Tiago Freitas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiago.frt@gmail.com URL|https://www.redhat.com/archives/ataraid- | |list/2007-September/msg00019.html | Status|RESOLVED |REOPENED Component|Installation |Kernel Resolution|FIXED | Summary|Intel ICH9R raid controller not supported on |Intel ICH9R raid controller not supported on |10.3RC2, all dmraid arrays broken after (LiveCD)|10.3 since beta3, all dmraid arrays broken after |boot |boot (libata problem) Version|RC 2 |Final --- Comment #35 from Tiago Freitas 2007-10-10 07:06:47 MST --- Any kernel with "static int ata_ignore_hpa = 1" in linux-source/drivers/ata/libata-core.c will fail because it alters hard drive native sector size (see https://bugs.launchpad.net/ubuntu/+bug/141435 ). Until 10.3 beta3 it worked. Debian changed the kernel in 2.6.22-11.33. In the changelog of Debian's kernel 2.6.22-11.33: linux-source-2.6.22 (2.6.22-11.33) ; urgency=low [Ben Collins] * libata: Default to hpa being overridden You have made the same and it probably affects other sata controllers too. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c37 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |tiago.frt@gmail.com --- Comment #37 from Jeff Mahoney 2007-10-15 12:10:32 MST --- Ugh. Another HPA (Host Protected Area) problem. This fix was introduced because other users were running into problems with their disks. Suddenly the disk ended up being smaller than originally reported, and they were seeing problems as well. We've found that as a general solution, ignoring the HPA has worked. It seems as though this is a special case. Does booting with libata.ignore_hpa=0 work 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388#c39 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|tiago.frt@gmail.com | --- Comment #39 from Stephan Kulow 2007-11-22 23:53:55 MST --- info is kind of provided -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388 User tiago.frt@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=328388#c41 Tiago Freitas changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|creator@dir.bg | --- Comment #41 from Tiago Freitas 2007-12-15 11:34:08 MST --- Kernel command line: BOOT_IMAGE=linux initrd=initrd,10240768.spl ramdisk_size=512000 splash=silent vga=0x317 libata.ignore_hpa=0 Unknown boot option `libata.ignore_hpa=0': ignoring That's why it didn't work...more here: http://www.spinics.net/lists/fedora-devel/msg57564.html I tried it with the latest live dvd and the first 10.3 installer. Linux linux 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC i686 i686 i386 GNU/Linux Any alternate fix? Can I make a new installer with the modified kernel? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=328388#c43 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |teheo@novell.com --- Comment #43 from Jeff Mahoney 2008-01-11 11:01:42 MST --- Tejun, this is HPA related. I'm not sure why changing the source would fix it but passing the module parameter wouldn't. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=328388 User tiago.frt@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=328388#c45 Tiago Freitas changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Kernel OS/Version|openSUSE 10.3 |openSUSE 11.0 Product|openSUSE 10.3 |openSUSE 11.0 Target Milestone|Final |openSUSE 11.1 --- Comment #45 from Tiago Freitas 2008-09-15 04:07:42 MDT --- It still happens in 11.0. linux:/home/linux # dmesg | grep libata Command line: BOOT_IMAGE=linux initrd=initrd,10240768.spl ramdisk_size=512000 ramdisk_blocksize=4096 splash=silent vga=0x317 libata.ignore_hpa=0 Kernel command line: BOOT_IMAGE=linux initrd=initrd,10240768.spl ramdisk_size=512000 ramdisk_blocksize=4096 splash=silent vga=0x317 libata.ignore_hpa=0 Unknown boot option `libata.ignore_hpa=0': ignoring libata version 3.00 loaded. linux:/home/linux # dmraid -ay ERROR: isw: unsupported map state 0x3 on /dev/sda for RAID0:1 ERROR: adding /dev/sda to RAID set "isw_chgffgbhfa" ERROR: removing RAID set "isw_chgffgbhfa" No RAID sets The boot option should not be ignored... -- 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.