[SOLVED] can't access tty; job control turned off /# _
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.
... mount:mounting /dev sda5 on /mnt failed:No such device ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead. You can try to fix it. type 'exit' when things are done.
/bin/sh: can't access tty; job control turned off /# _
I can't see that I can type a single letter
but I can boot in huge recovery mode (5.15.27 x86_64 (tty1)
has somebody an advise for me how to handle with this issue?
Thanx
Last edited by slacnovitz; 03-26-2022 at 04:05 AM.
Reason: more info
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 462
Rep:
Quote:
Originally Posted by slacnovitz
would I have to consider something in advance?
well when I was supposed to do this init.gz manually, than obviously not...
was this a point in the Beginners guide?
I can't remember exactly what document it's in off the top of my head.
The good news is, it's a fairly straightforward fix. Go ahead and boot with the huge kernel. Then, run $(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r /boot/vmlinuz-generic) as root. This will make a new initrd for 5.15.27 at /boot/initrd.gz.
It's possible to customize initrd further (the mkinitrd_command_generator man page is a good resource for that), but that'll get you up and running for the time being.
And now I can't any longer restart the normal way:
when I klick [Log Out) the options [Restart] and [Shut Down]are greyed.
When I press [Log Out] there is a promt :
You installed the system from a dvd or a usb stick? Use it to boot. You get a message telling:
Code:
...
In a pinch, you can boot your system from here with a command like:
boot: huge.s root=/dev/sda1 initrd= ro
In the example above, /dev/sda1 is the / Linux partition.
...
You don't need 'huge.s root=/dev/sda5 initrd= ro'. It's not a command but it's something you can give as a kernel command line if you have to boot the install usb.
Quote:
Originally Posted by slacnovitz
can I run
/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.27 | bash
in my normal terminal?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.