I have 11 disks in this pool. 3x4TB SSHD's, 2x3TB HDD's, and 6x256GB SSD's. None of these disks are given drive letters, and instead are connected directly to the Pool.
I recently purchased a new HBA (m1015, cross-flashed to 9211-IT mode) and reconnected all the disks successfully. Everything was running great, and I was getting ready to rename the disks in the Disk Manager to reflect their physical connections.
Upon doing that, I noticed some disk duplication in the DrivePool (eg. The pool was showing duplicates of the same disk, new name non-pooled with old-name pooled). So, I thought I could just remove the old names, then go back and re-add the new names. Oh man, was I wrong. After doing that, DrivePool stopped even seeing two of the SSD's. Disk Manager sees them just fine; so does Scanner, Diskpart and CrystalMark. In fact, everything sees them just fine, except DrivePool.
Anyone know of a way to get them back in there? Hopefully there's a quick way to resolve. I'd hate to have to blow these disks away, Diskpart/clean them and re-create them into the pool.
[/EDIT]
AHA!! I just found what went wrong in the FAQ! (kinda). Apparently, when I removed the disk in DrivePool via the link, I told it "that the disks weren't coming back"..... They still have data on them that hadn't yet duplicated to the archive disks (per the FAQ and settings in the Balancers).. That's kind of a stupid feature if you can't just snap them back in. The only thing I see immediately that references such a thing is here. Is this what I am experiencing? Is "erasing the DrivePool metadata" still a work-around? Has this been fixed in the past 3½ years?
Question
collapsed
I have 11 disks in this pool. 3x4TB SSHD's, 2x3TB HDD's, and 6x256GB SSD's. None of these disks are given drive letters, and instead are connected directly to the Pool.
I recently purchased a new HBA (m1015, cross-flashed to 9211-IT mode) and reconnected all the disks successfully. Everything was running great, and I was getting ready to rename the disks in the Disk Manager to reflect their physical connections.
Upon doing that, I noticed some disk duplication in the DrivePool (eg. The pool was showing duplicates of the same disk, new name non-pooled with old-name pooled). So, I thought I could just remove the old names, then go back and re-add the new names. Oh man, was I wrong. After doing that, DrivePool stopped even seeing two of the SSD's. Disk Manager sees them just fine; so does Scanner, Diskpart and CrystalMark. In fact, everything sees them just fine, except DrivePool.
Anyone know of a way to get them back in there? Hopefully there's a quick way to resolve. I'd hate to have to blow these disks away, Diskpart/clean them and re-create them into the pool.
[/EDIT]
AHA!! I just found what went wrong in the FAQ! (kinda). Apparently, when I removed the disk in DrivePool via the link, I told it "that the disks weren't coming back"..... They still have data on them that hadn't yet duplicated to the archive disks (per the FAQ and settings in the Balancers).. That's kind of a stupid feature if you can't just snap them back in. The only thing I see immediately that references such a thing is here. Is this what I am experiencing? Is "erasing the DrivePool metadata" still a work-around? Has this been fixed in the past 3½ years?
Link to comment
Share on other sites
4 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.