[Bug 213594] New: YaST installation detects an incorrect RAID partitions and corrupts partition table
https://bugzilla.novell.com/show_bug.cgi?id=213594 Summary: YaST installation detects an incorrect RAID partitions and corrupts partition table Product: openSUSE 10.2 Version: Alpha 5 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: belphegor@belbel.or.jp QAContact: jsrain@novell.com On the YaST new installation, "Partitioning" subsection shows an unexpected software RAID array (suggestion) as follows; * Create extended raid partition pdc_cgbejije_part4 (24.7GB) * Create raid partition pdc_cgbejije_part5 (70.5MB) for /boot with ext2 * Create swap raid partition pdc_cgbejije_part6 (1.6GB) * Create raid partition pdc_cgbejije_part7 (9.3GB) for / with reiserfs * Create raid partition pdc_cgbejije_part8 (13.8GB) for /home with reiserfs * /dev/hda1 mounts to /windows/C * /dev/hda3 mounts to /windows/D * /dev/mapper/pdc_cgbejije_part1 mounts to /windows/E * /dev/mapper/pdc_cgbejije_part3 mounts to /windows/F Since I want to correct them, follow the "Partitioning" link and "Custom partitioning (for expert)". But YaST shows as follows; (Expert Partitioner) * /dev/mapper/pdc_cgbejije 74.5GB * /dev/mapper/pdc_cgbejije_part1 24.4GB DM Raid * /dev/mapper/pdc_cgbejije_part2 15.6GB DM Raid * /dev/mapper/pdc_cgbejije_part3 9.7GB DM Raid * /dev/hda 74.5GB ST380021A RAID pdc_cgbejije When I try to delete /dev/mapper/pdc_cgbejije and continue to install against YaST's will, all of partitions are disappered. (Requires partition salvaging utility to recover). It should be (and SUSE 10.0/10.1 and "fdisk -l" shows); * /dev/hda 74.5GB ST380021A * /dev/hda1 24.4GB NTFS * /dev/hda2 15.6GB ext3 * /dev/hda3 9.7GB NTFS I've not ever defined any software/hardware RAID arrays, and none of RAID card exists in it. How do I correct? -- 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=213594 ------- Comment #1 from belphegor@belbel.or.jp 2006-10-19 05:56 MST ------- Created an attachment (id=102026) --> (https://bugzilla.novell.com/attachment.cgi?id=102026&action=view) This is /var/log/y2log during YaST installation -- 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=213594 martin.lasarsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |fehr@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=213594 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |belphegor@belbel.or.jp ------- Comment #2 from fehr@novell.com 2006-10-19 10:41 MST ------- The logs shows that dmraid tells that you have a raid setup on your disk. Maybe the disk was part of a raid set in another machine and the raid signature still resides at the end of the disk. The raid signature can be removed with the command dmraid --erase_metadata /dev/hda To check if raid sets are detected you can execute dmraid -r -c -c (this command is used by YaST2 to detect dmraid). What exactly did you that caused the partitions from /dev/hda to become removed? This seems to be the most serious problem that happened. -- 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=213594 belphegor@belbel.or.jp changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|belphegor@belbel.or.jp | ------- Comment #3 from belphegor@belbel.or.jp 2006-10-20 08:42 MST ------- Thank you for detailed exposition. Surely "dmraid -r -c -c" shows "/dev/hda:pdc:pdc_cgbejije:stripe:ok:1563014125:0" on this machine. ("No Software RAID disks" on another machine)
What exactly did you that caused the partitions from /dev/hda to become removed? This seems to be the most serious problem that happened.
Ok, this is a detailed procedure what I did. (1) Boot SUSE-10.1Alpha5 DVD and select "new installation". (2) YaST scans and detects devices, set clocks etc. (3) YaST suggests as described previously ("Create extended raid partition..") in "Installation settings". (4) Follow "partitioning" link and select "Create custom partition setup" -> "custom partitioning (for experts)". (5) YaST (Expert Partitioner) shows RAID partitions as I described. (6) Select "/dev/mapper/pdc_cgbejije" and push "delete" (with confirm). (7) Then YaST (Expert Partitioner) shows proper partitions as I think; "/dev/hda1, /dev/hda2, /dev/hda3". (8) Select "/dev/hda2" and push "edit". (9) Select to format with ext3 and set the mount point to "/". (10) Push "Accept" to finish partitioning (YaST warns that there is no swap, push "no".). (11) Return to "Installation settings". "partitioning" section shows "Remove raid pdc_cgbejije", "Format /dev/hda2 (15.6GB) for / with ext3". (12) Push "accept" to start installation. Some of confirmation appears. (13) YaST shows a message "Deleting device mapper /dev/mapper/pdc_cgbejije" with progress bar (0%). (14) Device mapper deletion does not proceed anymore. Push CTRL+ALT+DEL to reset. (15) After reboot, all of partitions are disappered. No partition can show on SUSE 10.1/10.2-alpha5 rescue system, other partitioning tools (just like PartitionMagic). For recovering, use a partition salvaging utility or edit partition table manually. None of data seems to be destroyed. -- 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=213594 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Fixed in Milestone|--- |Beta 1 ------- Comment #4 from fehr@novell.com 2006-10-23 08:12 MST ------- Thanks for detailed description. With this I was able to reproduce the problem here. Of course deleting the partitions of the disk the BIOS raid was mapped to was a bug in YaST2. This bug will be fixed in beta#1. An additional bug caused the hang you observed. In beta#1 the behaviour will be as expected: The BIOS RAID gets removed and the partitions of the underlying disk become usable and might be used for installation. BTW: my above comment above removal of raid signature from disk is wrong. Correct is: The raid signature can be removed with the command dmraid --raid-devices --erase_metadata /dev/hda -- 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=213594 ------- Comment #5 from belphegor@belbel.or.jp 2006-10-28 04:45 MST ------- Thanks. I've tested 10.2-beta1 and verified that this problem was fixed. But one minor problem still exist. An error message as follows was shown while deleting software RAID array /dev/mapper/pdc_cgbejije. "Fatal error occured during executing the following action. Formatting the partition /dev/hda2 (15.6GB) as xfs System error code was: -3008 /sbin/mkfs.xfs -q -f /dev/hda2 mkfs.xfs: cannot open /dev/hda2: Device or resource busy." YaST installer aborted after this message. However the deletion of RAID signature was already completed, YaST installer can go on after reboot. I think that the YaST installer does not re-scan devices after RAID deletion, so that this problem can occur. -- 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=213594 ------- Comment #6 from fehr@novell.com 2006-10-30 03:14 MST ------- The problem you are obeserving now could be a duplicate of 214682 since it made it impossible to remove DM devices. To be erally sure I would need the logs of the failing installation. If these are not available you could retrry with beta#2 where 214682 should be fixed. -- 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=213594 belphegor@belbel.or.jp changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED ------- Comment #7 from belphegor@belbel.or.jp 2006-11-01 04:34 MST ------- Thanks. This minor bug (comment #5) is surely equivalent to bug#214682 since the proposed patch for this bug works 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com