Changing mount options without restarting
by Patrick O'Callaghan
I'm getting "filesystem not responding" messages from an NFS-mounted
NAS which I suspect is just slow (it spins down its disks when not in
use). I'm using automount and that appears to be related as it never
used to happen with normal mounting. I've changed the 'timeo' parameter
in the /etc/fstab line and run 'mount -a' but the mount parameters for
the filesystem have not changed. I've also restarted anything that
seems relevant from systemd:
systemctl restart storage-Backups.mount
and
systemctl restart proc-fs-nfsd.mount
and
systemctl restart proc-sys-fs-binfmt_misc.automount
to no effect.
How can I get this to work without rebooting?
poc
5 years, 3 months
Optical track ball finally arrived
by Robert Moskowitz
Thanks to all.
The kensington Expert Track ball arrived today. Crazy Michigan
no-fault... It had to be ordered via a doctors order for workstation
modification and then through an approved medical supply house that
could only order it directly from Kensington...
But it is here and I CAN work with it left-handed. This keeps my right
hand on the keyboard with less stress not having to reach for a
right-hand mouse (I just could not control a regular mouse left-handed).
This is going to make a difference in my work and my recovery.
BTW, I am taking my first steps without a cane and am 'graduating' to
out-patient PT for the walking. But the dislocated shoulder has another
3 weeks to go...
Take care
5 years, 3 months
incomplete boot after Fc26-27 upgrade
by Jon LaBadie
My primary system was still running Fedora 26 and I'm in the process of
updating stepwise using the dnf-system-upgrade plugin.
The download and update to F27 seemed to go fine. But reboots fail
and put me in "emergency/rescue" mode.
Once I've logged in as root and su'ed to my personal account, I can
turn networking on, run startx or mate-session for a desktop session.
VirtualBox also works in the desktop.
Hardware if pertainent:
MB Gigabyte X79-UP4
CPU Intel 3930K at 3.8GHz
MEM 32GB
VID nVidia GTX 660 Ti
DISK 4, Mix of SSD and rotating,
all but /boot managed by LVM
KERN 4.18.19-100.fc27.x86_64
I've cut and pasted the error messages from 'journalctl -b' (i.e.,
the ones colored red) and include a little context on some.
I do not see the problem, hopefully others will.
Error output from "journalctl -b".
There were 12 pairs of these messages varying only in the string "_SB.C00X".
The "X" was hex 0-B.
Fedora 24, 25, and 26 gave these same messages but ran ok.
Nov 30 18:29:22 cyber.jgcomp.com kernel: ACPI BIOS Error (bug): Could not resolve [\TST0], AE_NOT_FOUND (20180531/psargs-330)
Nov 30 18:29:22 cyber.jgcomp.com kernel: ACPI Error: Method parse/execution failed \_SB.C000._TPC, AE_NOT_FOUND (20180531/psparse-516)
The vbox modules mentioned in these message were loaded into the kernel
at another point. VirtualBox (Windows 7) runs ok.
Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxdrv
Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxnetflt
Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxnetadp
Nov 30 18:29:22 cyber.jgcomp.com systemd-modules-load[304]: Failed to find module vboxpci
Nov 30 18:29:24 cyber.jgcomp.com systemd-udevd[825]: Specified group plugdev unknown
These messages are correct, I'm not using ECC memory.
Fedora 26 had same messages but worked fine.
Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Couldn't find mci handler
Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Failed to register device with error -19.
...
Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Couldn't find mci handler
Nov 30 18:29:25 cyber.jgcomp.com kernel: EDAC sbridge: Failed to register device with error -19.
Only last line colored red by 'journalctl (hold queue overflow)'
Nov 30 18:29:30 cyber.jgcomp.com kernel: kauditd_printk_skb: 115 callbacks suppressed
Nov 30 18:29:30 cyber.jgcomp.com kernel: audit: type=1131 audit(1543620570.726:96): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=
Nov 30 18:29:30 cyber.jgcomp.com kernel: audit: audit_lost=38 audit_rate_limit=0 audit_backlog_limit=64
Nov 30 18:29:30 cyber.jgcomp.com kernel: audit: kauditd hold queue overflow
As above, only the "hold queue overflow" lines were colored
Nov 30 18:29:34 cyber.jgcomp.com 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'
Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: type=1130 audit(1543620574.804:97): 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'
Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: audit_lost=39 audit_rate_limit=0 audit_backlog_limit=64
Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: kauditd hold queue overflow
Nov 30 18:29:34 cyber.jgcomp.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: type=1130 audit(1543620574.816:98): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: audit_lost=40 audit_rate_limit=0 audit_backlog_limit=64
Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: kauditd hold queue overflow
Nov 30 18:29:34 cyber.jgcomp.com kernel: audit: type=1131 audit(1543620574.816:99): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
This may be after login as root to "rescue mode" and "su-ing to my personal account.
Nov 30 18:29:54 cyber.jgcomp.com su[1727]: pam_systemd(su-l:session): Failed to connect to system bus: No such file or directory
Any ideas?
Jon
5 years, 3 months
night light mode
by Patrick Dupre
Hello,
Since I set the night light mode in manual, I cannot return to
automatic mode.
How can I change this set up to default?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
5 years, 3 months
Re: DNF problems
by Frank McCormick
On 12/1/18 7:21 PM, stan wrote:
> On Sat, 1 Dec 2018 09:08:45 -0500
> Frank McCormick <beacon(a)videotron.ca> wrote:
>
>> I would assume DNF would update the 6 files from rpm-fusion ??
>
> Probably dependency errors. Try
> dnf update --best
> That should show you any package conflicts.
>
I'll try that when I get back into Fedora...I am also
currently dealing with a kernel problem on Debian Sid.
Thanks
5 years, 3 months
DNF problems
by Frank McCormick
Running Fedora 29, a fresh installation.
When I run dnf check-update this is what I get :
[root@localhost ~]# dnf check-update
unitedrpms 29 - x86_64 133 kB/s | 1.0 MB 00:07
Fedora Modular 29 - x86_64 314 kB/s | 1.5 MB 00:04
Fedora Modular 29 - x86_64 - Updates 768 kB/s | 1.6 MB 00:02
Fedora 29 - x86_64 - Updates 2.8 MB/s | 15 MB 00:05
Fedora 29 - x86_64 3.8 MB/s | 62 MB 00:16
google-chrome 3.0 kB/s | 3.6 kB 00:01
RPM Fusion for Fedora 29 - Free - Test Updates 13 kB/s | 36 kB 00:02
RPM Fusion for Fedora 29 - Free - Updates 60 kB/s | 112 kB 00:01
RPM Fusion for Fedora 29 - Free 778 kB/s | 759 kB 00:00
faad2-libs.x86_64 1:2.8.8-2.fc29 rpmfusion-free
libaacs.x86_64 0.9.0-5.fc29 rpmfusion-free
libbdplus.x86_64 0.1.2-6.fc29 rpmfusion-free
libmpeg2.x86_64 0.5.1-16.fc29 rpmfusion-free
opencore-amr.x86_64 0.1.5-5.fc29 rpmfusion-free
vo-amrwbenc.x86_64 0.1.3-8.fc29 rpmfusion-free
[root@localhost ~]# dnf update
Last metadata expiration check: 0:00:54 ago on Sat 01 Dec 2018 09:05:08
AM EST.
Dependencies resolved.
Nothing to do.
I would assume DNF would update the 6 files from rpm-fusion ??
Thanks
5 years, 3 months
Trying to get gpt + software raid + LVM in kickstart
by Digimer
Hi all,
I've for a Fedora 28 kickstart file booting from a PXE server. I can't
seem to work out the magic incantation to format it though.
Here's the PXE invocation (note 'inst.gpt');
====
kernel fedora28/vmlinuz
append initrd=fedora28/initrd.img
root=live:http://10.1.4.1/fedora28/x86_64/os/images/install.img
inst.stage2=http://10.1.4.1/fedora28/x86_64/os/ ip=dhcp
inst.ks=http://10.1.4.1/fedora28/x86_64/kickstart/striker.ks inst.gpt
inst.sshd
====
The partition section in the kickstart is;
====
zerombr
clearpart --all --drives=/dev/vda,/dev/vdb
ignoredisk --only-use=/dev/vda,/dev/vdb
bootloader --location=mbr --driveorder=/dev/vda,/dev/vdb
--boot-drive=/dev/vda
# biosboot
part biosboot --fstype=biosboot --size=2 --ondisk=/dev/vda
part biosboot --fstype=biosboot --size=2 --ondisk=/dev/vdb
part raid.11 --size 1024 --ondisk=/dev/vda
part raid.12 --size 1024 --ondisk=/dev/vdb
raid /boot --fstype=ext4 --device=md0 --level=RAID1 raid.11 raid.12
# LVM PV
part raid.21 --size 100 --grow --ondisk=/dev/vda
part raid.22 --size 100 --grow --ondisk=/dev/vdb
raid pv.1 --fstype=lvmpv --device=md1 --level=RAID1 raid.21 raid.22
# LVM Volume groups
volgroup striker_69E6A4A0 pv.1
# LVM logical volumes
logvol swap --fstype=swap --size=4096 --name=lv_swap
--vgname=striker_69E6A4A0
logvol / --fstype=xfs --size=16382 --name=lv_root
--vgname=striker_69E6A4A0
====
I zero out the two disks in the client machine;
====
[anaconda root@localhost ~]# parted /dev/vda print free
Error: /dev/vda: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vda: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
[anaconda root@localhost ~]# parted /dev/vdb print free
Error: /dev/vdb: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vdb: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
====
When I run the install, it fails with:
====
('new lv is too large to fit in free space', 'striker_69E6A4A0')
====
When I log into the server, it shows that nothing was done on the disks;
====
[anaconda root@localhost ~]# parted /dev/vda print free
Error: /dev/vda: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vda: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
[anaconda root@localhost ~]# parted /dev/vdb print free
Error: /dev/vdb: unrecognised disk label
Model: Virtio Block Device (virtblk)
Disk /dev/vdb: 21.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
====
Here's the anaconda log:
====
[anaconda root@localhost ~]# cat /tmp/anaconda.log
09:00:17,113 INF main: /sbin/anaconda 28.22.10-1.fc28
09:00:17,450 INF isys: 2171368 kB (2120 MB) are available
09:00:17,466 INF startup_utils: check_memory(): total:2120, needed:320,
graphical:410
09:00:17,480 INF main: anaconda called with cmdline = ['/sbin/anaconda']
09:00:17,480 INF main: Default encoding = utf-8
09:00:17,546 INF dbus.connection: Connecting to a default bus at
unix:abstract=/tmp/dbus-Rktjjl7n4T,guid=efed0a38c7f04387181cd3025bffaaa1.
09:00:18,331 INF startup_utils: Waiting 60 sec for modules to be started.
09:00:19,334 INF startup_utils: Waiting 59 sec for modules to be started.
09:00:20,337 INF startup_utils: Waiting 58 sec for modules to be started.
09:00:21,341 INF startup_utils: Waiting 57 sec for modules to be started.
09:00:22,504 INF startup_utils: Parsing kickstart: /run/install/ks.cfg
09:00:22,584 ERR core.util: Failed to import module docker from path
/usr/share/anaconda/addons/com_redhat_docker/ks/docker.py in collect: No
module named 'pyanaconda.iutil'
09:00:24,134 WRN kickstart: Command firstboot will be parsed in DBus module.
09:00:24,136 WRN kickstart: Command keyboard will be parsed in DBus module.
09:00:24,136 WRN kickstart: Command timezone will be parsed in DBus module.
09:00:24,137 WRN kickstart: Command lang will be parsed in DBus module.
09:00:24,137 WRN kickstart: Command rootpw will be parsed in DBus module.
09:00:24,139 WRN kickstart: Command zerombr will be parsed in DBus module.
09:00:24,139 WRN kickstart: Command clearpart will be parsed in DBus module.
09:00:24,139 WRN kickstart: Command ignoredisk will be parsed in DBus
module.
09:00:24,142 WRN misc:
/usr/lib/python3.6/site-packages/pykickstart/commands/partition.py:416:
UserWarning: A partition with the mountpoint biosboot has already been
defined.
warnings.warn(_("A partition with the mountpoint %s has already been
defined.") % pd.mountpoint)
09:00:24,492 DBG localization: setting locale to: en_CA.UTF-8
09:00:24,546 DBG network: devices found ['ens12', 'ens3']
09:00:24,587 DBG network: ensure single initramfs connections
09:00:24,805 DBG network: apply kickstart
09:00:24,855 WRN network: apply kickstart: --device does not exist
09:00:24,858 DBG network: create missing ifcfg files
09:00:25,305 DBG network: set real ONBOOT value
09:00:25,332 WRN network: set ONBOOT: --device does not exist
09:00:25,339 INF threading: Running Thread: AnaWaitForConnectingNMThread
(140225530734336)
09:00:25,342 DBG anaconda: setting display mode to TUI
09:00:25,356 WRN stdout: Not asking for VNC because of an automated install
09:00:25,357 WRN stdout: Not asking for VNC because text mode was
explicitly asked for in kickstart
09:00:25,360 INF anaconda: Display mode is set to 'interactive text mode'.
09:00:25,362 INF isys: 2171368 kB (2120 MB) are available
09:00:25,383 INF startup_utils: check_memory(): total:2120, needed:320,
graphical:410
09:00:25,493 INF network: got 0 NTP servers from DHCP
09:00:25,500 INF threading: Thread Done: AnaWaitForConnectingNMThread
(140225530734336)
09:00:25,517 DBG installclass: Searching
/usr/lib64/python3.6/site-packages/pyanaconda/installclasses.
09:00:25,536 DBG installclass: Found Fedora (FedoraBaseInstallClass).
09:00:25,536 DBG installclass: Found Atomic Host (AtomicHostInstallClass).
09:00:25,537 DBG installclass: Found Red Hat Enterprise Linux
(RHELBaseInstallClass).
09:00:25,537 DBG installclass: Found Fedora (DefaultInstallClass).
09:00:25,537 DBG installclass: Found Fedora Server
(FedoraServerInstallClass).
09:00:25,538 DBG installclass: Found Scientific Linux
(ScientificBaseInstallClass).
09:00:25,538 DBG installclass: Found Fedora Workstation
(FedoraWorkstationInstallClass).
09:00:25,539 DBG installclass: Found CentOS Linux (CentOSBaseInstallClass).
09:00:25,539 INF installclass: Using a visible install class Fedora
Server (FedoraServerInstallClass).
09:00:26,444 DBG payload: getting release version from tree at None (28)
09:00:26,445 DBG payload: using default release version of 28
09:00:26,449 INF bootloader: bootloader GRUB2 on X86 platform
09:00:26,452 INF autopart: Detected 2.07 GiB of memory
09:00:26,453 INF autopart: Suggested swap size (2.07 GiB) exceeds 10 %
of disk space, using 10 % of disk space (0.0) instead.
09:00:26,454 INF autopart: Swap attempt of 0.0
09:00:26,456 INF bootloader: bootloader GRUB2 on X86 platform
09:00:26,630 DBG storage_utils: LABEL=OEMDRV matches [] for
devicetree=None and disks_only=True
09:00:26,637 INF threading: Running Thread: AnaStorageThread
(140225530734336)
09:00:26,644 INF threading: Running Thread: AnaTimeInitThread
(140225428047616)
09:00:26,708 DBG payload: Restarting payload thread
09:00:26,710 INF threading: Running Thread: AnaPayloadRestartThread
(140225419654912)
09:00:26,711 INF geoloc: Geolocation is disabled due to automated
kickstart based installation.
09:00:26,713 INF threading: Running Thread: AnaPayloadThread
(140225411262208)
09:00:26,714 INF threading: Thread Done: AnaPayloadRestartThread
(140225419654912)
09:00:26,715 DBG payload: Updating payload thread state: 0
09:00:26,721 DBG payload: Updating payload thread state: 1
09:00:26,873 DBG simpleline: GLib event loop is used!
09:00:27,004 INF threading: Thread Done: AnaTimeInitThread (140225428047616)
09:00:27,020 INF lifecycle: Adding controller: SummaryHub
09:00:27,031 INF lifecycle: Module initialized: TimeSpoke
09:00:27,439 INF lifecycle: Module initialized: LangSpoke
09:00:27,445 INF threading: Running Thread: AnaSoftwareWatcher
(140225428047616)
09:00:27,447 INF threading: Running Thread: AnaSourceWatcher
(140225419654912)
09:00:27,455 INF threading: Running Thread: AnaStorageWatcher
(140225402869504)
09:00:28,399 INF lifecycle: Module initialized: NetworkSpoke
09:00:28,423 INF lifecycle: Module initialized: PasswordSpoke
09:00:28,502 WRN ui.tui.hubs: Spoke PasswordSpoke initialization failure!
09:00:28,506 INF lifecycle: Module initialized: UserSpoke
09:00:28,508 WRN ui.tui.hubs: Spoke UserSpoke initialization failure!
09:00:28,509 INF lifecycle: Initialization of all modules (8) has been
started.
09:00:29,749 INF threading: Thread Done: AnaStorageThread (140225530734336)
09:00:29,750 DBG payload: Updating payload thread state: 2
09:00:29,751 DBG payload: Updating payload thread state: 4
09:00:29,754 INF lifecycle: Module initialized: StorageSpoke
09:00:29,755 INF threading: Thread Done: AnaStorageWatcher (140225402869504)
09:00:29,798 DBG payload: getting release version from tree at
http://10.1.4.1/fedora28/x86_64/os/ (28)
09:00:29,798 DBG payload: retrieving treeinfo from
http://10.1.4.1/fedora28/x86_64/os/ (proxy: ; sslverify: True)
09:00:29,798 INF payload: Trying to download '.treeinfo'
09:00:29,805 DBG payload: Retrieved '.treeinfo' from
http://10.1.4.1/fedora28/x86_64/os/
09:00:29,807 DBG payload: using treeinfo release version of 28
09:00:29,846 DBG payload: Updating payload thread state: 5
09:00:30,555 INF payload: Refreshing environmentAddons
09:00:30,562 DBG payload: Updating payload thread state: 6
09:00:30,563 DBG ui.tui.spokes.software_selection: Payload restarted,
set new info and clear the old one.
09:00:30,564 INF threading: Thread Done: AnaPayloadThread (140225411262208)
09:00:30,564 DBG ui.tui.spokes.software_selection: Apply called old env
None, new env None and addons set()
09:00:30,564 INF lifecycle: Module initialized: SoftwareSpoke
09:00:30,565 INF threading: Thread Done: AnaSoftwareWatcher
(140225428047616)
09:00:30,566 INF lifecycle: Module initialized: SourceSpoke
09:00:30,566 INF lifecycle: All modules have been initialized.
09:00:30,567 INF threading: Thread Done: AnaSourceWatcher (140225419654912)
09:00:31,610 DBG storage: clearpart: initializing vda
09:00:31,735 DBG storage: clearpart: initializing vdb
09:00:32,023 DBG storage_utils: /dev/vda matches ['vda'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
existing 1024 MiB cdrom sr0 (8)
existing 20 GiB disk vdb (13) with non-existent gpt disklabel
existing 0 B file /tmp/curl_fetch_url0/install.img (deleted) (18)
existing 0 B loop loop0 (22)
existing 0 B file /LiveOS/rootfs.img (32)
existing 0 B loop loop1 (36) with existing ext4 filesystem
existing 2 GiB dm live-rw (60) with existing ext4 filesystem
existing 2 GiB dm live-base (70) with existing ext4 filesystem
existing 0 B file /overlay (deleted) (46)
existing 0 B loop loop2 (50)
and disks_only=True
09:00:32,132 DBG storage_utils: /dev/vdb matches ['vdb'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
existing 1024 MiB cdrom sr0 (8)
existing 20 GiB disk vdb (13) with non-existent gpt disklabel
existing 0 B file /tmp/curl_fetch_url0/install.img (deleted) (18)
existing 0 B loop loop0 (22)
existing 0 B file /LiveOS/rootfs.img (32)
existing 0 B loop loop1 (36) with existing ext4 filesystem
existing 2 GiB dm live-rw (60) with existing ext4 filesystem
existing 2 GiB dm live-base (70) with existing ext4 filesystem
existing 0 B file /overlay (deleted) (46)
existing 0 B loop loop2 (50)
and disks_only=True
09:00:32,137 DBG bootloader: new disk order: ['vda', 'vdb']
09:00:32,244 DBG storage_utils: /dev/vda matches ['vda'] for
devicetree=existing 20 GiB disk vda (3) with non-existent gpt disklabel
existing 1024 MiB cdrom sr0 (8)
existing 20 GiB disk vdb (13) with non-existent gpt disklabel
existing 0 B file /tmp/curl_fetch_url0/install.img (deleted) (18)
existing 0 B loop loop0 (22)
existing 0 B file /LiveOS/rootfs.img (32)
existing 0 B loop loop1 (36) with existing ext4 filesystem
existing 2 GiB dm live-rw (60) with existing ext4 filesystem
existing 2 GiB dm live-base (70) with existing ext4 filesystem
existing 0 B file /overlay (deleted) (46)
existing 0 B loop loop2 (50)
and disks_only=True
09:00:33,221 ERR ui.tui.spokes.storage: storage configuration failed:
The following problem occurred on line 68 of the kickstart file:
('new lv is too large to fit in free space', 'striker_69E6A4A0')
09:00:35,323 ERR bootloader: bios order specified unknown disk vdb
09:00:35,324 ERR bootloader: bios order specified unknown disk vda
09:00:35,622 DBG simpleline: Scheduling screen SummaryHub
09:00:35,624 DBG simpleline: New signal RenderScreenSignal enqueued with
source ScreenScheduler
09:00:35,625 DBG simpleline: Scheduling screen ProgressSpoke
09:00:35,626 DBG simpleline: Starting main loop
09:00:35,626 DBG simpleline: Processing screen
ScreenData(SummaryHub,None,False)
09:00:35,648 DBG payload: Source http://10.1.4.1/fedora28/x86_64/os/
needs network for installation
09:00:35,874 DBG simpleline: Input is required by
ScreenData(SummaryHub,None,False) screen
09:00:35,879 DBG payload: Source http://10.1.4.1/fedora28/x86_64/os/
needs network for installation
====
In the past, I would just do a manual install and then examine
'anaconda-ks.cfg' to see what it generated for the partitioning, but
that no longer seems to be recorded.
Any help in figurin out what I'm doing wrong would be my appreciated.
--
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
5 years, 3 months
hibernate stops working after upgrade to F29 from F28
by Ranjan Maitra
Hi,
I tried the following:
systemctl hibernate
and I get:
Failed to hibernate system via logind: Resume not configured, can't hibernate
I have never previously had to configure anything on an upgraded system already capable of hibernating (once hibernated). Has something changed? What do I do to fix this issue?
Many thanks and best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
5 years, 4 months