"udevadm trigger is not permitted while udev is unconfigured."

[cleverbubbles123]

root@ubuntu:/# sudo update-initramfs -u -k all
sudo: unable to resolve host ubuntu
update-initramfs: Generating /boot/initrd.img-2.6.35-23-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-2.6.35-23-generic





what is wrong?

[AlexanderDGreat]

gzip: stdout: No space left on device

what is wrong?

[Mecasickle]

In my case, I get this error:

ubuntu@ubuntu:~$ sudo dpkg-reconfigure xserver-xorg
ubuntu@ubuntu:~$ sudo update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-2.6.35-22-generic
cp: cannot stat `/vmlinuz': No such file or directory

What should I do about the /vmlinuz??
Thanks!

[AlexanderDGreat]

cp: cannot stat `/vmlinuz': No such file or directory

- it means it's not mounted. You need to mount it first, did you follow the exact steps here? Is your /boot a separate partition?

[Mecasickle]

I've follows these isntructions:
1) Boot Live CD (USB stick in my case for Ubuntu 10.10 in my case)
2) sudo fdisk -l
3) sudo mkdir /media/newroot
4) sudo mount /dev/sdb1 /media/newroot
5)sudo chroot /media/newroot
6) ls /boot
7) sudo update-initramfs -u -k 2.6.35-22-generic
8) Reboot & smile.

Basically on step 5 it bugs because it tells me that this when I perform the chroot operation:

ubuntu@ubuntu:~$ sudo chroot /media/newroot
chroot: failed to run command `/bin/bash': No such file or directory

When I perform the sudo fdisk -l
I get this:

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb33fd09d

Device Boot Start End Blocks Id System
/dev/sda1 1 5 40131 de Dell Utility
/dev/sda2 * 6 1918 15360000 7 HPFS/NTFS
/dev/sda3 1918 38914 297169240 7 HPFS/NTFS

Disk /dev/sdb: 4009 MB, 4009754624 bytes
93 heads, 8 sectors/track, 10526 cylinders
Units = cylinders of 744 * 512 = 380928 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 10527 3915772 c W95 FAT32 (LBA)

-----

I guess that what I have to mount is my sdba1 partition, ive tried every other option, with my sda1, sda2, sd3 partition too, but no luck. So I really don't understand if I'm "moutning my boot partition correctly"

How do I know if my /boot is a separate partition ?

Thanks man! Sorry for the late replay, I've been busy with exams.

Any other direction I should be pointing out to?

[Mecasickle]

Figured out that the best thing to do, is to reinstall ubuntu (wubi version).

Cheers

[AlexanderDGreat]

I'm so sorry haven't been able to reply. But really, if you have time you should study more on how to CHROOT.

Simply put, CHROOT, is just mounting your whole system to a folder and going inside that folder and have your little private space in there to install, run commands, apart from what is running in your current LOGIN desktop.

Here, I pasted a simple CHROOT'ing example:

METHOD 3 - CHROOT

This method of installation uses the chroot command to gain access to the broken
system's files. Once the chroot command is issued, the LiveCD treats the broken
system's / as its own. Commands run in a chroot environment will affect the broken
systems filesystems and not those of the LiveCD.

1. Boot to the LiveCD Desktop (Ubuntu 9.10 or later). Please note that the
Live CD must be the same as the system you are fixing - either 32-bit or
64-bit (if not then the chroot will fail).

2. Open a terminal - Applications, Accessories, Terminal.

3. Determine your normal system partition - (the switch is a lowercase "L")

      sudo fdisk -l
          * If you aren't sure, run

            df -Th. Look for the correct disk size and ext3 or ext4 format. 
4. Mount your normal system partition:
          * Substitute the correct partition: sda1, sdb5, etc. 

      sudo mount /dev/sdXX /mnt # Example: sudo mount /dev/sda1 /mnt
5.

      Only if you have a separate boot partition:
          * sdYY is the /boot partition designation (for example sdb3)
          *

            sudo mount /dev/sdYY /mnt/boot 
6. Mount the critical virtual filesystems:

      sudo mount --bind /dev  /mnt/dev
      sudo mount --bind /dev/pts  /mnt/dev/pts
      sudo mount --bind /proc /mnt/proc
      sudo mount --bind /sys  /mnt/sys
7. Chroot into your normal system device:

      sudo chroot /mnt
8. If there is no /boot/grub/grub.cfg or it's not correct, create one using

      update-grub
9. Reinstall GRUB 2:
          *

            Substitute the correct device - sda, sdb, etc. Do not specify a
partition number. 

      grub-install /dev/sdX
10.

      Verify the install (use the correct device, for example sda. Do not specify a
partition): sudo grub-install --recheck /dev/sdX
11.

      Exit chroot: CTRL-D on keyboard
12. Unmount virtual filesystems:

      sudo umount /mnt/dev/pts
      sudo umount /mnt/dev
      sudo umount /mnt/proc
      sudo umount /mnt/sys
          * If you mounted a separate /boot partition:

            sudo umount /mnt/boot 
13. Unmount the LiveCD's /usr directory:

      sudo umount /mnt/usr
14. Unmount last device:

      sudo umount /mnt
15. Reboot.

      sudo reboot 

Post-Restoration Commands

Once the user can boot to a working system, try to determine why the
system failed to boot. The following commands may prove useful in locating and/or fixing the problem.

    *

      To refresh the available devices and settings in /boot/grub/grub.cfg
          o

            sudo update-grub 
      To look for the bootloader location.
          o

            grub-probe -t device /boot/grub 

      To install GRUB 2 to the sdX partition's MBR (sda, sdb, etc.)
          o

            sudo grub-install /dev/sdX 
      To recheck the installation. (sda, sdb, etc.)
          o

            sudo grub-install --recheck /dev/sdX

It's taken from here: https://help.ubuntu.com/community/Gr...0from%20LiveCD - when a user wants to FIX GRUB, just pay attention to METHOD #3 - And ignore all the rest of technojabber.

I've looked on this myself when I was studying and messing with my GRUB. It helped me a lot to understand what CHROOT is all about when I was on the udevadm problem.

Hope you find it useful.

[potiphera]

After a kernel update and reboot on 64-bit Ubuntu Studio 10.04, I'm getting this error, in combination with an error that says "cryptsetup: lvm device name [long hexadecimal device name] does not begin with /dev/mapper/" (I have full disk encryption enabled). I've gotten the latter error before, and was able to fix it by pressing Shift and entering GRUB. Now I can't because of the udevadm error. I tried Audi200Q's advice, and all the commands seemed to work except the update-initramfs commands gave me an error saying "cryptsetup: WARNING: invalid line in /etc/crypttab -", and my system still won't boot. I posted more about it here. Is there anything else I can try? Thanks!