systemd no longer starts; sysV still ok

Message

Charlie Brown · #41 Post by **Charlie Brown** » Sat Jan 20, 2024 10:19 am

dolphin_oracle wrote: Sat Jan 20, 2024 9:37 am... I may have two threads confused...

#42 Post by **quackser** » Sat Jan 20, 2024 10:47 am

dolphin_oracle wrote: Sat Jan 20, 2024 9:37 am 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 sda1 and sda2 are both ntfs.
How should I be seeing this?

Thanks.

[EDIT] and sdb1 and sdb2 are shown in fstab as sda1 and sda2 are shown in blkid... ?

#43 Post by **dolphin_oracle** » Sat Jan 20, 2024 10:52 am

the sdXY designations can change, which is why fstab uses UUID, which are unique identifiers.

#44 Post by **quackser** » Sat Jan 20, 2024 10:53 am

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.

#45 Post by **quackser** » Sat Jan 20, 2024 11:03 am

@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 Windows box.
I do see that they are commented out.

#46 Post by **dolphin_oracle** » Sat Jan 20, 2024 11:09 am

commented out means they will be ignored.

#47 Post by **quackser** » Sat Jan 20, 2024 1:08 pm

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.

#48 Post by **quackser** » Tue Jan 23, 2024 9:30 am

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 original install.
When it was done installing I used the KDE updater to install 311 updates, and I had some problems.
Started over again, and used MXPI to do the updates; no problems. 295 updates later I had a working system.
Another 33 updates and I still had a working system.
I installed nginx, got it going, got my website going, and everything is working - WITH systemd.
It still bugs me that I didn't discover a culprit. I have not yet installed the nvidia driver and I may not, but if I do, I'll snapshot and make a new live USB immediately ahead of that.
Thanks very much to @j2mcgreg , @Charlie Brown , and @dolphin_oracle for your patience and assistance.
The moral support was nice to have, and I learned a fair number of things in the process.

MX Linux Forum

systemd no longer starts; sysV still ok [Solved]

Re: systemd no longer starts; sysV still ok

Re: systemd no longer starts; sysV still ok

Re: systemd no longer starts; sysV still ok

Re: systemd no longer starts; sysV still ok

Re: systemd no longer starts; sysV still ok

Re: systemd no longer starts; sysV still ok

Re: systemd no longer starts; sysV still ok

Re: systemd no longer starts; sysV still ok [Solved]