This seems to be recreateable as I've seen it on three different Juno IOC-L systems when installing Fedora16. Downloaded and burned the following ISO dated 24-Oct-2011 19:28 http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/16-Alpha/Fedora/ppc64/iso/Fedora-16-ppc64-DVD.iso # The image checksum(s) are generated with sha256sum. cf93e1deb37cec183c0f4f038ee00afbaa6d1f569307af89cf2ab33776ccfe7e *Fedora-16-ppc64-DVD.iso a3b5d2f6d485a129f63f4c04159e55d29fabe9a2a3e8bf36993e63e9f99e67e8 *Fedora-16-ppc64-netinst.iso Installed onto three Juno IOC-L systems and neither system rebooted after Fedora16 install completed. At the end of the install I got the normal "REBOOT" button in the lower right hand corner but the system didn't reboot. The console showed these lines but the partition never rebooted even after more than an hour of waiting. Sending SIGTERM to remaining processes... NetworkManager[1166]: <info> (eth1): now unmanaged NetworkManager[1166]: <info> (eth1): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] NetworkManager[1166]: <info> (eth1): cleaning up... NetworkManager[1166]: <info> (eth1): taking down device. NetworkManager[1166]: <info> (eth2): now unmanaged NetworkManager[1166]: <info> (eth2): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] NetworkManager[1166]: <info> (eth2): cleaning up... NetworkManager[1166]: <info> (eth2): taking down device. NetworkManager[1166]: <info> (eth3): now unmanaged NetworkManager[1166]: <info> (eth3): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] NetworkManager[1166]: <info> (eth3): cleaning up... NetworkManager[1166]: <info> (eth3): taking down device. NetworkManager[1166]: <info> (eth4): now unmanaged NetworkManager[1166]: <info> (eth4): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] NetworkManager[1166]: <info> (eth4): cleaning up... NetworkManager[1166]: <info> (eth4): taking down device. NetworkManager[1166]: <info> (eth5): now unmanaged NetworkManager[1166]: <info> (eth5): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36] NetworkManager[1166]: <info> (eth5): cleaning up... NetworkManager[1166]: <info> (eth5): taking down device. NetworkManager[1166]: <info> exiting (success) Sending SIGKILL to remaining processes... Unmounting file systems. Unmounted /mnt/sysimage/sys/fs/selinux. Unmounted /mnt/sysimage/sys. Unmounted /mnt/sysimage/proc/bus/usb. Unmounted /mnt/sysimage/proc. Unmounted /mnt/sysimage/home. Unmounted /mnt/sysimage/dev/shm. Unmounted /mnt/sysimage/dev/pts. Unmounted /mnt/sysimage/dev. Unmounted /mnt/sysimage/boot. Unmounted /mnt/sysimage. Unmounted /mnt/install/source. Unmounted /dev/hugepages. Unmounted /sys/kernel/debug. Unmounted /sys/kernel/security. Unmounted /dev/mqueue. The DVD was ejected but the system doesn't reboot. I checked PHYP and see that the partition has NOT rebooted. Linux ppc64 03500000 10/26/2011 23:52:45 #1 SMP Wed Oct 12 22:41:01 UTC 2011 LPAR IPL IPL Sys IPL System Sys Operating Id Name Mode Keylock Reason State Action Reference Code Attn System ----- ---------- ------ -------- --------- ---------- -------- -------------------- ---- ---------- 1 JI-20005 Normal Normal Normal On IPL Linux ppc64 Off RPA As shown the partition ref code and date stamp shows it hasn't changed since starting the installation. I am able to force a reboot of the partition using phyp command "vsp -id 1 -func 3" and this then lets me boot up on the newly install Fedora16. I never had this problem until using the new Alpha Fedora16. Here is the anaconda console showing the time the install started Running anaconda 16.21, the Fedora system installer - please wait. 23:58:05 Starting VNC... 23:58:09 The VNC server is now running. 23:58:09 WARNING!!! VNC server running with NO PASSWORD! You can use the vncpassword=<password> boot option if you would like to secure the server. 23:58:09 Please manually connect your vnc client to pfdioc03b.austin.ibm.com:1 (9.3.181.188) to begin the install. 23:58:09 Starting graphical installation. Press <enter> for a shell ERROR: modinfo: could not open /lib/modules/3.1.0-0.rc9.git0.2.fc16.kh.ppc64/kernel/fs/nls/nls_utf8.ko: No such file or directory Fedora16 installation settings I used. boot: linux serial vnc debug English English Chicago Time Zone Use All Space for hdisk/partitioning Minimal install Customize now picking Base System -> Base & System Tools I'm attaching the contents of /tmp after the Fedora16 install completed but before clicking the reboot button. Another person also observed this on a 8231-E2B, also with a vnc install, but noted that is succeeds when using VIOS and a virtual CD. There are *many* sr0 errors in the syslog. I'm not sure that this is an anaconda issue, but that seems like the best starting point.
Created attachment 530510 [details] contents of /tmp from anaconda install
On a PowerMac G5: * the display entered power-saving mode * the DVD was ejected * no reboot occurred I didn't have another console to see any kernel or anaconda messages.
Did you run media check and verify this installation media before continuing? All those sr0 errors are indicative of a read problem, which can manifest itself in many ways.
I can't speak for the original reporter, but yes, I ran a media check on my G5 before experiencing this problem.
------- Comment From dlshaw.com 2011-11-02 11:04 EDT------- (In reply to comment #6) > Did you run media check and verify this installation media before continuing? > All those sr0 errors are indicative of a read problem, which can manifest > itself in many ways. I did NOT run a media check. Next time I install I will do so and comment here. Currently I don't have any plans to install Fedora16 on another system though so not sure when that will be.
Hm, anaconda doesn't control the unmounting of filesystems and rebooting anymore. We just call out to systemctl to do the rebooting so the output you're seeing now is occurring after anaconda has been terminated. Reassigning to systemd so they can check if there are known ppc rebooting problems. I suppose it's possible we need to do something different, in which case this report can just get assigned back.
(In reply to comment #0) ... > Unmounted /dev/hugepages. > Unmounted /sys/kernel/debug. > Unmounted /sys/kernel/security. > Unmounted /dev/mqueue. Looks like a hang at a similar point as in bug 752593.
Can this be retested with latest rawhide iso's which included the latest version of anaconda and systemd to see if this is still an issue? Thanks
I'm sorry, this system is inconvenient to reinstall, so I can't do it just on the off-hand chance that something might have changed. On the other hand, if you can give me a systemd package version in which you think this problem has been resolved, I'd be happy to verify that.
If regular reboot just works normally and has worked since install time then it's the installer. ( Anaconda uses it's own systemd target which it boots into )
Just adding here for reference two bugs that might be related bug 756767 and bug 753339
Oops, I was responding to the wrong bug in comment 9. Sorry, carry on.
------- Comment From clnperez.com 2012-06-22 19:32 EDT------- Closing on our end as we haven't been able to find time to get back to this, and FC 17 for Power just GA'd.
OK. Closing.