Immediate problem: boot fails every 2-3 seconds and recycles. Hardware: 8-core Intel Core I7-7700K, 32Gb RAM, SSD boot disk plus half a dozen others. GeForce GTX1080Ti graphics. Upgraded M6 with M7 x86_64 beta3 went well and was current. Started behaving badly, mostly due to ran out of disk space, but in context I was concerned re virus etc and did RC re-install. Used existing partitions, formatted install partition. Was OK for 2-3 days Seemed to 'go bad' over couple of days. opencpn which had been working normally came up with greyed-out screen. Was nouveau; attempts to install proprietary Nvidia driver failed after partial download (never seen that before. Fast cable so that's not the issue). Now boot attempts cycling every 3 sec or so. Only able to use system now after advanced options boot to root recovery prompt, then init 5 brings up graphical session - but falls over again after power-down. I'll attach output of journalctl -r in compressed format once bug established.
Created attachment 11118 [details] ouput of journalctl -r
Whiteboard: (none) => 7RC
(In reply to Tony Blackwell from comment #1) > Created attachment 11118 [details] > ouput of journalctl -r Can you try disabling the Xorg / gdm service? See https://duckduckgo.com/?q=gdm+systemd&atb=v140-1&ia=web . It seems to fail there.
CC: (none) => shlomif
disabling gdm and enabling sddm instead does not change the behaviour; boot still fails and startup cycles every 2-3 seconds. Tony
Can we take it that the M7 system is up-to-date? If I understand your description correctly, if you boot 'rescue' and then 'init 5', that session works OK; and it is the *next* normal re-boot that fails. I was confused by the number of sessions the journal contained, and what they represented. I wonder whether, the re-boot fault occuring rapidly, you could then re-boot rescue as you describe, and once that session flies, save the journal file. It is possible to time-limit it e.g. to today. The -r does not help. This might enable comparison between the failing boot and one that (via rescue) works. Despite the earlier download problem, can you try the proprietary nVidia driver in case that alters things?
CC: (none) => lewyssmith
If the boot is failing after 2-3 seconds, I doubt the journal is helping us - the boot will still be running off the initrd, so nothing will be saved on disk. A system going bad over a couple of days makes me immediately suspect a hardware problem. Have you tried running smartctl to check your disks are healthy?
CC: (none) => mageia
Martin: I take your point. Some of the issue was the system running out of disk space, and I wonder if some corruption as a result. Disks are healthy. Lewis, I absolutely appreciate your time and effort going through the journal - yes, I found it hard to track as well. Appreciate your suggestions as to how to narrow it down. This being my main system, I've decided to go to a clean install of released M7 x86_64, and after some days all is well. So, I've got over the problem without a satisfying explanation, but very grateful for the support and ideas from you both. Marking as resolved. My thanks Tony
Status: NEW => RESOLVEDWhiteboard: 7RC => 7Resolution: (none) => WORKSFORME