https://bugzilla.novell.com/show_bug.cgi?id=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c Ye Yuan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c2 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |secure@aphofis.com InfoProvider|secure@aphofis.com | --- Comment #2 from Scott Couston 2013-07-18 09:44:23 EST --- (In reply to comment #1)

I'm not exactly sure what happens. Is that an installation from Live CD or a regular installation?

Default Opensuse 12.3 Default KDE install from DVD, non automated... Not pre-deployed preferences! During the installation phase the install runs perfectly correct up until the final Online Update phase has completed. The >Next dumps the install out of GUI as a console screen showing services starting and stopping. The early termination of the GUI at the end of the online update phase >Next is the problem as the install script fails and terminates into console. What Logs do you need -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c4 --- Comment #4 from Scott Couston 2013-07-20 09:18:04 EST --- Created an attachment (id=548724) --> (http://bugzilla.novell.com/attachment.cgi?id=548724) yast-files-compressed as requested -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c6 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|secure@aphofis.com | --- Comment #6 from Scott Couston 2013-07-21 10:55:35 EST --- The other more I did and the ore installs on X_64 Systems the error can be more easily identified and might need to change the classification to kernel. This error is the result of all the online updates being installed and the first software initiated boot of the PC to load for the first time from HDD. The error is presented on the screen as a long list of services being shut down because the software cannot initiate a reboot of the newly installed system...Hope this helps -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c8 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|secure@aphofis.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #8 from Scott Couston 2013-08-10 12:32:45 EST --- Reset to Defaults due change in version problem 12.2 and still exists in 12.3 -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c Xiyuan Liu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |tonyj@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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c12 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #12 from Lukas Ocilka 2013-11-08 16:56:53 UTC --- Please attach /var/log/zypp/history That file could contain more info Online update was called: 2013-07-17 00:01:33 2013-07-19 07:51:42 -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c14 --- Comment #14 from Lukas Ocilka 2013-11-08 17:07:30 UTC --- (In reply to comment #2)

During the installation phase the install runs perfectly correct up until the final Online Update phase has completed. The >Next dumps the install out of GUI as a console screen showing services starting and stopping.

The early termination of the GUI at the end of the online update phase >Next is the problem as the install script fails and terminates into console.

Yast online update (during second stage installation) usually does two things: - If libzypp/zypper/online-update related patch is installed, Yast restarts itself and starts over again, then it should continue with other patches - If Kernel update is installed, Yast reboots the system After the reboot, Yast should continue with second stage right after the online update phase. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c Xiyuan Liu changed: What |Removed |Added ---------------------------------------------------------------------------- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c17 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|secure@aphofis.com | --- Comment #17 from Scott Couston 2013-11-11 19:31:26 EST --- (In reply to comment #16)

Scott, please attach /var/log/zypp/history as requested in comment #12. Thanks.

