users November 2018

users@lists.fedoraproject.org

142 participants
150 discussions

Mounting internal disk spins up connected external USB disks
by Wolfgang Pfeiffer 24 Mar '19

24 Mar '19

Mounting an internally installed disk on a laptop spins up all disks connected to this machine via USB. And I try to prevent these externally connected disks to spin up. The behaviour, IIRC, started a few months ago on the previous F27 and continues now on F28. Before that I don't remember this behaviour to have happened. I thought it was some smartd issue, and stopped this service ("/usr/bin/systemctl stop smartd.service") - to no avail: mounting the internal disk still spins up the external ones. The internal disk is identified by "smartctl -d test /dev/sda" like so: [ ... ] /dev/sda: Device of type 'scsi' [SCSI] detected /dev/sda [SAT]: Device open changed type from 'scsi' to 'sat' /dev/sda [SAT]: Device of type 'sat' [ATA] opened (On a side note: I'm astonished that a smartctl simple info flag is changing some device type like shown above) External disks are identified by a smartctl test like so: One: "[USB Sunplus]: Device of type 'usbsunplus' [ATA] detected" the other one: "[SAT]: Device of type 'sat' [ATA] detected" Anyone an idea about where to start investigating this issue? Where could such behaviour possibly be set up? Thanks in anticipation. Wolfgang

7 16

F29 support for Intel Rapid Storage Technology (RST)
by dsavage＠peaknet.net 22 Feb '19

22 Feb '19

Does Fedora 29 support the Intel RST (Rapid Storage Technology) chip for hardware RAID? My new ThinkPad P72 came with an RST chip set up with two 2TB PCIe M.2 SSDs in a RAID1 config. The Fedora-29-MATE-Compiz spin DVD doesn't "see" it. Nor does Clonezilla. There's a BIOS mode setting for the Intel RST: "RST" mode for RAID, and "AHCI" mode for separate SATA drives. Changing that setting to AHCI will probably break the RAID1 array and render the P72 unbootable. I don't know if that would a destructive, irreversible change, or if changing the mode setting back to RST would restore everything. I've only tried the MATE spin. One purpose of this question is to find out if the full installation DVD supports the Intel RST chip. --Doc Robert G. (Doc) Savage Fairview Heights, IL "Perfection is the enemy of good enough." -- Admiral of the Fleet Sergei G. Gorshkov

5 9

Failed to start Load Kernel Modules.
by Sudhir Khanger 17 Jan '19

17 Jan '19

Hello, I get *Failed to start Load Kernel Modules* during the boot. Everytime Kernel is updated VirtualBox modules fail I have to reboot into the new Kernel, run the following commands and then it starts working. $ sudo akmods --force $ sudo dracut -v -f $ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg Then everything starts working again and the boot error goes away. You can found the background of the issue in the link below. https://bugzilla.redhat.com/show_bug.cgi?id=1254340 My question is how can I automate this task.

5 20

ACPI errors (was: f24 boot fails; need help).
by William 19 Dec '18

19 Dec '18

Good evening, One of the problems reported in the log file "rdsosreport.txt" generated by the failed boots discussed in the "f24 boot fails; need help" topic was a set of "ACPI" errors. Here are the relevant lines (with added line numbers) from that log file (the first and last lines are just for context): ---------- 862 [ 1.218683] coyote kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 863 [ 1.218927] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 864 [ 1.219196] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 865 [ 1.219856] coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max UDMA/133 866 [ 1.220017] coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA 867 [ 1.220812] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 868 [ 1.221100] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543) 869 [ 1.221620] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 870 [ 1.221909] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 871 [ 1.222200] coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100 872 [ 1.222374] coyote kernel: ata2.00: configured for UDMA/133 873 [ 1.222582] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 874 [ 1.222908] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 875 [ 1.222919] coyote kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5 876 [ 1.223466] coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100 877 [ 1.226360] coyote kernel: ata7: SATA link down (SStatus 0 SControl 300) 878 [ 1.226407] coyote kernel: ata9: SATA link down (SStatus 0 SControl 300) 879 [ 1.226501] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 880 [ 1.226507] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543) 881 [ 1.226519] coyote kernel: ata6.00: configured for UDMA/100 882 [ 1.227197] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359) 883 [ 1.227204] coyote kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543) 884 [ 1.227217] coyote kernel: ata4.00: configured for UDMA/100 ---------- What is this all about? Is this a real problem or a false alarm? How do I fix it? thanks, Bill.

5 10

Install on Zotac Zbox CI327?
by wwp 11 Dec '18

11 Dec '18

Hello there, (after a looong time not using Fedora, just back to it!) I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron N3450 inside) but this happens to fail. I've tried F25 but it has not the right kernel to make it (I've read about 4.10 minimum), then tried F26-Alpha-1.7 Live and Rawhide-20170518 Live but none could reach the graphical login. They both boot, some steps take a lot of time and I end up in a state I don't understand but which is not friendly ;-). Here's a link to a rdsosreport.txt file generated using Rawhide, I must admit that I don't know what to do now.. https://paste.fedoraproject.org/paste/iRx8d~7Luk2TC3bsaDuuT15M1UNdIGYhyRLiv… BTW, I could install and run a Ubuntu 17.10 daily (artful-desktop-amd64-20170519.iso) - wow it starts up pretty quickly - and that gave me hope! Any hint or experience w/ such hardware? Regards, -- wwp

2 3

VPN Interface not Remaining Active With Firewall?
by Stephen Morris 10 Dec '18

10 Dec '18

Hi, When I start one of the two vpn definitions, that have been in networkmanager for years and used to work fine (I haven't used them in quite a while), it starts and I get a pop-up message saying that interface tun0 has been activated in the firewall default zone (being fedoraworkstation). This interface remains active for about a minute or so until I get the pop-up message that interface tun0 has been deactivated in the firewall default zone, and the vpn is no longer connected. The vpn connection is using Openvpn. I have checked dmesg for any message relative to tun0 or firewall and there are no messages for either. How do I determine why the vpn won't stay active? regards, Steve

9 74

Changing mount options without restarting
by Patrick O'Callaghan 03 Dec '18

03 Dec '18

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

6 18

Optical track ball finally arrived
by Robert Moskowitz 03 Dec '18

03 Dec '18

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

4 3

night light mode
by Patrick Dupre 02 Dec '18

02 Dec '18

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 6

Trying to get gpt + software raid + LVM in kickstart
by Digimer 01 Dec '18

01 Dec '18

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

2 1

Jump to page: