[SOLVED] Slack64-current doesn't start after update
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.