Re: Update FC23 - doesn't boot - ssh preboot not working anymore

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10.11.2015 13:23, Gerhard Wiesinger wrote:
On 09.11.2015 15:58, Harald Hoyer wrote:
Am 03.11.2015 um 22:39 schrieb Gerhard Wiesinger:
Hello,

After upgrading one machine it does't boot anymore. Booting the old FC22 kernel
works well.

Reached target Basic System.
Found device /dev/mapper/luks-9fbecd95-508a-45ca-997a-42a613c4e5bf
Found device /dev/mapper/fedora_hostname-root

Also integration of ssh preboot authentication is not available anymore.

blkid:
/dev/vda2: UUID="f3e2c8a9-51b1-4110-aef5-039cf714425a" TYPE="ext4"
PARTLABEL="Linux filesystem" PARTUUID="6bc53fb0-771b-4b52-b584-c87735715a47" /dev/vda3: UUID="9fbecd95-508a-45ca-997a-42a613c4e5bf" TYPE="crypto_LUKS" PARTLABEL="Linux filesystem" PARTUUID="090ffe9b-6791-46df-b9a4-f30adbb95e50"
/dev/mapper/luks-9fbecd95-508a-45ca-997a-42a613c4e5bf:
UUID="A3RzKd-F7ym-pN6a-F01g-Q0Gw-DrVr-jhTgbo" TYPE="LVM2_member"
/dev/mapper/fedora_hostname-swap: UUID="cef5950c-43bc-485c-ae2b-832fcbe752c7"
TYPE="swap"
/dev/mapper/fedora_hostname-root: UUID="8f5436a3-28cb-4c7e-91df-e3f9249d17d2"
TYPE="ext4"
/dev/vda1: PARTLABEL="BIOS Boot Partition"
PARTUUID="35685b7e-917c-4cc5-9133-69f00f5a1e2f"

Any ideas?

Thank you.

Ciao,
Gerhard


https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_troubleshooting

please file a bugzilla on the fedora/redhat bugzilla and add rdsosreport.txt



Hello Harald,

Applied kernel parameters from link but I dont't get a shell. Very strange, it looks like if you wait for minutes it works well and I get a password prompt. But afterwards it is still slow on booting, but get the log file after some long waiting and tricks. It looks like it hangs in some endless loop when working on string operations.

Send you a private email with further private information about the issue (screenshots).

Will open a bug report later on.


Thanx for Harald figuring out/helping that with FC23 changed something: interfaces are not anymore eth0 but new interface naming schemes is now active e.g. ens18 Therefore dracut couldn't boot waiting for eth0 specified on kernel command line which didn't exist anymore because it is named now ens18.

As I use networking in initramfs with dracut and get networking up there you can't change the network interface easily (it is possible when you unload the network driver modile but for some reason this did not work reliable).

For reference: Nevertheless I found a solution to get persisent netnames in dracut and later on in the "regular" kernel.
# /etc/grub2.cfg kernel parameters
# before:
ip=1.2.3.4::1.2.3.1:255.255.255.0:myhostname:eth0:off nameserver=8.8.8.8 nameserver=8.8.4.4
# after:
ifname=lan0:26:a0:fc:12:34:56 ip=1.2.3.4::1.2.3.1:255.255.255.0:myhostname:lan0:off nameserver=8.8.8.8 nameserver=8.8.4.4
# and adapt network config and firewall to new interfaces

Harald, thnx for your help.

Ciao,
Gerhard

--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux