Ich habe eben ein Update gemacht und dabei kommt es zu einem Fehler; jedenfalls wird offensichtlich der fallback-Kernel installiert. Muss ich mir Sorgen machen, dass ich das System nicht mehr starten kann?
yaourt -Suya schrieb
...
Pakete (11): linux-3.5.4-1 linux-headers-3.5.4-1 lirc-utils-1:0.9.0-27 nvidia-304.43-2 sudo-1.8.6.p2-1 tzdata-2012f-1 virtualbox-4.2.0-2 virtualbox-additions-4.1.22-1 [removal] virtualbox-host-modules-4.2.0-2 virtualbox-iso-additions-4.2.0-1 virtualbox-modules-4.1.22-1 [removal]
Installation fortsetzen? [J/n]
:: Empfange Pakete von core...
linux-3.5.4-1-x86_64
headers-3.5.4-1-x86_64
...
Aktualisiere linux
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.5.4-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
==> ERROR: file not found: `fsck.btrfs'
==> WARNING: No fsck helpers found. fsck will not be run on boot.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.5.4-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful