Bug 2232406
| Summary: | coreos-installer-growfs.service fails to start Grow root filesystem in Onlogic HX401 bare-metal hardware | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Mario Cattamo <mcattamo> |
| Component: | rust-coreos-installer | Assignee: | RHCOS SST <rhcos-sst> |
| Status: | NEW --- | QA Contact: | RHCOS SST QE <rhcos-sst-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 9.3 | CC: | amurdaca, miabbott, perobins, qzhang, xiaofwan, yih |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Mario Cattamo
2023-08-16 16:50:35 UTC
This should be a bug, because the nvme has different partition name, like nvme0n1p[0-9], compared with /dev/sda[0-9]. https://github.com/coreos/coreos-installer-dracut/blob/e3568c4be6b1db019b792fcd08323435b185c27a/dracut/scripts/coreos-installer-growfs#L30C24-L30C30 does not work with nvme disk partition. Here's example of nvme partition: ➜ cat /proc/partitions major minor #blocks name 259 0 1000204632 nvme0n1 259 1 524288 nvme0n1p1 259 2 1048576 nvme0n1p2 259 3 780519424 nvme0n1p3 259 4 209715200 nvme0n1p4 259 5 8388608 nvme0n1p5 252 0 8388608 zram0 As noted by @perobins in the Dev/Doc/QE sync meeting, we will encounter a similar error when using storage devices based on SD cards: ``` pi@pihole:~ $ cat /proc/partitions major minor #blocks name 1 0 4096 ram0 1 1 4096 ram1 1 2 4096 ram2 1 3 4096 ram3 1 4 4096 ram4 1 5 4096 ram5 1 6 4096 ram6 1 7 4096 ram7 1 8 4096 ram8 1 9 4096 ram9 1 10 4096 ram10 1 11 4096 ram11 1 12 4096 ram12 1 13 4096 ram13 1 14 4096 ram14 1 15 4096 ram15 179 0 31166976 mmcblk0 179 1 262144 mmcblk0p1 179 2 30900736 mmcblk0p2 ``` We need to make the `coreos-installer-growfs` script more robust to handle the different ways partitions are represented. Perhaps by using one of the `/dev/disk/by-*` identifiers? The output of lsblk command is showing that the size of partition nvme0n1p4 is 9.5G.
[admin@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 119.2G 0 disk
├─nvme0n1p1 259:1 0 1M 0 part
├─nvme0n1p2 259:2 0 127M 0 part /boot/efi
├─nvme0n1p3 259:3 0 384M 0 part /boot
└─nvme0n1p4 259:4 0 9.5G 0 part
└─luks-94da2594-8d33-4aba-b3d4-416a098861e6 253:0 0 9.5G 0 crypt
└─rootvg-rootlv 253:1 0 9G 0 lvm /var
/sysroot/ostree/deploy/redhat/var
/usr
/etc
/
/sysroot
Comparing that size with the command output of a successful installation generated by edge-installer, seems the partition above should be much bigger. Just like @perobins mentioned in the Dev/Doc/QE sync meeting.
[admin@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 119.2G 0 disk
├─nvme0n1p1 259:1 0 600M 0 part /boot/efi
├─nvme0n1p2 259:2 0 1G 0 part /boot
└─nvme0n1p3 259:3 0 117.7G 0 part
├─rhel-root 253:0 0 70G 0 lvm /var
| /usr
| /
| /sysroot
├─rhel-swap 253:1 0 7.6G 0 lvm [SWAP]
└─rhel-home 253:2 0 40.1G 0 lvm /var/home
|