LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-17-2018, 12:56 AM   #1
aihaike
Member
 
Registered: Feb 2006
Location: Paris, France
Distribution: Slackware, CentOS
Posts: 270

Rep: Reputation: 20
Question Slack64-current doesn't start after update


Hey,

I recently updated my Slack64-current which updated starting scripts.
Now the system boots correctly, mounts disks, everything goes smoothly till it stops right after having started the OpenSSH SSH daemon.

I'm wondering whether someone else experienced this issue as well.
Also, I'm using ELILO v3.16 for booting (without prompting) and I'd like to know if there is a way to boot in single user or start in interactive mode.
If not, I think I'll have to boot from a USB stick in order to edit the booting scripts.
Actually, that'd be nice to know what part causes the issue.

Thanks.
 
Old 08-17-2018, 06:01 AM   #2
lougavulin
Member
 
Registered: Jul 2018
Distribution: Slackware,x86_64,current
Posts: 279

Rep: Reputation: 100Reputation: 100
It's been a while since I used it, so I'm not sure and I can not test now, but I recall that if hold shift key you stop lilo and to get access to prompt, tab key.

Then at prompt to start in single mode :
Code:
<Your entry name> 1
If this works, you should add in elilo config 1 sec as timeout and also an entry to boot in single mode.
 
1 members found this post helpful.
Old 08-17-2018, 07:59 AM   #3
twy
Member
 
Registered: Jun 2004
Distribution: Slackware64
Posts: 99

Rep: Reputation: Disabled
I use LILO, not ELILO, but the situation is probably similar. At the "ELILO boot:" prompt, I might try entering

linux rdinit=/bin/sh

This assumes that "linux" is the name of your kernel. The rdinit kernel parameter specifies the "root disk init" program. The root disk /init program is often a shell script that (1) loads any required modules for the real root device, (2) mounts the real root disk on /mnt, (3) switches root to make /mnt into /, (4) executes /sbin/init to start services and login terminals. Instead, using rdinit=/bin/sh, you can just run sh (command line shell) and run commands manually to see where there is a problem. If you are using an initial root disk (initrd), then sh will be running inside that init root disk environment. Otherwise, sh is running on your real root disk.

Once at the sh command line, you can attempt to look into your /init script (on initrd root) or into your /etc/rc.d/ files (on real root), and run commands or scripts manually as your init would have normally. You might spot the problem and fix it, then reboot. You might have to set PATH for commands to work, like:

export PATH=/bin:/sbin:/usr/bin:/usr/sbin

You could then reboot as:

sync; reboot

You can also first try booting in runlevel 1, as suggested already. But, that might not avoid the SSH problem (not sure if it loads in runlevel 1 or not). The rdinit=/bin/sh lets you get in before anything at all happens. It could be useful.
 
1 members found this post helpful.
Old 08-20-2018, 12:34 AM   #4
aihaike
Member
 
Registered: Feb 2006
Location: Paris, France
Distribution: Slackware, CentOS
Posts: 270

Original Poster
Rep: Reputation: 20
Thumbs up

Thank you guys for your useful replies.
Actually, I realized that I could connect to the machine from an other one.
Finlay, the problem came from a stuck nfs mount.
Thanks again.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Okular 0.14.3: why doesn't it start searching from the current page when said so. stf92 Linux - Software 1 01-21-2014 12:27 AM
Current Update, now can't start desktop??? heavyonion Slackware 9 06-18-2013 11:51 PM
[SOLVED] Slackware current x64 and KDE doesn't start? hsahin4 Slackware 6 02-02-2011 02:00 PM
Slack64-current - CTRL-ALT-BACKSPACE doesn't kill X GrapefruiTgirl Slackware 8 08-29-2009 09:32 AM
Current-Update:'libart_lgpl' causing X to not start BearClaw Slackware 1 09-11-2003 02:12 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:23 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration