[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2015-10-31 Thread Dominic Raferd
I have been having this problem (intermittently) with Ubuntu Server 15.04 and now with 15.10 on my Intel NUC5CPYH for the last 3 months (since I bought it in fact). It only seems to happen when rebooting (never from a cold boot), and it doesn't always happen. I've attached an image of the console

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2013-05-18 Thread dino99
https://wiki.ubuntu.com/Releases ** Changed in: udev (Ubuntu Natty) Status: Triaged = Invalid ** Changed in: udev (Ubuntu Maverick) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2013-05-18 Thread dino99
upstream should have been synced ** Changed in: udev (Ubuntu Lucid) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613273 Title: run-init: nuking initramfs

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2013-01-29 Thread Gernot Hillier, Siemens CT
As already mentioned in comment 10, we experienced the same bug at the end of 2011 and were hit by it in internal tests every few weeks. After applying the mentioned change, it disappeared. Since somewhen in 2012, we're in the field with about hundred systems running Lucid with this patch and

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-12-25 Thread Jack Yan
I have this issue as well with the latest update (referred here from https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/155689): making initramfs contents: Directory not empty Kernel panic—not syncing: attempted to kill init I’m really inexperienced on Ubuntu 10—just wanted to note

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-06-26 Thread Pontiy_Pilat
Thank you, Mekk! Reproduce this trouble after upgrade from lucid to precise. Remove simlink /run and make dir /run in guest - fix problem. rm /run mkdir /run Please fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-06-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udev (Ubuntu Lucid) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613273 Title:

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-04-06 Thread Mekk
I got this very message, for the first time, after upgrade to 12.04 Precise. Can't boot that machine. Root on md -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613273 Title: run-init: nuking

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-04-06 Thread Mekk
My case resolved: somehow during upgrade I got /run as symlink to /var/run and /var/run as symlink to /run. After I patched this, the problem is gone. But it took time to spot it. Regarding bug title: I find this error message to be not too informative… Providing some detail about the problem

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-02-20 Thread Paolo Maero
Please, can someone register this as also affecting udev (Ubuntu Lucid)? This kind of errors on an LTS version should be fixed, I think. Affecting on random systems, but when it happens I get it on 40% of reboots... -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-02-20 Thread Scott Moser
** Also affects: initramfs-tools (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Lucid) Importance: Undecided Status: New -- You received this bug notification

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2012-02-20 Thread Scott Moser
** Changed in: initramfs-tools (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux (Ubuntu Lucid) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613273

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2011-11-08 Thread Daniel Ellis
I agree Bernie, so I changed the title. I don't believe you need particular privileges to do this. ** Summary changed: - kernel panic on ec2 in system_call_fastpath + run-init: nuking initramfs contents: directory not empty -- You received this bug notification because you are a member of

[Bug 613273] Re: run-init: nuking initramfs contents: directory not empty

2011-11-08 Thread Daniel Ellis
Please can someone register this as also affecting udev (Ubuntu Lucid). I have tried, but cannot find a method to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/613273 Title: run-init: