[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#637481: marked as done (/init: /init: 318: cannot open /root/dev/console: No such file)

Your message dated Tue, 5 Jun 2012 17:56:56 +0000
with message-id <20120605175656.GJ17569@vostochny.stro.at>
and subject line Re: /init: /init: 318: cannot open /root/dev/console: No such file
has caused the Debian Bug report #637481,
regarding /init: /init: 318: cannot open /root/dev/console: No such file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
637481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637481
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----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-----

--- End Message ---
--- Begin Message --- 
release hoping is *not* supported, you are entirely on your own
for doing such a thing. Next time jump from a relase to it's successor.

> I'm not sure if this makes sence to do so at this stage -- 1.10.2 is
> very old, it is pre-squeeze...  If not, fell free to close this bug.

Also I see no point in adding such old breaks,
it hasn't happened that often this error, thus closing.

good luck and thank you.

-- 
maks

--- End Message ---
Reply to: