users September 2018

users@lists.fedoraproject.org

104 participants
108 discussions

Startup messages shown twice on EFI boot
by Richard Shaw 04 Sep '18

04 Sep '18

For some time now (i.e. multiple Fedora releases) I've noticed that on two of my laptops that use EFI instead of BIOS booting, all of the startup lines from SystemD are shown twice. No big issue but o a whim I decided to google the problem and couldn't find much. I can't be the only person that's seen this though... Any easy fix known? Thanks, Richard

5 5

Problem with copying files to externel USB connected disk
by Joerg Lechner 02 Sep '18

02 Sep '18

Hi, I copy frequently TV films from my internal disk to an usb connected external disk. This is ok for let's say a bunch of 20GB. Then there occurs a situation where one film is not copied and the system has to be shut down and rebooted again to continue. But the film, which blocked the system, can not be copied again. But it can be handled with windows 8.1. Is there a cache or other "memory system" in Fedora (i.e. F28), which can be deleted, so hat Fedora can copy this blocking film again? I have a similar problem in Windows 8.1, but his is solved, when I reboot Windows. My system: Acer Laptop Aspire E15 E5-571G, cheap USB adapter to an external disk (old internal disk used as external disk with usb adapter). Windows 8.1 on the laptop internal disk, F28 on an USB 3.0 32GB Flash medium. Kind regards

5 10

Noveau crashes / How to restart automatically
by Javier Perez 02 Sep '18

02 Sep '18

Hi Noveau is crashing frequently, mostly whenever I run Civ 4 under wine. The error looks like "nouveau 0000:01:00.0: Xorg[5268]: nv50cal_space: -16" I have seen something similar in bugzilla so I hope they solve it. Meanwhile, each time it happens, the whole graphical system freezes and I have to do a "systemctl restart lightdm.service" from a remote ssh session because mouse and keyboard become unresponsive. My question is, how can I do this automatically. Is there an efficient way to monitor if noveau crashes and send the restart sequence? I think I could cook a some sort of journalctl -f > "something" but it seems too much like brute force. Is there any trigger or something that could be applied in journal or somewhere else to pick up this kind of situations? Thanks -- ------------------------------ /\_/\ |O O| pepebuho(a)gmail.com ~~~~ Javier Perez ~~~~ While the night runs ~~~~ toward the day... m m Pepebuho watches from his high perch.

2 2

Update of cockpit-ws kills networking
by Richard Shaw 02 Sep '18

02 Sep '18

This has been going on for a while but to took several times before I narrowed down which package was the cause. Basically, whenever the cockpit-ws package is updated, I loose all networking. No amount of turning ethernet off and on or restarting NetworkManager brings it back. My only choice thus far has been to reboot. I haven't been able to recreate this in a VM so I'm confused as to what specifically is different in my system that this has started happening. Thoughts? Thanks, Richard

1 0

Weirdness with new kernel
by Robert Moskowitz 01 Sep '18

01 Sep '18

