DebianThis forum is for the discussion of Debian 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.
Hi all !
A minor incident, (progress bar not working anymore in bootsplash) led me to some awkward manipulations : I first wanted to reinstall all what goes along with bootsplash, and in particular sysv-rc-bootsplash. But since this package provides irreversibled patch on rc, I thought, well, lets reinstall this as well.... plus the dependencies.
Anyway, I ended up removing, to then reinstall, sysv-rc, sysvinit, modutils, sysv-rc, and sysv-rc-bootsplash (I think this last one is still on thought...). And I should have not messed with modutils, because now.... my debian doesn't boot anymore!!! I get this:
Code:
Target filesystem doesn't have /sbin/init
BusyBox v1.13 (Debian 1:1.1.3-3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
And of course, I'm not really sure about the meaning. Is there any way I could get the OS boot again, avoiding complete reinstallation of debian ?
Can I bring it back to life from a live CD; should I recompile the kernel to solve it all ? Any idea and help very welcome !!!
I suppose I don't. Grubs proposes initrd.img-2-6-18, which is failing,and a recovery mode one, I tried to boot on but fails as well. Booting from a gentoo live cd and mounting the filesystem, I 've reached /boot and found out that there was a initrd.img-2-6-18.bak. I presumed that this was the "recovery mode" one; still I've updated grub's menu.lst to boot on this last one, but same error. I do have a vmlinuz-2.6.17.1,in /boot, that appears in grub's menu.lst as well. I tried to boot on it, but then, nothing happens ! The screen remains black, and there isn't any hardware activity. It just hangs... As a matter of fact, when I check the menu.lst, the part related to 2.6.17.1 doesn't have the initrd flag.
The .bak is the previous initrd that is kept.
I took the asumption that your initrd was regenerated during your problematic update, but was it really?
If I remember well, the steps are:
kernel + initrd loaded
kernel goes to initrd by uncompression initrd to /dev/ram0, a ramdisk
a specific script from initrd is launched, modules are loaded, and the real / is mounted
pivot_root is used to switch from /dev/ram0 to real /
/sbin/init is executed
So you still seem to be in the initramfs, pivot_root seems to have been executed (we see no message of error)
but /sbin/init is not found like if / wasn't found
With your livecd, can you check if you really have /sbin/init?
Also check the file /etc/inittab which is what /sbin/init reads for executing.
Sorry I have no clear idea.
In busybox, try to do some commands like ls, mount,.. to see what could have gone wrong. Not easy..
You're right nx5000, it just is the same issue... But I've been a bit forward, and since /sbin/init seemed to be missing,I've copied it over from a ubuntu live cd, and I now get:
Then... my root's login and psswrd don't work of course. Should I get back to the same state before the copying of /sbin/init and try HappyTux solution ? I'm gonna do that and see what happens. If you feel inspired, go ahead, let me know, thanx again for your concern.
Well your user/password are not stored in /sbin/init so it should work. The (none) would mean that it was not able to mount a partition and then probably no /etc/passwd file is found.
Yes, use what HappyTux said, its much cleaner than getting "something" from Ubuntu.
You can still boot this broken debian by appending init=/bin/bash in grub menu.lst
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.