not able to install Centos 7 on system running Windows 10

[gary20783]

Hello,

I need to install Centos 7 because the Radeon drivers do not support Centos 8 yet.

I have a Windows 10 system that has 2 raid controllers, asmedia 106x(disk 0) and perc6i(disk 1). The controllers are running in mirroring mode. The target disk is located on the perc6i (disk 1). UEFI boot is enabled.

Each of the controllers has a Windows 10 installation. However, they are not tied together. To boot the Windows 10 installed on the perc6i, I have to select the perc6i from the motherboard's boot device menu. The Centos 7 install does not see the asmedia controller which I expected.

I am able to boot the Centos installation from my USB drive, and complete the GUI configuration. When I click on "begin installation", the "unknown error" appears. I was not able to figure out how to save the log file.

Thoughts?

Regards,
Gary

[TrevorH]

Could you boot the CentOS install media and choose the "Rescue" option off the initial menu under the Troubleshooting option. That will drop you to a root comamd prompt. From there please run fdisk -lu /dev/sd[a-z] and post that output here.

[gary20783]

Hello,

sd_drives.txt - output from "ls /dev/sd*".
sd.text - output from output from "disk -lu /dev/sd[a-e]"

The output from "ls /dev/sd*" was not what I expected. I was expecting to see one of the following.

• 2 devices since their are 2 disks in each mirror set
• 2 devices with a single partition and 2 devices with 4 partitions

The sde device is the USB thumb drive.

Code: Select all

brw-rw----. 1 root disk 8,  0 Sep 18 15:25 /dev/sda
brw-rw----. 1 root disk 8,  1 Sep 18 15:25 /dev/sda1
brw-rw----. 1 root disk 8,  2 Sep 18 15:25 /dev/sda2
brw-rw----. 1 root disk 8,  3 Sep 18 15:25 /dev/sda3
brw-rw----. 1 root disk 8,  4 Sep 18 15:25 /dev/sda4

brw-rw----. 1 root disk 8, 16 Sep 18 15:25 /dev/sdb
brw-rw----. 1 root disk 8, 17 Sep 18 15:25 /dev/sdb1

brw-rw----. 1 root disk 8, 32 Sep 18 15:25 /dev/sdc
brw-rw----. 1 root disk 8, 33 Sep 18 15:25 /dev/sdc1
brw-rw----. 1 root disk 8, 34 Sep 18 15:25 /dev/sdc2
brw-rw----. 1 root disk 8, 35 Sep 18 15:25 /dev/sdc3
brw-rw----. 1 root disk 8, 36 Sep 18 15:25 /dev/sdc4
brw-rw----. 1 root disk 8, 37 Sep 18 15:25 /dev/sdc5

brw-rw----. 1 root disk 8, 48 Sep 18 15:25 /dev/sdd
brw-rw----. 1 root disk 8, 49 Sep 18 15:25 /dev/sdd1
brw-rw----. 1 root disk 8, 50 Sep 18 15:25 /dev/sdd2
brw-rw----. 1 root disk 8, 51 Sep 18 15:25 /dev/sdd3
brw-rw----. 1 root disk 8, 52 Sep 18 15:25 /dev/sdd4
brw-rw----. 1 root disk 8, 53 Sep 18 15:25 /dev/sdd5

brw-rw----. 1 root disk 8, 64 Sep 18 15:25 /dev/sde
brw-rw----. 1 root disk 8, 65 Sep 18 15:25 /dev/sde1

Code: Select all

Disk /dev/sda: 999.7 GB, 999653638144 bytes, 1952448512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x5b813bbe

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1  4294967295  2147483647+  ee  GPT


Disk /dev/sdb: 999.7 GB, 999653638144 bytes, 1952448512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x8c2f93f3

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  1952444415   976221184    7  HPFS/NTFS/exFAT


Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sde: 15.5 GB, 15534653440 bytes, 30341120 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x11165047

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *        2048    30341119    15169536    c  W95 FAT32 (LBA)

[TrevorH]

Post the output from lspci -nn

[gary20783]

The output from "lspci -nn" has been attached.

Code: Select all

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 Host Bridge [1002:5a14] (rev 02)
00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GFX port 0) [1002:5a16]
00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 0) [1002:5a18]
00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 1) [1002:5a19]
00:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 4) [1002:5a1c]
00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 5) [1002:5a1d]
00:0b.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD990 PCI to PCI bridge (PCI Express GFX2 port 0) [1002:5a1f]
00:0c.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD990 PCI to PCI bridge (PCI Express GFX2 port 1) [1002:5a20]
00:0d.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP2 Port 0) [1002:5a1e]
00:11.0 RAID bus controller [0104]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [RAID5 mode] [1002:4393] (rev 40)
00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] (rev 40)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40)
00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge [1002:4384] (rev 40)
00:14.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399]
00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0]
00:15.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) [1002:43a1]
00:15.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2) [1002:43a2]
00:15.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 3) [1002:43a3]
00:16.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
00:16.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 [1022:1600]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 [1022:1601]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 [1022:1602]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 [1022:1603]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 [1022:1604]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 [1022:1605]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev ef)
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0]
02:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller [1b21:1042]
07:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 1078 [1000:0060] (rev 04)
0b:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 09)
0c:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller [1b21:1042]
0d:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller [1b21:1042]

I have converted your text file attachment to an inline [ code ] [ /code ] list as it's much friendlier to read.

[TrevorH]

I am about 99% sure that your ASMedia controllers are not RAID capable and I suspect that if you have devices RAID'ed in Windows then they are either using BIOS RAID or Windows RAID. Both use the host processor for all operations and BIOS RAID is not really a RAID controller at all. The current array that you have on there may be unreadable in CentOS.

Your LSI Logic 1078 based card is a hardware RAID controller but I'm confused as to why you appear to have 2 separate disks when you think they should be presented as a single device. That makes me suspect that it's not actually using the hardware capabilities of the controller in Windows. It will present a BIOS splash as you boot up and there is a key combination that you have to press to get into its integrated BIOS setup. From there you can inspect the state of the hardware RAID and see how it is configured. It looks from your previous output as though it has 2 separate "arrays" of a single disk, effectively in RAID 0. I suspect the BIOS RAID is also sitting on top of that. What the controller BIOS tells you should sort that out. Feel free to take a screenshot of it with a camera and post it if it doesn't make sense to you.

[gary20783]

Hi Trevor,

Your observations and suspicions are in line with mine. However, I remember reading that sometimes even with hardware raid, the raid presentation is not made.

When I look in the BIOS setup for both the onboard and PERC devices, I see the devices configured appropriately, 2 disks configured for mirroring.

When booting to a command prompt, are the standard log files present? I'm asking because want to see what disks the system is finding.

After looking at the output from "ls -lh/dev/sd*" again in light of your comments, I think the BIOS raid, Asmedia 106X, is being recognized as 2 separate disks because there are 5 partitions in that raidset. Where as the OS drive(sda) on the Perc has 4 partitions. While the data drive(sdb) only has 1 partition. Which is what I would expect.

So the install only displays the PERC OS and data drive along with the Centos OS install USB media drive. However, I just looked at the "Unknown" partitions, and expected only to see 4 partitions. There are 9 partitions listed. See the attached picture.

[TrevorH]

When I look in the BIOS setup for both the onboard and PERC devices, I see the devices configured appropriately, 2 disks configured for mirroring.

Are you seeing that information in one place in the motherboard BIOS? The PERC controller should have its own, on Dell servers it's usually entered by pressing (iirc) F8 when you see the PERC initialization messages during the boot. Are you seeing that Dell PERC BIOS splash during the boot up with a few lines of status about the arrays defined?

[gary20783]

To view the raid configuration, I'm looking at the bios for each of the raid cards. So 2 different entry points before windows boots. And I previously confirmed that the raid devices complained when one member was missing.

I managed to figure out the location of anaconda log files and have attached the anaconda.log file. The error being reported is as follows.

Code: Select all

20:29:59,826 CRIT anaconda: Traceback (most recent call last):

  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)

  File "/usr/lib64/python2.7/threading.py", line 765, in run
    self.__target(*self.__args, **self.__kwargs)

  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 206, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg)

  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 235, in turnOnFilesystems
    storage.doIt(callbacks)

  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 386, in doIt
    self.devicetree.processActions(callbacks)

  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 371, in processActions
    self._preProcessActions()

  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 295, in _preProcessActions
    device.preCommitFixup()

  File "/usr/lib/python2.7/site-packages/blivet/devices/partition.py", line 373, in preCommitFixup
    _partition = _disklabel.partedDisk.getPartitionBySector(_sector)

AttributeError: 'DeviceFormat' object has no attribute 'partedDisk'

[gary20783]

I unplugged the 2 drives connected to the asmedia 106x onboard controller, and was able to install Centos 7 successfully.

Not sure why the install had problems.

I'm not sure how to thank Trevor for his assistance.