Re: Update FC22 - doesn't find root fs and doesn't boot
On 15.06.2015 11:42, Harald Hoyer wrote: > On 11.06.2015 11:06, poma wrote: >> On 31.05.2015 20:08, Bruno Wolff III wrote: And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be. >>> >>> In the past changes with this effect were reverted. This time they were >>> not. >>> This generally just affects people upgrading, as anaconda has been adding >>> the needed stuff on the kernel command line for a while now. >>> >>> You can also hostonly_cmdline=yes to the dracut config or set hostonly=no >>> if you are willing to have a larger initramfs file. The latter will also >>> help >>> if you switch out hardware. >>> >>> I am not sure why hostonly_cmdline=yes is not the default when >>> hostonly=yes. >>> That would seem to be a better default. >>> >> >> >> dracut.conf.d/fedora.conf.example >> +hostonly_cmdline="no" >> >> http://pkgs.fedoraproject.org/cgit/dracut.git/commit/0001-fedora.conf-do-not-store-cmdline-in-image-by-default.patch?id=43a1228 >> http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/dracut.conf.d/fedora.conf.example?id=38e2177 >> >> no explanation why this was done > > > Basically it's because compiled in arguments are hard to override and people > could not boot after they changed disk configuration. > > I guess, s.th. like "rd.cmdline=clean rd.auto" or "rd.helpIwanttobootnow" is > the better solution. > rd.OhLordwontyoubuymeaMercedesBenzMyfriendsalldrivePorschesImustmakeamends -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update FC22 - doesn't find root fs and doesn't boot
On 11.06.2015 11:06, poma wrote: > On 31.05.2015 20:08, Bruno Wolff III wrote: >>> And already we have fought for this user's side simplification, but it >>> seems developers are very persistent when they do not need to be. >> >> In the past changes with this effect were reverted. This time they were not. >> This generally just affects people upgrading, as anaconda has been adding >> the needed stuff on the kernel command line for a while now. >> >> You can also hostonly_cmdline=yes to the dracut config or set hostonly=no >> if you are willing to have a larger initramfs file. The latter will also >> help >> if you switch out hardware. >> >> I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. >> That would seem to be a better default. >> > > > dracut.conf.d/fedora.conf.example > +hostonly_cmdline="no" > > http://pkgs.fedoraproject.org/cgit/dracut.git/commit/0001-fedora.conf-do-not-store-cmdline-in-image-by-default.patch?id=43a1228 > http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/dracut.conf.d/fedora.conf.example?id=38e2177 > > no explanation why this was done Basically it's because compiled in arguments are hard to override and people could not boot after they changed disk configuration. I guess, s.th. like "rd.cmdline=clean rd.auto" or "rd.helpIwanttobootnow" is the better solution. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update FC22 - doesn't find root fs and doesn't boot
On 31.05.2015 20:08, Bruno Wolff III wrote: >> And already we have fought for this user's side simplification, but it seems >> developers are very persistent when they do not need to be. > > In the past changes with this effect were reverted. This time they were not. > This generally just affects people upgrading, as anaconda has been adding > the needed stuff on the kernel command line for a while now. > > You can also hostonly_cmdline=yes to the dracut config or set hostonly=no > if you are willing to have a larger initramfs file. The latter will also help > if you switch out hardware. > > I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. > That would seem to be a better default. > dracut.conf.d/fedora.conf.example +hostonly_cmdline="no" http://pkgs.fedoraproject.org/cgit/dracut.git/commit/0001-fedora.conf-do-not-store-cmdline-in-image-by-default.patch?id=43a1228 http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/dracut.conf.d/fedora.conf.example?id=38e2177 no explanation why this was done -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update FC22 - doesn't find root fs and doesn't boot
And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be. In the past changes with this effect were reverted. This time they were not. This generally just affects people upgrading, as anaconda has been adding the needed stuff on the kernel command line for a while now. You can also hostonly_cmdline=yes to the dracut config or set hostonly=no if you are willing to have a larger initramfs file. The latter will also help if you switch out hardware. I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. That would seem to be a better default. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Update FC22 - doesn't find root fs and doesn't boot
On 28.05.2015 14:19, Gerhard Wiesinger wrote: > On 27.05.2015 15:27, Harald Hoyer wrote: >> Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger: >>> On 27.05.2015 15:07, Harald Hoyer wrote: Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger: > On 27.05.2015 14:43, Harald Hoyer wrote: >> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger: >>> On 27.05.2015 14:25, Harald Hoyer wrote: Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov: > On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger > > wrote: >> On 27.05.2015 13:56, Harald Hoyer wrote: >>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger: Hello, After upgrading one machine it does't boot anymore. Booting the old kernel works well. It is a RAID, LUKS, LVM setup. Find relevant details below. So it looks RAID assembling doesn't work any more. Any ideas? Thank you. Ciao, Gerhard blkid /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member" PARTUUID="5ec6792c-01" /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member" PARTUUID="1c7cffaf-01" /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member" PARTUUID="0079dfc3-01" /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member" PARTUUID="fadeaffe-01" /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member" PARTUUID="539b5814-01" /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member" PARTUUID="badeaffe-01" /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member" PARTUUID="15631562-01" /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member" PARTUUID="162f0d0b-01" blkid -o udev ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37 ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=5ec6792c-01 ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37 ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=1c7cffaf-01 ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37 ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=0079dfc3-01 ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300 ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=fadeaffe-01 ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300 ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=539b5814-01 ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300 ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=badeaffe-01 ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534 ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=15631562-01 ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534 ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534 ID_FS_TYPE=linux_raid_member ID_FS_PARTUUID=162f0d0b-01 [2.479836] myhost systemd[1]: Device dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared twice with different sysfs paths /sys /devices/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh and /sys/devices/pci:00/:00:02.1/usb1/1-5/1-5:1.0/host8/target 8:0:0/8:0:0:0/block/sdg [2.500826] myhost systemd[1]: Device dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device appeared twice with different sysfs p aths /sys/devices/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1 and /sys/devices/p
