-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug report: Some SATA hard drives are not visible in AlmaLinux but others are visible #164
Comments
Hi. Thanks for your report. RHEL (and therefore us) removed support for certain SAS controllers. You can install the drivers for these controllers from ELRepo (https://elrepo.org). They also provide driver update disks (DUD) to enable these controllers at install time. You can find more info on their site, and also here: https://elrepo.org/bugs/view.php?id=927 |
There is no problem with the SAS drive. The problem is that it cannot see two of the SATA drives. All 3 of the SATA drives are connected to the same SATA backplane and connected to SATA on the motherboard, but Almalinux can only see one of the three. |
Additionally, there is another weird bug which I was sure was a problem during install. When booting using CentOS 7, it shows a certain amount of storage. Same problem was replicated on another system NOT using a RAID controller. |
I actually have a cloudlinux subscription (Almalinux is made by the Cloudlinux team) so maybe it will solve the issue to simply upgrade the server to Cloudlinux? Do you have a CloudLinux ISO I can burn to the flash drive and test the boot to see if the drive shows during the CloudLinux install? Or does CloudLinux only convert the live system? Edit: I got the iso. But at least you can solve this bug for the future. Still would like to know the answer, will report back whenever I have tested the cloudlinux iso to see if the issue is the same. |
If this does actually happen to be causing the issue, would it not make sense to update the install with this driver? And how do I install that driver? The link you gave me goes to CentOS 8, not Almalinux 9. The link you gave me is also for a different controller. It still might not even be relevant and might not have anything to do with this issue. Especially since the same issue occurred on different hardware without any raid controller. Would appreciate if someone can tell me if this page https://access.redhat.com/solutions/3751841 shows my controller or not. Keep in mind I installed Almalinux just fine on my controller. It is 2 of the SATA drives that are not showing in Almalinux. |
CloudLinux 9.1 also cannot see the same two disks. I just burned the latest CloudLinux ISO and showed the same bugs: Also the same weird bug where the USB drive which is not selected as shown in the above screen, shows as a partition and reduces the available space for the install by that much (30GB in this case for this 30GB drive): Remember I am booting from a USB stick. And CentOS 7 is able to see all the drives. So I don't think this is a controller issue. Also CentOS doesn't have this weird partition issue where the flash drive I'm booting on shows as a partition on the partitioning screen. Both Almalinux and CloudLinux both have both these same bugs. This seems to be a bug. |
Hello @jamesdev01 |
I downloaded and burned the RHEL9 iso and I'm booting from it now. |
Ok, RHEL 9.1 doesn't see the two drives either. And it has the same bug also about the USB drive that it is booting from is added as another partition and reducing the available space by the size of the USB flash drive. So it does seem to be an upstream bug. Maybe you can send this up the chain to RHEL. I don't have a subscription with RedHat.
Ok, I'll also check CentOS Stream next. |
@andrewlukoshko lets go ahead and file this with Stream. It does indeed seem like a hardware support regression |
@jamesdev01 is this still happens with 8.9? |
Hello @jamesdev01, Since yesterday I have been trying to install Almalinux 8.6 and am facing the same issue. Have you found any solution for this by chance? Please do let me know! |
@andrewlukoshko @jaboutboul could you please guide me on this issue? |
AlmaLinux install disk and booted system cannot see 2 drives, but CentOS install disk and booted system can.
I installed the latest AlmaLinux 9 onto an SAS SSD and everything is working fine. However, it doesn't see 2 of the SATA drives, but it does see another SATA drive. All 3 SATA drives are connected to the same backplane, so why it can see one but not the other two is the question.
I also tried the same with AlmaLinux 8, just to check, but it has the same issue.
I tried all these and the two 12TB drives do not show up in the AlmaLinux system:
df -h
lsblk
blkid
fdisk -l
parted -l
lsscsi
lshw -class disk
What does show up are:
What does not show in the AlmaLinux system:
Now, in the same system, I rebooted back into the original SATA SSD system (which is running CentOS 7) just to make sure the drives are there. Yes, they show just fine there.
The 3 SATA drives (18TB, 12TB, 12TB) are all connected to the backplane (which is plugged into the SATA ports on the motherboard), although the SAS drive is connected directly to the motherboard via an SAS connector. AlmaLinux can see one of these three drives on this same backplane.
It should also be noted that these 2 drives also did not show up during installation as an install location. I noticed this at that time but didn't want to install a system onto the 12TB drives, so I ignored it.
When I booted into a CentOS 7 install disk on the same SAS controller, all 4 drives shows up including the two 12TB drives. But when I boot into AlmaLinux (also happens with AlmaLinux 8, I tried that too), AlmaLinux doesn't see the disks.
So the problem is not the drives, or the controller, or the backplane, or the SAS, because I narrowed it down since all drives show up in the CentOS install disk booted from SAS drive and the CentOS booted system, but not from the AlmaLinux install disk or the AlmaLinux booted system.
So, summary:
Almalinux works fine, but since it cannot see two of my disks, my server is missing 24TB of data...
Debugging: This is on a a Supermicro motherboard with a hardware RAID controller which the SAS SSD connected to it is set up in JBOD mode.
Motherboard:
Supermicro
Raid controller:
MegaRAID SAS 2208 [Thunderbolt]
Raid mode:
JBOD (passthrough)
Boot disk:
Hitachi Ultrastar Enterprise SAS SSD
(connected directly to motherboard)Drive that shows:
WD Ultrastar 18TB HDD
(connected to SATA backplane)Drives that do not:
WD Ultrastar 12TB HDD
(connected to same SATA backplane)Install disk:
USB thumb drive
Method of creating bootable flash drive:
dd
Secondary method of creating bootable flash drive:
etcher for Linux in GUI
(same result)The text was updated successfully, but these errors were encountered: