On Sun, 2019-11-10 at 13:11 +0800, Ed Greshko wrote: > On 11/10/19 12:56 PM, sixpack13 wrote: > > okay, so we are both liars ! > > fine by me, "endowed" with that "competence" let's fix the OP pain > > ! > > :-) > > > > the priciest questions are (just to put AND remove in one step a > > topic on my list): > > - OP, do have multi-card readers in your box ? > > - do you or does fedora do "magic" mapping with them ? > > - are there still media's the that devices ? > > - maybe, a install dvd, still in the drive, which could prevent > > clean shutdown, somehow ? > > ( last Q. is NOT meant as an attack ...!!!) > > I really don't think any of that is relevant. > > Note the log the OP supplied. > > Nov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_STOP pid=1 > uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" > hostname=? addr=? termina> > Nov 08 19:14:18 localhost.localdomain systemd[1]: Stopped Monitoring > of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. > Nov 08 19:14:18 localhost.localdomain systemd[1]: lvm2- > monitor.service: Succeeded. > Nov 08 19:14:18 localhost.localdomain lvm[14772]: 3 logical volume(s) > in volume group "fedora_localhost-live" unmonitored > Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdf: open > failed: No medium found > > > The "Succeeded" and "Stopped Monitoring of LVM2" would indicate that > this phase > has completed. And, the log does have "Reached target Final Step" > > I feel Tom had the best suggestion at this point.... > > "If you turn off rhgb and quiet on the kernel boot line, > you can (usually) watch lots of messages on the console as > it tries to shutdown" Ok, some progress! I reconfigured the BIOS boot settings to pick the hard drive first, and not an EFI partition. Then I reinstalled Fedora 31 from scratch, updated it and installed the additional packages that I need, and restored home from backup. The machine now shuts down normally. It would appear that the problem is somehow related to booting an EFI partition. This machine is a kickass 2011-vintage Gateway machine, so it may have some kind of EFI shutdown bug. I use it for my daily driver because the i7 processor and motherboard is plenty quick enough and does not have most of the hardware bugs associated with the last n generations of intel design errors. Unfortunately, I cannot update the BIOS, as Gateway is no longer in business. So, I guess I will have to use a non-EFI boot for the forseeable future on this machine. As an aside, I also have 2 older Lenovo machines that boot Fedora 31 in EFI mode just fine. Thanks for helping me out everyone! _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
