Bug#637481: /init: /init: 318: cannot open /root/dev/console: No such file
On Thu, Aug 11, 2011 at 10:37:16PM +, auto38092...@hushmail.com wrote: In addition to Petter's comments, I'd just like to add that: /init: /init: 223: [: not found /init: /init: 223: sh: not found /init: /init: 239: umount: not found /init: /init: 242: mount: not found /init: /init: 273: [: not found /init: /init: 318: cannot open /root/dev/console: No such file Note that /init is a part of the initramfs. And that '[', 'sh', 'mount' and 'umount' are all provided by busybox by default in the initramfs. This is just a shell script you can look at--you can unpack the initrd by hand if you want to inspect it. Note that you could, as documented in initramfs-tools(8), use the break=(top|bottom|init|...) to run a shell in the initramfs environment. This will allow you to look at what's wrong, e.g. are the programs/symlinks actually present? As Petter suggested, run update-initramfs to ensure it's up-to-date, and ensure that your system, busybox and initramfs-tools in particular, are definitely the correct current versions before doing it. WRT your comment about IRC, I don't have the time to do that, and I also can't be sure to reply in 24 hours--we're all volunteers here, and this is not paid technical support. Note that mail is archived and so others who may have the same problem will benefit from that where they would not with IRC. It also requires us to be available at the same time, and since Debian is a global project, that's often difficult. In consequence, IRC is not an efficient use of time since the same issue might need to be dealt with more than once with different people, and it's not amenable for others to participate, unlike public bug reports, which are a resource available to all, and preserve a historical record which will be useful for years to come. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#637481: /init: /init: 318: cannot open /root/dev/console: No such file
I have the same issue! I have a debian testing box, which started complaining when apt-get dist-upgrade installed the 2.6.38 kernel (2.6.32 worked fine) a few weeks (months?) ago. I just set grub's default to the earlier kernel, which worked fine. Yesterday I ran apt-get dist-upgrade again, and a 3.x kernel was installed. This morning, the box crashed on boot, with the same error. So I manually selected the oldest kernel in grub, and ran update-initramfs and update-grub to see if that would fix the problem. Unfortunately, now even the 2.6.32 doesn't boot anymore! Unfortunately, I can't create a boot CD, and the box can't boot from USB, and the grub shell (is that busybox?) has no edit functionality it seems, so I'm kinda stuck! Regards, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637481: /init: /init: 318: cannot open /root/dev/console: No such file
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: sysvinit Version: 2.88dsf-13.11 Thank you very much for maintaining Debian's crucially important sysvinit package. You'll know better than I, but it seems to me that I may have stumbled upon a bug in it. I upgraded from version 2.86.ds1-60 to 2.88dsf-13.11 and booted, and soon after the bootloader (grub) ran, I was greeted with the following messages, which I dutifully copied by hand for your edification and amusement. (Hopefully the web based email editor that I'm using won't wrap them...) /init: /init: 223: [: not found /init: /init: 223: sh: not found /init: /init: 223: [: not found /init: /init: 223: [: not found /init: /init: 224: [: not found /init: /init: 239: [: not found /init: /init: 239: [: not found /init: /init: 239: [: not found /init: /init: 239: [: not found /init: /init: 239: umount: not found /init: /init: 242: mount: not found /init: /init: 243: mount: not found /init: /init: 273: [: not found /init: /init: 291: [: not found /init: /init: 293: [: not found /init: /init: 318: cannot open /root/dev/console: No such file [1.103189] Kernelpanic - not syncing: Attempted to kill init! [1.103253] Pid: 1, comm: init Not tainted 3.0.0-1-686-pae #1 [1.103313] Call Trace: [1.103377] [c12ac14e] ? panic+0x4d/0x141 [1.103439] [c1038ed8] ? do_exit+0x8f/0x633 [1.103499] [c11bfa25] ? tty_write+0x1db/0x1db [1.103559] [c1039671] ? do_group_exit+0x11/0x14 [1.103619] [c10396a5] ? sys_exit_group+0x11/0x14 [1.103682] [c12b221f] ? sysenter_do_call+0x12/0x28 Others and I suspected that upgrading all packages to their latest versions in the unstable distribution might solve the problem, and I did a dist-upgrade. Unfortunately, the problem persisted. I can wait for maybe twenty four hours for your wise questions and informed suggestions. After that, I need to try to restore the system from a backup. As you know, that'll make it harder to debug this. Maybe the fastest way to coordinate would be through IRC on freenode's #debian channel. So, that's what I think I know about it. Thanks again for your time and attention maintaining such an important package, Kingsley -BEGIN PGP SIGNATURE- Charset: UTF8 Version: Hush 3.0 Note: This signature can be verified at https://www.hushtools.com/verify wsBcBAEBAgAGBQJORFmcAAoJEJcphLrL8UMTnyoH/0aMxvT8xBYTLWujTeFAhZh4oiAL TB+EwDISCTpgFJACI7Rg1/EIwKTUsrF7Wnig2HG/wJfl+P/s3x4BoUQn/heoxAcNP6MO RHPnrTyFmWVFmjNZnSidGkBY0J8DhF8dn2cs/kJjos0O/kIu/3qGfWIyBdmQcd4x8Fw3 /9MepER4KzN6cGPSJkqqXWMPaz34176kCDDzuGBZGWSPAlMuCqwEQMhw7WmYVvicObfd muzUhChNqhApbmm8j8jGIDBOA7ubkqXBS4tPp3cLqvEbuUW2FfpzGpXk8r678F7tozPa 6zzFwpOdkLxeJLMKaooESX7epZDIX2lfb1R5371kRAo= =mxio -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637481: /init: /init: 318: cannot open /root/dev/console: No such file
I upgraded from version 2.86.ds1-60 to 2.88dsf-13.11 and booted, and soon after the bootloader (grub) ran, I was greeted with the following messages, This upgrade had a very long jump in the version numbers of sysvinit. Which verision of Debian did you start with and which did you upgrade to? The messages you included sound like a broken initrd, missing key binaries (or some busybox symlinks). Does it help to run update-initramfs -u to update the initrd after the upgrade? The problem happen before sysvinit is executed, so the bug is probabliy in some other package. Not sure which. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
