https://bugzilla.novell.com/show_bug.cgi?id=388622 Summary: Partitions on RAID device cannot be formatted Product: openSUSE 11.0 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: adam.cetnerowski@intel.com QAContact: jsrain@novell.com Found By: --- Created an attachment (id=213845) --> (https://bugzilla.novell.com/attachment.cgi?id=213845) logs Description: Installation program on OpenSuse 11.0 beta2 recognizes RAID0 and RAID1 volumes created in OROM (displays a volume name, proper size etc.), creates based partitions, but installation stops after a few minutes with the following message: "Waiting for device /dev/mapper/isw_cjhhadifji_MYVOLUME_part2 to appear: ................. Could not find /dev/mapper/isw_cjhhadifji_MYVOLUME_part2. Want me to fall back to /dev/mapper/isw_cjhhadifji_MYVOLUME_part2? (Y/n). Waiting for device /dev/mapper/isw_cjhhadifji_MYVOLUME_part2 to appear: ................. not found - exiting to /bin/sh" The command "dmraid -s" displays correct volume parameters. The volume is active. If we try to display content of /dev/mapper directory, we can find the following partitions: /dev/mapper/isw_cjhhadifji_MYVOLUME-part1 /dev/mapper/isw_cjhhadifji_MYVOLUME-part2 /dev/mapper/isw_cjhhadifji_MYVOLUME-part3 So, it is not surprising why the installation program can't use the partition isw_cjhhadifji_MYVOLUME_part2, while the partition's name is isw_cjhhadifji_MYVOLUME-part2 ("-part2" doesn't equal "_part2"). Kind of error message depends on drives we choose to RAID volume. If we choose other disks than before from 6 disks available, error msg will be a little bit different, but the problem may be similar. Installation program creates partition isw_babefecgdc_MYVOLUMEp8, but it tries to use isw_babefecgdc_MYVOLUME_part8. Screen shots have been attached for this issue. "Error, Failure occurred during following action: Formatting raid partition /dev/mapper/isw_babefecgdc_MYVOLUME_part8 (443.6 GB) with ext3. System error code was: -3030." If we choose LVM partitions, the problem will occur again. After a few minutes, an error will be displayed: fsck 1.40.8 (13-Mar-2008) error on stat() /dev/mapper/isw_cjhhadifji_MYVOLUME_part1: No such file or directory error on stat() /dev/mapper/isw_cjhhadifji_MYVOLUME_part1: No such file or directory fsck.ext3: No such file or directory while trying to open /dev/mapper/isw_cjhhadifji_MYVOLUME_part1 Tested RAID types: RAID0 - volume visible, installation stops RAID1 - volume visible, installation stops RAID10 - volume not visible in installation program RAID5 - volume not visible in installation program Steps to reproduce: 1. Choose New Installation. 2. On Suggested Partitioning page use Partition Based (default). 3. Use default settings on all pages. 4. Error will appear in a few minutes. Environment Details: -OS: OpenSUSE 11.0 Beta2 i386 -Chipset: ICH9 -CRB: Intel DQ35JO dmraid version: 1.0.0.rc14 (2006.11.08) dmraid library version: 1.0.0.rc14 (2006.11.08) -- 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.