I *think* I did a shutdown Friday instead of a suspend, as I had to powerup this evening instead of resume. I will check back into the logs. So given this was a fresh boot (kernel 4.17.144), I did a dnf update and got a new kernel (4.17.19). I rebooted, and it would not boot up. I was seeing repeating messages scrolling on the screen, but really too fast to read. So I tried booting from the prior kernel (4.17.14), but it now would not boot up either and looked like the same failure messages. So I booted into rescue mode, providing the root password. Still plenty of space on /boot, so that was not the problem. Looked at messages and found a bunch of dracut failures. So I grepped on all dracut messages (see some below), and it looked like rescue mode had rescued dracut. So I rebooted into 4.17.19 and it worked. Which is why I am able to send this email. So warning, something with 4.17.19 kernel update, or at least from 4.17.14. If it looks wrong and keeps looping on messages, try rescue mode. Here are the dracut messages from today. If I get any requests, I can perhaps dig for other info: Sep 1 21:26:04 lx121e dracut-cmdline[157]: dracut-28 (Twenty Eight) dracut-048-14.git20180726.fc28 Sep 1 21:26:04 lx121e dracut-cmdline[157]: Using kernel command line parameters: BOOT_IMAGE=/vmlinuz-4.17.14-202.fc28.x86_64 root=UUID=5991a70b-e2d5-40dc-8014-87752b69e93b ro resume=UUID=a1fc25b5-62d8-4f90-8eb5-bf097e9c813a rhgb quiet LANG=en_US.UTF-8 Sep 1 21:26:04 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-cmdline comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:04 lx121e systemd[1]: Started dracut cmdline hook. Sep 1 21:26:04 lx121e kernel: audit: type=1130 audit(1535851564.397:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-cmdline comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:04 lx121e systemd[1]: Starting dracut pre-udev hook... Sep 1 21:26:04 lx121e systemd[1]: Started dracut pre-udev hook. Sep 1 21:26:04 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-udev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:04 lx121e kernel: audit: type=1130 audit(1535851564.497:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-udev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:04 lx121e systemd[1]: Starting dracut initqueue hook... Sep 1 21:26:07 lx121e kernel: audit: type=1130 audit(1535851567.702:16): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:07 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:07 lx121e systemd[1]: Started dracut initqueue hook. Sep 1 21:26:08 lx121e systemd[1]: Starting dracut pre-pivot and cleanup hook... Sep 1 21:26:08 lx121e systemd[1]: Started dracut pre-pivot and cleanup hook. Sep 1 21:26:08 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-pivot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e kernel: audit: type=1130 audit(1535851568.394:20): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-pivot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e systemd[1]: Stopped dracut pre-pivot and cleanup hook. Sep 1 21:26:08 lx121e audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-pivot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e systemd[1]: Stopped dracut initqueue hook. Sep 1 21:26:08 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e systemd[1]: Stopped dracut pre-udev hook. Sep 1 21:26:08 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-udev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-udev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e systemd[1]: Stopped dracut cmdline hook. Sep 1 21:26:08 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-cmdline comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:08 lx121e audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-cmdline comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:16 lx121e kernel: audit: type=1130 audit(1535851576.274:80): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:26:16 lx121e audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 1 21:49:46 lx121e dracut[18387]: dracut-048-14.git20180726.fc28 Sep 1 21:49:47 lx121e dracut[18389]: Executing: /usr/bin/dracut -f /boot/initramfs-4.17.19-200.fc28.x86_64.img 4.17.19-200.fc28.x86_64 Sep 1 21:49:48 lx121e dracut[18389]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! Sep 1 21:49:49 lx121e dracut[18389]: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found! Sep 1 21:49:49 lx121e dracut[18389]: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! Sep 1 21:49:50 lx121e dracut[18389]: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! Sep 1 21:49:50 lx121e dracut[18389]: dracut module 'stratis' will not be installed, because command 'stratisd-init' could not be found! Sep 1 21:49:51 lx121e dracut[18389]: *** Including module: bash *** Sep 1 21:49:51 lx121e dracut[18389]: *** Including module: systemd *** Sep 1 21:49:53 lx121e dracut[18389]: *** Including module: systemd-initrd *** Sep 1 21:49:53 lx121e dracut[18389]: *** Including module: nss-softokn *** Sep 1 21:49:53 lx121e dracut[18389]: *** Including module: i18n *** Sep 1 21:49:54 lx121e dracut[18389]: *** Including module: network *** Sep 1 21:49:55 lx121e dracut[18389]: *** Including module: ifcfg *** Sep 1 21:49:55 lx121e dracut[18389]: *** Including module: drm *** Sep 1 21:49:58 lx121e dracut[18389]: *** Including module: plymouth *** Sep 1 21:50:00 lx121e dracut[18389]: *** Including module: kernel-modules *** Sep 1 21:50:03 lx121e dracut[18389]: *** Including module: kernel-network-modules *** Sep 1 21:50:03 lx121e dracut[18389]: *** Including module: resume *** Sep 1 21:50:03 lx121e dracut[18389]: *** Including module: rootfs-block *** Sep 1 21:50:04 lx121e dracut[18389]: *** Including module: terminfo *** Sep 1 21:50:04 lx121e dracut[18389]: *** Including module: udev-rules *** Sep 1 21:50:04 lx121e dracut[18389]: Skipping udev rule: 40-redhat.rules Sep 1 21:50:04 lx121e dracut[18389]: Skipping udev rule: 50-firmware.rules Sep 1 21:50:04 lx121e dracut[18389]: Skipping udev rule: 50-udev.rules Sep 1 21:50:05 lx121e dracut[18389]: Skipping udev rule: 91-permissions.rules Sep 1 21:50:05 lx121e dracut[18389]: Skipping udev rule: 80-drivers-modprobe.rules Sep 1 21:50:05 lx121e dracut[18389]: *** Including module: dracut-systemd *** Sep 1 21:50:05 lx121e dracut[18389]: *** Including module: usrmount *** Sep 1 21:50:05 lx121e dracut[18389]: *** Including module: base *** Sep 1 21:50:05 lx121e dracut[18389]: *** Including module: fs-lib *** Sep 1 21:50:06 lx121e dracut[18389]: *** Including module: shutdown *** Sep 1 21:50:06 lx121e dracut[18389]: *** Including modules done *** Sep 1 21:50:06 lx121e dracut[18389]: *** Installing kernel module dependencies *** Sep 1 21:50:07 lx121e dracut[18389]: *** Installing kernel module dependencies done *** Sep 1 21:50:07 lx121e dracut[18389]: *** Resolving executable dependencies *** Sep 1 21:50:11 lx121e dracut[18389]: *** Resolving executable dependencies done*** Sep 1 21:50:11 lx121e dracut[18389]: *** Hardlinking files *** Sep 1 21:50:11 lx121e dracut[18389]: *** Hardlinking files done *** Sep 1 21:50:11 lx121e dracut[18389]: *** Stripping files *** Sep 1 21:50:11 lx121e dracut[18389]: *** Stripping files done *** Sep 1 21:50:11 lx121e dracut[18389]: *** Generating early-microcode cpio image *** Sep 1 21:50:11 lx121e dracut[18389]: *** Constructing AuthenticAMD.bin **** Sep 1 21:50:12 lx121e dracut[18389]: *** Store current command line parameters *** Sep 1 21:50:12 lx121e dracut[18389]: *** Creating image file '/boot/initramfs-4.17.19-200.fc28.x86_64.img' *** Sep 1 21:50:56 lx121e dracut[18389]: *** Creating initramfs image file '/boot/initramfs-4.17.19-200.fc28.x86_64.img' done ***

1 0

Very odd solitaire glitch just now
by Tom Horsley 01 Sep '18

01 Sep '18

I try to start freecell solitaire. Nothing happens for about 30 seconds, then the window pops up. I run it under strace and see it getting bazillions of FUTEX_WAIT_PRIVATE resource temporarily unavail errors when I'm waiting for it to come up. I decide it maybe needs a fresh start, so I "dnf update" the system which gets me a new kernel among other things, reboot the system, and now it pops right up. Is the nvidia driver leaking futexs or something? Anyone ever seen anything like this before? Just sort of curious (up to the point where I have to reboot much more frequently to make it stop).

1 0

Unable to restore LVM metadata.
by David Scriven 01 Sep '18

01 Sep '18

I'm afraid this is a very long post, but I need to describe the situation: I had one disk fail out of two and in trying to restore the home directory on the primary I erased the lvm directory data I was trying to keep: root@localhost-live ~]# pvscan WARNING: Device for PV F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 not found or rejected by a filter. PV /dev/sda2 VG vg_debussy lvm2 [931.00 GiB / 0 free] PV [unknown] VG vg_debussy lvm2 [931.50 GiB / 0 free] Total: 2 [<1.82 TiB] / in use: 2 [<1.82 TiB] / in no VG: 0 [0 ] [root@localhost-live ~]# vgscan Reading volume groups from cache. WARNING: Device for PV F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 not found or rejected by a filter. Found volume group "vg_debussy" using metadata type lvm2 [root@localhost-live ~]# lvs WARNING: Device for PV F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 not found or rejected by a filter. LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_home vg_debussy -wi-----p- 1.75t lv_root vg_debussy -wi-a----- 50.00g lv_swap vg_debussy -wi-ao---- <17.69g [root@localhost-live ~]# lvscan WARNING: Device for PV F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 not found or rejected by a filter. ACTIVE '/dev/vg_debussy/lv_root' [50.00 GiB] inherit inactive '/dev/vg_debussy/lv_home' [1.75 TiB] inherit ACTIVE '/dev/vg_debussy/lv_swap' [<17.69 GiB] inherit [root@localhost-live ~]# pvdisplay WARNING: Device for PV F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 not found or rejected by a filter. --- Physical volume --- PV Name /dev/sda2 VG Name vg_debussy PV Size 931.02 GiB / not usable 24.00 MiB Allocatable yes (but full) PE Size 32.00 MiB Total PE 29792 Free PE 0 Allocated PE 29792 PV UUID KSk5KO-Su5d-H8LO-a8t0-s8gH-WdWA-DXQZTr --- Physical volume --- PV Name [unknown] VG Name vg_debussy PV Size 931.51 GiB / not usable 12.00 MiB Allocatable yes (but full) PE Size 32.00 MiB Total PE 29808 Free PE 0 Allocated PE 29808 PV UUID F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 So at this point I tried to get rid of the disk that was no longer there - BIG MISTAKE! root@localhost-live ~]# vgreduce --removemissing --force vg_debussy WARNING: Device for PV F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 not found or rejected by a filter. WARNING: Removing partial LV vg_debussy/lv_home. Logical volume "lv_home" successfully removed Wrote out consistent volume group vg_debussy. [root@localhost-live ~]# pvdisplay --- Physical volume --- PV Name /dev/sda2 VG Name vg_debussy PV Size 931.02 GiB / not usable 24.00 MiB Allocatable yes PE Size 32.00 MiB Total PE 29792 Free PE 27626 Allocated PE 2166 PV UUID KSk5KO-Su5d-H8LO-a8t0-s8gH-WdWA-DXQZTr [root@localhost-live ~]# lvscan ACTIVE '/dev/vg_debussy/lv_root' [50.00 GiB] inherit ACTIVE '/dev/vg_debussy/lv_swap' [<17.69 GiB] inherit OK I got a blank disk and tried to recreate the missing PV: [root@localhost-live ~]# pvcreate --uuid "F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1" --restorefile /etc/lvm/archive/vg_debussy_00000-611197733.vg /dev/sdc1 Couldn't find device with uuid F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1. WARNING: ext4 signature detected on /dev/sdc1 at offset 1080. Wipe it? [y/n]: y Wiping ext4 signature on /dev/sdc1. Physical volume "/dev/sdc1" successfully created. [root@localhost-live ~]# pvscan PV /dev/sda2 VG vg_debussy lvm2 [931.00 GiB / 863.31 GiB free] PV /dev/sdc1 lvm2 [<1.82 TiB] Total: 2 [<2.73 TiB] / in use: 1 [931.00 GiB] / in no VG: 1 [<1.82 TiB] [root@localhost-live ~]# pvdisplay --- Physical volume --- PV Name /dev/sda2 VG Name vg_debussy PV Size 931.02 GiB / not usable 24.00 MiB Allocatable yes PE Size 32.00 MiB Total PE 29792 Free PE 27626 Allocated PE 2166 PV UUID KSk5KO-Su5d-H8LO-a8t0-s8gH-WdWA-DXQZTr "/dev/sdc1" is a new physical volume of "<1.82 TiB" --- NEW Physical volume --- PV Name /dev/sdc1 VG Name PV Size <1.82 TiB Allocatable NO PE Size 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID F3lvXa-42cI-6Tx2-hmSr-3E0M-0PFE-W7kLj1 So - vgcfgrestore should work now? - NO! [root@localhost-live ~]# vgcfgrestore vg_debussy -f /etc/lvm/archive/vg_debussy_00000-611197733.vg Cannot restore Volume Group vg_debussy with 1 PVs marked as missing. Restore failed. So there is nothing missing but the PV is still marked as missing?? I'm stuck I have simply no idea how to proceed. DS

2 1

tip: found a flash drive for direct install
by ToddAndMargo 01 Sep '18

01 Sep '18

Hi All, I finally found a flash drive I like for installing Fedora directly (not live). Flash drives break down when a lot of small files go fly around and bog the OS down and often corrupt. I have had issues with both Kanguru and Kingston drives. I also test a Patriot drive. They goof around with parameters so that large file transfers give good numbers at the expense of small file transfers being so bad the stick almost unusable. Fedora on a Patriot was a joke. On a lark I tried a Samsung MUF-64BE3/AM and a Samsung MUF-64DA1/WW. Both are USB 3.1. And Wow. On two customer machines running USB 2, they preformed flawlessly. Actually even faster than the native Windows. And no corruptions and no ten minutes to shutdown Firefox. On my own USB 3.0 machine, they ran almost as 1/2 as fast as native (I have an NVMe drive). Both these guys ate Fedora 28 Xfce x64 alive, meaning it handled multiple small file transfers with ease. Anyone want to know the special tweaks to run off a USB drive, drop me a line. -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 2