Hide Forgot
Description of problem: Windows PV driver does not work with software raid Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: - Launch a Windows 2008 R2 AMI. - Connect 4 EBS volumes of the same size create a text file c:\dp.txt and populate it with: select disk 1 clean convert dynamic select disk 2 clean convert dynamic select disk 3 clean convert dynamic select disk 4 clean convert dynamic create volume raid disk=1,2,3,4 list volume Then execute: diskpart /s c:\dp.txt Actual results: You'll see that the volume is in a failed state immediately. Expected results: Volume works as expected Additional info:
What version of the PV drivers? Can this be reproduced outside EC2?
It has been tested with version 1.2 and 1.3.4 of the Redhat PV driver. Both exhibit the same problem.
Created attachment 494914 [details] patch to fix the bug
It is the same as comment 0, except that you add four xvdNN volumes. Then you follow the diskpart commands in comment 0. You can use the diskpart command line instead of a file, that will make it easier to follow what's happening. At the end of the process, the RAID volume will show as "Resynching" in My Computer > Manage > Storage Management when the bug is fixed, as "Failed Redundancy" without the fix.
Verified with xenpv-win-1.3.12.3. test steps: Boot up a Win2008R2 guest, and attach 4 disks with "tap:aio:/path/to/disk,xvd*,w", then create the software raid in guest: [1] with the xenpv-win-1.3.4-9, the volume is in a failed state immediately after diskpart. [2] with xenpv-win-1.3.12-3, the software raid could be built successfully, after the rebuild of RAID, all the volumes and disks show as "Healthy". here is the log: ---------------- C:\Users\Administrator>diskpart /s c:/dp.txt Microsoft DiskPart version 6.1.7100 Copyright (C) 1999-2008 Microsoft Corporation. On computer: WIN-B2PS5JFKV25 Disk 1 is now the selected disk. DiskPart succeeded in cleaning the disk. DiskPart successfully converted the selected disk to dynamic format. Disk 2 is now the selected disk. DiskPart succeeded in cleaning the disk. DiskPart successfully converted the selected disk to dynamic format. Disk 3 is now the selected disk. DiskPart succeeded in cleaning the disk. DiskPart successfully converted the selected disk to dynamic format. Disk 4 is now the selected disk. DiskPart succeeded in cleaning the disk. DiskPart successfully converted the selected disk to dynamic format. DiskPart successfully created the volume. Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C OS_Install NTFS Partition 14 GB Healthy System * Volume 1 RAW RAID-5 6140 MB Rebuild C:\Users\Administrator>diskpart Microsoft DiskPart version 6.1.7100 Copyright (C) 1999-2008 Microsoft Corporation. On computer: WIN-B2PS5JFKV25 DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 15 GB 358 MB Disk 1 Online 2048 MB 0 B * Disk 2 Online 2048 MB 0 B * Disk 3 Online 2048 MB 0 B * Disk 4 Online 2048 MB 0 B * DISKPART> list volume Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 RAW RAID-5 6140 MB Healthy Volume 1 C OS_Install NTFS Partition 14 GB Healthy System
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause - Paravirtualized Xen drives did not handle properly the MODE SENSE command. Consequence - Windows failed to initialize a mirror or striped dynamic volume that included a paravirtualized Xen drive, leaving the volume in failed state. Fix - The MODE SENSE command is now implemented. Result - Dynamic volumes work with paravirtualized Xen drive.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0195.html