[Bug 829834] New: New KDE Default Non-Automated Installation Fails to Complete with System Frozen but Hardware Completely Functional
https://bugzilla.novell.com/show_bug.cgi?id=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c0 Summary: New KDE Default Non-Automated Installation Fails to Complete with System Frozen but Hardware Completely Functional Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: secure@aphofis.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Standard 12.3 KDE Non Automated New Installation Fails to complete. Install runs smoothly until the last of the patch updates are installed>Next...dump out of GUI environment with list of processes than frozen after Suse Firewall Part 2..... Installation does restart but the X_64 require hardware soft-restart to continue. On the + Side, the Release Notes DO Download and Test for Network Connection Actually works. On the - Side, at time of Restart we can still see the text...creating RAM Disk.....Can we simply change the colour of this text to be black on black so it doesn't look so out of place..Its not tidy at all...Same in 12.1. 12.2. Reproducible: Always Steps to Reproduce: 1. Multiple Attempts fails at same point in time New Install after New Install. 2. At beginning of all the Installs ALL HDD partitions are Newly formatted, including SWAP 3. Actual Results: The only value are the log files which I'll happily assist with Log files when and if Bug gets Assigned and will work with the Assignee Expected Results: Installation completes without error..The Hardware is not frozen at all so we can take the specific PC's Hardware out of the question Be specific with your request for log files...I would normally include them out front. I'll happily assist with Log files when and if Bug gets Assigned and will work with the Assignee. -- 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 Ye Yuan <yyuan@suse.com> 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#c1 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #1 from Steffen Winterfeldt <snwint@suse.com> 2013-07-17 08:24:55 CEST --- I'm not exactly sure what happens. Is that an installation from Live CD or a regular 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c2 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |secure@aphofis.com InfoProvider|secure@aphofis.com | --- Comment #2 from Scott Couston <secure@aphofis.com> 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#c3 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #3 from Steffen Winterfeldt <snwint@suse.com> 2013-07-18 08:00:41 CEST --- Please attach /var/log/YaST2/ -- 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 <secure@aphofis.com> 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#c5 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|snwint@suse.com |secure@aphofis.com --- Comment #5 from Scott Couston <secure@aphofis.com> 2013-07-20 09:19:37 EST --- Created an attachment (id=548725) --> (http://bugzilla.novell.com/attachment.cgi?id=548725) tast-files as requested part 2 of 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c6 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|secure@aphofis.com | --- Comment #6 from Scott Couston <secure@aphofis.com> 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#c7 --- Comment #7 from Scott Couston <secure@aphofis.com> 2013-07-24 07:51:21 EST --- Final conclusion. This halt to the installation program is caused by not being able to restart the PC for first time to load O/S from HDD. The following conditions need to be present to reproduce this bug 1. It must be X_64 Architecture with UEFI BIOS Support ON Jiri,Suggest reassignment to Kernel -- 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 <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|secure@aphofis.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #8 from Scott Couston <secure@aphofis.com> 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 Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.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#c Xiyuan Liu <xyliu@suse.com> 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#c11 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@suse.com --- Comment #11 from Lukas Ocilka <locilka@suse.com> 2013-11-08 16:53:44 UTC --- OK, just briefly scanned through Yast logs, and this is a bit suspicious: 2013-07-16 22:36:32 ModulesConf.cc(getTimeStamp):282 Failed to stat /etc/modprobe.d/50-yast.conf: No such file or directory ModulesConf.cc(writeFile):560 Modules not modified, not writing ModulesConf.cc(~ModulesConf):103 Can't write configuration file in destructor. But this is from Installer. After the installation, online update has been called and if anything was broken afterwards, it doesn't seem to be Yast issue. Udate calls libzypp to apply new patches. Nothing less, nothing more. And still, libzypp downloads and installs patches, it's usually the patch/RPM that is broken. -- 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 <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #12 from Lukas Ocilka <locilka@suse.com> 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#c13 --- Comment #13 from Lukas Ocilka <locilka@suse.com> 2013-11-08 17:03:33 UTC --- This comes from mkinitrd.log log (shortened): 2013-07-15 21:55:11 mkinitrd called with arguments -k /boot/vmlinuz-3.7.10-1.1-desktop -i /boot/initrd-3.7.10-1.1-desktop 2013-07-16 07:58:07 mkinitrd called with arguments 2013-07-16 10:03:32 mkinitrd called with arguments -k /boot/vmlinuz-3.7.10-1.16-desktop -i /boot/initrd-3.7.10-1.16-desktop 2013-07-16 10:03:56 mkinitrd called with arguments 2013-07-16 10:04:32 mkinitrd called with arguments 2013-07-16 10:05:24 mkinitrd called with arguments 2013-07-16 10:06:01 mkinitrd called with arguments 2013-07-16 10:07:49 mkinitrd called with arguments 2013-07-16 10:08:32 mkinitrd called with arguments 2013-07-17 00:12:56 mkinitrd called with arguments -- 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 <locilka@suse.com> 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#c15 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|secure@aphofis.com | --- Comment #15 from Scott Couston <secure@aphofis.com> 2013-11-09 08:29:53 EST --- The following may help. I never ever perform automated installations. I go though every single part of every installation step by step so install is not calling the next phase. I can tell you in my sleep every single part of an unattended installation as I never ever use it and your correct about the usual second online update that is most always required. No point in debugging the whole of install without looking at each step in isolation. I would suggest that up until beta that auto call next stage should be inhibited. I would hope this requires little testing as the only time you are going to see faults with the progression of each module is if unattended install is off. I may have stumbled across the answer and you supplying details of log information has helped a great deal. What's not traditional here are two things. Its X_64 and the BIOS is UEFI active. During the install of 12.3 if the existing disk format is modified or imported there is no warning of the need for a boot partition to exist on FAT /boot/uefi. If I create a completely new disk partitioning, on exit and without a FAT /boot/eufi mount point, the partitioner issues a huge warnings regarding boot failure but only If I start off afresh and don’t simply modify or accept pre-existing or system generated formatting, mount point suggestions. This really stuffs up update installation that I have not tested. I have a completely successful useful and boot/suspend of a 12.3 system on X_64 with UEFI BIOS using 12.3 when I set a boot partition of FAT and a mount point of /boot/uefi as the partitioner sternly warns only if I create a completely new Disk Partitioning system. I most often use a RAID5 mount point to hold data I don’t want to loose due disk failure using some obtuse mount point but never /home or /root or /boot mount points. To tell you the truth I have no damn idea why we suddenly have decided that a UEFI BIOS in X_64 has complications with our kernel; probably as we have refined the Kernel to where my mind has absolutely no idea where...Sure I have a few thoughts. Provisional finding is I have a working system on 12.3 on X_64 UEFI Hardware/BIOS only when I have a FAT /boot/uefi disk partition. I don’t know if this is by accident or in keeping with log data showing errors...that I have to leave to you to talk to the kernel and Hardware guys about...Leaving status for now. -- 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 <xyliu@suse.com> 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#c16 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #16 from Lukas Ocilka <locilka@suse.com> 2013-11-11 08:48:46 UTC --- Scott, please attach /var/log/zypp/history as requested in comment #12. 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c17 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|secure@aphofis.com | --- Comment #17 from Scott Couston <secure@aphofis.com> 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#c18 --- Comment #18 from Lukas Ocilka <locilka@suse.com> 2013-11-11 09:47:12 UTC --- Steffen, you better take this over as you know more about requirements while UEFI BIOS is in use... -- 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 <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #19 from Steffen Winterfeldt <snwint@suse.com> 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#c20 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|secure@aphofis.com | --- Comment #20 from Scott Couston <secure@aphofis.com> 2013-11-12 06:36:19 EST --- Sure happy to test 13.1 If the user accepts the automated formatting and partitioning of the HDD, I trust it creates /boot/efi on FAT. As I mostly edit the partition setup no such warning is generated by the partitioner in 12.3 however If I start a completely new partition setup, the partitioner does warn of failure to boot where no /boot/uefi on FAT is present. If I had seen the warning in the above install, I would not have needed to trouble report it. I'll test in 12.3 and 13.1. If it just requires a modification to install where some error responses are suppressed; it can be changed retro I would hope. Leaving as NEEDINFO pending download of 13.1 and testing -- 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 <secure@aphofis.com> 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#c22 --- Comment #22 from Scott Couston <secure@aphofis.com> 2013-11-18 22:09:02 EST --- Created an attachment (id=567862) --> (http://bugzilla.novell.com/attachment.cgi?id=567862) This is the only zypp history I could find All this installations history and log files will remain current as its my online PC this 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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c23 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|snwint@suse.com |aschnell@suse.com --- Comment #23 from Steffen Winterfeldt <snwint@suse.com> 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#c Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |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=829834 https://bugzilla.novell.com/show_bug.cgi?id=829834#c24 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #24 from Arvin Schnell <aschnell@suse.com> 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#c25 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|secure@aphofis.com | --- Comment #25 from Scott Couston <secure@aphofis.com> 2013-11-21 15:04:09 EST --- (In reply to comment #24)
Please give the exact message of the warning you are referring to in comment #21.
Its completely reproducible without the need to go through an installation. Just enter the partitioner and create the conditions as set out be the above details -- 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 <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |NORESPONSE --- Comment #26 from Arvin Schnell <aschnell@suse.com> 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#c27 --- Comment #27 from Scott Couston <secure@aphofis.com> 2013-11-28 04:37:57 EST --- Created an attachment (id=569384) --> (http://bugzilla.novell.com/attachment.cgi?id=569384) Image showing no seperate boot mount point Apologies for the late reply. Every year every hard disk on ever PC/Server on my LAN is formatted and recovered from backup. It reinforces the phrase 'you only backup in order to restore'. As you can see the screen pic here on this X_64 only has a / mount point and no warning will be given -- 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 <secure@aphofis.com> 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#c29 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NORESPONSE | --- Comment #29 from Scott Couston <secure@aphofis.com> 2013-11-28 04:44:15 EST --- If you need further clarification please ask -- 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 <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #30 from Arvin Schnell <aschnell@suse.com> 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#c31 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|secure@aphofis.com | --- Comment #31 from Scott Couston <secure@aphofis.com> 2013-11-28 10:55:54 EST --- Are you saying you cannot reproduce the warning message by going into the partitioner and proceeding as I have detailed. The partitioner will not execute untill you dismiss the warning as described above...Advise -- 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 <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #32 from Arvin Schnell <aschnell@suse.com> 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#c33 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | AssignedTo|aschnell@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #33 from Scott Couston <secure@aphofis.com> 2013-11-29 08:35:54 EST --- Bug 806490 doesnt specify hardware nor O/S version hardware is being used and that in itself is hugely vague. However it perfectly support the logic here!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Its not quite a dupe. 806490 refers to a live install...where I am referring to the actual reason the restart fails in the install much the same. The reason the install fails on the first boot is very well documented above. Its a consequence the failing of the partitioner under the conditions above. I spend 2 days trashing install after install to provide logs and come to the accurate conclusion of why the first boot part of install fails and its simply the partitioner in Yast. You dont need to do an install or go trolling through code to find error levels. Find an X_64 PC and do 2 tests. 1. Propose a partition of only /, /home, SWAP and commit. 2. Propose a partition setup of /boot, /, SWAP and commit. Then the error response will clearly show you why during install, and when a user has proposed a HDD partition condition if fails to reboot down at the end of online update. If your using automated installations to test with then stoop it right now as you get to see what possible failures which are suppressed during automated install when it just falls over. 100% Reproducible bugs are gold mines as you can see what happens on your own tube and validate the above. I cannot be more helpful I am sorry...you have a reproducible bug -- 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 <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |secure@aphofis.com --- Comment #34 from Jeff Mahoney <jeffm@suse.com> 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#c35 --- Comment #35 from Jeff Mahoney <jeffm@suse.com> 2013-11-28 20:22:03 EST --- Erp, comment #30. -- 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 <secure@aphofis.com> 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#c37 --- Comment #37 from Arvin Schnell <aschnell@suse.com> 2013-11-29 08:48:02 UTC --- I would recommend to test with 13.1 since EFI detection is broken in 12.3 (see bug #806490) from some media. -- 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 <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|secure@aphofis.com | Resolution| |FIXED --- Comment #38 from Scott Couston <secure@aphofis.com> 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#c39 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #39 from Scott Couston <secure@aphofis.com> 2013-12-03 13:52:37 EST --- Feel a bit uneasy with closing as fixed in 13.1. Not quite sure we resolved much in dialogue bug #806490 Please create test case
This means that we have basically two options: - introduce something that will take care of writing install.inf for the live CD - make partitioner (and possibly also bootloader) detect EFI a different way (Bootloader seems to check presence of /sys/firmware/efi directory)
Thomas, I'm sorry I cannot help more now...
I think its tell us we need a different way of detecting EFI on install. Currently a non-automated install where the user sets the whole partition table without any /boot partition; the partitioner is satisfied not to check and install continues I will leave this matter for discussion, however, using the preface that a user is always going to accept defaults and use an automated installs is a dangerous assumption and we should not go past beta of any version before testing a non-automated install with user intervention. -- 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 <secure@aphofis.com> 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 <secure@aphofis.com> 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#c41 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |aschnell@suse.com --- Comment #41 from Scott Couston <secure@aphofis.com> 2013-12-05 21:21:13 EST --- I'm have also tested for 13.1 and its the same...I believe we need to look at the #C39...Jiri at how we determine the BIOS. I did note in the 13.1 install error log there was an error: in obtaining CPU frequency in ACPI calls... -- 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 <secure@aphofis.com> 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#c43 --- Comment #43 from Scott Couston <secure@aphofis.com> 2013-12-06 10:08:47 EST --- The installation went through without any errors or problems when booting.For installation to propose a boot HDD because of its label is lunacy. If I had not overridden the auto proposed use of HDD the system would only have proposed /boot/eft FAT on sdb and did not want to utilise any of the other two HDD...Whats the disk label got anything to do with mount points when the default is to load HDD by disk ID...we have to fix up this wrong warning message. There are limited community repos available at the end on scan for community repos...Nvida is missing in a big way as well as mozilla, some of the extra KDE's...in short a great deal are missing and the ever present wrong url location for the banshee repo that’s been wrong since 12.1 and that bug was closed as wontfix. I still cant understand why when I did simply testing in both 12.3 and now 13.1 this error was not seen so I'm anxious to hear from Arvin -- 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 <secure@aphofis.com> 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#c45 --- Comment #45 from Scott Couston <secure@aphofis.com> 2013-12-23 13:07:26 EST --- Arvin Could you please provide needinfo asap -- 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 <secure@aphofis.com> 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#c47 --- Comment #47 from Scott Couston <secure@aphofis.com> 2014-01-01 16:45:02 EST --- 14-01-01 16:41:36 EST I am duplicating the experiment with 13.1 install and will be able to provide some more precise screen pics and any log data you need....As I'm not working over the holiday I have turned a production PC into a test vehicle...it also makes my own internal restore from backup work successfully as its tested every year like this...not too much of a wait now...but would appreciate needinfo reply -- 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 <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|aschnell@suse.com | Resolution| |FIXED --- Comment #48 from Scott Couston <secure@aphofis.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com