Skip to content
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

mount failure on ppc64le with NVMe boot drives #143

Closed
manojnkumar opened this issue Jan 17, 2020 · 4 comments
Closed

mount failure on ppc64le with NVMe boot drives #143

manojnkumar opened this issue Jan 17, 2020 · 4 comments
Labels
legacy legacy branch

Comments

@manojnkumar
Copy link

manojnkumar commented Jan 17, 2020

Running into this issue on a brand-new ppc64le system, that boots RHEL 8 fine. The boot disk is NVMe.

[  104.638649] coreos-installer[2860]: Wiping /dev/nvme0n1
[  104.657365] coreos-installer[2860]: /dev/nvme0n1: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
[  104.657495] coreos-installer[2860]: Writing disk image
[  104.658765] coreos-installer[2860]: 2+0 records in
[  104.658841] coreos-installer[2860]: 2+0 records out
[  104.658917] coreos-installer[2860]: 2 bytes copied, 4.088e-05 s, 48.9 kB/s
[  220.262600] coreos-installer[2860]: Waiting for udev
[  220.280953] coreos-installer[2860]: Embedding provided Ignition config
[  220.290255] coreos-installer[2860]: mount: /mnt/boot_partition: no filesystem type specified.

...

[  250.413009] coreos-installer[2860]: failed mounting boot partition
Usage: /usr/libexec/coreos-installer [options]
Options:
    -d DEVICE   Install to the given device, alternatively specify
                coreos.inst.install_dev on the kcmdline.
    -i IGNITION The URL (or path) to the given Ignition config,
                alternatively specify coreos.inst.ignition_url on the
                kcmdline.
    -b BASEURL  The URL to the image, alternatively specify
                coreos.inst.image_url on the kcmdline.
    -h          This.

This tool installs CoreOS style disk images on a block device.

@cgwalters has recommended that I add:

--- a/coreos-installer
+++ b/coreos-installer
@@ -323,6 +323,7 @@ mount_boot_partition() {
     while true
     do
         output=$(lsblk "${DEST_DEV}" --output NAME,LABEL,UUID --pairs | grep 'LABEL="boot"')
+        echo ${output}
         eval $(echo $output | tr ' ' '\n' | tail -n 1)
         mount "/dev/disk/by-uuid/${UUID}" "$boot_partition"
         RETCODE=$?
@cgwalters cgwalters added the legacy legacy branch label Jan 17, 2020
@manojnkumar
Copy link
Author

manojnkumar commented Jan 17, 2020

:/usr/libexec# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0    0  1.5T  0 disk 
:/usr/libexec# lsblk /dev/nvme0n1 --output NAME,LABEL,UUID --pairs 
NAME="nvme0n1" LABEL="" UUID=""

@manojnkumar
Copy link
Author

coreos-installer works fine on the same system with SATA ssd.

@manojnkumar
Copy link
Author

The NVMe drives were set to 4k sectors. When I reformatted the drives to 512b sectors, the installer proceeded to completion.

i.e. This issue is the same as: coreos/fedora-coreos-tracker#385

@bgilbert
Copy link
Contributor

Great, thanks for tracking this down. I'll close as a duplicate of coreos/fedora-coreos-tracker#385.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy legacy branch
Projects
None yet
Development

No branches or pull requests

3 participants