On 2014-05-10 9:24 AM, Stephen E. Baker wrote:
Hello,
As of yesterday I cannot boot, regardless of whether I choose the
regular or failback kernel from the boot loader.
I haven't been able to find anything on google, so I was hoping
someone here might know what's going on.
Last time my system was up I installed updates including the latest
kernel, and I ran e4defrag over the disk.
The computer is a ThinkPad T60, with a Core 2 Duo and 2GB of Ram. I am
running the i686 version of Arch Linux.
My boot loader is syslinux.
In the mean time I'm downloading a new copy of the Arch Install ISO
(all my existing recovery disks are too old to chroot from), and I
will try reinstalling the kernel.
Output:
Loading ../vmlinuz-linux... ok
Loading ../initramfs-linux.img...ok
Probing EDD (edd=off to disable)... ok
early console in decompress_kernel
Decompressing Linux...
Out of memory while allocating z_stream
-- System halted
Reinstalling the kernel does not help (kernel version is 3.14.2-2)
Booting into the system from System Rescue CD takes me to a root
console, where I can see the following errors in journalctl transcribed
by hand:
systemd-modules-load[400]:
Failed to lookup alias 'vhba': Function not implemented
Failed to lookup alias 'nfs': Function not implemented
Failed to lookup alias 'cuse': Funtion not implemented
Failed to lookup alias 'snd-seq-oss': Function not implemented
systemd[1]:
systemd-modules-load.service: main process exited, code=exited,
status=1/Failure
Failed to start Load Kernel Modules.
Unit systemd-modules-load.service entered failed sate.
...
(several modules successfully start)
...
mount[410]: unknown filesystem type 'binfmt_misc'
systemd[1]: proc-sys-fs-binfmt_misc.mount process exited, code=exited
status=32
systemd[1]: Failed to mount Arbitrary Executeable File Formats File System
Unit proc-sys-fs-binfmt_misc.mount entered failed state.
(repeat of the above)
(repeat of the above with additional line) systemd-binfmt[403]: Failed
to add binary format: No such device
(repeat of above)
systemd[1]: Unit systemd-binfmt.service entered a failed state.
systemd-udevd[416]:
invalid key/value pair in file /etc/udev/rules.d/51-android.rules on
line 1,starting at character 1 ('U')
(repeat for line 2 and 3)
systemd[1]: Job
dev-disk-by\x2duuid-0ee048dd\x2d2e11\x2d4499\x2d97ad\x2dc581a0eb3fba.device/start
timed out.
systemd[1]: Timed out waiting for device
dev-disk-by\x2duuid-0ee048dd\x2d2e11\x2d4499\x2d97ad\x2dc581a0eb3fba.device
systemd[1]: Dependency failed for /boot.
systemd[1]: Dependency failed for Local File Systems.
systemd[1]: Dependency failed for File System Check on
/dev/disk/by-uuid/0ee048dd-2e11-4499-97ad-c581a0eb3fba
systemd[1]: Job
dev-disk-by\x2duuid-081bbc62\x2d30be\x2d4333\x2daee0\x2dc9d2f6ed5e55.device/start
timed out.
systemd[1]: Timed out waiting for device
dev-disk-by\x2duuid-081bbc62\x2d30be\x2d4333\x2daee0\x2dc9d2f6ed5e55.device
systemd[1]: Dependency failed for
/dev/disk/by-uuid/081bbc62/30be/4333/aee0/c9d2f6ed5e55.
systemd[1]: Dependency failed for Swap.
...
(several services shut down, several others successfully start)
systemd[474]: Failed at step EXEC spawning /bin/plymouth: No such file
or directory
