Page 4 of 5
Re: systemd no longer starts; sysV still ok
Posted: Tue Jan 16, 2024 1:44 pm
by quackser
NVidia driver reinstall fixed KDE and I have a gui again! debconf-kde-helper was apparently installed during the driver install; may be no reason to worry about Debconf::FrontEnd::Qt.
Re: systemd no longer starts; sysV still ok
Posted: Tue Jan 16, 2024 2:52 pm
by Charlie Brown
quackser wrote: Tue Jan 16, 2024 1:44 pm... NVidia driver reinstall fixed KDE and I have a gui again!..
So nice to hear that :)
Re: systemd no longer starts; sysV still ok
Posted: Tue Jan 16, 2024 9:27 pm
by quackser
installed gparted on the main system, took another snapshot and made a new live USB (since the old one didn't have gparted).
Two things booting from the USB:
1) tlp lacks permission to run (message is: "tlp: permission denied")
2) nginx fails to start (eventual message: "startpar: service(s) returned failure: tlp nginx ... failed")
As a result it boots to CLI.
I go into /etc/X11, rename xorg.conf to xorg.conf.bak, run startx, voila! it comes up.
OOOPS! spoke too soon - it did come up, most of the way, and then locked up.
Re: systemd no longer starts; sysV still ok
Posted: Wed Jan 17, 2024 12:54 am
by quackser
so... I booted from the original live USB, the one I used to install the first time round.
I installed gparted on that, and ran "check" on the "production" partitions.
It had free block and free inode count errors on both; it corrected them. I ran it again, and they came up clean.
I also ordered a 500GB SATA SSD to replace that drive. When it comes in, I'll have to decide whether to start over completely with a fresh install of MX, or to clone the existing system with its warts and see what I've got.
I'm not crazy about either idea.
Re: systemd no longer starts; sysV still ok
Posted: Wed Jan 17, 2024 8:34 pm
by quackser
on the TLP issue:
i installed TLP and TLPUI from MXPI and used TLPUI to disable it, set the defaults to no-battery system. This is a desktop.
Now sysV boots without complaining of TLP issues, not so systemd, which still doesn't boot ...
I'm ready to put this on hold until the new SSD comes in.
When it does, I'm going to try the Live USB i created from a snapshot of the current system; if I can't get any satisfaction from that I'll start over from the distro ISO.
@Charlie Brown and @j2mcgreg, I will post here again in a few days when all that's done. Thank you for your help thus far.
Re: systemd no longer starts; sysV still ok
Posted: Wed Jan 17, 2024 10:19 pm
by dolphin_oracle
still would like to see the
for the system.
Re: systemd no longer starts; sysV still ok
Posted: Fri Jan 19, 2024 6:00 pm
by quackser
@dolphin_oracle sorry, I hadn't noted that request.
here it is:
/dev/sda2: LABEL="homeMX" UUID="818c3e6a-3a9f-488e-90c3-42703effa9b4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="71fe454e-02"
/dev/sda1: LABEL="rootMX23" UUID="842e9019-1296-4d64-89df-cb9db81f819f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="71fe454e-01"
all good?
Thanks.
btw, what does that info do for you/me?
Re: systemd no longer starts; sysV still ok
Posted: Fri Jan 19, 2024 6:18 pm
by dolphin_oracle
quackser wrote: Fri Jan 19, 2024 6:00 pm
@dolphin_oracle sorry, I hadn't noted that request.
here it is:
/dev/sda2: LABEL="homeMX" UUID="818c3e6a-3a9f-488e-90c3-42703effa9b4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="71fe454e-02"
/dev/sda1: LABEL="rootMX23" UUID="842e9019-1296-4d64-89df-cb9db81f819f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="71fe454e-01"
all good?
Thanks.
btw, what does that info do for you/me?
I was going to check it against the /etc/fstab posted to make sure everything was valid, but you said you did that already so all good.
Re: systemd no longer starts; sysV still ok
Posted: Sat Jan 20, 2024 9:34 am
by quackser
@dolphin_oracle I hadn't checked blkid directly against fstab; if i said i did that, I misspoke. what I should have said is that the fstab entries looked ok to me.
Right now, that is not the case: here's the current fstab, with the system running...
Code: Select all
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
#Entry for /dev/sdb1 :
UUID=842e9019-1296-4d64-89df-cb9db81f819f / ext4 noatime 1 1
#Entry for /dev/sda1 :
#UUID=A8D09F2AD09EFDAE /media/1TB1P1 ntfs-3g defaults,uid=1000,gid=100,dmask=0002,fmask=0113,utf8,x-gvfs-show 0 0
#Entry for /dev/sda2 :
#UUID=18A4C7E1E9F18119 /media/1TB1P2 ntfs-3g defaults,uid=1000,gid=100,dmask=0002,fmask=0113,utf8,x-gvfs-show 0 0
#Entry for /dev/sda4 :
#UUID=000000004F6DD9BD /media/1TB1P3 ntfs-3g defaults,uid=1000,gid=100,dmask=0002,fmask=0113,utf8,x-gvfs-show 0 0
#Entry for /dev/sda5 :
#UUID=000000009EDC07E6 /media/1TB1P4 ntfs-3g defaults,uid=1000,gid=100,dmask=0002,fmask=0113,utf8,x-gvfs-show 0 0
#Entry for /dev/sdb2 :
UUID=818c3e6a-3a9f-488e-90c3-42703effa9b4 /home ext4 noatime 1 0
/swap/swap swap swap defaults 0 0
I don't know how to interpret what I see.
Re: systemd no longer starts; sysV still ok
Posted: Sat Jan 20, 2024 9:37 am
by dolphin_oracle
looks ok now. didn't you say elsewhere you removed an old entry? I may have two threads confused.