Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
On Wed, May 25, 2016 at 10:13 PM, Bill Perkins wrote: > > The problem I had was in the GRUB_CMDLINE_LINUX line in the > /etc/default/grub file. The first rd.md.uuid was supposed to be the > uuid for the Linux RAID member disks that make up the mdraid devices > from which you want to boot. > > The second rd.md.uuid that pointed to the RAID member disks used for > the root filesystems and LVM was missing! Yes, I figured it'd be something like that once I realized there really were two mdraid arrays, but only one rd.md.uuid parameter. What's curious is that its absence wasn't causing a problem before the upgrade. > > Correcting both rd.md.uuid entries to reflect the correct devices > in that file and running dracut -f before rebooting resolved my > problem. Well in the end that's all that matters. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
On 2016.05.25 15:25, Chris Murphy wrote: > May 24 00:07:00 redwood.localnet kernel: Command line: > BOOT_IMAGE=/vmlinuz-4.4.9-200.fc22.x86_64 root=/dev/mapper/vg0-lv1 ro > rd.md.uuid=5a1848ce:cff64c1f:a622dc1f:e5f06d55 LANG=en_US.UTF-8 > SYSFONT=True rd.lvm.lv=vg0/lv0 rd.lvm.lv=vg0/lv1 KEYTABLE=us > rd.luks=0 > rd.dm=0 > > > There is an rd.md.uuid= parameter, so that's good. > > > > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: > Could > not boot. > May 24 00:10:08 redwood.localnet systemd[1]: Received SIGRTMIN+20 > from > PID 349 (plymouthd). > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: > /dev/mapper/vg0-lv1 does not exist > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: > /dev/vg0/lv0 does not exist > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: > /dev/vg0/lv1 does not exist > May 24 00:10:08 redwood.localnet systemd[1]: Starting Dracut > Emergency > Shell... > > OK so yeah, it's basically not finding rootfs. 29 seconds later... > > May 24 00:10:37 redwood.localnet kernel: md: md0 stopped. > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md: raid1 personality > registered for level 1 > May 24 00:10:37 redwood.localnet kernel: md/raid1:md0: active with 2 > out of 2 mirrors > May 24 00:10:37 redwood.localnet kernel: md0: detected capacity > change > from 0 to 262078464 > May 24 00:10:37 redwood.localnet kernel: md: md1 stopped. > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md/raid1:md1: active with 2 > out of 2 mirrors > May 24 00:10:37 redwood.localnet kernel: created bitmap (15 pages) > for > device md1 > May 24 00:10:37 redwood.localnet kernel: md1: bitmap initialized from > disk: read 1 pages, set 0 of 29804 bits > May 24 00:10:37 redwood.localnet kernel: md1: detected capacity > change > from 0 to 268632576 > May 24 00:10:54 redwood.localnet systemd[1]: Found device > /dev/mapper/vg0-lv1. > May 24 00:10:54 redwood.localnet systemd[1]: Starting File System > Check on /dev/mapper/vg0-lv1... > May 24 00:10:54 redwood.localnet systemd-fsck[2685]: /: clean, > 529693/1048576 files, 3263599/4194304 blocks > May 24 00:10:54 redwood.localnet systemd[1]: Started File System > Check > on /dev/mapper/vg0-lv1. > > > So now it's found, I'm gonna guess this is your manual attempt at > starting up the array? > > What do you get for cat /proc/mdstat at the dracut prompt before you > do anything else? And also the results from > > mdstat -E /dev/sda1 > mdstate -E /dev/sdb1 > blkid > > These can be redirected to fpaste or a file. If you have network > access this early it's easiest to redirect to fpaste but I'm not sure > if it's in the initramfs. > > >From your mdadm.conf, you have UUIDs that do not match what's on the > command line. > > cmdline: > rd.md.uuid=5a1848ce:cff64c1f:a622dc1f:e5f06d55 > > mdadm.conf > UUID=c45384af:aa8fc7ca:7eebaeb8:f0ca1523 > UUID=524079c6:521ca76f:126164a9:3232e116 > > Looks like the mdadm.conf is stale and should be recreated, and > recreate the initramfs. Thing is, the rd.md.uuid ought to be enough > for dracut to startup that array, the mdadm.conf is really just about > assigning a particular md array to a particular /dev/mdX assignment, > which by the way has changed recently so there might be confusion > going on there. > > You might just try renaming the current mdadm.conf, or commenting out > all of the lines, except for one: > > ARRAY /dev/md0 UUID=5a1848ce:cff64c1f:a622dc1f:e5f06d55 > > And after saving it, use dracut -f. > > Chris Murphy > Okay. I have figured this out after a lot of digging through Google. I finally found this page and a post by eileon (Comment: 10) https://bugzilla.redhat.com/show_bug.cgi?id=1085922 The problem turned on differences between a file: /etc/default/grub and the output of: dracut --print-cmdline As eileon stated what is given by the output above by dracut, needed to be reflected in the /etc/default/grub file before you did ran: grub2-mkconfig -o /boot/grub2/grub.cfg and then: dracut -f The problem I had was in the GRUB_CMDLINE_LINUX line in the /etc/default/grub file. The first rd.md.uuid was supposed to be the uuid for the Linux RAID member disks that make up the mdraid devices from which you want to boot. The second rd.md.uuid that pointed to the RAID member disks used for the root filesystems and LVM was missing! Correcting both rd.md.uuid entries to reflect the correct devices in that file and running dracut -f before rebooting resolved my problem. Thank you Chris for your assistance and pointing me in the right direction. Cheers! Bill -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Cod
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
Slight change in suggestions: On Wed, May 25, 2016 at 1:25 PM, Chris Murphy wrote: > > What do you get for cat /proc/mdstat at the dracut prompt before you > do anything else? Do this still. Then assemble the array manually as you have been and continue the boot normally. >And also the results from > > mdstat -E /dev/sda1 > mdstate -E /dev/sdb1 > blkid These are easier done after basic target is reached, rather than at the dracut shell. Also, the first two have bad typos so here's the revised version: mdadm -E /dev/sda[12] mdadm -D /dev/md[01] blkid > You might just try renaming the current mdadm.conf, or commenting out > all of the lines, except for one: > > ARRAY /dev/md0 UUID=5a1848ce:cff64c1f:a622dc1f:e5f06d55 > > And after saving it, use dracut -f. Skip this for now. I'd rather just collect info rather than change anything. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
On Wed, May 25, 2016 at 1:25 PM, Chris Murphy wrote: > May 24 00:07:00 redwood.localnet kernel: Command line: > BOOT_IMAGE=/vmlinuz-4.4.9-200.fc22.x86_64 root=/dev/mapper/vg0-lv1 ro > rd.md.uuid=5a1848ce:cff64c1f:a622dc1f:e5f06d55 LANG=en_US.UTF-8 > SYSFONT=True rd.lvm.lv=vg0/lv0 rd.lvm.lv=vg0/lv1 KEYTABLE=us rd.luks=0 > rd.dm=0 > > > There is an rd.md.uuid= parameter, so that's good. > > > > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: Could not > boot. > May 24 00:10:08 redwood.localnet systemd[1]: Received SIGRTMIN+20 from > PID 349 (plymouthd). > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: > /dev/mapper/vg0-lv1 does not exist > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: > /dev/vg0/lv0 does not exist > May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: > /dev/vg0/lv1 does not exist > May 24 00:10:08 redwood.localnet systemd[1]: Starting Dracut Emergency > Shell... > > OK so yeah, it's basically not finding rootfs. 29 seconds later... > > May 24 00:10:37 redwood.localnet kernel: md: md0 stopped. > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md: raid1 personality > registered for level 1 > May 24 00:10:37 redwood.localnet kernel: md/raid1:md0: active with 2 > out of 2 mirrors > May 24 00:10:37 redwood.localnet kernel: md0: detected capacity change > from 0 to 262078464 > May 24 00:10:37 redwood.localnet kernel: md: md1 stopped. > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md: bind > May 24 00:10:37 redwood.localnet kernel: md/raid1:md1: active with 2 > out of 2 mirrors > May 24 00:10:37 redwood.localnet kernel: created bitmap (15 pages) for > device md1 > May 24 00:10:37 redwood.localnet kernel: md1: bitmap initialized from > disk: read 1 pages, set 0 of 29804 bits > May 24 00:10:37 redwood.localnet kernel: md1: detected capacity change > from 0 to 268632576 > May 24 00:10:54 redwood.localnet systemd[1]: Found device > /dev/mapper/vg0-lv1. > May 24 00:10:54 redwood.localnet systemd[1]: Starting File System > Check on /dev/mapper/vg0-lv1... > May 24 00:10:54 redwood.localnet systemd-fsck[2685]: /: clean, > 529693/1048576 files, 3263599/4194304 blocks > May 24 00:10:54 redwood.localnet systemd[1]: Started File System Check > on /dev/mapper/vg0-lv1. > > > So now it's found, I'm gonna guess this is your manual attempt at > starting up the array? > > What do you get for cat /proc/mdstat at the dracut prompt before you > do anything else? And also the results from > > mdstat -E /dev/sda1 > mdstate -E /dev/sdb1 > blkid > > These can be redirected to fpaste or a file. If you have network > access this early it's easiest to redirect to fpaste but I'm not sure > if it's in the initramfs. > > From your mdadm.conf, you have UUIDs that do not match what's on the > command line. > > cmdline: > rd.md.uuid=5a1848ce:cff64c1f:a622dc1f:e5f06d55 > > mdadm.conf > UUID=c45384af:aa8fc7ca:7eebaeb8:f0ca1523 > UUID=524079c6:521ca76f:126164a9:3232e116 > > Looks like the mdadm.conf is stale and should be recreated, and > recreate the initramfs. Thing is, the rd.md.uuid ought to be enough > for dracut to startup that array, the mdadm.conf is really just about > assigning a particular md array to a particular /dev/mdX assignment, > which by the way has changed recently so there might be confusion > going on there. > > You might just try renaming the current mdadm.conf, or commenting out > all of the lines, except for one: > > ARRAY /dev/md0 UUID=5a1848ce:cff64c1f:a622dc1f:e5f06d55 > > And after saving it, use dracut -f. > > > > Chris Murphy > I am having TONS of problems with f22 (af ter reinstalling it from DVD media, due to system corruption). FOr example, after using dnf to install all the mate packages that were previously installed (I had saved the names of those packages in a different drive). I had no desktop control. Mouse and KB did not work. The one app that automatically came up (due to settings of the mate env) was firefox , and for some reason KB within the FF window worked, but nowhere else. yara ... yara ...yara.. When it rains problems, it pours :) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
On Wed, May 25, 2016 at 2:07 PM, Bill Perkins wrote: > No The hostname did not change that I can see, > and I did not knowingly change it. > > I am wondering why you ask the question? It's embedded in the mdadm superblock, and it might be initrd based auto-activation (metadata 1.x and higher) may fail if the actual host name and the one in the superblock don't match. There is a way to update this information at assemble time with mdadm --assemble --update= But that might be a distraction. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
On 2016.05.25 15:51, Chris Murphy wrote: > Did the hostname change since the array was created? > > -- > Chris Murphy > No The hostname did not change that I can see, and I did not knowingly change it. I am wondering why you ask the question? The host name is redwood. Chris, I am still working on a reply to your previous message. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
Did the hostname change since the array was created? -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
May 24 00:07:00 redwood.localnet kernel: Command line: BOOT_IMAGE=/vmlinuz-4.4.9-200.fc22.x86_64 root=/dev/mapper/vg0-lv1 ro rd.md.uuid=5a1848ce:cff64c1f:a622dc1f:e5f06d55 LANG=en_US.UTF-8 SYSFONT=True rd.lvm.lv=vg0/lv0 rd.lvm.lv=vg0/lv1 KEYTABLE=us rd.luks=0 rd.dm=0 There is an rd.md.uuid= parameter, so that's good. May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: Could not boot. May 24 00:10:08 redwood.localnet systemd[1]: Received SIGRTMIN+20 from PID 349 (plymouthd). May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: /dev/mapper/vg0-lv1 does not exist May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: /dev/vg0/lv0 does not exist May 24 00:10:08 redwood.localnet dracut-initqueue[347]: Warning: /dev/vg0/lv1 does not exist May 24 00:10:08 redwood.localnet systemd[1]: Starting Dracut Emergency Shell... OK so yeah, it's basically not finding rootfs. 29 seconds later... May 24 00:10:37 redwood.localnet kernel: md: md0 stopped. May 24 00:10:37 redwood.localnet kernel: md: bind May 24 00:10:37 redwood.localnet kernel: md: bind May 24 00:10:37 redwood.localnet kernel: md: raid1 personality registered for level 1 May 24 00:10:37 redwood.localnet kernel: md/raid1:md0: active with 2 out of 2 mirrors May 24 00:10:37 redwood.localnet kernel: md0: detected capacity change from 0 to 262078464 May 24 00:10:37 redwood.localnet kernel: md: md1 stopped. May 24 00:10:37 redwood.localnet kernel: md: bind May 24 00:10:37 redwood.localnet kernel: md: bind May 24 00:10:37 redwood.localnet kernel: md/raid1:md1: active with 2 out of 2 mirrors May 24 00:10:37 redwood.localnet kernel: created bitmap (15 pages) for device md1 May 24 00:10:37 redwood.localnet kernel: md1: bitmap initialized from disk: read 1 pages, set 0 of 29804 bits May 24 00:10:37 redwood.localnet kernel: md1: detected capacity change from 0 to 268632576 May 24 00:10:54 redwood.localnet systemd[1]: Found device /dev/mapper/vg0-lv1. May 24 00:10:54 redwood.localnet systemd[1]: Starting File System Check on /dev/mapper/vg0-lv1... May 24 00:10:54 redwood.localnet systemd-fsck[2685]: /: clean, 529693/1048576 files, 3263599/4194304 blocks May 24 00:10:54 redwood.localnet systemd[1]: Started File System Check on /dev/mapper/vg0-lv1. So now it's found, I'm gonna guess this is your manual attempt at starting up the array? What do you get for cat /proc/mdstat at the dracut prompt before you do anything else? And also the results from mdstat -E /dev/sda1 mdstate -E /dev/sdb1 blkid These can be redirected to fpaste or a file. If you have network access this early it's easiest to redirect to fpaste but I'm not sure if it's in the initramfs. From your mdadm.conf, you have UUIDs that do not match what's on the command line. cmdline: rd.md.uuid=5a1848ce:cff64c1f:a622dc1f:e5f06d55 mdadm.conf UUID=c45384af:aa8fc7ca:7eebaeb8:f0ca1523 UUID=524079c6:521ca76f:126164a9:3232e116 Looks like the mdadm.conf is stale and should be recreated, and recreate the initramfs. Thing is, the rd.md.uuid ought to be enough for dracut to startup that array, the mdadm.conf is really just about assigning a particular md array to a particular /dev/mdX assignment, which by the way has changed recently so there might be confusion going on there. You might just try renaming the current mdadm.conf, or commenting out all of the lines, except for one: ARRAY /dev/md0 UUID=5a1848ce:cff64c1f:a622dc1f:e5f06d55 And after saving it, use dracut -f. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
On 2016.05.24 15:45, Chris Murphy wrote: > On Mon, May 23, 2016 at 11:13 PM, Bill Perkins > wrote: > > > > I have this system that I have been using that was running Fedora > 21. > > I just updated it today (Monday) to Fedora 22. It is an old Dell > > Optiplex GX620 with two 2TB disk drives set up with two partitions > > each in a RAID One configuration. LVM2 runs on top of the second > > partition with several logical volumes. This system had been > running > > just fine before I did the upgrade. After the upgrade, the system > will > > not boot using one of the new Fedora 22 kernels. It boots just > fine > > using one of the old Fedora 21 kernels that did not get replaced > during > > the upgrade. > > > > I can get the system up using one of the new kernels, but I have to > > wait until it stops at a Dracut prompt. I then manual run "mdadm > -- > > assemble --scan" to get the RAID One partitions assembled, and "lvm > > vgchange -a y" to get the Volume Group built. After that, I issue > an > > "exit" and the system completes the boot process. I need to figure > out > > why this system will not boot without intervention. Any > suggestions > > would be appreciated. > > > > I have tried to rebuild the initramfs with dracut, no joy doing > that. > > > > Here is some of the data: > > > > # cat /etc/mdadm.conf > > MAILADDR root > > AUTO +imsm +1.x -all > > ARRAY /dev/md0 metadata=0.90 > UUID=c45384af:aa8fc7ca:7eebaeb8:f0ca1523 > > ARRAY /dev/md1 metadata=1.2 name=test3.localnet:md1 > > UUID=524079c6:521ca76f:126164a9:3232e116 > > > > # cat /etc/fstab > > UUID=5a1848ce-cff6-4c1f-a622-dc1fe5f06d55 /boot ext3 defaults 1 2 > > UUID=762b53d0-b5a0-41dc-b804-d339fa58b119 swap swap defaults 0 0 > > /dev/mapper/vg0-lv1 / ext4 defaults 1 1 > > /dev/mapper/vg0-lv2 /usr/local ext4 defaults 1 2 > > /dev/mapper/vg0-lv3 /varext4 defaults 1 2 > > /dev/mapper/vg0-lv4 /tmpext4 defaults 1 2 > > /dev/mapper/vg0-lv5 /optext4 defaults 1 2 > > /dev/mapper/vg0-lv6 /home ext4 defaults 1 2 > > /dev/mapper/vg0-lv7 /work ext4 defaults 1 2 > > /dev/sr0/cd0auto noauto,owner,user,ro0 0 > > > > # uname -a > > Linux redwood 4.4.9-200.fc22.x86_64 #1 SMP Fri May 6 17:42:20 UTC > 2016 > > x86_64 x86_64 x86_64 GNU/Linux > > Can you put up journalctl -b somewhere? > > > -- > Chris Murphy > > Chris, This link should work: http://roo.grnwood.net/redwood-journal-b-160524.gz Gzip file is 692,498 bytes. Original file is 11,702,620 bytes. Thank you for looking at this problem. Bill -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New kernel will not boot after upgrade from fedora-21 to fedora-22
On Mon, May 23, 2016 at 11:13 PM, Bill Perkins wrote: > > I have this system that I have been using that was running Fedora 21. > I just updated it today (Monday) to Fedora 22. It is an old Dell > Optiplex GX620 with two 2TB disk drives set up with two partitions > each in a RAID One configuration. LVM2 runs on top of the second > partition with several logical volumes. This system had been running > just fine before I did the upgrade. After the upgrade, the system will > not boot using one of the new Fedora 22 kernels. It boots just fine > using one of the old Fedora 21 kernels that did not get replaced during > the upgrade. > > I can get the system up using one of the new kernels, but I have to > wait until it stops at a Dracut prompt. I then manual run "mdadm -- > assemble --scan" to get the RAID One partitions assembled, and "lvm > vgchange -a y" to get the Volume Group built. After that, I issue an > "exit" and the system completes the boot process. I need to figure out > why this system will not boot without intervention. Any suggestions > would be appreciated. > > I have tried to rebuild the initramfs with dracut, no joy doing that. > > Here is some of the data: > > # cat /etc/mdadm.conf > MAILADDR root > AUTO +imsm +1.x -all > ARRAY /dev/md0 metadata=0.90 UUID=c45384af:aa8fc7ca:7eebaeb8:f0ca1523 > ARRAY /dev/md1 metadata=1.2 name=test3.localnet:md1 > UUID=524079c6:521ca76f:126164a9:3232e116 > > # cat /etc/fstab > UUID=5a1848ce-cff6-4c1f-a622-dc1fe5f06d55 /boot ext3 defaults 1 2 > UUID=762b53d0-b5a0-41dc-b804-d339fa58b119 swap swap defaults 0 0 > /dev/mapper/vg0-lv1 / ext4 defaults 1 1 > /dev/mapper/vg0-lv2 /usr/local ext4 defaults 1 2 > /dev/mapper/vg0-lv3 /varext4 defaults 1 2 > /dev/mapper/vg0-lv4 /tmpext4 defaults 1 2 > /dev/mapper/vg0-lv5 /optext4 defaults 1 2 > /dev/mapper/vg0-lv6 /home ext4 defaults 1 2 > /dev/mapper/vg0-lv7 /work ext4 defaults 1 2 > /dev/sr0/cd0auto noauto,owner,user,ro0 0 > > # uname -a > Linux redwood 4.4.9-200.fc22.x86_64 #1 SMP Fri May 6 17:42:20 UTC 2016 > x86_64 x86_64 x86_64 GNU/Linux Can you put up journalctl -b somewhere? -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
New kernel will not boot after upgrade from fedora-21 to fedora-22
I have this system that I have been using that was running Fedora 21. I just updated it today (Monday) to Fedora 22. It is an old Dell Optiplex GX620 with two 2TB disk drives set up with two partitions each in a RAID One configuration. LVM2 runs on top of the second partition with several logical volumes. This system had been running just fine before I did the upgrade. After the upgrade, the system will not boot using one of the new Fedora 22 kernels. It boots just fine using one of the old Fedora 21 kernels that did not get replaced during the upgrade. I can get the system up using one of the new kernels, but I have to wait until it stops at a Dracut prompt. I then manual run "mdadm -- assemble --scan" to get the RAID One partitions assembled, and "lvm vgchange -a y" to get the Volume Group built. After that, I issue an "exit" and the system completes the boot process. I need to figure out why this system will not boot without intervention. Any suggestions would be appreciated. I have tried to rebuild the initramfs with dracut, no joy doing that. Here is some of the data: # cat /etc/mdadm.conf MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md0 metadata=0.90 UUID=c45384af:aa8fc7ca:7eebaeb8:f0ca1523 ARRAY /dev/md1 metadata=1.2 name=test3.localnet:md1 UUID=524079c6:521ca76f:126164a9:3232e116 # cat /etc/fstab UUID=5a1848ce-cff6-4c1f-a622-dc1fe5f06d55 /boot ext3 defaults 1 2 UUID=762b53d0-b5a0-41dc-b804-d339fa58b119 swap swap defaults 0 0 /dev/mapper/vg0-lv1 / ext4 defaults 1 1 /dev/mapper/vg0-lv2 /usr/local ext4 defaults 1 2 /dev/mapper/vg0-lv3 /varext4 defaults 1 2 /dev/mapper/vg0-lv4 /tmpext4 defaults 1 2 /dev/mapper/vg0-lv5 /optext4 defaults 1 2 /dev/mapper/vg0-lv6 /home ext4 defaults 1 2 /dev/mapper/vg0-lv7 /work ext4 defaults 1 2 /dev/sr0/cd0auto noauto,owner,user,ro0 0 # uname -a Linux redwood 4.4.9-200.fc22.x86_64 #1 SMP Fri May 6 17:42:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Other versions of kernels that work just fine: 3.18.9-200 & 4.1.13-100 both from the Fedora 21 distribution. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: New Kernel will not boot
On 04/01/2010 07:03 PM, Lawrence E Graves wrote: > I am having trouble with the installing of the new kernel release about > 2 days ago. When I install it and reboot my system it stops at the > Fedora sign in the middle of the screen. It is hard for me to explain > exactly what is happening because I am not good with the technical terms > used. > If all of the things other friends have guided to you don't work, please just try to login to Run level 1. If/Once you are at the prompt that asks you to login. The issue is caught, login the system using ROOT credentials and check for GDM installation. # rpm -q gdm if this command does not return any thing, please install GDM, it happened with me so considering same with you too. -- Saurabh Sharma Linux user number: 490644 http://sawrub-blog.blogspot.com/ Open your doors...It's time to look beyond Windows -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
Michael Miles wrote: > On 04/01/2010 06:33 AM, Lawrence E Graves wrote: >> I am having trouble with the installing of the new kernel release about >> 2 days ago. When I install it and reboot my system it stops at the >> Fedora sign in the middle of the screen. It is hard for me to explain >> exactly what is happening because I am not good with the technical terms >> used. >> > What are you using for a Video Card. > The problem could be when you updated your kernel your video drivers did > not get updated. You have that backwards, the video drivers did get updated and the ones in the kernel are... I can't find a polite term, let's just say not functional on many display systems. While you can use the vendor drivers in some cases, the quick way to see if this is the problem is to add "nomodeset video=vesafb" to the end of the boot commands after "quiet." That should make almost anything boot if video is the issue. > The proper kernel mod for your kernel must be installed as well as the > driver If you are a gamer, have multiple displays, or have some need for 3D other than because wobbling windows a "kewl," go to it. It is not a requirement for normal operation. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
New Kernel will not boot
On Fri, 2010-04-02 at 02:40 +, users-requ...@lists.fedoraproject.org wrote: > Send users mailing list submissions to > users@lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-requ...@lists.fedoraproject.org > > You can reach the person managing the list at > users-ow...@lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > >1. (no subject) (Don Vogt) >2. Re: FPL steps down: what's the real story? (Rahul Sundaram) >3. Re: (Steven Stern) >4. Re: N wifi broke after kernel update (Mail Lists) >5. (charles zeitler) >6. Re: (Rahul Sundaram) >7. Re: Fox News Channels videos won't play (Aram J. Agajanian) >8. Re: gedit ...cannot create backup !!! (Aram J. Agajanian) >9. Re: FPL steps down: what's the real story? (suvayu ali) > 10. Re: FPL steps down: what's the real story? (Marcel Rieux) > 11. Re: FPL steps down: what's the real story? (Craig White) > 12. Re: Fox News Channels videos won't play (Temlakos) > 13. Re: FPL steps down: what's the real story? (Craig White) > 14. Re: FPL steps down: what's the real story? (Marcel Rieux) > > > -- > > Message: 1 > Date: Thu, 1 Apr 2010 16:10:21 -0700 (PDT) > From: Don Vogt > To: users@lists.fedoraproject.org > Message-ID: <472611.75616...@web84102.mail.mud.yahoo.com> > Content-Type: text/plain; charset=iso-8859-1 > > --- > > > > Message: 1 > > Date: Thu, 1 Apr 2010 21:13:55 +0200 > > From: David Garc?a Granda > > Subject: Re: New Firefox Won't run > > To: Community support for Fedora users > > Message-ID: > > ??? > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Hi Don, > > > > > Yesterday I updated to kernel 2.6.32.9.70 fc12 and to > > firefox-3.5.9-1.fc12 and now firefox won't start. I get a > > notice in the bottom bar for a few seconds and then it goes > > blank. > > > > Strange, I have the same package versions and firefox runs > > fine... > > > > > I tried starting firefox in a terminal and it returned > > "can't load XPCOM" > > > I tried 'locate XPCOM' and it returned some files in > > /usr/lib/VirtualBox and > > /usr/lib/xulrunner-1.9.1/modules/XPCOMUtils.jsm > > > > Uhmmm... I don't have virtualbox installed, so this can > > make the difference. > > > > > I have VirtualBox installed, but I am not trying to > > run firefox in virtualBox, but on the desktop. > > > ?I just found that xulrunner-1.9.1.9-1.fc12 was > > installed at the same time as the new firefox so I suspect > > the problem is between firefox and xulrunner. > > > > I think the problem here is VirtualBox. > > > OK, I will try to remove VirtualBox, if I can figure out how > > > > > > ?I don't know what to try next. I have been using fc12 > > for a long time successfully for quite a while Any help or > > advice would be appreciated. > > > > Is it possible for you to check if XPCOM files related from > > VirtualBox > > conflict with Firefox/xulrunner ones?. Maybe something not > > compatible > > from VirtualBox is loaded instead of the right one. > > I will see what I can figure out about the related files > > > > > HTH, > > > > David > > > > > > > > > Message: 13 > > Date: Thu, 1 Apr 2010 14:20:42 -0700 > > From: suvayu ali > > Subject: Re: New Firefox Won't run > > To: Community support for Fedora users > > Message-ID: > > ??? > > Content-Type: text/plain; charset=ISO-8859-1 > > > > On 1 April 2010 12:13, David Garc?a Granda > > wrote: > > > Hi Don, > > > > > >> Yesterday I updated to kernel 2.6.32.9.70 fc12 and > > to firefox-3.5.9-1.fc12 and now firefox won't start. I get a > > notice in the bottom bar for a few seconds and then it goes > > blank. > > > > > > Strange, I have the same package versions and firefox > > runs fine... > > > > > >> I tried starting firefox in a terminal and it > > returned "can't load XPCOM" > > >> I tried 'locate XPCOM' and it returned some files > > in /usr/lib/VirtualBox and > > /usr/lib/xulrunner-1.9.1/modules/XPCOMUtils.jsm > > > > > > Uhmmm... I don't have virtualbox installed, so this > > can make the difference. > > > > > >> I have VirtualBox installed, but I am not trying > > to run firefox in virtualBox, but on the desktop. > > >> ?I just found that xulrunner-1.9.1.9-1.fc12 was > > installed at the same time as the new firefox so I suspect > > the problem is between firefox and xulrunner. > > > > > > I think the problem here is VirtualBox. > > > > > > > It is improper methodology to start blaming other "most > > unlikely" > > packages before going through the proper troubleshooting > > steps. I > > don't have VBox installed and that file is there in my > > system. > > xulrunn
Re: New Kernel will not boot
Lawrence E Graves wrote: > I don't know how I can explain this problem. I am not able to record it > or take picture of it a part of problem with computers is that people tend to forget what pencils and paper are for. > there is just too much information on the screen. _normally_, everything you see on screen is not related to why system did not boot. therefore, posting last 4 or 5 lines on screen may get you help you need. also, try booting to level 3, then level 1 to see if system stops. if you can boot level 3 or 1, have a look in '/var/log' to see what is in files 'boot.log', 'dmesg' and 'messages'. if you can not boot level 3 or 1, boot with a previous kernel, or, installation cd/dvd in rescue mode, or, a live cd/dvd, mount drive/partition failing system is on and read above files to see what they show. hth. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today. ** to mess up a linux box, you need to work at it. to mess up an ms windows box, you just need to *look* at it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
Am Donnerstag, den 01.04.2010, 07:33 -0600 schrieb Lawrence E Graves: > When I install it and reboot my system it stops at the > Fedora sign in the middle of the screen. Press the ESC key to see any messages. Maybe https://bugzilla.redhat.com/show_bug.cgi?id=578217 applies to you. Greets. -- Rodolfo Alcazar Portillo - nosp...@gmail.com otbits.blogspot.com / counter.li.org: #367962 -- The Microsoft Torque Wrench: what do you want to shear today? -- Malcolm Ray -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
New Kernel will not boot
I don't know how I can explain this problem. I am not able to record it or take picture of it and there is just too much information on the screen. If I can be told what to look for, this might help fix the problem. I really don't know what to do.:-S Lawrence E Graves -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On Thu, 2010-04-01 at 15:45 +0100, Michal wrote: > On 01/04/2010 15:18, Bruno Wolff III wrote: > > On Thu, Apr 01, 2010 at 07:33:09 -0600, > > Lawrence E Graves wrote: > >> I am having trouble with the installing of the new kernel release about > >> 2 days ago. When I install it and reboot my system it stops at the > >> Fedora sign in the middle of the screen. It is hard for me to explain > >> exactly what is happening because I am not good with the technical terms > >> used. > > > > When you report issues like this please state the kernel version you are > > using. New kernels come out pretty often and even if we new which Fedora > > release you are using, we wouldn't be sure which kernel version you are > > using. > > I have seen this, if memory serves correct while it's doing this you can > press F7 or F8 (I can't remember which) and it shows text instead of an > image. It could have trouble starting a service or running chkdsk. Do > this and say where it is stuck. Press Esc (Escape) for console messages. Also, chkdsk is a Windows utility. I presume you mean fsck. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On 04/01/2010 06:33 AM, Lawrence E Graves wrote: > I am having trouble with the installing of the new kernel release about > 2 days ago. When I install it and reboot my system it stops at the > Fedora sign in the middle of the screen. It is hard for me to explain > exactly what is happening because I am not good with the technical terms > used. > Next time you boot, hold down Ctrl at the bios screen -- it will let you select which kernel version to boot. Most likely, the kernel version you can't boot is 2.6.32.10-90 -- I'm having problems with it as well. Specifically, on 2 Dell laptops, one using nvidia driver, another one using open source radeon driver. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On 04/01/2010 08:18 AM, Bruno Wolff III wrote: > dell inspiron e1705 The former laptop has a Ati chipset and the 1705 has a Nvidia chipset. I would suggest it is the Video driver setup that is causing the problem Whenever I do a update that has a new kernel the kernel mod must be installed for the new kernel Nvidia 195.36 proprietary driver need mod for kernel 2.6.32.10-90 Same for Ati drivers -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On 04/01/2010 06:33 AM, Lawrence E Graves wrote: > I am having trouble with the installing of the new kernel release about > 2 days ago. When I install it and reboot my system it stops at the > Fedora sign in the middle of the screen. It is hard for me to explain > exactly what is happening because I am not good with the technical terms > used. > What are you using for a Video Card. The problem could be when you updated your kernel your video drivers did not get updated. The proper kernel mod for your kernel must be installed as well as the driver Michael -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On Thu, Apr 01, 2010 at 08:35:19 -0600, Lawrence E Graves wrote: > On Thu, 2010-04-01 at 09:18 -0500, Bruno Wolff III wrote: > > On Thu, Apr 01, 2010 at 07:33:09 -0600, > > Lawrence E Graves wrote: > > > I am having trouble with the installing of the new kernel release about > > > 2 days ago. When I install it and reboot my system it stops at the > > > Fedora sign in the middle of the screen. It is hard for me to explain > > > exactly what is happening because I am not good with the technical terms > > > used. > > > > When you report issues like this please state the kernel version you are > > using. New kernels come out pretty often and even if we new which Fedora > > release you are using, we wouldn't be sure which kernel version you are > > using. > I guess that would make sense. With all that you have going on, being > precise would help. The kernel I am talking about is > 2.6.32.10-90.fc12.x86_64. I am trying to install it on dell inspiron > 1501 and dell inspiron e1705. Is this enough information? Please let me > know. > I am trying to learn. I am going to push this back over to the users list so that other can see the information. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On 01/04/2010 15:18, Bruno Wolff III wrote: > On Thu, Apr 01, 2010 at 07:33:09 -0600, > Lawrence E Graves wrote: >> I am having trouble with the installing of the new kernel release about >> 2 days ago. When I install it and reboot my system it stops at the >> Fedora sign in the middle of the screen. It is hard for me to explain >> exactly what is happening because I am not good with the technical terms >> used. > > When you report issues like this please state the kernel version you are > using. New kernels come out pretty often and even if we new which Fedora > release you are using, we wouldn't be sure which kernel version you are > using. I have seen this, if memory serves correct while it's doing this you can press F7 or F8 (I can't remember which) and it shows text instead of an image. It could have trouble starting a service or running chkdsk. Do this and say where it is stuck. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On Thu, Apr 01, 2010 at 07:33:09 -0600, Lawrence E Graves wrote: > I am having trouble with the installing of the new kernel release about > 2 days ago. When I install it and reboot my system it stops at the > Fedora sign in the middle of the screen. It is hard for me to explain > exactly what is happening because I am not good with the technical terms > used. When you report issues like this please state the kernel version you are using. New kernels come out pretty often and even if we new which Fedora release you are using, we wouldn't be sure which kernel version you are using. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: New Kernel will not boot
On Thu, Apr 1, 2010 at 9:33 AM, Lawrence E Graves wrote: > I am having trouble with the installing of the new kernel release about > 2 days ago. When I install it and reboot my system it stops at the > Fedora sign in the middle of the screen. It is hard for me to explain > exactly what is happening because I am not good with the technical terms > used. Immediately before Fedora boots, you should see a countdown of a few seconds. Hit ESC or some key and you will see a menu. - This is a menu of kernels installed. On the trouble kernel, hit the 'E' key to EDIT the current kernel options. Scroll to the right of the 'kernel' line. Remove the following 2 words: quiet rhgb After you remove those words, hit ENTER, then B (to boot). This should provide some information as to what is happening when the system locks up. What error or messages do you see when it stops. Alternatively in the menu you can select your previous kernel to boot so you can access your system. -- Mauriat Miranda http://www.mjmwired.net/linux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
New Kernel will not boot
I am having trouble with the installing of the new kernel release about 2 days ago. When I install it and reboot my system it stops at the Fedora sign in the middle of the screen. It is hard for me to explain exactly what is happening because I am not good with the technical terms used. -- Lawrence E Graves -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
