Hi, I have installed debian on my new MSI Cyborg 14. Installation went smooth without any error or issues. However after installing and booting, the boot goes into a loop of starting and killing JournalD.
Following is the error occored:Not sure what the error messages would mean. Any help is appreciated.
Following is the error occored:
Code:
[2710.826727) systemd[2710.826732] systemd[1]: systemd-journald.service: Found left-over process 773 (systemd-Journal) in control group while starting unit. Ignoring. [2710.826733] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. .[ 2710.826738] systemd[1]: systemd-journald.service: Found left-over process 775 (systemd-Journal) in control group while starting unit. Ignoring 2710.826739] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.[ See 'systemctl status systemd-journald.service' for details.[OK] Stopped systemd-Journald.service Journal Service.[2710.854773] systemd[1]: Starting systemd-Journald.service Journal Service...Starting systemd-Journald.service Journal Service...[2718.873832] systemd-journald [777]: File /run/log/Journal/bbfc4ef375824985965189cd656b1084/system. Journal corrupted or uncleanly shut down, renaming and replacing.[] Job systemd-Journald.service/start running (imin 29s/1min 30s)1 Job systemd-journald.service/start running (3min / 3min)2891.314702] systemd[1]: systemd-Journald.service: State 'stop-sigterm' timed out. Killing. 2891.318096) systemd[1]:systemd-Journald.service: Killing process 777 (systemd-journal) with signal SIGKILL. 2891.320961] systemd[1]: systemd-journald.service: Killing process 379 (systemd-Journal) with signal SIGKILL.2891.321598] systemd[1]: systemd-Journald.service: Killing process 768 (systemd-Journal) with signal SIGKILL.2891.322230] systemd[1]: systemd-journald.service: Killing process 769 (systemd-Journal) with signal SIGKILL.[ 2891.322921] systemd[1]: systemd-journald.service: Killing process 770 (systemd-journal) with signal SIGKILL.2891.323532] systemd[1]: systemd-journald.service: Killing process 773 (systemd-Journal) with signal SIGKILL.1 Job systemd-journald.service/start running (4min 30s / 4min 30s) 1 Job systemd-journald.service/start running (6min/6min)[3071.814709] systemd[1]: systemd-journald.service: State 'final-sigterm' timed out. Killing.[3071.818040] systemd[1]: systemd-journald.service: Killing process 777 (systemd-journal) with signal SIGKILL. [3071.821044] systemd[1]: systemd-journald.service: Killing process 379 (systemd-journal) with signal SIGKILL.[3071.821657] systemd[1]: systemd-journald.service: Killing process 768 (systemd-Journal) with signal SIGKILL.[3071.822266] systemd[1]: systemd-journald.service: Killing process 769 (systemd-Journal) with signal SIGKILL.[3871.822861] systemd[1]: systemd-journald.service: Killing process 778 (systemd-Journal) with signal SIGKILL.3071.829451] systemd[1]: systemd-journald.service: Killing process 773 (systemd-Journal) with signal SIGKILL.[x] Job systemd-Journald.service/start running (7min 30s / 7min 30s)3162.064698) systemd[1]: systemd-journald.service: Processes still around after final SIGKILL. Entering failed mode.[3162.068101] systemd[1]: systemd-journald.service: Failed with result 'timeout'[3162.071689] systemd[1]: systemd-journald.service: Unit process 379 (systemd-Journal) remains running after unit stopped.3162.072522] systemd[1]: systemd-journald.service: Unit process 768 (systemd-journal) remains running after unit stopped.[3162.073527] systemd[1]: systemd-journald.service: Unit process 769 (systemd-Journal) remains running after unit stopped. 3162.077201] systemd[1]: systemd-journald.service: Unit process 770 (systemd-journal) remains running after unit stopped. [[ 3162.088542] systemd[1]: systemd-Journald.service: Unit process 773 (systemd-journal) remains running after unit stopped.[3162.083472] systemd[1]: systemd-Journald.service: Unit process 775 (systemd-Journal) remains running after unit stopped.[ [FAILED] Falled to start systemd-journald.service Journal Service. status systemd-journald.service for details.3162.086100) systemd[1]: systemd-journald.service: Unit process 777 (systemd-journal) remains running after unit stopped.See 'systemctl 3162.092646] systemd[1]: systemd-journald.service: Scheduled restart Job, restart counter is at 7.[3162.092842] systemd[1]: Stopped systemd-Journald.serviceJournal Service.OKJ Stopped systemd-journald.service Journal Service.[ 3162.098178] systemd[1]: systemd-journald.service: Found left-over process 379 (systemd-journal) in control group while starting unit. Ignoring.3162.098190] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [[3162.098226] systemd[1]: systemd-Journald.service: Found left-over process 768 (systemd-Journal) in control group while starting unit. Ignoring. [3162.098232] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.[ 3162.098294 ] systemd[1]: systemd-journald.service: Found left-over process 769 (systemd-journal) in control group while starting unit. Ignoring.[ 3162.098299] systemd[1]: This usually indicates unclean termination of a previous run, or service Implementation deficiencies.3162.098327] systemd[1]: systemd-Journald.service: Found left-over process 778 (systemd-Journal) in control group while starting unit. Ignoring. 3162,098333] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.[3162.0983611 systemd[1]: systemd-journald.service: Found left-over process 773 (systemd-Journal) in control group while starting unit. Ignoring. [ 3162.098367] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.[ 3162.098398) systemd[1]: systemd-journald.service: Found left-over process 775 (systemd-journal) in control group while starting unit. Ignoring. 3162.098483) systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.[3162.098441] systemd[1]: systemd-Journald.service: Found left-over process 777 (systemd-journal) in control group while starting unit. Ignoring. 3162.098446] systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. [[ 3162.126686] systemd[1]: Starting systemd-Journald.service Journal service... Starting systemd-Journald.service Journal Service...3162.137764] systemd-Journald [779]: File /run/log/Journal/bbfc4ef375a249e5965189cd656b1084/system. Journal corrupted or uncleanly shut down, renaming and replacing. 1 Job systemd-Journald.service/start running (imin 295/1min 30s)Job systemd-Journald.service/start running (2min 2s / 3min)
Statistics: Posted by janakad — 2025-03-01 15:45 — Replies 2 — Views 137