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
richb
Administrator
Posts: 17490
Joined: Wed Jul 12, 2006 2:17 pm

Curious Issue sysvinit systemd boot [SOLVED]

#1 Post by richb » Wed Jul 04, 2018 4:05 pm

I have always booted sysvinit. After 14 days of uptime I had occasion to reboot and could not boot. An error message regarding acpi. (I will try to capture it on the next boot). However I successfully booted with systemd. I have made no conscious changes to the system except keeping up to date as updates were available. It happens with all ssd's that I have with MX installed. and kernels 4.15, 4.16 and 4.17 Curious.

Code: Select all

System:    Host: mxyola Kernel: 4.17.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3 
           Distro: MX-17.1_x64 Horizon March 5, 2018 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <root required> 
           Mobo: Gigabyte model: F2A68HM-H v: x.x serial: <root required> UEFI: American Megatrends v: FB 
           date: 04/22/2015 
CPU:       Topology: Quad Core model: AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G bits: 64 type: MCP 
           L2 cache: 2048 KiB 
           Speed: 1397 MHz min/max: 1400/3100 MHz Core speeds (MHz): 1: 1397 2: 1393 3: 1395 4: 1395 
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics] driver: amdgpu v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Gallium 0.4 on AMD KAVERI (DRM 3.25.0 / 4.17.0-1-amd64 LLVM 3.9.1) 
           v: 4.3 Mesa 13.0.6 
Audio:     Card-1: Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio driver: snd_hda_intel 
           Card-2: Advanced Micro Devices [AMD] FCH Azalia driver: snd_hda_intel 
           Sound Server: ALSA v: k4.17.0-1-amd64 
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: down mac: 40:8d:5c:0d:62:1b 
           Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k 
           IF: wlan0 state: up mac: 60:e3:27:08:b6:6c 
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:    HDD Total Size: 1.03 TiB used: 185.20 GiB (17.6%) 
           ID-1: /dev/sda vendor: Seagate model: ST3320820SCE size: 298.09 GiB 
           ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-4: /dev/sdd vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
           ID-5: /dev/sde type: USB vendor: SanDisk model: Extreme size: 58.43 GiB 
Partition: ID-1: / size: 23.91 GiB used: 15.85 GiB (66.3%) fs: ext4 dev: /dev/sdc3 
           ID-2: /home size: 26.54 GiB used: 2.90 GiB (10.9%) fs: ext4 dev: /dev/sdc2 
           ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc4 
Sensors:   System Temperatures: cpu: 35.0 C mobo: N/A gpu: amdgpu temp: 19 C 
           Fan Speeds (RPM): cpu: 2039 fan-2: 1021 fan-3: 965 fan-4: 0 fan-5: 0 gpu: amdgpu fan: 0 
Info:      Processes: 258 Uptime: 43m Memory: 14.69 GiB used: 2.09 GiB (14.2%) Shell: bash inxi: 3.0.10 
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: 4482
Joined: Wed Jul 12, 2006 4:05 pm

Re: Curious Issue sysvinit systemd boot

#2 Post by timkb4cq » Wed Jul 04, 2018 4:39 pm

I don't see any updates in my logs over that time period that should have caused something like that, except perhaps for libgcrypt20, but unless you encrypt a partition I can't see that preventing boot up.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

turtlebay777
Forum Regular
Forum Regular
Posts: 245
Joined: Sat Apr 14, 2018 2:40 pm

Re: Curious Issue sysvinit systemd boot

#3 Post by turtlebay777 » Wed Jul 04, 2018 5:11 pm

I'm so glad I insist on using systemd! Another good reason for using it over and above that Vokoscreen always crashes the computer when I usesysinit.
Must be why Vokoscreen always crashes Antix too.

User avatar
anticapitalista
Forum Veteran
Forum Veteran
Posts: 5828
Joined: Sat Jul 15, 2006 10:40 am

Re: Curious Issue sysvinit systemd boot

#4 Post by anticapitalista » Wed Jul 04, 2018 5:33 pm

turtlebay777 wrote:
Wed Jul 04, 2018 5:11 pm
I'm so glad I insist on using systemd! Another good reason for using it over and above that Vokoscreen always crashes the computer when I usesysinit.
Must be why Vokoscreen always crashes Antix too.
If Vokoscreen does crash on non-systemd distros, then that is a problem with Vokoscreen or how it is packaged in Debian.

https://packages.debian.org/stretch/vokoscreen

shows that there is no systemd dependency.
anticapitalista
Reg. linux user #395339.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX-17 "Heather Heyer" - lean and mean.
https://antixlinux.com

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

Re: Curious Issue sysvinit systemd boot

#5 Post by richb » Wed Jul 04, 2018 5:45 pm

timkb4cq wrote:
Wed Jul 04, 2018 4:39 pm
I don't see any updates in my logs over that time period that should have caused something like that, except perhaps for libgcrypt20, but unless you encrypt a partition I can't see that preventing boot up.
I checked logs also and did not see anything I would supect. I do not use encryption.
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
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10052
Joined: Sun Dec 16, 2007 1:17 pm

Re: Curious Issue sysvinit systemd boot

#6 Post by dolphin_oracle » Wed Jul 04, 2018 5:57 pm

speculation without the actual error is not going to get us anywhere.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

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

Re: Curious Issue sysvinit systemd boot

#7 Post by Richard » Wed Jul 04, 2018 6:09 pm

Probably because Vokoscreen is hardwired for systemd only.
MX18b1: Lenovo T430: Intel Ivy Bridge i5-3320M, 8GB RAM, 4.9.0-8-amd64, 119 GB SSD
MX18b1: Eee&AA1 NBs: Dual Core Atom N270, 1GB RAM, 4.9.0-8-686, 150 GB HDD
DoubleCmd/Thunar, LibO613, Dropbox, Vivaldi/Firefox, CherryTree, Vbox. LinuxCounter #208633

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

Re: Curious Issue sysvinit systemd boot

#8 Post by richb » Wed Jul 04, 2018 6:24 pm

False positive with systemd boot being successful. Subsequent trials after the first success yield the same error message.I am assuming it is a hardware failure.Image a bit fuzzy but readable.
(I am on my laptop now)
You do not have the required permissions to view the files attached to this post.
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

turtlebay777
Forum Regular
Forum Regular
Posts: 245
Joined: Sat Apr 14, 2018 2:40 pm

Re: Curious Issue sysvinit systemd boot

#9 Post by turtlebay777 » Wed Jul 04, 2018 6:40 pm

Just thinking 'outside the box', can you (Richb) discount the possibility of a virus or other malware which might have been somehow injected into your sysint? Is it possible to replace the sysinit with a fresh copy?
Is it worth suggesting to an expert like yourself, that which would be suggested to a newbie, ie to run up a live version of MX which would test if it's a hardware fault or a system fault?

(Sorry if these suggestions are too basic, I'm only trying to help!)

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

Re: Curious Issue sysvinit systemd boot

#10 Post by richb » Wed Jul 04, 2018 6:55 pm

I have three SSD's in the computer with different versions of MX. all fail to 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

Post Reply

Return to “MX Help”