Sorry Lukas I did not look closely enough at #12 and thought it was still asking for /var/log/YaST2/ again. I think I will include zypp log data as a mater of course when Yast2 logs are required for other bugs. I no longer have log data that goes back to that install. My apologies I should have read more clearly. I know first online update progressed all o.k and it was the restart that halted everything but you need log proof certainly. Would you like me to redo the test on the same PC as it sits on my LAN as a test PC only to run different scenarios. I dont mind really because this is important and if I am correct, has implications on the install program that many need to test for UEFI BIOS in the same way that the partitioner does ONLY when I delete all existing partitioning and dont edit or import past mount points. I'm not quite sure why there arn't more testers with X_64 with New UEFI BIOS and Hardware and a LAN environment. Under the above test condition I can state the I did not use any type of /boot mount point as only / was used on the same physical HDD along with a /swap. I would have normally included a /home mount point on the same physical HDD but this I cannot swear too but / and swap I definitely can. This should rule out the possibility of the / mount point somehow not being available at the time of restart. It was only after this failure that I started to create a /boot mount point and to be honest I havn't tested that the partitioner issues a warning if only / is specified. Whats the deal now in needing a FAT partition for /boot and a UEFI BIOS or is that a never-ending story that the kernel guy's dont want to commit to paper :-) -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c19 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #19 from Steffen Winterfeldt 2013-11-11 12:08:00 CET --- Scott, on UEFI systems a special UEFI system partition is needed (FAT32, will be mounted at /boot/efi). Normally the installer should propose to create such a partition. If it fails to do so, the boot config will not work. But the visible effect is that the _second_ restart fails (the first is done using kexec). It would be nice if you could redo the install and have an eye on the boot config. As 13.1 is out by now, you might preferably test 13.1 instead. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c21 --- Comment #21 from Scott Couston 2013-11-18 22:07:16 EST --- Created an attachment (id=567861) --> (http://bugzilla.novell.com/attachment.cgi?id=567861) log fiiles I was getting variable test results when I was using different install scenarios that appeared to have no logic. I then swapped to an X_64 Hardware that pre-dates a UEFI BIOS. The seemingly illogical then became logical. When the partitioner is called on any X_64 software if the user creates their own partitioning and created a /boot, / , /home and SWAP all formatted with Ext*; before its committed the partitioner puts up a warning that a /boot/uefi formatted with FAT need to be done. This is on an X_64 PC but with NO UEFI BIOS. So it looks like who ever wrote the check for and warning could only foresee that X_64 must have a UEFI BIOS in 12.3. Prior versions made no such warnings and I'm not sure where the warnings are coming from. Now for the kicker...on the same test machine if I only partition a / and a /home and SWAP and no separate /boot entry no warning is generated if I'm using a PC with or without a UEFI BIOS. I'm not quite sure how you would test to see what type of BIOS via ACPI calls????..got me there...I dont think its possible so that may explain, why the stuff up; most all of our reboot during install in X_64 software in 12.3 at the re-boot after first online update. Ive attached the log files of the PC I tested as X_64 but NO UEFI BIOS. As a very ugly thought whilst we are here all of my X_64 PC's with different branded motherboards all provide a boot option to boot under UEFI or not. That ugly complication I will leave to the kernel guys think about what to do cause this makes things very very very ugly indeed. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c23 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|snwint@suse.com |aschnell@suse.com --- Comment #23 from Steffen Winterfeldt 2013-11-18 13:17:07 CET --- This is about the partition proposal. Assigning to yast2-storage maintainer. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c24 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #24 from Arvin Schnell 2013-11-20 11:19:04 UTC --- Please give the exact message of the warning you are referring to in comment #21. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c26 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |NORESPONSE --- Comment #26 from Arvin Schnell 2013-11-21 09:19:12 UTC --- I don't get the message mentioned in comment #21. So I don't know what you are talking about and cannot check anything in the source code. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c28 --- Comment #28 from Scott Couston 2013-11-28 04:42:25 EST --- Created an attachment (id=569386) --> (http://bugzilla.novell.com/attachment.cgi?id=569386) Screen Image In this screen shot you can see that a /boot mount point was created and not left simply to / On the occasion where you have any X_64 PC AND you specify a /boot mount point, when you commit you get the error...and I'll have to paraphrase it as this is 100% reproducible and if its no please send me a pic of your partitioning mount point on your X_64 PC Warning....there may be an issue in being able to boot the PC....you need to create a /boot/efi formatted with FAT....do you really want to proceed -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c30 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #30 from Arvin Schnell 2013-11-27 22:02:59 UTC --- I cannot find a message in YaST that fits your description. Please the exact wording (or even a screen shot). -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c32 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #32 from Arvin Schnell 2013-11-28 08:10:48 UTC --- Yes, that's what I'm saying. I'm still not exactly sure what you are doing. Anyway, I assume it's a duplicate if bug #806490. Thus fixed in 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c34 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #34 from Jeff Mahoney 2013-11-28 20:18:44 EST --- Setting NEEDINFO based on comment #31. If Arvin says he can't reproduce it, he can't reproduce it. He's asked for a screen shot. Even a photo will do. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c36 --- Comment #36 from Scott Couston 2013-11-29 17:41:34 EST --- Give me 4 or so days as I have to setup to trash and offline PC Jeff -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c38 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|secure@aphofis.com | Resolution| |FIXED --- Comment #38 from Scott Couston 2013-12-02 08:08:25 EST --- Bug #806490 shows this to be an issue of RC1 of 12.3 and very succinctly shows all of the above and more. Nice to know the problem exists and is well known in validation of this bug. Happy to let Jiri take it from here between factory and yast...If its fixed in 13.1 as I read from...all is o.k -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c40 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Component|Installation |Installation Resolution|FIXED | AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | Product|openSUSE 12.3 |openSUSE 13.1 --- Comment #40 from Scott Couston 2013-12-05 21:19:58 EST --- (In reply to comment #30)

