Page 3 of 4
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Mon Apr 21, 2025 7:56 pm
by CharlesV
@samegold When you get to a command line, enter
startx
and do you get error messages there or does the GUI start ?
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Mon Apr 21, 2025 8:28 pm
by samegold
CharlesV wrote: Mon Apr 21, 2025 7:56 pm
@samegold When you get to a command line, enter
startx
and do you get error messages there or does the GUI start ?
no it doesnt.
i get this:
https://ibb.co/TMy5Qmws
so right now im concentrating on "unlocking" the homefolder of the broken install by accessing it from a different linux machine. i hope i can atleast save some data that way:
https://postimg.cc/MX5r96Bd
it shows 0bytes, even though its over 300GB. so i think i need to take ownership of my own home folder, which is not trivial. all that happened because i assigned a password for root in mx user manager...
internet access is there but its also impossible to install anything at that stage as it says disk is full, even though there is still 20gb left...
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Mon Apr 21, 2025 8:35 pm
by siamhie
samegold wrote: Sun Apr 20, 2025 6:27 am
i got locked out after a kernel change with mx package installer.
Let's try this. Do you still get a grub menu? If so, select Advanced Options and boot to the previous working kernel.
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Mon Apr 21, 2025 8:40 pm
by samegold
samegold wrote: Mon Apr 21, 2025 8:28 pm
CharlesV wrote: Mon Apr 21, 2025 7:56 pm
@samegold When you get to a command line, enter
startx
and do you get error messages there or does the GUI start ?
no it doesnt.
i get this:
https://ibb.co/TMy5Qmws
so right now im concentrating on "unlocking" the homefolder of the broken install by accessing it from a different linux machine. i hope i can atleast save some data that way:
https://postimg.cc/MX5r96Bd
it shows 0bytes, even though its over 300GB. so i think i need to take ownership of my own home folder, which is not trivial. all that happened because i assigned a password for root in mx user manager...
internet access is there but its also impossible to install anything at that stage as it says disk is full, even though there is still 20gb left...
file system is btfrs, if that matters.
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Mon Apr 21, 2025 8:52 pm
by samegold
i tried to select other kernel in grub ofcourse, i get something like:
modprobe fatal module vmmon not found in directory /lib/modules/*kernelversion*
failure: tlpsysstat failed.
filesystem is btfrs
i think it must be something about the root user not being configured in the autologin of KDE, as i had the first user configured as autologin.
but rightnow i just want to access the data in the locked homefolder, i dont care about the installation so much, i installed mx and other distros many times already , so i will do it again, no big deal.
timeshift also doesnt work.
edit: sorry for doublepost, you can delete the above post with the quotes.
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Mon Apr 21, 2025 10:03 pm
by siamhie
Post the QSI from the live USB drive. That will show how the partitions are set up.
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Tue Apr 22, 2025 2:09 am
by samegold
Code: Select all
Drives:
Local Storage: total: 1.36 TiB used: 1.05 TiB (77.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Force MP510 size: 447.13 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: ECFM12.3 temp: 34.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSDPR-CX400-512-G2 size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.5
scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
scheme: GPT
Partition:
ID-1: / raw-size: 400.39 GiB size: 393.03 GiB (98.16%) used: 312.95 GiB (79.6%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
its "ID-3: /dev/sdb"
so is it "normal" that a folder shows size/size on disk "0 B" in a file manager?
if i run "properties" on ALL folders on that disk i get "size 22GB", but the "free space is 21GB of 410GB".
so, im not a mathematician, but that seems like BS. theres obviously over 300GB missing, and thats the 300 something GB of the home folder.
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Tue Apr 22, 2025 8:00 am
by j2mcgreg
@samegold
I think that the fact that Linux uses GiB as a memory measurement unit rather than GB which is used by Microsoft and all the manufacturers may have confused you. Read this for a good explanation:
https://massive.io/file-transfer/gb-vs- ... ifference/
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Tue Apr 22, 2025 9:18 am
by siamhie
samegold wrote: Tue Apr 22, 2025 2:09 am
its "ID-3: /dev/sdb"
so is it "normal" that a folder shows size/size on disk "0 B" in a file manager?
What does this show in a terminal?
p.s. next time post the full QSI output and not a trimmed or edited version.
Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account
Posted: Tue Apr 22, 2025 11:26 am
by fehlix
samegold wrote: Sun Apr 20, 2025 6:27 am
the problem i think is with the root account which i didnt enable at install.so i had a system which doesnt require password for root account and uses first user as administrator/superuser. this worked quite well until i got locked out after a kernel change with mx package installer. i have still no idea why that happens but the internet says its quite common and timeshift saved the day. the issue is described here for fedora, but its the same thing:
Don't thing changing the password of the root-account is the cause of the issue.
I guess rather somehow is related to the first issue mentioned with the other thread, where you suddenly have been forced
to enter into "Maintanaince mode", which you couldn't do without a root password.
So giving blind advises without analyzing the cause of the issue may not help or maybe misleading.
Also note: Using the term "Home" folder is potentially misleading (and confusing) by it's own,
b/c you can call "/home" directory a "Home folder", but you can also call "/home/samegold" the Home folder f the user "samegold".
And note also the, "/home" directory is properly owned by root but readable by all users, in oder they have access to
the subfolders to find their "home". And further root's "Home folder is not under /home but is "/root".
And yes, trying to GUI-login or autologin as root may not work. KDE will probably not work under root-account.