I have this bug on the latest update of Ubuntu 10 (had to enter this in
Windows as I can’t get past the error screen in Ubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/155689
Title:
nuking
In short, the problem should be fixed for oneiric, but for the versions of
udev used in older releases there
doesn't seem to be any way to fix the problem 100% of the time.
I'm still experiencing this bug on oneiric.
--
You received this bug notification because you are a member of Ubuntu
This problem is caused by being unable to fully terminate udev when
switching from the initramfs to the real root filesystem. Bug 613273 has
a more detailed description of the situation. In short, the problem
should be fixed for oneiric, but for the versions of udev used in older
releases there
I am having this problem intermittently. I have Ubuntu 10.10 on an Asus
EEE PC 1005 HA (Hard drive), 1 Mb of RAM, dual booting with Windows XP.
This has been updated from Ubuntu 10.04 (which was all OK) just a week
ago, so this might possibly related to the upgrade (?).
Additional info: this
Haven't see my problem since the 29th March!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/155689
Title:
nuking initramfs contents: Kernel panic at boot
--
ubuntu-bugs mailing list
I've started getting this intermittently in the past week on
10.10/Maverick Meerkat. It's hard to get a log of the error message when
it does happen but it includes:
run-init: nuking initramfs contents: Directory not empty
Kernel panic - not syncing: Attempted to kill init!
run-init not tainted
(I am using LVM if that is important.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/155689
Title:
nuking initramfs contents: Kernel panic at boot
--
ubuntu-bugs mailing list
I am using the linux 2.6.24.4
I reduced the kernel configuration my removing many modules and drivers.
But after removing the last few modules I am getting the following
errors as my kernel panics
run-init: nuking initramfs contents: Directory not empty
...Kernel panic - not syncing: Attempted
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = Invalid
--
nuking initramfs contents: Kernel panic at boot
https://bugs.launchpad.net/bugs/155689
You received this bug notification because you are a member
Some time after I reported this bug, the problem disappeared (and I
forgot about the bugreport). I didn't change anything on my system,
except for installing updates. So I have no idea what caused the problem
or what may have fixed it.
--
nuking initramfs contents: Kernel panic at boot
Yan Li, thanks for testing and the update. I'm glad to hear things are
working for you.
Jef, since you are the original bug reporter, I'd like to get
confirmation from you before closing this. Thanks.
--
nuking initramfs contents: Kernel panic at boot
https://bugs.launchpad.net/bugs/155689
I'm running Hardy kernel on this machine and it's no longer suffering
from this problem.
--
nuking initramfs contents: Kernel panic at boot
https://bugs.launchpad.net/bugs/155689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The Hardy Heron Alpha series is currently under development and contains
an updated version of the kernel. It would be helpful if you could test
the latest Hardy Alpha release: http://www.ubuntu.com/testing . You
should be able to then test the new kernel via the LiveCD. If you can,
please
I met same problem on my ThinkPad T43p: Occasionally (about 2 out of 5),
my Gutsy system got panic on boot. I've installed my Gutsy system using
alternative CD with encrypted root partition (no encryption of swap nor
/boot). The panic occurred soon after I enter the correct root partition
password
After entered my encrypt filesystem password, I press Alt-F1 swiftly
to switch to console, and got this screenshot of panic.
It's a rather annoying bug. For several times I wanna show my Ubuntu
Gutsy to my friends and met this problem in the field, embarrassed me!
Hope this would be fixed soon.
I am also using LVM.
--
nuking initramfs contents: Kernel panic at boot
https://bugs.launchpad.net/bugs/155689
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Same problem on startup and the HDD led flash. I think there is maybe a
problem with the file system ( I am using LVM )
Error :
unlink_secure : chown(/dev/.tmp-254-6, 0 , 0) failed : no sufh file or directory
unlink_secure : chown(/dev/.tmp-254-6, ) failed : no sufh file or directory
17 matches
Mail list logo