I cannot find a message in YaST that fits your description. Please the exact wording (or even a screen shot).

The exact wording 12 13.3 and 13.1 is presented if the PC is an X_64 with or without an EFI BIOS or if is able to be toggled on or Off Warning: With you current setup, your openSUSE installation will encounter problems when booting, because you have no FAT partition mounted on /boot/efi This will cause severe problems with the normal boot setup. If you do not know ecactly what you are doing, use a normal FAT partition for your files bwloe /boot/efi. Really use this setup? End quote.....I setup this install and it took me about 8 mins to reproduce it..If I can do this reliably can you please tell me exactly what you did to not see this message. -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c42 --- Comment #42 from Scott Couston 2013-12-05 21:51:38 EST --- In the proposed setup of FAT on /boot/efi this was proposed on sdc and I moved it to sda..when I went to confirm I got a further warning from the partitioner during a 13.1 install...as follows quote. Warning: With you current setup, your openSUSE installation will encounter problems when booting, because the disk you have your /boot partition is located does not contain a GTP Disk Label. It is probably not possible to boot such a setup. If you need to use this disk installation, you should destroy the disk label in the expert partitioner Really use this setup Y/N Unquote...When I view the Disk Label of sda which contains my FAT /boot/efi its Label is MSDOS The disk label of sdb is GTP and sdc is MSDOS. The Three HDD are SATA devices and I can change the label in the partitioner and to my mind in should not matter...This may be a hangover from suse.com SLES where a Netware very much care about the disk label if SLES were to be run as a VM under V/Netware Servers.....or I could be talking out my ear...I'll continue on with my set-up even though the warning above am I going to override ..We need the Hardware guys in now...how about giving us all back comsurf utility to really test our SATA and SCSI Disks...lol -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c44 --- Comment #44 from Scott Couston 2013-12-06 12:21:53 EST --- Another failure to install condition. The initial boot from media to start the installation must be under under its NON-UEFI DVDRAM or the installation falls over at the creation of the partition setup. It would appear that you need to boot the DVD under a NON-UEFI state. The varying boot options are pretty standard across X_64 new mother boards the hold AMD X_64 CPU's. This is perfectly understandable when I propose a complete HDD proportioning and still using the enquired /boot/ufi formatted as FAT. I'll attach the log files soon enough or if your want more than yast2 ogs please advise on these 2 needinfo questions? ? -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c46 --- Comment #46 from Scott Couston 2013-12-30 12:48:42 EST --- As this goes to the heart of the partitioner and its current discovery of UEFI BIOS and the install fails if the user elects their own partitioning format I think we need to devote more resources to fixing this and help me understand what was intrinsically different to NEEDINFO environment and mine. I know is Christmas but if we could get onto this please as I need to help you resolve this before I can trash a PC and provide log answers for another bug with 13.1. Jiri, I'm reassigning back to you so we can get all parties working together. Hoping everyone in Europe didn't freeze or loose power and all were warm cause its 40C down here in OZ -- 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c48 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|aschnell@suse.com | Resolution| |FIXED --- Comment #48 from Scott Couston 2014-01-01 17:00:46 EST --- Fixed in BUG 850056 Alberto Planas Dominguez and Karl Eichwalder say as much as I did in first entries and 15 and 17 and 21 and used the same logic and fixed with a minimum of fuss -- 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.