Hide Forgot
Created attachment 1193519 [details] Installation failed Description of problem: RHEL installation failed when with a ntfs formatted datadisk. Version-Release number of selected component (if applicable): Host: kernel: 3.10.0-492.el7.x86_64 qemu-kvm-rhev-2.6.0-22.el7.x86_64 Guest: RHEL 7.2 x86_64 How reproducible: 100% Steps to Reproduce: 1.Create a new empty disk in host: #qemu-img create -f qcow2 sysdisk 30G 2.Prepare a NTFS formatted disk file "datadisk5G.qcow2". 3.Start VM installation with following commands: ... -device virtio-scsi-pci,id=scsi_pci_bus0 \ -drive file=/home/sysdisk,format=qcow2,id=drive_sysdisk,if=none,cache=none,aio=native,werror=stop,rerror=stop \ -device scsi-hd,drive=drive_sysdisk,bus=scsi_pci_bus0.0,id=device_sysdisk,bootindex=0 \ -drive file=/home/backup/RHEL-7.2-20151030.0-Server-x86_64-dvd1.iso,if=none,media=cdrom,id=drive_syscd,readonly=on,format=raw \ -device scsi-disk,bus=scsi_pci_bus0.0,drive=drive_syscd,id=device_syscd,bootindex=1 \ -device virtio-scsi-pci,id=scsi \ -drive file=/home/datadisk5G.qcow2,format=qcow2,id=drive_datadisk5G,if=none,cache=none,aio=native,werror=stop,rerror=stop \ -device scsi-hd,drive=drive_datadisk5G,bus=scsi.0,id=device_datadisk5G \ .... Actual results: Installation failed as attachment "Installation failed". Additional info: Installation can go on after deleting the partition in ntfs formatted datadisk: 1.Enter shell in anaconda through send key "Ctrl+Alt+F2". 2.Delete partition in /dev/sdb as attachment "Delete partition in /dev/sdb". 3.Restart through send key "Ctrl+Alt+Del" and continue the installation.
It is reproducible with qemu-kvm-rhev-2.3.0-31.el7_2.21.x86_64
Created attachment 1193521 [details] Delete partition in /dev/sdb
Full command line is as attachment "Full CMD". Available installation log files are as attachments.
Created attachment 1193536 [details] Full CMD
Created attachment 1193537 [details] anaconda.log
Created attachment 1193538 [details] anaconda-yum.conf
Created attachment 1193539 [details] ifcfg.log
Created attachment 1193540 [details] packaging.log
Created attachment 1193541 [details] program.log
Created attachment 1193542 [details] storage.log
Created attachment 1193543 [details] syslog
Created attachment 1193545 [details] X.log
(In reply to yduan from comment #0) > Steps to Reproduce: > 1.Create a new empty disk in host: > #qemu-img create -f qcow2 sysdisk 30G > > 2.Prepare a NTFS formatted disk file "datadisk5G.qcow2". > Please explain this step, as the error appears to be related to the layout/contents of the disk partition table. I can't see how QEMU would be at fault here.
(In reply to Ademar Reis from comment #14) > (In reply to yduan from comment #0) > > Steps to Reproduce: > > 1.Create a new empty disk in host: > > #qemu-img create -f qcow2 sysdisk 30G > > > > 2.Prepare a NTFS formatted disk file "datadisk5G.qcow2". > > > > Please explain this step, as the error appears to be related to the > layout/contents of the disk partition table. I can't see how QEMU would be > at fault here. File "datadisk5G.qcow2" was created as datadisk in former windows10 guest test, and it was formatted to NTFS in windows10 guest. In this test case, i accidentally used this file "datadisk5G.qcow2" as datadisk too and then met this issue. I‘m not sure whether it is related to QEMU. Please feel free to reassign it to corresponding component if it is not QEMU's fault. Thanks!
I looked at the attached logs a bit. I think it's a problem with blivet, or maybe even intentional behavior from blivet. I'm unsure, but I think we can ask the blivet owners to take a look. So, reassigning just for the purpose of triaging. Thanks!
The attached logs don't seem to match the reported failure. However, you will not see this failure in RHEL-7.3 due to an improvement in the handling of corrupt/unsupported disklabels. Generally, if you want to change the storage layout on the console while the installer is running, first wait until it has finished scanning the storage. Then make your changes and, finally, tell the installer to refresh its view of the storage (there's a refresh/rescan button). You could just as easily reboot after making the change if you cannot find the rescan button.
Thank you, David!