Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1"
This is what I have in the kickstart file
# Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel autopart --nohome --type=lvm --fstype=xfs ================
When I install from a USB drive it works OK and I have the following in /dev/disk/by-id
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2 drwxr-xr-x. 2 root root 400 Jul 5 10:28 . lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2
It's looks like that I am not doing the disk drive stuff in the config file correctly.
--
Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491
On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard g.hooton@ucc.ie wrote:
Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1"
The above says that the system thinks your box is multipath but the other drives are not showing up correctly. You will need to provide a lot more information for anyone to be able to help diagnosis this for you:
1. What is the build system 2. What kind of drives/drive controller is it 3. What is the rest of the kickstart that might tell it that it is multipath? 4. What are the pxe/uefi boot options in case that is telling it to try and probe for multipath that doesn't exist.
This is what I have in the kickstart file
# Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel autopart --nohome --type=lvm --fstype=xfs ================
When I install from a USB drive it works OK and I have the following in /dev/disk/by-id
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2 drwxr-xr-x. 2 root root 400 Jul 5 10:28 . lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2
It's looks like that I am not doing the disk drive stuff in the config file correctly.
--
Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491 _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
The computer is Lenovo Thinkstation p620 From df command I see: Filesystem Size Used Avail Use% Mounted on devtmpfs 16G 0 16G 0% /dev tmpfs 16G 0 16G 0% /dev/shm tmpfs 16G 26M 16G 1% /run tmpfs 16G 0 16G 0% /sys/fs/cgroup /dev/mapper/cs_uews027-root 70G 7.1G 63G 11% / /dev/nvme0n1p2 1014M 386M 629M 39% /boot /dev/nvme0n1p1 599M 7.3M 592M 2% /boot/efi /dev/mapper/cs_uews027-home 390G 2.8G 387G 1% /home tmpfs 3.2G 8.0K 3.2G 1% /run/user/42 tmpfs 3.2G 0 3.2G 0% /run/user/0
See attached files for more info. -----Original Message----- From: Stephen John Smoogen <smooge@gmail.commailto:Stephen%20John%20Smoogen%20%3csmooge@gmail.com%3e> Reply-To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> Subject: Re: [CentOS] Problems with CentOS 8 kickstart Date: Mon, 05 Jul 2021 07:28:05 -0400
[EXTERNAL] This email was sent from outside of UCC.
On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard <
g.hooton@ucc.ie
wrote:
Hi All,
I am having problems with a kickstart install of CentOS 8
When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file.
Then I see the following message
"kickstart install Started cancel waiting for multipath siblings for nvme0n1"
The above says that the system thinks your box is multipath but the
other drives are not showing up correctly. You will need to provide a
lot more information for anyone to be able to help diagnosis this for
you:
1. What is the build system
2. What kind of drives/drive controller is it
3. What is the rest of the kickstart that might tell it that it is multipath?
4. What are the pxe/uefi boot options in case that is telling it to
try and probe for multipath that doesn't exist.
This is what I have in the kickstart file
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
autopart --nohome --type=lvm --fstype=xfs
================
When I install from a USB drive it works OK and I have the following in /dev/disk/by-id
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2
drwxr-xr-x. 2 root root 400 Jul 5 10:28 .
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2
It's looks like that I am not doing the disk drive stuff in the config file correctly.
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
_______________________________________________
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.
_______________________________________________
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491
Is the information in the two file sufficient or do I need to add more?
-----Original Message----- From: "Hooton, Gerard" <g.hooton@ucc.iemailto:%22Hooton,%20Gerard%22%20%3cg.hooton@ucc.ie%3e> Reply-To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> To: centos@centos.org <centos@centos.orgmailto:%22centos@centos.org%22%20%3ccentos@centos.org%3e> Subject: Re: [CentOS] Problems with CentOS 8 kickstart Date: Mon, 05 Jul 2021 11:57:09 +0000 Mailer: Evolution 3.36.5-0ubuntu1
[EXTERNAL] This email was sent from outside of UCC.
The computer is Lenovo Thinkstation p620
From df command I see:
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 26M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/mapper/cs_uews027-root 70G 7.1G 63G 11% /
/dev/nvme0n1p2 1014M 386M 629M 39% /boot
/dev/nvme0n1p1 599M 7.3M 592M 2% /boot/efi
/dev/mapper/cs_uews027-home 390G 2.8G 387G 1% /home
tmpfs 3.2G 8.0K 3.2G 1% /run/user/42
tmpfs 3.2G 0 3.2G 0% /run/user/0
See attached files for more info.
-----Original Message-----
From: Stephen John Smoogen <
smooge@gmail.com
<mailto:
mailto:Stephen%20John%20Smoogen%20%3csmooge@gmail.com
Stephen%20John%20Smoogen%20%3csmooge@gmail.com
%3e>>
Reply-To: CentOS mailing list <
centos@centos.org
<mailto:
mailto:CentOS%20mailing%20list%20%3ccentos@centos.org
CentOS%20mailing%20list%20%3ccentos@centos.org
%3e>>
To: CentOS mailing list <
centos@centos.org
<mailto:
mailto:CentOS%20mailing%20list%20%3ccentos@centos.org
CentOS%20mailing%20list%20%3ccentos@centos.org
%3e>>
Subject: Re: [CentOS] Problems with CentOS 8 kickstart
Date: Mon, 05 Jul 2021 07:28:05 -0400
[EXTERNAL] This email was sent from outside of UCC.
On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard <
<mailto:
g.hooton@ucc.ie
g.hooton@ucc.ie
wrote:
Hi All,
I am having problems with a kickstart install of CentOS 8
When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file.
Then I see the following message
"kickstart install Started cancel waiting for multipath siblings for nvme0n1"
The above says that the system thinks your box is multipath but the
other drives are not showing up correctly. You will need to provide a
lot more information for anyone to be able to help diagnosis this for
you:
1. What is the build system
2. What kind of drives/drive controller is it
3. What is the rest of the kickstart that might tell it that it is multipath?
4. What are the pxe/uefi boot options in case that is telling it to
try and probe for multipath that doesn't exist.
This is what I have in the kickstart file
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
autopart --nohome --type=lvm --fstype=xfs
================
When I install from a USB drive it works OK and I have the following in /dev/disk/by-id
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2
drwxr-xr-x. 2 root root 400 Jul 5 10:28 .
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2
It's looks like that I am not doing the disk drive stuff in the config file correctly.
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
_______________________________________________
CentOS mailing list
<mailto:
CentOS@centos.org
CentOS@centos.org
<
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.
_______________________________________________
CentOS mailing list
<mailto:
CentOS@centos.org
CentOS@centos.org
<
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
_______________________________________________
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491
On Mon, 5 Jul 2021 at 07:57, Hooton, Gerard g.hooton@ucc.ie wrote:
The computer is Lenovo Thinkstation p620 From df command I see: Filesystem Size Used Avail Use% Mounted on devtmpfs 16G 0 16G 0% /dev tmpfs 16G 0 16G 0% /dev/shm tmpfs 16G 26M 16G 1% /run tmpfs 16G 0 16G 0% /sys/fs/cgroup /dev/mapper/cs_uews027-root 70G 7.1G 63G 11% / /dev/nvme0n1p2 1014M 386M 629M 39% /boot /dev/nvme0n1p1 599M 7.3M 592M 2% /boot/efi /dev/mapper/cs_uews027-home 390G 2.8G 387G 1% /home tmpfs 3.2G 8.0K 3.2G 1% /run/user/42 tmpfs 3.2G 0 3.2G 0% /run/user/0
I am not familiar with this hardware, and a quick looks shows that there are a lot of variations on the p620. However I did find https://download.lenovo.com/pccbbs/thinkcentre_pdf/ts_p620_redhat_enterprise... and https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/pdf...
I haven't used multipath and hope some people who have better ideas will chime in, but at this point I would see if passing the PXE kernel boot a `nvme_core.multipath=N` helps any.
See attached files for more info. -----Original Message----- From: Stephen John Smoogen <smooge@gmail.commailto:Stephen%20John%20Smoogen%20%3csmooge@gmail.com%3e> Reply-To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> Subject: Re: [CentOS] Problems with CentOS 8 kickstart Date: Mon, 05 Jul 2021 07:28:05 -0400
[EXTERNAL] This email was sent from outside of UCC.
On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard <
g.hooton@ucc.ie
wrote:
Hi All,
I am having problems with a kickstart install of CentOS 8
When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file.
Then I see the following message
"kickstart install Started cancel waiting for multipath siblings for nvme0n1"
The above says that the system thinks your box is multipath but the
other drives are not showing up correctly. You will need to provide a
lot more information for anyone to be able to help diagnosis this for
you:
What is the build system
What kind of drives/drive controller is it
What is the rest of the kickstart that might tell it that it is multipath?
What are the pxe/uefi boot options in case that is telling it to
try and probe for multipath that doesn't exist.
This is what I have in the kickstart file
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
autopart --nohome --type=lvm --fstype=xfs
================
When I install from a USB drive it works OK and I have the following in /dev/disk/by-id
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2
drwxr-xr-x. 2 root root 400 Jul 5 10:28 .
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2
It's looks like that I am not doing the disk drive stuff in the config file correctly.
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491 _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I put nvme_core.multipath=N in the grub.cfg as follows linuxefi /Centos8/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=CentOS-8-x86_64-dvd nvme_core.multipath=N rd.live.check inst.ks=http://192.168.1.10/kickstart/ks.cfghttp://143.239.132.208/kickstart/ks.cfg
This did not solve the problem.
-----Original Message----- From: Stephen John Smoogen <smooge@gmail.commailto:Stephen%20John%20Smoogen%20%3csmooge@gmail.com%3e> Reply-To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> Subject: Re: [CentOS] Problems with CentOS 8 kickstart Date: Tue, 06 Jul 2021 06:49:24 -0400
[EXTERNAL] This email was sent from outside of UCC.
On Mon, 5 Jul 2021 at 07:57, Hooton, Gerard <
g.hooton@ucc.ie
wrote:
The computer is Lenovo Thinkstation p620
From df command I see:
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 26M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/mapper/cs_uews027-root 70G 7.1G 63G 11% /
/dev/nvme0n1p2 1014M 386M 629M 39% /boot
/dev/nvme0n1p1 599M 7.3M 592M 2% /boot/efi
/dev/mapper/cs_uews027-home 390G 2.8G 387G 1% /home
tmpfs 3.2G 8.0K 3.2G 1% /run/user/42
tmpfs 3.2G 0 3.2G 0% /run/user/0
I am not familiar with this hardware, and a quick looks shows that
there are a lot of variations on the p620. However I did find
https://download.lenovo.com/pccbbs/thinkcentre_pdf/ts_p620_redhat_enterprise...
and
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/pdf...
I haven't used multipath and hope some people who have better ideas
will chime in, but at this point I would see if passing the PXE kernel
boot a `nvme_core.multipath=N` helps any.
See attached files for more info.
-----Original Message-----
From: Stephen John Smoogen <
smooge@gmail.com
<mailto:
mailto:Stephen%20John%20Smoogen%20%3csmooge@gmail.com
Stephen%20John%20Smoogen%20%3csmooge@gmail.com
%3e>>
Reply-To: CentOS mailing list <
centos@centos.org
<mailto:
mailto:CentOS%20mailing%20list%20%3ccentos@centos.org
CentOS%20mailing%20list%20%3ccentos@centos.org
%3e>>
To: CentOS mailing list <
centos@centos.org
<mailto:
mailto:CentOS%20mailing%20list%20%3ccentos@centos.org
CentOS%20mailing%20list%20%3ccentos@centos.org
%3e>>
Subject: Re: [CentOS] Problems with CentOS 8 kickstart
Date: Mon, 05 Jul 2021 07:28:05 -0400
[EXTERNAL] This email was sent from outside of UCC.
On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard <
<mailto:
g.hooton@ucc.ie
g.hooton@ucc.ie
wrote:
Hi All,
I am having problems with a kickstart install of CentOS 8
When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file.
Then I see the following message
"kickstart install Started cancel waiting for multipath siblings for nvme0n1"
The above says that the system thinks your box is multipath but the
other drives are not showing up correctly. You will need to provide a
lot more information for anyone to be able to help diagnosis this for
you:
1. What is the build system
2. What kind of drives/drive controller is it
3. What is the rest of the kickstart that might tell it that it is multipath?
4. What are the pxe/uefi boot options in case that is telling it to
try and probe for multipath that doesn't exist.
This is what I have in the kickstart file
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
autopart --nohome --type=lvm --fstype=xfs
================
When I install from a USB drive it works OK and I have the following in /dev/disk/by-id
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2
drwxr-xr-x. 2 root root 400 Jul 5 10:28 .
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2
It's looks like that I am not doing the disk drive stuff in the config file correctly.
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
_______________________________________________
CentOS mailing list
<mailto:
CentOS@centos.org
CentOS@centos.org
<
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.
_______________________________________________
CentOS mailing list
<mailto:
CentOS@centos.org
CentOS@centos.org
<
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
_______________________________________________
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.
_______________________________________________
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491
On Wed, 7 Jul 2021 at 08:29, Hooton, Gerard g.hooton@ucc.ie wrote:
I put nvme_core.multipath=N in the grub.cfg as follows linuxefi /Centos8/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=CentOS-8-x86_64-dvd nvme_core.multipath=N rd.live.check inst.ks=http://192.168.1.10/kickstart/ks.cfghttp://143.239.132.208/kickstart/ks.cfg
This did not solve the problem.
OK remove that suggestion and try the following from https://docs.fedoraproject.org/en-US/Fedora/24/html/Installation_Guide/sect-...
try adding the following to the kickstart
ignoredisk --only-use=nvme0n1
-----Original Message----- From: Stephen John Smoogen <smooge@gmail.commailto:Stephen%20John%20Smoogen%20%3csmooge@gmail.com%3e> Reply-To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> To: CentOS mailing list <centos@centos.orgmailto:CentOS%20mailing%20list%20%3ccentos@centos.org%3e> Subject: Re: [CentOS] Problems with CentOS 8 kickstart Date: Tue, 06 Jul 2021 06:49:24 -0400
[EXTERNAL] This email was sent from outside of UCC.
On Mon, 5 Jul 2021 at 07:57, Hooton, Gerard <
g.hooton@ucc.ie
wrote:
The computer is Lenovo Thinkstation p620
From df command I see:
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 26M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/mapper/cs_uews027-root 70G 7.1G 63G 11% /
/dev/nvme0n1p2 1014M 386M 629M 39% /boot
/dev/nvme0n1p1 599M 7.3M 592M 2% /boot/efi
/dev/mapper/cs_uews027-home 390G 2.8G 387G 1% /home
tmpfs 3.2G 8.0K 3.2G 1% /run/user/42
tmpfs 3.2G 0 3.2G 0% /run/user/0
I am not familiar with this hardware, and a quick looks shows that
there are a lot of variations on the p620. However I did find
https://download.lenovo.com/pccbbs/thinkcentre_pdf/ts_p620_redhat_enterprise...
and
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/pdf...
I haven't used multipath and hope some people who have better ideas
will chime in, but at this point I would see if passing the PXE kernel
boot a `nvme_core.multipath=N` helps any.
See attached files for more info.
-----Original Message-----
From: Stephen John Smoogen <
smooge@gmail.com
<mailto:
mailto:Stephen%20John%20Smoogen%20%3csmooge@gmail.com
Stephen%20John%20Smoogen%20%3csmooge@gmail.com
%3e>>
Reply-To: CentOS mailing list <
centos@centos.org
<mailto:
mailto:CentOS%20mailing%20list%20%3ccentos@centos.org
CentOS%20mailing%20list%20%3ccentos@centos.org
%3e>>
To: CentOS mailing list <
centos@centos.org
<mailto:
mailto:CentOS%20mailing%20list%20%3ccentos@centos.org
CentOS%20mailing%20list%20%3ccentos@centos.org
%3e>>
Subject: Re: [CentOS] Problems with CentOS 8 kickstart
Date: Mon, 05 Jul 2021 07:28:05 -0400
[EXTERNAL] This email was sent from outside of UCC.
On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard <
<mailto:
g.hooton@ucc.ie
g.hooton@ucc.ie
wrote:
Hi All,
I am having problems with a kickstart install of CentOS 8
When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file.
Then I see the following message
"kickstart install Started cancel waiting for multipath siblings for nvme0n1"
The above says that the system thinks your box is multipath but the
other drives are not showing up correctly. You will need to provide a
lot more information for anyone to be able to help diagnosis this for
you:
What is the build system
What kind of drives/drive controller is it
What is the rest of the kickstart that might tell it that it is multipath?
What are the pxe/uefi boot options in case that is telling it to
try and probe for multipath that doesn't exist.
This is what I have in the kickstart file
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
autopart --nohome --type=lvm --fstype=xfs
================
When I install from a USB drive it works OK and I have the following in /dev/disk/by-id
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1
lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2
drwxr-xr-x. 2 root root 400 Jul 5 10:28 .
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2
lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2
It's looks like that I am not doing the disk drive stuff in the config file correctly.
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
CentOS mailing list
<mailto:
CentOS@centos.org
CentOS@centos.org
<
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.
CentOS mailing list
<mailto:
CentOS@centos.org
CentOS@centos.org
<
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton.
Senior Technical Officer
School of Engineering.
University College Cork.
College Road.
Cork.
Ireland.
Loc8: WDR-04-60G
Tel: +353 21 4902296
Mobile: +353 852813491
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on BBS...
time to reboot.
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
https://lists.centos.org/mailman/listinfo/centos
--
Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491 _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Thanks for sharing such detailed information, Gerard. It looks like the issue you're facing with CentOS 8 Kickstart and multipath on the Lenovo ThinkStation P620 is rooted in how the NVMe drives are being interpreted during PXE/UEFI boot. The fact that installation works fine via USB but not through PXE strongly suggests the boot kernel might be incorrectly detecting multipath-capable devices, especially with high-performance NVMe like the SAMSUNG MZVL2512HCJQ.
The suggestion to try booting with nvme_core.multipath=N is a good one and often resolves these types of issues by disabling NVMe native multipathing support that can misinterpret single-disk setups.
As you're working with a workstation-class machine like the P620, it's worth mentioning the importance of pairing it with enterprise-grade storage. In this context, Solid State Drives SAS 12Gbps SSD 480GB-RI-2.5Inch https://serverorbit.com/solid-state-drives-ssd/sas-12gbps-ssd/480gb-ri-2-5in... are a great match for such environments. These drives offer superior reliability and speed, particularly in read-intensive workloads such as automated installs, provisioning, and data logging—common in lab and research settings. Their robust firmware and error-handling also make them less prone to issues during automated installations and multipath misdetections.
Best of luck with the install—and definitely keep an eye on the boot parameters and firmware versions. Updating your system firmware and BIOS might also help reduce compatibility quirks with advanced storage subsystems.
-
Hooton, Gerard -
Stephen John Smoogen -
xevacor742＠boxmach.com