-
Notifications
You must be signed in to change notification settings - Fork 141
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
installimage sometimes confuses one disk for another #14
Comments
Probably the random mapping comes from the rescue system. I've just started two hosts in the rescue mode and they show different mappings:
|
I'm having the same problem. Example: root@hostname ~ # lsblk root@hostname ~ # Ansible-triggered Reboot Broadcast message from root@hostname(Wed 2019-04-24 17:24:53 CEST): Ansible-triggered Reboot Connection to ****** closed by remote host.
Last login: Wed Apr 24 17:20:56 2019 from ****** My installimage file: DRIVE1 /dev/nvme0n1 also tried: DRIVE1 /dev/nvme0n1 |
The kernel does not guarantee the order in which devices are detected. This is not an installimage issue. However, installimage will always use UUIDs for that reason. If UUIDs are also used to reference the second disk, the order should not be an issue. Nevertheless, converting at least /boot to a RAID1 and installing grub on both drives, should provide a bootable system no matter in which order the disks are detected. |
Hello.
PX62-NVMe server has two disks: nvme0n1 and nvme1n1. I need them separately - not in a raid. I also need the first one as some partitions and the second one as a raw device.
I run
installimage -a -r no -p /boot:ext3:512M,/:ext4:20G,/kafka:ext4:all -d nvme0n1 -f no -s en -i /root/.oldroot/nfs/install/../images/Ubuntu-1804-bionic-64-minimal.tar.gz
Sometimes it works as expected and sometimes (quite often apparently)
installimage
thinks that nvme0n1 is nvme1n1:Looks like installimage is relying somewhere on some strict order, which actually can be random
The text was updated successfully, but these errors were encountered: