From rashmjain at gmail.com Wed Feb 6 04:03:53 2019 From: rashmjain at gmail.com (Rashmi Jain) Date: Tue, 5 Feb 2019 20:03:53 -0800 Subject: RHEL 7.5 customized kickstart installation sometime stops on "Installation Destination" - No disks selected Message-ID: Setup : appliance with 2 VDrives in RAID 10 and RAID 1 RHEL 7.5 based install with customized paritioning, text based install. Most of the time the customized works fine but sometimes it stops on Generatign customized storage configuration. Installation Destination (No disks selected) Rebooting the system and trying again - this works and install goes through. Any suggestions on how to debug this further - and what are the possible points to check ============================================================================= Installation 1) [x] Language settings 2) [x] Time settings (English (United States)) (America/Los_Angeles timezone) 3) [x] Installation source 4) [x] Software selection (Local media) (Custom software selected) 5) [!] Installation Destination 6) [x] Kdump (No disks selected) (Kdump is disabled) 7) [ ] Network configuration 8) [ ] User creation -------------- next part -------------- An HTML attachment was scrubbed... URL: From bishop at platypus.bc.ca Wed Feb 6 04:51:16 2019 From: bishop at platypus.bc.ca (Bishop) Date: Tue, 5 Feb 2019 20:51:16 -0800 Subject: RHEL 7.5 customized kickstart installation sometime stops on "Installation Destination" - No disks selected In-Reply-To: References: Message-ID: <3022bb7a-9b90-e0ed-f9b6-3817e0bf2994@platypus.bc.ca> 1. How do you have 2 disks in RAID10 AND ALSO RAID1 ? For RAID-1-10 you'd need 8. 2. Consider diverting your syslog to another server, and see what the message is when it dies. 3. I'm using Packer, for instance, and I think its install (force-fed kickstart with an attached ISO) hasn't seen that kind of behaviour yet, so we'd almost need to see your kickstart and any scaffolding required to replicate it in our own environments. I say 'almost' because I'm fully booked, but I hope to save someone else time asking for the same info. - .. Rashmi Jain wrote: > Setup : appliance with 2 VDrives in RAID 10 and RAID 1 > RHEL 7.5 based install with customized paritioning, text based install. > Most of the time? the? customized works fine? but sometimes it stops on? > Generatign customized storage configuration. Installation Destination > (No disks selected) > > Rebooting the system and trying again - this works and install goes > through. Any suggestions on how to debug this further - and what are the > possible points to check > > ============================================================================= > > Installation > > 1) [x] Language settings 2) [x] Time settings > (English (United States)) (America/Los_Angeles timezone) > 3) [x] Installation source 4) [x] Software selection > (Local media) (Custom software selected) > 5) [!] Installation Destination 6) [x] Kdump > (No disks selected) (Kdump is disabled) > 7) [ ] Network configuration 8) [ ] User creation > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x9437DAFDB6187995.asc Type: application/pgp-keys Size: 7711 bytes Desc: not available URL: From gregory.young at solarwinds.com Wed Feb 6 20:11:40 2019 From: gregory.young at solarwinds.com (Young, Gregory) Date: Wed, 6 Feb 2019 20:11:40 +0000 Subject: RHEL 7.5 customized kickstart installation sometime stops on "Installation Destination" - No disks selected In-Reply-To: <3022bb7a-9b90-e0ed-f9b6-3817e0bf2994@platypus.bc.ca> References: , <3022bb7a-9b90-e0ed-f9b6-3817e0bf2994@platypus.bc.ca> Message-ID: What is your RAID showing up as? Is it /dev/sda? /dev/cciss/? You may need to run a %pre script to detect the disks and inject them into the kickstart. Get Outlook for iOS ________________________________ From: kickstart-list-bounces at redhat.com on behalf of Bishop Sent: Tuesday, February 5, 2019 23:52 To: kickstart-list at redhat.com Subject: Re: RHEL 7.5 customized kickstart installation sometime stops on "Installation Destination" - No disks selected 1. How do you have 2 disks in RAID10 AND ALSO RAID1 ? For RAID-1-10 you'd need 8. 2. Consider diverting your syslog to another server, and see what the message is when it dies. 3. I'm using Packer, for instance, and I think its install (force-fed kickstart with an attached ISO) hasn't seen that kind of behaviour yet, so we'd almost need to see your kickstart and any scaffolding required to replicate it in our own environments. I say 'almost' because I'm fully booked, but I hope to save someone else time asking for the same info. - .. Rashmi Jain wrote: > Setup : appliance with 2 VDrives in RAID 10 and RAID 1 > RHEL 7.5 based install with customized paritioning, text based install. > Most of the time the customized works fine but sometimes it stops on > Generatign customized storage configuration. Installation Destination > (No disks selected) > > Rebooting the system and trying again - this works and install goes > through. Any suggestions on how to debug this further - and what are the > possible points to check > > ============================================================================= > > Installation > > 1) [x] Language settings 2) [x] Time settings > (English (United States)) (America/Los_Angeles timezone) > 3) [x] Installation source 4) [x] Software selection > (Local media) (Custom software selected) > 5) [!] Installation Destination 6) [x] Kdump > (No disks selected) (Kdump is disabled) > 7) [ ] Network configuration 8) [ ] User creation > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chavanpushpendra at gmail.com Thu Feb 7 01:51:36 2019 From: chavanpushpendra at gmail.com (Pushpendra Chavan) Date: Thu, 7 Feb 2019 07:21:36 +0530 Subject: RHEL 7.5 customized kickstart installation sometime stops on "Installation Destination" - No disks selected In-Reply-To: References: Message-ID: > Rebooting the system and trying again - this works and install goes through. Any suggestions on how to debug this further - and what are the possible points to check This makes me think that there is no issues with your kickstart file, there can be a problem for first instance disk detection and wipeout of RAID signatures which doesn't let you deploy first time. In such situations, it's always great to capture anaconda logs which you can get in /tmp of tty2 else, you can append the anaconda boot parameters as follows linux inst.ks= inst.sshd=1 sshpw=testpassword ip=192.168.0.100 netmask=255.255.255.0 gateway=192.168.0.1 nameserver=192.168.0.1 This enables your system's sshd during installation and when you get any problem, just ssh to this system using Windows Putty or from other Linux system with root and password as "testpassword" without quotes, you will get anaconda shell. On this shell, you can go to /tmp and here are our logs. These logs can be read, program.log will show you which command was executed last and what's it's return value. The disk names can be found in /proc/partitions or using parted command. So you can troubleshoot from here. Back to the problem, anaconda might not be able to wipeout the preinstalled raid signatures from your disks, so you might want to force clean it by adding a %pre script as follows. %pre wipefs -a -f /dev/sda wipefs -a -f /dev/sdb %end Considering your disks names are /dev/sda and /dev/sdb. Please note that above two commands in %pre section will fully wipe out your filesystems on /dev/sda and /dev/sdb, if you are not sure about the disk naming which can get changed across reboots, you can consider replacing those names with /dev/disk/by-id values too, which will hard-code the kickstart, to make it dynamic, you will need to inject little scripting into it. Additionally, how does your kickstart partitioning stanza looks like? Does the clearpart statement have --all --drive=sda,sdb with it? On Wed, Feb 6, 2019 at 9:35 AM Rashmi Jain wrote: > Setup : appliance with 2 VDrives in RAID 10 and RAID 1 > RHEL 7.5 based install with customized paritioning, text based install. > Most of the time the customized works fine but sometimes it stops on > Generatign customized storage configuration. Installation Destination (No > disks selected) > > Rebooting the system and trying again - this works and install goes > through. Any suggestions on how to debug this further - and what are the > possible points to check > > > ============================================================================= > > Installation > > 1) [x] Language settings 2) [x] Time settings > (English (United States)) (America/Los_Angeles timezone) > 3) [x] Installation source 4) [x] Software selection > (Local media) (Custom software selected) > 5) [!] Installation Destination 6) [x] Kdump > (No disks selected) (Kdump is disabled) > 7) [ ] Network configuration 8) [ ] User creation > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Thanks, Pushpendra M Chavan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From simpsonar77 at gmail.com Wed Feb 13 22:56:02 2019 From: simpsonar77 at gmail.com (Andrew Simpson) Date: Wed, 13 Feb 2019 17:56:02 -0500 Subject: kickstart RHEL 7 won't reboot when installing NVIDIA drivers Message-ID: I have a kickstart that detects if nvidia cards are present in the pre section and creates a .ks file with the appropriate nvidia RPMS for install during the normal package installation section. This seems to work fine. after all of the post sections are completed, every system that has the nvidia drivers installed fails to auto reboot. If I switch to the GUI screen on F6, the system immediately reboots. AMD and intel systems reboot fine without having to do this. Otherwise, the system will sit in this state on the post terminal output screen for hours. This used to work prior to RHEL 7.4. I have been unable to determine what the cause is. There don't appear to be any error or warning in the logs. Some reading suggests it might be a modesetting issue, which I plan on testing soon. A workaround might be to try and add an /sbin/reboot as the last line in the post. Thoughts/Suggestions? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: