https://bugzilla.novell.com/show_bug.cgi?id=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c2 --- Comment #2 from Michal Veselenyi 2013-11-10 11:57:39 UTC --- Created an attachment (id=566787) --> (http://bugzilla.novell.com/attachment.cgi?id=566787) 13.1-rc2 boot failure - on splash console -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c4 --- Comment #4 from Michal Veselenyi 2013-11-10 11:59:05 UTC --- Created an attachment (id=566789) --> (http://bugzilla.novell.com/attachment.cgi?id=566789) 13.1-rc2 partition setup - rescue system -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c5 Joachim Wagner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwagner@computing.dcu.ie --- Comment #5 from Joachim Wagner 2013-11-11 17:41:10 UTC --- The link "in this bug" links to show_bug.cgi?id=4 which gives a "Access Denied" message. Is the bug number incomplete or can you re-paste the configuration here? I installed a Raid 1 setup with RC2 last weekend without problems. I didn't open the boot loader page during installation though. Is step 4 essential to replicate the bug? Note that I'm just another user, not an OpenSUSE developer. -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c7 Michal Veselenyi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmicho@gmail.com --- Comment #7 from Michal Veselenyi 2013-11-11 21:00:45 UTC --- (In reply to comment #5)

The link "in this bug" links to show_bug.cgi?id=4 which gives a "Access Denied" message. Is the bug number incomplete or can you re-paste the configuration here? I installed a Raid 1 setup with RC2 last weekend without problems. I didn't open the boot loader page during installation though. Is step 4 essential to replicate the bug? Note that I'm just another user, not an OpenSUSE developer.

PS: the bug word in "in this bug" was translated into a random link (why id 4?) by issue tracker. I really meant to say only "in this bug". PS2: I'll not be able to test this too often as I already installed 12.3 on the PC and I'm using it. Unless it is for testing of something most probably fixed/working. I don't actually have any other PC with 2 hdds. PS3: step 4 is most probably not essential. It was surely a bug before in 12.3-beta or 12.2. PS4: dunno if 'mdadm --zero-superblock' would help as I recreated several times the partitions + raid drives (or what is it called) so the md should ignore any other data not on expected position. And anyway, the very 1st setup I've made was on disks with very random data (was 2 years somewhere on shelf, turned off). -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c8 --- Comment #8 from Michal Veselenyi 2013-11-11 21:06:34 UTC --- (In reply to comment #5)

I installed a Raid 1 setup with RC2 last weekend without problems. I didn't open the boot loader page during installation though. Is step 4 essential to replicate the bug? Note that I'm just another user, not an OpenSUSE developer.

Did you usa same / similar setup? -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c10 --- Comment #10 from Joachim Wagner 2013-11-14 12:42:18 UTC --- I tried a simpler and more virtualisation-friendly setup with RAID0 with 4MB chunk size for / and /home and plain partitions for swap and /boot. (RAID1 on a single physical disk would cause heavy I/O slowing down the test, especially during the initial RAID re-sync.) I can confirm that named md devices cause a blank screen after the 2nd reboot (the first reboot after the first auto-login). Furthermore, I can answer Neil's request for the contents of /etc/mdadm.conf: this file does not exist (su - + ls /etc/md* shows "no such file or directory"). Details: * in first auto-login after installation, "df" shows /dev/md126 mounted on /home and /dev/md127 mounted on / * no file /etc/md* * /etc/fstab uses the names /dev/md/root and /dev/md/home * after restart and grub2, the screen stays black; on ctrl+alt+F1 to F7, there is a blinking cursor on the black screen * rescue system from the installation DVD shows /dev/md126 + 127; mounting them shows that md127 is /home and md126 / (the other way around than in the first auto-login) * manually changing /etc/fstab to use /dev/md126 for / and /dev/md127 for /home allows the system to boot but auto-login fails. Logging in as root, /home is not mounted and manually mounting it shows the same contents as / ; "df" shows that / is md127 despite /etc/fstab specifying it differently. Checking grub.cfg, / is referred to by uuid and mduuid. * manually changing /etc/fstab to use /dev/md127 for / and /dev/md126 for /home fixes all problems * changing the hostname to "linux", /dev/md/home and /dev/md/root also work in /etc/fstab (in my test it was no problem that dhcp overwrites the hostname -- presumably this happens after the md devices are assembled) I experimented a good bit to come up with a simple workaround but correcting the md name with commands like mdadm --assemble "/dev/md/linux-7hhd:root" --name="linux-7hhd:root" \ --update=name /dev/vda[23] is not enough (mdadm --examine after a reboot shows that this was successful; note also that this should be equivalent to Neil's suggestion to use --homehost=$TARGETHOST during the installation). Maybe the md name "linux:root" is used somewhere in the initrd. I checked the grub configuration and it uses uuids and mmuids, rather than device names. Workaround 1 (tested but complicated and stuck with the hostname "linux" which is no good if the goal is to share hard drives between multiple hosts): * in a rescue system, look at /proc/mdstat and mount your / fs * the tested way (my steps above): edit your fstab to use md numbers rather than names; consider that / and maybe /boot are assembled early and therefore become md127 and/or md126 even though they may have different numbers in the rescue system; repeat until system boots; then run YaST2 to change the hostname to "linux" and restore the fstab with md names. * alternatively -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c12 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |aschnell@suse.com InfoProvider|aschnell@suse.com | --- Comment #12 from Arvin Schnell 2013-11-20 14:13:06 UTC --- (In reply to comment #9)

Arvin: what do you know about the use of "/dev/md/data" in /etc/fstab?

This was added on purpose for fate #315590. It's reasonable that the user gives a name to the RAID to actually use the name.

Would it be possible to add "--homehost=any" to the "mdadm" command when creating arrays?

That shouldn't be a problem.

It would be best to use the final host name there (rather than 'any'), but 'any' is better than "linux".

