[Bug 733299] New: Installation on raid crashed
https://bugzilla.novell.com/show_bug.cgi?id=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c0 Summary: Installation on raid crashed Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: petr.m@seznam.cz QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0) During installation I've got this error: -------- Yast2 Failure occurred during following action: make RAID /dev/md0 from /dev/sda1 /dev/sdb1 System error code: -6008 /bin/ls -| --full-times '/dev/sda1' '/dev/sdb1';sbin modprobe raid1;/sbin/mdadm --create '/dev/md0' --run --level=raid1 -e1.0 -b internal --chunk 4 --raid-devices=2..... mdadm:super1.x cannot open /dev/sda1: Device or resource busy mdadm:/dev/sda1 is not suitable for this array mdadm:super1.x cannot open /dev/sdb1: Device or resource busy mdadm:/dev/sdb1 is not suitable for this array ------ My config: md0 swap (sda1,sdb1) md1 / (sda2,sdb2) Reproducible: Always -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c1 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |aschnell@suse.com InfoProvider| |petr.m@seznam.cz --- Comment #1 from Arvin Schnell <aschnell@suse.com> 2011-11-30 14:08:26 UTC --- Please provide YaST logs, see http://en.opensuse.org/openSUSE:Bugreport_YaST. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c2 --- Comment #2 from Petr Matula <petr.m@seznam.cz> 2011-11-30 14:21:05 UTC --- Created an attachment (id=464879) --> (http://bugzilla.novell.com/attachment.cgi?id=464879) yast logs -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c3 --- Comment #3 from Arvin Schnell <aschnell@suse.com> 2011-11-30 15:09:24 UTC --- The logs contain the call to create a RAID but it succeeds. Maybe from another installation but useless to analyse the problem. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c4 --- Comment #4 from Petr Matula <petr.m@seznam.cz> 2011-12-01 07:43:47 UTC --- Created an attachment (id=465091) --> (http://bugzilla.novell.com/attachment.cgi?id=465091) yast logs 2 -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c5 --- Comment #5 from Arvin Schnell <aschnell@suse.com> 2011-12-01 13:38:23 UTC --- Did you execute any commands next to YaST? -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Installation on raid |Installation on MD RAID |crashed |failed -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c6 --- Comment #6 from Petr Matula <petr.m@seznam.cz> 2011-12-01 13:59:48 UTC --- When the window with an error message appeared I clicked on the button to continue and ignore error. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c7 Petr Matula <petr.m@seznam.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|petr.m@seznam.cz | --- Comment #7 from Petr Matula <petr.m@seznam.cz> 2011-12-01 14:07:16 UTC --- after the installation is properly created md1 but instead md0 I have md127 -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c8 --- Comment #8 from Arvin Schnell <aschnell@suse.com> 2011-12-01 14:35:59 UTC --- The mdadm command to create the RAID fails with "device or resource busy" (already shown in comment #0). From the logs I cannot see a reason why the devices should be busy, e.g. no mounts, no dm tables, no md raids. YaST also called "udevadm --settle" before the mdadm command. Another strange thing is that first mdadm does not see any raids during assemble and /proc/mdstat is empty. But after the failed create commands /proc/mdstat shows two raids. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |nfbrown@suse.com |ovo.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.
https://bugzilla.novell.com/show_bug.cgi?id=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c9 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |petr.m@seznam.cz --- Comment #9 from Neil Brown <nfbrown@suse.com> 2012-01-05 04:48:51 UTC --- I cannot reproduce this. Would you be able to describe exactly the steps you went through. i.e. - how were the devices formatted to start with - were they partitioned? if so, what type? Were there filesystems? Were they configured for RAID already. - what did yast see when you got to disk setup? Did you have to deconstruct anything before making the RAID arrays? - What - as exactly as possible - were your sequence of steps? One thing I found was that if I started with 2 drives, each with two partitions, one marked 'swap' and one containing a filesystem, then yast would not let me use the two 'swap' partitions in a RAID. I first had to tell it that those weren't 'swap' any more - which I thought was a bit odd. Thanks. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c10 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh@inai.de --- Comment #10 from Jan Engelhardt <jengelh@inai.de> 2012-07-16 13:51:11 CEST --- Could it be that there was a preexisting swap partition that yast activated and used? Switch to tty2 and have a look at /proc/swaps. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c11 --- Comment #11 from Jan Engelhardt <jengelh@inai.de> 2012-07-16 13:57:51 CEST --- Or that there were preexisting raids (incompletely assembled); this will be visible when `mdadm -D /dev/mdX` won't work, but /proc/mdadm contains mdX and `mdadm -S /dev/mdX` also succeeds. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c12 --- Comment #12 from Petr Matula <petr.m@seznam.cz> 2012-09-04 20:17:33 UTC --- error persists in the opensuse 12.2 My config: md0 swap (sda1,sdb1) md1 / (sda2,sdb2) I deleted before installation all partitions. During installation I've got this error: -------- Yast2 Failure occurred during following action: make RAID /dev/md0 from /dev/sda1 /dev/sdb1 System error code: -6008 .... mdadm:super1.x cannot open /dev/sda1: Device or resource busy mdadm:/dev/sda1 is not suitable for this array mdadm:super1.x cannot open /dev/sdb1: Device or resource busy mdadm:/dev/sdb1 is not suitable for this array ----------- I interrupted the installation and started a new installation. During new installation I chose "Import Partition Setup.. and voila my config (md0 swap (sda1,sdb1);md1 / (sda2,sdb2)) is imported. md1 formating this time with no errors -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c Petr Matula <petr.m@seznam.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Installation AssignedTo|nfbrown@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 12.1 |openSUSE 12.2 Target Milestone|--- |Final OS/Version|SUSE Other |openSUSE 12.2 -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c13 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@suse.com --- Comment #13 from Neil Brown <nfbrown@suse.com> 2012-09-13 01:30:03 UTC --- It sounds like something is racing with the mdadm --create. Maybe udev notices the devices for some reason and runs "mdadm -I" on the devices and it turns them into an array before "mdadm --create" can get around to doing it. It seems unlikely but it is the only scenario that I can imagine at all. As you seem to have found a work-around, and as we cannot reproduce it, I wonder if there is much point pursuing this bug further. There are some locking changed in upstream mdadm which could remove this problem it is something like my guess, so there is a modest chance it will be fixed for the next release.... -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c14 --- Comment #14 from Jan Engelhardt <jengelh@inai.de> 2012-09-13 03:37:01 CEST --- If seem to loosely remember that swap block devices may be automatically activated if found. In case they were not automatically activated, then, given a machine with insufficient enough RAM (that I clearly remember), linuxrc will ask you to give it a swap partition to use during the installation, choosing from preexisting ones. However, it looks like said swap partitions are not deactivated before the partition table is changed/mkswap is called/mdadm -C is called, leading to said error. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c15 Torsten Rosenberger <rosenberger@taoweb.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rosenberger@taoweb.at --- Comment #15 from Torsten Rosenberger <rosenberger@taoweb.at> 2012-09-13 08:02:44 UTC --- Same error. Today i tried 4 times to install OpenSuSE 12.2 with /boot 500MB RAID1 format ext4 swap to 4 GB each disk / 30GB RAID1 format ext4 /opt 10 GB RAID1 Format ext4 /var 30 GB RAID1 Format ext4 /tmp 10 GB RAID1 Format ext4 /home 50 GB RAID1 format ext4 100GB RAID1 not formatted 500GB RAID1 not formatted 50GB RAID1 not formatted /work 150GB format ext4 same error as above. Failure occurred during following action: make RAID /dev/md0 from /dev/sda1 /dev/sdb1 System error code: -6008 Error appear during creation of every md device BR/Torsten -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c16 --- Comment #16 from Torsten Rosenberger <rosenberger@taoweb.at> 2012-09-13 11:18:52 UTC --- I tried 5 different installations with swap partition but not formatted without swap partition only with 2 raid devices but always the same error. on the rescue console it is possible to create an md array when the creation of the md array during Yast installation fails it is possible to stop the md124 md125 ... raid arrays with mdadm --stop /dev/md124 an if all the missed arrays are stopped it is possible to create new array with mdadm. I also tried OpenSuSE 12.1 with the same error! Hardware: HP DL120 G7 no Software raid used. BR/Torsten -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c17 Torsten Rosenberger <rosenberger@taoweb.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|petr.m@seznam.cz | --- Comment #17 from Torsten Rosenberger <rosenberger@taoweb.at> 2012-09-13 12:43:38 UTC --- Created an attachment (id=505613) --> (http://bugzilla.novell.com/attachment.cgi?id=505613) My Last y2log from OpenSuSE 12.2 -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c18 --- Comment #18 from Torsten Rosenberger <rosenberger@taoweb.at> 2012-09-13 12:45:07 UTC --- know I tried OpenSuSE 11.4 an there all works fine!! I also tried OpenSuSE 12.2 again and it still fails but here are the y2log https://bugzilla.novell.com/attachment.cgi?id=505613 BR/Torsten -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c19 --- Comment #19 from Torsten Rosenberger <rosenberger@taoweb.at> 2012-09-17 09:32:34 UTC --- Hello again. now I'm confused. I installed OpenSuSE 12.2 today on an identical hardware with the same Setup with SUCCESS. Only difference is the RAM before 8GB Kingsten and on the second HP DL120 G7 8GB Samsung ? BR/Torsten -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |snwint@suse.com |ovo.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.
https://bugzilla.novell.com/show_bug.cgi?id=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c20 Petr Matula <petr.m@seznam.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Installation Platform|x86-64 |All AssignedTo|snwint@suse.com |yast2-maintainers@suse.de Product|openSUSE 12.2 |openSUSE 13.1 OS/Version|openSUSE 12.2 |openSUSE 13.1 --- Comment #20 from Petr Matula <petr.m@seznam.cz> 2014-07-13 10:30:36 UTC --- The same problem exists in 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c21 --- Comment #21 from Petr Matula <petr.m@seznam.cz> 2014-07-13 12:12:11 UTC --- error persists in the opensuse 13.1 My expected config: md0 swap (sda1,sdb1) md1 / (sda2,sdb2) I deleted before installation all partitions. During installation I've got this error: -------- Yast2 Failure occurred during following action: make RAID /dev/md0 from /dev/sda1 /dev/sdb1 System error code: -6008 .... mdadm:super1.x cannot open /dev/sda1: Device or resource busy mdadm:/dev/sda1 is not suitable for this array mdadm:super1.x cannot open /dev/sdb1: Device or resource busy mdadm:/dev/sdb1 is not suitable for this array ----------- I interrupted the installation and started a new installation. I open yast partitioner: I can see hdd md126 ended on 262 cylinder and RAID dev/md/linux:1 started on 262 cylinder (not 263?) I cleared hdd md126 and RAID /dev/mdlinux:1 I recreate sda2 and sda3 from 263 cylinder, create RAIDs again and started instalation again. -- 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=733299 https://bugzilla.novell.com/show_bug.cgi?id=733299#c22 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #22 from Arvin Schnell <aschnell@suse.com> 2014-09-02 14:50:24 UTC --- When our mdadm expert cannot reproduce nor explain the issue the YaST team cannot help either, sorry. So since the bug report was assigned to YaST again I can only close it as WORKSFORME. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com