Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Curious Issue sysvinit systemd boot [SOLVED]

Help for Current Versions of MX
Message
Author
User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4264
Joined: Wed Jul 12, 2006 4:05 pm

Re: Curious Issue sysvinit systemd boot

#11 Post by timkb4cq » Wed Jul 04, 2018 7:02 pm

That could be a bad SATA cable, but I assume you've tried another when you switched drives.
It looks to me like a failing PSU, or failing regulators on the motherboard.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
Richard
Posts: 1823
Joined: Fri Dec 12, 2008 10:31 am

Re: Curious Issue sysvinit systemd boot

#12 Post by Richard » Wed Jul 04, 2018 7:06 pm

That is sad.
My condolences.
Best wishes for a speedy recovery.
MX17.1____: T430-2017, 8 GB RAM, 4.15.0-1-amd64, 119 SSD
antiX-/MX-171: AA1/Eee, 1 GB RAM, 4.15.0-1-686-pae, 149 HDD
DC9, LibO605, Dropbox, FF61, FFesr, mPDFed, Py3, CherryT, Vbox
linux counter #288562

User avatar
richb
Administrator
Posts: 16910
Joined: Wed Jul 12, 2006 2:17 pm

Re: Curious Issue sysvinit systemd boot

#13 Post by richb » Wed Jul 04, 2018 8:49 pm

timkb4cq wrote:
Wed Jul 04, 2018 7:02 pm
That could be a bad SATA cable, but I assume you've tried another when you switched drives.
It looks to me like a failing PSU, or failing regulators on the motherboard.

All three SSD's are permanently installed with their own cables. Looks like I go searching for a new motherboard, maybe start with the PSU.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4264
Joined: Wed Jul 12, 2006 4:05 pm

Re: Curious Issue sysvinit systemd boot

#14 Post by timkb4cq » Wed Jul 04, 2018 9:14 pm

PSU is more likely. Failing regulators, unless they have just let out the magic smoke, would likely have caused issues with high CPU loads or random usb port problems before getting to this point.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
handy
Forum Novice
Forum  Novice
Posts: 46
Joined: Mon Apr 23, 2018 2:00 pm

Re: Curious Issue sysvinit systemd boot

#15 Post by handy » Wed Jul 04, 2018 10:21 pm

@rickb, I'd turn off acpi just to see what happens.

My notebook has a bug in the BIOS. It has taken me sooooo long to realise that this is the case. It has always needed a second (& always successful) attempt to start win7. OpenBSD & Void had no problem, but the 3 Debian based (systemd free) distros do. They too need to be rebooted due to a very early kernel panic (mentions acpi too from memory - not that I think you have the same problem as mine rickb).

Anyway, on doing a little research, I found that it is known that this BIOS has a bug - all this time I had been just putting it down to the xxxxxxx OS's that MS builds (& I consider win7 to be the best of them). I have had to reinstall win7 once, fairly recently, & the behavior (bug) remained - I was hoping that I'd get rid of corruption or whatever had been causing the problem, no such luck. This was of course prior to my realising it was a BIOS bug.

I lived with this bug for years, (I just treat it the same as arthritis...) so I'll see how long it takes me to get my act together & flash the BIOS with an upgrade...
Clevo N'book (2014): P150SM-A
CPU: i7-4810MQ (Haswell) Speed: 2800/3800 MHz
RAM: 16 GiB 1600 MHz DDR3
GPU-1: i915
GPU-2: NVIDIA GK104M [GeForce GTX 880M] vRAM: 8GB 2500 Mhz DDR5
Storage: TOSHIBA 931.51 GiB. HGST 931.51 GiB. Crucial 223.57 GiB (M.2 SSD)

User avatar
HessenZone
Forum Novice
Forum  Novice
Posts: 81
Joined: Wed Jun 27, 2018 11:17 am

Re: Curious Issue sysvinit systemd boot

#16 Post by HessenZone » Thu Jul 05, 2018 2:17 am

Looks like potentially a hard disk related error to me ...
https://ubuntuforums.org/showthread.php?t=2272486

More useful info. from Fedora forum ...
https://forums.fedoraforum.org/showthre ... re-problem

Last but certainly not least ...
https://superuser.com/questions/1166750 ... d-shutdown
.

MX Linux Rocks, in America, in Europa, in Australien, einfach ÜBERALL. :linuxlove:

User avatar
richb
Administrator
Posts: 16910
Joined: Wed Jul 12, 2006 2:17 pm

Re: Curious Issue sysvinit systemd boot

#17 Post by richb » Thu Jul 05, 2018 5:33 am

I have noticed a clicking every second or so as the error block repeats. One would think HD but I have SSD's.
Doubt that all 3 SSD's went bad at the same time.

EDIT: Just recalled there is an HD in a caddy that I do not boot from. and rarely use. I removed it and the problem is resolved. Thanks for all the comments.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

User avatar
oops
Forum Regular
Forum Regular
Posts: 206
Joined: Tue Apr 10, 2018 5:07 pm

Re: Curious Issue sysvinit systemd boot

#18 Post by oops » Thu Jul 05, 2018 7:10 am

richb wrote:
Thu Jul 05, 2018 5:33 am
...
EDIT: Just recalled there is an HD in a caddy that I do not boot from. and rarely use. I removed it and the problem is resolved. Thanks for all the comments.
Unbelievable .. So it was a Darwin issue, ssds do not like to share the same space with hdds ;)
$ inxi -S : System: Host:XEON Kernel: 4.16.0-xeon-01.efi x86_64 bits: 64 Desktop: Xfce 4.12.3 - Distro: MX-17.1_x64 Horizon


User avatar
richb
Administrator
Posts: 16910
Joined: Wed Jul 12, 2006 2:17 pm

Re: Curious Issue sysvinit systemd boot

#19 Post by richb » Thu Jul 05, 2018 7:20 am

oops wrote:
Thu Jul 05, 2018 7:10 am
richb wrote:
Thu Jul 05, 2018 5:33 am
...
EDIT: Just recalled there is an HD in a caddy that I do not boot from. and rarely use. I removed it and the problem is resolved. Thanks for all the comments.
Unbelievable .. So it was a Darwin issue, ssds do not like to share the same space with hdds ;)
Evolution. They coexisted for three years and then came to blows. Actually I just think the HD failed. Not sure why I rarely used it. and never boot from it .But I suppose being in the computer it still wound up on boot.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4264
Joined: Wed Jul 12, 2006 4:05 pm

Re: Curious Issue sysvinit systemd boot [SOLVED]

#20 Post by timkb4cq » Thu Jul 05, 2018 8:20 am

The system can't tell whether that drive is a boot drive or not until it can iterate it. Usually that won't make a boot fail, just delay it for a minute or two, but drive failures can have odd symptoms.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

Post Reply

Return to “MX Help”