The final name is likely not known during installation. E.g. the system might use DHCP during the first steps of the installation and a proper network setup is done later (that's the current workflow of 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c14 --- Comment #14 from Joachim Wagner 2013-11-20 20:56:31 UTC --- Confirmed in 13.1 final (with setup of comment 10): * after restart and grub2, the screen stays black; on ctrl+alt+F1 to F7, there is a blinking cursor on the black screen -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c15 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@suse.com AssignedTo|nfbrown@suse.com |aschnell@suse.com --- Comment #15 from Neil Brown 2013-11-27 05:17:37 UTC --- Re comment 10, I found that using "--assemble .. --update=name --name=..." did work providing I used that to change the names in all arrays other the '/'. '/' doesn't need a new name as the initrd contains an mdadm.conf which has the uuid of the array associated with /dev/md/root, is it gets assembled with that name. So there are two ways to fix this, both require changes to the installer. 1/ Add "--homehost=any" to the command line used to create md arrays. As an alternate, if the final hostname is know, --hostname=$HOSTNAME could be used. 2/ create an /etc/mdadm.conf which lists all the array with their desired names. After the arrays have been created, the command mdadm -Ds >> /etc/mdadm.conf will achieve this. Making both of these changes would be acceptable and probably preferable. If an install with the current DVD has completed and reboot has failed it can be fixed by entering the root password to get a shell, then running mdadm -Es >> /dev/mdadm.conf reboot Note that the command suggested for inclusion in the installed has "D", while the command to run if reboot has failed has "E". Arvin: I hope it is OK to re-assign this to you for completion. 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c17 --- Comment #17 from Michal Veselenyi 2013-11-27 08:48:40 UTC --- So what's the current workaround? Is it sufficient to leave the name blank (hoping installator will not create named raids), or one must manually change fstab after 1st boot? -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c19 --- Comment #19 from Joachim Wagner 2013-11-27 09:53:16 UTC --- added this to https://en.opensuse.org/openSUSE:Most_annoying_bugs_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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c21 --- Comment #21 from Joachim Wagner 2013-11-29 15:02:03 UTC --- (In reply to comment #20)

Why is it not possible to insert the Naming from the Bios "Volume1 / Vol1" like in other Distribution ? I added your feature request to openfate as case #316749.

Please vote for it and the related request #315590. You can login on openfate with the same details you use for this page. Note that this is a slightly different issue: You are talking about RAIDs created in the Bios before installation. This bug report is about RAIDs created by YaST during 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.

https://bugzilla.novell.com/show_bug.cgi?id=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c23 --- Comment #23 from Joachim Wagner 2013-12-02 10:35:29 UTC --- (In reply to comment #22)

BTW: Why is the host part of the device name "linux"? The machine got its name "Bowman" via DHCP from the very beginning [...] See comment 13.

For the purpose of this bug report, I think "--homehost=any" is the way forward. I added a summary of the ideas and comments around the RAID hostname, initial hostname and DHCP to the feature request openfate #315590. -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c25 --- Comment #25 from Arvin Schnell 2014-01-09 15:24:16 UTC --- Fixed for openSUSE 13.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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c27 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #27 from Arvin Schnell 2014-03-12 07:40:28 UTC --- *** Bug 867514 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=867514 -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c29 --- Comment #29 from Andrey Borzenkov 2014-03-12 19:07:39 UTC --- I tested openSUSE-Factory-NET-i586-Build0105-Media.iso (dated 12.03.2014) and I get exactly the same problem as in bnc#867514. So what exactly is "fixed" here? I'm tempted to reopen it ... -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c31 Andrey Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|Installation |Installation Version|Final |13.2 Milestone 0 Resolution|FIXED | AssignedTo|aschnell@suse.com |yast2-maintainers@suse.de Product|openSUSE 13.1 |openSUSE Factory --- Comment #31 from Andrey Borzenkov 2014-03-13 12:28:00 UTC --- OK, reopened, because ... (In reply to comment #30)

The problem with changing IP address should be fixed by using --homehost any when creating mdadm RAIDs.

That's not a solution. It makes it impossible to have more than one installation on the same system using the same names. MDs are host-specific for a reason. The correct solution is to either use mdadm.conf to force names for the right UUIDs or (in addition) put correct host name; it should be possible with single stage installer which is planned (not sure whether this is already implemented).

The problem with not generating a mdadm.conf is fixed.

There is no /etc/mdadm.conf present after installation. I can provide whatever logs are needed from this VM. -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c33 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |arvidjaar@gmail.com --- Comment #33 from Arvin Schnell 2014-03-13 13:57:18 UTC --- For the missing mdadm.conf I need log files from the installation. The --homehost=any usage was added after recommendations by our mdadm expert Neil, see comment #15. I you do not agree here I suggest to create a feature request since I cannot change such things all the time. -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c35 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #35 from Arvin Schnell 2014-03-13 14:32:06 UTC --- In the logs I see: libstorage version 2.24.8 libstorage source moddate: Tue 15 Oct 10:29:14 CEST 2013 Current version is 2.25.9. The fix was included in version 2.25.6 on January 9th. Somehow you did not correctly use the NET ISO. AFAIR since the NET ISO does not contain the complete installation system you have to provide URL for that. But I never use the NET ISO so I cannot explain details. And no, Neil suggested to do both changes: "Making both of these changes would be acceptable and probably preferable." So I again consider the issue as fixed, but see comment #24. -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c37 --- Comment #37 from Arvin Schnell 2014-03-13 15:21:06 UTC --- With openSUSE-Factory-DVD-x86_64-Build0108-Media.iso (likely only available internal) /etc/mdadm.conf is written. Unfortunately I found a bug in the bootloader proposal (bug #868226 - likely not visible external). -- 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=849752 https://bugzilla.novell.com/show_bug.cgi?id=849752#c39 --- Comment #39 from Arvin Schnell 2014-03-13 17:01:38 UTC --- Yes, in one test I had three named BOOT, ROOT and SWAP. -- 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.