I believe that is bug report is now stale. Please reopen if not.
Thanks.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I do not have this issue with either precise or trusty.
Regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/98911
Title:
I keep getting an error with initramfs every time it tries to load a
This bug is quite old. Does this still happen in supported Ubuntu
versions? Thank you for helping us!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/98911
Title:
I keep getting an error with
What about those of us that do use RAID? I have a file / web server in
my basement running a RAID0 (concatenating 4 9GB hard disks). The
upgrade process from Edgy to Feisty succeeded, but I got the above error
while rebuilding the initramfs, so I am afraid to reboot it with the new
kernel until
While upgrading from Edgy to Feisty, I also saw lots of falling back to
emergency procedure in initramfs error messages scroll by. Before I
rebooted, I applied Victor's temporary solution from above
(https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/98911/comments/12) and my machine
Temporary solution detailed:
if you don't use RAID, then
- remove the mdadm package
If necesserary (it was for me):
- remove the mdadm service (install sysv-rc-conf and use it to unselect mdadm +
mdadm-raid)
- reinstall grub (it had been remove during the upgrade, probably, and needed
to run
If you don' t use RAID, you can solve it by removing mdadm. I
successfully restarted the system after an upgrade to feisty without
mdadm.
--
I keep getting an error with initramfs every time it tries to load a new initrd
image
https://bugs.launchpad.net/bugs/98911
You received this bug
Le 4984 Septembre 1993, Nathan Willis a tapoté:
What to do?
The only workaround I found is to boot on the live CD.
Then mount the root device under /mnt/:
$ sudo bash
# mount /dev/hdXY /mnt
Mount /proc /dev and /sys
# mount --bind /proc /mnt/proc
# mount --bind /dev /mnt/dev
# mount --bind
Seems like lots of folk don't have any MD devices and don't plan to.
Removing the mdadm package will stop the errors and allow an initrd to be built
OK. And since it's only necessary when accessing MD devs, it won't cause
problems if you don't use that feature.
--
I keep getting an error with
This is a very serious problem that has affected me badly.
Since upgrading to Feisty i have lost the ability to run ANY usb devices - my
external hard drive, ipod etc
i reinstalled mdadm to see if that did anything and this is what i got:
The following NEW packages will be installed:
mdadm
0
Same problem
- unable to finish the upgrade to Feisty: kernel 2.6.20 not activated
- getting stuck every time I want to install a package that requires kernel
dependancies
- having to wait for every time failing configuration each time I want to
install anything
- no clue about what is mdadm is
Same problem here. dist-upgrading from edgy to feisty fails hard; this
is serious.
*apt-get --reinstall install ___ fails to help
*apt-get -f install fails to help
*dpkg --configure -a fails to help
What to do?
--
I keep getting an error with initramfs every time it tries to load a new initrd
This bug is blocking my upgrade to Feisty, and I have no idea how to fix
it except maybe add a raid array. Why is this bug still unconfirmed and
undecided?
--
I keep getting an error with initramfs every time it tries to load a new initrd
image
https://bugs.launchpad.net/bugs/98911
You received
Maybe this bug report should be re-assigned to mdadm ? It seems to be
related to the mdadm initramfs hook.
Regards.
--
I keep getting an error with initramfs every time it tries to load a new initrd
image
https://bugs.launchpad.net/bugs/98911
You received this bug notification because you are
I got this problem today too, and I'm hoping for a fix. Any ideas?
Setting up initramfs-tools (0.85eubuntu9) ...
update-initramfs: Generating /boot/initrd.img-2.6.20-14-generic
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read
I have this problem with my feisty.
I have no md array and the initramfs hook complains about that.
Booting does not work, initramdik created by yaird are OK.
I think a test should be done to see if md are used, and it should honor the
/etc/default/mdadm configuration file:
INITRDSTART='none'
It appears to have gotten worse:
Setting up linux-restricted-modules-common (2.6.20.4-13.14) ...
Setting up linux-restricted-modules-2.6.20-13-generic (2.6.20.4-13.14)
...
Setting up mdadm (2.5.6-7ubuntu5) ...
update-initramfs: Generating /boot/initrd.img-2.6.20-13-generic
cp: cannot stat
17 matches
Mail list logo