AlmaLinux / AlmaLinux/almalinux-deploy

Bug report: Some SATA hard drives are not visible in AlmaLinux but others are visible

オープン
#164 コメント 19 件 リアクション 0 件 担当者 0 名 GitHub で見る
upstream bug
主要言語
Shell
スター
597
フォーク
80
平均マージ
6日 9時間
マージ済み PR(30日)
1

説明

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:
- The SAS SSD (AlmaLinux 9)
- The previous system's SATA SSD (CentOS 7)
- 18TB SATA HDD

What does not show in the AlmaLinux system:
- 12TB SATA HDD
- 12TB SATA HDD

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 8 and 9 install disks can't see the two drives
- The booted AlmaLinux system can't see the two drives
- CentOS 7 install disk can see all the drives fine
- CentOS 7 booted system can see all the drives fine

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)

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。