So I decided to do some more testing of DrivePool again in a Windows 7 VM and I noticed an issue.
My Windows 7 VM has 5 virtual disks attached (in addition to the boot drive).
Each drive is formatted as basic disk containing a single NTFS volume (partition).
I installed the latest 2.0 beta and the first issue I noticed is that not all drives are recognized by DrivePool in the "non-pool" section.
Only three out of five of my hard drives in Windows 7 VM are recognized so there are two drives which I cannot add to a pool.
In my attempt trying to resolve the issue, I reformatted all the drives using Computer Admin tool, re-assigned drive letters and even rebooted my Windows 7 VM several times but DrivePool would only recognize three out of five drives.
All five drives are accessible via Windows Explorer and CMD console so I don't know why DrivePool don't see all of them.
Finally, I decided to DELETE partitions on those two drives not recognized by DrviePool and RE-CREATE new NTFS volumes.
And THAT finally solved the issue.
However, this solution is not feasible in a production environment.
(I would need to backup data and re-create partitions).
Does anyone know what would prevent DrivePool from seeing all formatted NTFS volumes?
Does anyone ever have such issue in production environment running DrivePool?
Question
saiyan
So I decided to do some more testing of DrivePool again in a Windows 7 VM and I noticed an issue.
My Windows 7 VM has 5 virtual disks attached (in addition to the boot drive).
Each drive is formatted as basic disk containing a single NTFS volume (partition).
I installed the latest 2.0 beta and the first issue I noticed is that not all drives are recognized by DrivePool in the "non-pool" section.
Only three out of five of my hard drives in Windows 7 VM are recognized so there are two drives which I cannot add to a pool.
In my attempt trying to resolve the issue, I reformatted all the drives using Computer Admin tool, re-assigned drive letters and even rebooted my Windows 7 VM several times but DrivePool would only recognize three out of five drives.
All five drives are accessible via Windows Explorer and CMD console so I don't know why DrivePool don't see all of them.
Finally, I decided to DELETE partitions on those two drives not recognized by DrviePool and RE-CREATE new NTFS volumes.
And THAT finally solved the issue.
However, this solution is not feasible in a production environment.
(I would need to backup data and re-create partitions).
Does anyone know what would prevent DrivePool from seeing all formatted NTFS volumes?
Does anyone ever have such issue in production environment running DrivePool?
Thanks.
Link to comment
Share on other sites
10 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.