[Bug 895542] New: Partitions on Intel RAID (ICH10) not considered by YaST
https://bugzilla.novell.com/show_bug.cgi?id=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c0 Summary: Partitions on Intel RAID (ICH10) not considered by YaST Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers@suse.de ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=605387) --> (http://bugzilla.novell.com/attachment.cgi?id=605387) YaST log directory as tar archive (bzip-compressed) User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 When trying to install openSUSE 13.1 on a system with an Intel RAID1 (ICH10), the existing partitions are ignored by YaST, so that the proposal overwrites existing partitions (like Windows). If you are not careful, you'll loose your data when installing! Reproducible: Always Steps to Reproduce: 1. Start to install openSUSE 13.1 on a system using Intel RAID (ICH10) Actual Results: Existing partitions are detected by the kernel, but are ignored by YaST Expected Results: Existing partitions should be displayed in YaST In openSUSE 12.3 YaST displays the partitions of the RAID and suggests to add new partitions, keeping existing partitions. -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c1 --- Comment #1 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2014-09-08 11:43:37 CEST --- Created an attachment (id=605388) --> (http://bugzilla.novell.com/attachment.cgi?id=605388) YaST logs from an openSUSE 12.3 (same hardware as for openSUSE 13.1) -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com AssignedTo|yast2-maintainers@suse.de |aschnell@suse.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.
https://bugzilla.novell.com/show_bug.cgi?id=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c2 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Ulrich.Windl@rz.uni-regensb | |urg.de AssignedTo|aschnell@suse.com |puzel@suse.com --- Comment #2 from Arvin Schnell <aschnell@suse.com> 2014-09-08 10:29:32 UTC --- The partition table on the RAID seems broken. Parted reports: parted -s '/dev/md126' unit cyl print Error: Can't have overlapping partitions. Partition Table: unknown The kernel detects some partitions (/proc/partitions): 9 126 976748544 md126 259 0 1 md126p1 259 1 104864287 md126p2 259 2 524273211 md126p5 259 3 52436128 md126p6 Maybe the start/size values from /sys/block/md126/md126p*/* can help to understand the reason. Please provide those values. -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c3 --- Comment #3 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2014-09-08 13:16:02 CEST --- (On comment #2) Unfortunately I restored a backup with a different layout to the RAID after that. If the layout were actually invalid before that, I wonder why openSUSE 12.3 had no problems with it. I also don't know whether it is important to know that the two 1TB disks have 4kB physical sectors, but 512 bytes logical sectors. I can try openSUSE 13.1 again with the new layout in the evening. The layouts were created with WinPE 3 (32bit) using Acronis True Image Home Premium 2014's Universal Restore. I guess that the program doesn't create invalid partition layouts. -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c4 --- Comment #4 from Petr Uzel <puzel@suse.com> 2014-09-09 16:54:23 UTC --- (In reply to comment #3)
(On comment #2) Unfortunately I restored a backup with a different layout to the RAID after that. If the layout were actually invalid before that, I wonder why openSUSE 12.3 had no problems with it.
Good question, but I do not have an answer (not even a theory) yet.
I also don't know whether it is important to know that the two 1TB disks have 4kB physical sectors, but 512 bytes logical sectors. I can try openSUSE 13.1 again with the new layout in the evening.
That would be really helpful.
The layouts were created with WinPE 3 (32bit) using Acronis True Image Home Premium 2014's Universal Restore. I guess that the program doesn't create invalid partition layouts.
If you manage to recreate the faulty layout, I'd be interested in 1) cat /proc/partitions 2) fdisk -l -u=sectors /dev/md126 (and the same for RAID components) 3) parted -s /dev/md126 unit s print 4) strace -o /tmp/strace.out -s 512 parted -s /dev/md126 unit s print && cat /tmp/strace.out 5) dd if=/dev/md126 of=md126.mbr bs=512 count=1 That should shed some light on this. Thanks in advance. -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c5 --- Comment #5 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2014-09-10 08:16:53 CEST --- I have an update: With the new layout, openSUSE 13.2 suggested to add new partitions, keeping the existing ones. However I did not do an installation, because I had to create some other partitions first. Nevertheless this means the bug (if it occurs) is serious, but probably it's less likely to occur (than I assumed initially). Also IF Yast refuses an existing partition layout, that shouldn't be done silently, but should pop up an appropriate warning (big red alert box) saying that existing partitions will be destroyed. Finnally I'm somewhat surprised that YaST logs don't include enough information to see what was really wrong with the partitions. -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c6 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Ulrich.Windl@rz.uni-regensb | |urg.de | --- Comment #6 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2014-09-11 08:22:03 CEST --- I have bad news: My first impression seems to be the right one. As it seems YaST uses parted, and parted is crap (sorry for the word): --parted output-- Error: Can't have overlapping partitions. Model: Linux Software RAID Array (md) Disk /dev/md126: 121599cyl Sector size (logical/physical): 512B/4096B BIOS cylinder,head,sector geometry: 121599,255,63. Each cylinder is 8225kB. Partition Table: unknown Error: Can't have overlapping partitions. Model: Linux Software RAID Array (md) Disk /dev/md126: 1953497088s Sector size (logical/physical): 512B/4096B Partition Table: unknown --fdisk output-- Disk /dev/md126: 1000.2 GB, 1000190509056 bytes, 1953497088 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: dos Disk identifier: 0x00275bd7 Device Boot Start End Blocks Id System /dev/md126p1 * 2048 201345023 100671488 7 HPFS/NTFS/exFAT /dev/md126p2 201345024 620775423 209715200 7 HPFS/NTFS/exFAT /dev/md126p3 620775424 1953497087 666360832 f W95 Ext'd (LBA) /dev/md126p4 1669355520 1879085055 104864768 7 HPFS/NTFS/exFAT /dev/md126p5 620777472 1249923071 314572800 7 HPFS/NTFS/exFAT /dev/md126p6 1249925120 1669355519 209715200 6 FAT16 /dev/md126p7 1879087104 1953497087 37204992 bc Unknown -- (I'll attach an archive with some logs in a moment) -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c7 --- Comment #7 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2014-09-11 08:32:00 CEST --- Created an attachment (id=605887) --> (http://bugzilla.novell.com/attachment.cgi?id=605887) Archive with various logs showing the problem The archive contains: md.log: data as seen by MD-RAID in inst-sys (/proc/mdstat, mdadm -E, mdadm -Q, etc.) YaST-inst.tar.bz2: YaST logs from the installation system dmesg.log: Part of dmesg when the array is detected fdisk.log: disks and partitions as seen by fdisk -l parted.log: disks and partitions as seen by parted typescript.knoppix-7.4: For comparison partitions as seen by sfdisk -l (I wanted to use parted actually, but I was more sleeping that awake when I did it) Note: For some reason the RAID is not handled by MD-RAID, but by device mapper in Knoppix -- 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=895542 https://bugzilla.novell.com/show_bug.cgi?id=895542#c8 Petr Uzel <puzel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED --- Comment #8 from Petr Uzel <puzel@suse.com> 2014-09-11 10:10:25 UTC --- Thanks, this info should help to see what's going on. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=895542 http://bugzilla.novell.com/show_bug.cgi?id=895542#c17 Petr Uzel <puzel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #17 from Petr Uzel <puzel@suse.com> --- I am sorry, but I was not able to find time to look into this bug. Now openSUSE 13.1 is no longer supported, so I will close this bug. If it can still be reproduced with current and supported openSUSE version, please reopen. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com