Hey,
I'm booting the F22 squashfs using:
-kernel vmlinuz \
-initrd initrd.img \
-append "console=ttyS0 inst.ks=http://10.0.2.2:51738/kickstarts/rootfs.ks inst.stage2=http://10.0.2.2:51738/ quiet cmdline inst.virtiolog "
kernel, initrd, and squashfs are from the F22 dirs:
https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-22&arch=x86_64
and when I boot, I get:
==================================================
Starting Switch Root...
[FAILED] Failed to start Switch Root.
See "systemctl status initrd-switch-root.service" for details.
Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
[ 20.420170] blk_update_request: I/O error, dev fd0, sector 0
[ 20.492165] blk_update_request: I/O error, dev fd0, sector 0
Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.
:/# systemctl status initrd-switch-root.service -l
● initrd-switch-root.service - Switch Root
Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2015-02-12 18:22:18 UTC; 32s ago
Process: 1108 ExecStart=/usr/bin/systemctl --no-block --force switch-root /sysroot (code=exited, status=1/FAILURE)
Main PID: 1108 (code=exited, status=1/FAILURE)
Feb 12 18:22:18 localhost systemctl[1108]: Failed to switch root: Specified switch root path /sysroot does not seem to be an OS tree. os-release file is missing.
Feb 12 18:22:18 localhost systemd[1]: initrd-switch-root.service: main process exited, code=exited, status=1/FAILURE
Feb 12 18:22:18 localhost systemd[1]: Failed to start Switch Root.
Feb 12 18:22:18 localhost systemd[1]: Unit initrd-switch-root.service entered failed state.
Feb 12 18:22:18 localhost systemd[1]: initrd-switch-root.service failed.
==================================================
I also see that os-release is not in the squashfs and I can not make much of the "new?" initrd:
$ lsinitrd data/images/initrd.img
Image: data/images/initrd.img: 43M
========================================================================
with dracut modules:
========================================================================
drwxr-xr-x 3 root root 0 Feb 11 17:51 .
-rw-r--r-- 1 root root 2 Feb 11 17:51 early_cpio
drwxr-xr-x 3 root root 0 Feb 11 17:51 kernel
drwxr-xr-x 3 root root 0 Feb 11 17:51 kernel/x86
drwxr-xr-x 2 root root 0 Feb 11 17:51 kernel/x86/microcode
-rw-r--r-- 1 root root 25506 Feb 11 17:51 kernel/x86/microcode/AuthenticAMD.bin
========================================================================
My question is now: Are the images intended to boot anaconda?
Or am I doing something wrong?
Is something broken?
Greetings
fabian
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
