Bug 680404 - Installation not possible on a Intel Matrix Storage System (Raid1)
Summary: Installation not possible on a Intel Matrix Storage System (Raid1)
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: Installation (show other bugs)
Version: Final
Hardware: x86-64 Other
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: Neil Brown
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-17 08:48 UTC by Forgotten User QtBI7gWTIh
Modified: 2011-06-28 02:50 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
The YaST2 Logs (742.89 KB, application/x-bzip)
2011-03-17 08:48 UTC, Forgotten User QtBI7gWTIh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User QtBI7gWTIh 2011-03-17 08:48:45 UTC
Created attachment 419887 [details]
The YaST2 Logs

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.15) Gecko/20110303 SUSE/3.6.15-1.1 Firefox/3.6.15

Hello,

it is not possible to install 11.4 on a System with Intel Matrix Storage enabled (Full Disk Raid.

The first Problem I can't create Partitions In a 11.1 to 11.3 System the Problem to create Partitions become ever worse?

With 11.4 the old Trick to create the Partition before installing openSUSE is never more possible?

After first reboot the fstab (mdadm) don't find the Partitions?

When I change the fstab delete the UUID Entry und wrote /dev/md126p"X" in the fstab the system coming up ? 

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Forgotten User QtBI7gWTIh 2011-04-22 09:26:18 UTC
this is a not working fstab created by YaST2-Installer?

//
/dev/disk/by-id/ata-ST3320613AS_9SZ438BR-part1 swap                 swap       defaults              0 0
/dev/disk/by-id/md-uuid-55247ef6:e0e17b36:6d30e0c5:d8102a27-part8 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-ST3320613AS_9SZ4X64K-part1 /data                ext4       defaults              1 2
/dev/disk/by-id/ata-ST3320613AS_9SZ438BR-part2 /data1               ext4       defaults              1 2
/dev/disk/by-id/md-uuid-55247ef6:e0e17b36:6d30e0c5:d8102a27-part9 /home                ext4       acl,user_xattr        1 2
/dev/disk/by-id/md-uuid-55247ef6:e0e17b36:6d30e0c5:d8102a27-part5 /root_11.3           ext4       defaults              1 2
/dev/disk/by-id/md-uuid-55247ef6:e0e17b36:6d30e0c5:d8102a27-part2 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/md-uuid-55247ef6:e0e17b36:6d30e0c5:d8102a27-part3 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/md-uuid-55247ef6:e0e17b36:6d30e0c5:d8102a27-part10 /windows/Innomed     ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/md-uuid-55247ef6:e0e17b36:6d30e0c5:d8102a27-part1 /windows/System      ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
//


This is a "bad working" fstab after the my changes?

//
/dev/disk/by-id/ata-ST3320613AS_9SZ438BR-part1	swap	swap	defaults 0 0 
/dev/md126p8	/	ext4	acl,user_xattr 1 1 
/dev/disk/by-id/ata-ST3320613AS_9SZ4X64K-part1	/data	ext4	acl,user_xattr 1 2 
/dev/disk/by-id/ata-ST3320613AS_9SZ438BR-part2	/data1	ext4	acl,user_xattr 1 2 
/dev/md126p9	/home	ext4	acl,user_xattr 1 2 
/dev/md126p5	/root_11.3	ext4	acl,user_xattr 1 2 
/dev/md126p6	/home_11.3	xfs	defaults 1 2 
/dev/md126p2	/windows/C	ntfs-3g	users,gid=users,fmask=133,dmask=022,locale=de_AT.UTF-8 0 0 
/dev/md126p3	/windows/D	ntfs-3g	users,gid=users,fmask=133,dmask=022,locale=de_AT.UTF-8 0 0 
/dev/md126p10	/windows/Innomed	ntfs-3g	users,gid=users,fmask=133,dmask=022,locale=de_AT.UTF-8 0 0 
/dev/md126p1	/windows/System	ntfs-3g	users,gid=users,fmask=133,dmask=022,locale=de_AT.UTF-8 0 0 
proc	/proc	proc	defaults 0 0 
//
Comment 2 Neil Brown 2011-06-15 01:24:54 UTC
Hi,
 sorry for the long delay in responding to this.

I think I know what the problem is.  A recent change to
  /lib/udev/rules.d/64-md-raid.rules
broke the creation of device files for partitions.

The line 

TEST!="md/array_state", GOTO="md_end"


causes the problem.  Either removing it or changing it to

ENV{DEVTYPE}=="disk", TEST!="md/array_state", GOTO="md_end"

will fix it.  However I don't know how you could make that change
during installation.

Do I correctly deduce from you comment that you managed to get it working, but you had to make significant changes to /etc/fstab?

If you could you try making the change to 64-md-raid.rules and see if it still
works after reverting the changes to fstab??

An updated 'mdadm' package has been submitted to 'openSUSE:Factory' with this
bug fixed, and an update for 11.4 may be issued in due course.

Thanks for the report.
Comment 3 Neil Brown 2011-06-28 02:50:05 UTC
As mentioned is previous comment, I believe this is now fixed, and so am closing the bug accordingly.