MX Linux Forum

thanks. Just saw this, had the same issue, no more of this problem.

I'm going to close this.
I don't think it had anything to do with the HDD. I took a snapshot of the system, make a Live USB, booted from that and used it to install on a brand new SSD. Same issues, exactly the same.
I started over, installed from the MX-Linux / KDE live stick that I'd used for the ...

Ok.
Well, systemd still won't start, I have a new SSD coming in today I think, will see if installation from a snapshot/live USB of this system works any better on it - though I don't see why it would improve anything to install an image of a broken system. I'll post an update when I have one.

dolphin_oracle is there any issue with the ntfs entries in fstab? I see no way to mount those; they're probably obsolete but I don't want to eliminate them arbitrarily. I think they might be left over from the creation of the live USB I used to install this system; that USB was generated on a ...

dolphin_oracle wrote: Sat Jan 20, 2024 10:52 am the sdXY designations can change, which is why fstab uses UUID, which are unique identifiers.

oh ok thanks.

looks ok now. didn't you say elsewhere you removed an old entry? I may have two threads confused.


I don't think I said I edited fstab, and at any rate don't remember doing so.

I don't understand what I'm seeing in there bec sda1 is ext4 root and sda2 is ext4 home, and what I see looks like ...

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...

# /etc/fstab: static file system information ...

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 ...

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 ...

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 ...