Re: dnf upgrade to F26
On 08/27/2017 12:54 PM, jarmo wrote: > Sat, 26 Aug 2017 17:32:40 -0700 > Paolo Galtieri kirjoitti: > >> and here is where things went weird, there was no output at all on >> the monitor. The disk light was flashing, so something was going on, >> but nothing showed up on the monitor. After a while the disk light > I have had this. Found, tha If I use HDMI, I don't see any output > in monitor. > Second time, I took VGA cable, connected that into monitor and got > output ok. > > First time I just waited and dnf rebooted automatically and my HDMI > connected monitor played well again. > FWIW, my main monitor is connected via HDMI. My secondary monitor is connected via Display Port. During the upgrade from F25 to F26 (and prior upgrades) I always got the progress output to my HDMI connected monitor. -- Fedora Users List - The place to go to speculate endlessly signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: dnf upgrade to F26
Sat, 26 Aug 2017 17:32:40 -0700 Paolo Galtieri kirjoitti: > and here is where things went weird, there was no output at all on > the monitor. The disk light was flashing, so something was going on, > but nothing showed up on the monitor. After a while the disk light I have had this. Found, tha If I use HDMI, I don't see any output in monitor. Second time, I took VGA cable, connected that into monitor and got output ok. First time I just waited and dnf rebooted automatically and my HDMI connected monitor played well again. Jarmo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Installing F26; Question about ks.cfg when raid1 is used
On Sat, 26 Aug 2017 13:06:43 -0500
D&R wrote:
> On Mon, 21 Aug 2017 22:19:05 -0500
> D&R wrote:
>
> > On Sat, 19 Aug 2017 17:18:53 -0500
> > dwoody5...@gmail.com wrote:
> >
> > > On Wed, 9 Aug 2017 14:27:07 -0700
> > > Rick Stevens wrote:
> > >
> > > > On 08/09/2017 12:08 PM, D&R wrote:
> > > > > On Wed, 9 Aug 2017 12:00:00 -0700
> > > > > Rick Stevens wrote:
> > > > >
> > > > >> On 08/09/2017 11:52 AM, D&R wrote:
> > > > >>> When I boot into the install there is an error in the destination
> > > > >>> section.
> > > > >>>
> > > > >>> I looked at the debug info in the storage.log and there was an
> > > > >>> error about sdb1 did not exist. But...
> > > > >>>
> > > > >>> When I reboot to F24 then ...
> > > > >>>
> > > > >>> cat /proc/mdstat
> > > > >>>
> > > > >>> md126 : active raid1 sda2[2] sdb2[1]
> > > > >>> 961261568 blocks super 1.2 [2/2] [UU]
> > > > >>> bitmap: 2/8 pages [8KB], 65536KB chunk
> > > > >>>
> > > > >>> md127 : active raid1 sdb1[1] sda1[2]
> > > > >>> 15368064 blocks super 1.0 [2/2] [UU]
> > > > >>> bitmap: 1/1 pages [4KB], 65536KB chunk
> > > > >>>
> > > > >>> The section of ks.cfg for hard drive setup is as follows:
> > > > >>>
> > > > >>> ignoredisk --only-use=sda,sdb
> > > > >>> bootloader --location=mbr --boot-drive=sda
> > > > >>>
> > > > >>> # Partition clearing information
> > > > >>> clearpart --none --initlabel
> > > > >>>
> > > > >>> # Disk partitioning information
> > > > >>>
> > > > >>> part raid.6 --fstype=mdmember --noformat --onpart=sda1
> > > > >>> part raid.27 --fstype=mdmember --noformat --onpart=sdb1
> > > > >>> part raid.14 --fstype=mdmember --noformat --onpart=sda2
> > > > >>> part raid.32 --fstype=mdmember --noformat --onpart=sdb2
> > > > >>>
> > > > >>> raid / --device=root --fstype=ext4 --level=raid1 --useexisting
> > > > >>> raid /home --device=home --fstype=ext4 --level=raid1 --noformat
> > > > >>> --useexisting
> > > > >>>
> > > > >>> I currently have a raid1 setup with 2 drives sda and sdb
> > > > >>>
> > > > >>> Since I am using the option --useexisting do I still need to use
> > > > >>> the part commands?
> > > > >>>
> > > > >>> The last time I did an upgrade was to F24 I have not found anything
> > > > >>> that says the syntax has changed.
> > > > >>>
> > > > >>> Any Ideas?
> > > > >>
> > > > >> Uhm, when you're booting the install, is it possible that the CD/DVD
> > > > >> you're booting from becomes /dev/sda? If so, then your first hard
> > > > >> drive is /dev/sdb and the second is /dev/sdc and the
> > > > >>
> > > > >> ignoredisk --only-use=sda,sdb
> > > > >>
> > > > >> would block using the second hard drive, since it's /dev/sdc at this
> > > > >> time. This is just a wild guess.
> > > > >
> > > > > I am booting from an iso file from another computer. As I recall that
> > > > > is what I did when I installed F24 over F22.
> > > >
> > > > How are you booting an ISO file from another computer? Is this a
> > > > network kickstart install, where the iso image is located on an NFS or
> > > > CIFS server?
> > > >
> > > > Whatever it is, can you boot it again without invoking kickstart? If
> > > > you can, open up a command line window and do "fdisk -l", which should
> > > > list the disks the system sees. Verify the devices are the ones you
> > > > think they are. Remember that when you're booting F24 from the hard
> > > > disk, you are absolutely making /dev/sda the first hard drive. When
> > > > booting from the network, a CD/DVD or a bootp server, that may NOT be
> > > > the case and your drive letters may be different, in which the limits
> > > > in your "ignoredisk" line would prevent finding the second drive.
> > >
> > > Sorry it took so long to reply, I was out of town on vacation.
> > > However, I copied the Server iso for F24, F25, F26 to the home directory
> > > on a second computer. The directory listings is:
> > > -rw-r--r--. 1 root root 2401239040 Aug 17
> > > 21:33 /home/Fedora-Server-dvd-x86_64-26-1.5.iso -rw-r--r--. 1 root root
> > > 2018508800 Aug 19 14:49 /home/Fedora-Server-dvd-x86_64-25-1.3.iso
> > > -rw-r--r--. 1 root root 1868562432 Aug 19
> > > 16:28 /home/Fedora-Server-dvd-x86_64-24-1.2.iso
> > >
> > > The grub.cfg is setup up as:
> > >
> > > menuentry 'Remote Install' {
> > > load_video
> > > set gfxpayload=keep
> > > insmod gzio
> > > insmod part_msdos
> > > insmod diskfilter
> > > insmod mdraid1x
> > > insmod ext2
> > > set root='hd0,msdos1'
> > > echo'Loading Linux'
> > > # linux16 /boot/vmlinuz-remote acpi=off audit=0 selinux=0
> > >
> > > inst.repo=nfs:10.10.1.2:/home/Fedora-Server-dvd-x86_64-24-1.2.iso
> > > ramdisk_size=8192 panic=30
> > > linux16 /boot/vmlinuz-remote acpi=off audit=0 selinux=0
> > > inst.repo=nfs:10.10.1.2:/home/Fedora-Server-dvd-x86_64-25-1.3.iso
> > > ramdisk_size=8192 panic=30
> > > echo 'Loading initial ramdisk ...'
> > > initrd16 /boot/initrd-remote.img }
> > >
> > > F24
Re: dnf upgrade to F26
Paolo Galtieri writes: I tried to upgrade one of my systems to F26 according to the documentation at https://fedoraproject.org/wiki/DNF_system_upgrade I did the download and everything went fine. I then did sudo dnf system-upgrade reboot and here is where things went weird, there was no output at all on the monitor. The disk light was flashing, so something was going on, but nothing showed up on the monitor. After a while the disk light stopped flashing, and I assumed it was time to reboot. I rebooted, but nothing A successful upgrade reboots automatically. You never need to manually force- reboot an upgrade. Anyone know what I need to do to fix this system? There are 2 other systems It is certainly possible that you hit some kind of a bug that prevented the upgrade from either starting or successfully completing. But by force-rebooting you just made things worse. All signs are that the upgrade was in progress, but by force-rebooting you ended up with a completely messed-up, half-upgraded system. Experiences vary wildly, but, for example, one of my servers does not use rhgb, so the normal boot environment is text-only, and system upgrades are the same. However with that server's hardware text output to the system console is slow, and the last part of a system upgrade runs for about an hour with nothing happening but "Verifying " slowly being printed to the console, one by one for every one of the two thousand-odd packages that were just upgraded. No disk activity. Of course, the situation you described is slightly different - no terminal output whatsoever. But the point is that there are times during a large system upgrade that pass by with no apparent disk activity. I would not attempt to interrupt an upgrade for at least 3-4 hours, after seeing nothing happening. Anyway, if something truly prevented the upgrade from getting started, I would've expected little or no changes to have actually occured, and the system being mostly undamaged; but based on your description, it's very likely that you interrupted a full system upgrade in the middle, with most packages being half installed, or uninstalled. Basically, the whole system is hosed. Unfortunately there is no magic button anywhere someone can push, and fix a busted upgrade of this kind. Botched upgrades can often be recovered, by carefully investigating the state of the system, by using an install image to boot into recovery, and then picking apart the flaming wreckage. Once I accidentally SIGKILLed a regular "dnf upgrade". Not a full system upgrade, but a fairly large update, with several hundred packages. It was a mess, but it was recoverable. Unfortunately, as I said, there's no recipe for recovering from this kind of a botched system. The recovery process involves direct examination of the state of the crapped out system, and figuring out how to fix it. I want to upgrade, but after this experience I'm hesitant to go ahead with the others. This system is my test system so there's nothing important on it. Any help is appreciated. I would suggest wiping the test system, installing F25, installing all updates, then once against attempting an system upgrade to F26, but keeping careful notes this time. I do concur that F26 turned out to be one of those occasional, painful upgrades. The new version of qemu has some kind of a bug that fraks up guest VM reboots, causing my Windows 10 guests to reboot into a bizarre recovery mode, then claiming that the virtual disk is completely corrupted. Which is a bald-faced lie, there is nothing wrong with it. But I didn't figure it out until I already wiped one of my Windows 10 guest images, and reinstalled it from scratch. Still rather teed off, on that account. But that's what's life on the bleeding edge is all about… pgpMKKtDJUFAF.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
dnf upgrade to F26
I tried to upgrade one of my systems to F26 according to the documentation at https://fedoraproject.org/wiki/DNF_system_upgrade I did the download and everything went fine. I then did sudo dnf system-upgrade reboot and here is where things went weird, there was no output at all on the monitor. The disk light was flashing, so something was going on, but nothing showed up on the monitor. After a while the disk light stopped flashing, and I assumed it was time to reboot. I rebooted, but nothing happened, the system did not boot. I tried several times with the same result. That was yesterday. Today I downloaded the F26 Workstation DVD, burned to a disk and placed it in the DVD drive of the what appeared to be a dead system. This time the system booted, but there was no F26 kernel, only F25 kernels. However, there are f26 packages installed. I was going to redo the download and upgrade, but when I run dnf I get this: [pgaltieri@caseyjones ~]$ dnf Traceback (most recent call last): File "/usr/bin/dnf", line 57, in from dnf.cli import main ModuleNotFoundError: No module named 'dnf' Anyone know what I need to do to fix this system? There are 2 other systems I want to upgrade, but after this experience I'm hesitant to go ahead with the others. This system is my test system so there's nothing important on it. Any help is appreciated. Paolo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
several issues with F25
Over the last week I have observed several problems with how F25 runs on
my laptop.
Issue 1: The system does not suspend on lid closed. I have an external
monitor attached to it and I can continue working on the system despite
the lid being closed. When I run gnome-tweak-tool and indicates the
system should suspend on lid closed. I have attached the png image of
the gnome-tweak-tool screen.
Issue 2: Back in the F24 days and even prior to that I filed a bug
(1389019) which states that when I boot my laptop on battery and login
the power status applet is not displayed in the MATE top menu bar. It
does show up when I plug the AC cord in. This problem has now gotten
worse. The power applet is no longer displayed regardless of what I
try. I have had to re-open this bug since it was without it ever being
fixed.
Issue 3: I run the MATE desktop and so I also run the
mate-screensaver. This is configured to display pictures from my
Pictures directory. Under the the "Power Management" screen it is
configured to suspend on lid closed and to put the display to sleep
after 5 minutes. After 5 minutes the display is not put to sleep, the
pictures from the Pictures directory continue to be displayed.
Issue 4: If I close the lid prior to the screen saver kicking in, wait
a minute and then lift the lid my session resumes without being asked to
enter a password. This to me is a serious security issue.
I have installed updates as of 8/15/2017
None of these issues existed a couple of months ago, except for maybe
the suspend issue. It has been a recurring problem getting the system
to suspend on lid closed. Sometimes it works other times it doesn't and
I've made no changes :-(
Has anyone else seen these issues?
As a side note why is there no equivalent to gnome-tweak-tool for the
MATE desktop? When I run gnome-tweak-tool under MATE I get these errors:
[pgaltieri@terrapin ~]$ gnome-tweak-tool
WARNING : Shell not installed or running
WARNING : Shell not running
None
WARNING : Error detecting shell
Traceback (most recent call last):
File
"/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_group_shell_extensions.py",
line 275, in __init__
raise Exception("Shell not running or DBus service not available")
Exception: Shell not running or DBus service not available
Of these issues Issue 2 is probably the most critical. If I'm running
on battery I want to see how much time I have left before the battery
power is consumed. I know I can use the upower command to find this
out, but that is not a satisfactory solution.
Any help is appreciated.
Thank you,
Paolo
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Installing F26; Question about ks.cfg when raid1 is used
On Mon, 21 Aug 2017 22:19:05 -0500
D&R wrote:
> On Sat, 19 Aug 2017 17:18:53 -0500
> dwoody5...@gmail.com wrote:
>
> > On Wed, 9 Aug 2017 14:27:07 -0700
> > Rick Stevens wrote:
> >
> > > On 08/09/2017 12:08 PM, D&R wrote:
> > > > On Wed, 9 Aug 2017 12:00:00 -0700
> > > > Rick Stevens wrote:
> > > >
> > > >> On 08/09/2017 11:52 AM, D&R wrote:
> > > >>> When I boot into the install there is an error in the destination
> > > >>> section.
> > > >>>
> > > >>> I looked at the debug info in the storage.log and there was an
> > > >>> error about sdb1 did not exist. But...
> > > >>>
> > > >>> When I reboot to F24 then ...
> > > >>>
> > > >>> cat /proc/mdstat
> > > >>>
> > > >>> md126 : active raid1 sda2[2] sdb2[1]
> > > >>> 961261568 blocks super 1.2 [2/2] [UU]
> > > >>> bitmap: 2/8 pages [8KB], 65536KB chunk
> > > >>>
> > > >>> md127 : active raid1 sdb1[1] sda1[2]
> > > >>> 15368064 blocks super 1.0 [2/2] [UU]
> > > >>> bitmap: 1/1 pages [4KB], 65536KB chunk
> > > >>>
> > > >>> The section of ks.cfg for hard drive setup is as follows:
> > > >>>
> > > >>> ignoredisk --only-use=sda,sdb
> > > >>> bootloader --location=mbr --boot-drive=sda
> > > >>>
> > > >>> # Partition clearing information
> > > >>> clearpart --none --initlabel
> > > >>>
> > > >>> # Disk partitioning information
> > > >>>
> > > >>> part raid.6 --fstype=mdmember --noformat --onpart=sda1
> > > >>> part raid.27 --fstype=mdmember --noformat --onpart=sdb1
> > > >>> part raid.14 --fstype=mdmember --noformat --onpart=sda2
> > > >>> part raid.32 --fstype=mdmember --noformat --onpart=sdb2
> > > >>>
> > > >>> raid / --device=root --fstype=ext4 --level=raid1 --useexisting
> > > >>> raid /home --device=home --fstype=ext4 --level=raid1 --noformat
> > > >>> --useexisting
> > > >>>
> > > >>> I currently have a raid1 setup with 2 drives sda and sdb
> > > >>>
> > > >>> Since I am using the option --useexisting do I still need to use the
> > > >>> part commands?
> > > >>>
> > > >>> The last time I did an upgrade was to F24 I have not found anything
> > > >>> that says the syntax has changed.
> > > >>>
> > > >>> Any Ideas?
> > > >>
> > > >> Uhm, when you're booting the install, is it possible that the CD/DVD
> > > >> you're booting from becomes /dev/sda? If so, then your first hard
> > > >> drive is /dev/sdb and the second is /dev/sdc and the
> > > >>
> > > >>ignoredisk --only-use=sda,sdb
> > > >>
> > > >> would block using the second hard drive, since it's /dev/sdc at this
> > > >> time. This is just a wild guess.
> > > >
> > > > I am booting from an iso file from another computer. As I recall that
> > > > is what I did when I installed F24 over F22.
> > >
> > > How are you booting an ISO file from another computer? Is this a network
> > > kickstart install, where the iso image is located on an NFS or CIFS
> > > server?
> > >
> > > Whatever it is, can you boot it again without invoking kickstart? If you
> > > can, open up a command line window and do "fdisk -l", which should list
> > > the disks the system sees. Verify the devices are the ones you think
> > > they are. Remember that when you're booting F24 from the hard disk, you
> > > are absolutely making /dev/sda the first hard drive. When booting from
> > > the network, a CD/DVD or a bootp server, that may NOT be the case and
> > > your drive letters may be different, in which the limits in your
> > > "ignoredisk" line would prevent finding the second drive.
> >
> > Sorry it took so long to reply, I was out of town on vacation.
> > However, I copied the Server iso for F24, F25, F26 to the home directory
> > on a second computer. The directory listings is:
> > -rw-r--r--. 1 root root 2401239040 Aug 17
> > 21:33 /home/Fedora-Server-dvd-x86_64-26-1.5.iso -rw-r--r--. 1 root root
> > 2018508800 Aug 19 14:49 /home/Fedora-Server-dvd-x86_64-25-1.3.iso
> > -rw-r--r--. 1 root root 1868562432 Aug 19
> > 16:28 /home/Fedora-Server-dvd-x86_64-24-1.2.iso
> >
> > The grub.cfg is setup up as:
> >
> > menuentry 'Remote Install' {
> > load_video
> > set gfxpayload=keep
> > insmod gzio
> > insmod part_msdos
> > insmod diskfilter
> > insmod mdraid1x
> > insmod ext2
> > set root='hd0,msdos1'
> > echo'Loading Linux'
> > # linux16 /boot/vmlinuz-remote acpi=off audit=0 selinux=0
> > inst.repo=nfs:10.10.1.2:/home/Fedora-Server-dvd-x86_64-24-1.2.iso
> > ramdisk_size=8192 panic=30
> > linux16 /boot/vmlinuz-remote acpi=off audit=0 selinux=0
> > inst.repo=nfs:10.10.1.2:/home/Fedora-Server-dvd-x86_64-25-1.3.iso
> > ramdisk_size=8192 panic=30
> > echo 'Loading initial ramdisk ...'
> > initrd16 /boot/initrd-remote.img }
> >
> > F24 came up in the installer with no error.
> > F25 came up in the installer with an error 'device already in tree'
> > F26 came up in the installer with an error 'device already in tree'
> >
> > From a F25 install fdisk -l:
> >
> > Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
> >
Re: F26 guest in qemu/kvm and 4.12.8-300 kernel
On 08/26/2017 06:33 PM, Jon Ingason wrote: > Den 2017-08-26 kl. 02:50, skrev Ed Greshko: >> On 08/26/2017 08:44 AM, Ed Greshko wrote: >>> Has anyone tried running a F26 guest in qemu/kvm with the latest 4.12.8-300 >>> kernel? >>> >>> When it comes to GNOME I can only boot to multi-user mode, not graphical, >>> by removing >>> rhgb from the boot parameters. If I attempt to boot to graphical mode it >>> hangs at >>> "Started user manager for UID 42" with UID 42 belonging to gdm. If I boot >>> to >>> multi-user mode and then login and use "startx" I am presented with a black >>> screen >>> and maybe the "Activities" indicator in the upper left. >>> >>> When it comes to KDE, which is configured for sddm, it will boot to >>> graphical mode if >>> I remove "rhgb quiet" from the boot parameters. However, the screen cannot >>> be >>> resized and issuing a "xrandr --output Virtual-0 --auto" is not effective >>> and may >>> result an apparent hang or a display which goes wonky in that it seems it >>> thinks it >>> is resizedbut it isn't and the mouse isn't where it thinks it is. >>> >>> Any similar experiences? >>> >>> >> Just to clarify a bit. I'm talking about the guest running the latest >> kernel. My >> host is running the latest. I installed F26 guest and it worked fine with >> the >> initial kernel-4.11.11-300 but the above is what I'm seeing with the >> 4.12.8-300 >> kernel in the guest. >> > Yes, I got precise this problem with kernel 4.12.4-300 and 4.12.8-300 > for Gnome Workstation VM under KVM/qemu. I am running Fedroa 25 updated > yesterday (Friday 25th August 2017). Good to know I'm not alone. Now to try and figure out what component a BZ should be filed against. -- Fedora Users List - The place to go to speculate endlessly signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: F26 guest in qemu/kvm and 4.12.8-300 kernel
Den 2017-08-26 kl. 02:50, skrev Ed Greshko: > On 08/26/2017 08:44 AM, Ed Greshko wrote: >> Has anyone tried running a F26 guest in qemu/kvm with the latest 4.12.8-300 >> kernel? >> >> When it comes to GNOME I can only boot to multi-user mode, not graphical, by >> removing >> rhgb from the boot parameters. If I attempt to boot to graphical mode it >> hangs at >> "Started user manager for UID 42" with UID 42 belonging to gdm. If I boot to >> multi-user mode and then login and use "startx" I am presented with a black >> screen >> and maybe the "Activities" indicator in the upper left. >> >> When it comes to KDE, which is configured for sddm, it will boot to >> graphical mode if >> I remove "rhgb quiet" from the boot parameters. However, the screen cannot >> be >> resized and issuing a "xrandr --output Virtual-0 --auto" is not effective >> and may >> result an apparent hang or a display which goes wonky in that it seems it >> thinks it >> is resizedbut it isn't and the mouse isn't where it thinks it is. >> >> Any similar experiences? >> >> > > Just to clarify a bit. I'm talking about the guest running the latest > kernel. My > host is running the latest. I installed F26 guest and it worked fine with the > initial kernel-4.11.11-300 but the above is what I'm seeing with the > 4.12.8-300 > kernel in the guest. > Yes, I got precise this problem with kernel 4.12.4-300 and 4.12.8-300 for Gnome Workstation VM under KVM/qemu. I am running Fedroa 25 updated yesterday (Friday 25th August 2017). -- Regards Jon Ingason ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
