Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/25/20 in all areas

  1. Well, there may be some scenario where drive letters are required. But with 16 HDDs in my pool, I am more than happy to assign names to the HDDs and not have to bother with drive letters. In theory, DrivePool is able to pool many more than 26 HDDs, so you would reach a point where you would run out of drive letters anyway. If you need to assign a drive letter to a DrivePool HDD that has a name only, you can easily do that in Disk Management and it will not affect DrivePool at all. Again, DrivePool does not read the drive letter at all. It only uses the hidden PoolPart directory for identification. As mentioned, you may have to restart your computer if you decide to reassign drive letters to your DrivePool HDDs, not for DrivePool itself, but sometimes other Windows program will not recognize the newly named drive without a restart. IIRC, Disk Management will warn you about that when you change/add/remove a drive letter.
    1 point
  2. I just removed the letters on all 8 pool drives and nothing exploded! Same for SB scanner, business as usual (except for now blank drive letters You now have me interested in leaving them unlettered, but there must be a scenario/usage case where lettered pool drives are desirable. EDIT: Should a need arise, I could always revert to letters, but I'll leave them out for now and see how it goes. Thanks @gtaus
    1 point
  3. Yeah, old habits... When I removed the drive letters and just used drive names, life with DrivePool became easier with my 16 HDDs. It works better for me.
    1 point
  4. This sounds like good news to me I think when I started using drivepool, individual drives were "letter-less" (file explorer would only show pool drives, and non-pooled OS drive also, obviously).. For a specific reason I fail to remember (lets call it old habits), I switched to lettering and never looked back once. Thanks !
    1 point
  5. FWIW, I just removed all drive letters from my DrivePool HDDs. DrivePool does not need a drive letter to recognize a HDD in the pool. It uses the hidden PoolPart directory. Removing drive letters on the HDDs makes a less cluttered display in Windows 10 File Explorer as it will only show HDDs with drive letters. That works great for me as I currently have 16 HDDs in my DrivePool. Those HDDs are dedicated to DrivePool and nothing else. So I don't need any drive letters assigned to them. Of course, when you remove the drive letters, Windows 10 File Explorer can longer "see" the drive normally. You would have to go back into Disk Management and reassign a drive letter. I track all my pool HDDs by name, such as DP01, DP02, DP03, etc.... which also corresponds to the physical location on my rack. I also put the drive name sticker on the physical drive/case for easy identification. The HDDs in my pool do not have drive letters assigned to them, as I stated. The DrivePool UI lists the names all in alphabetic order, which is very nice. However, if for some reason I want to reassign a drive letter to a particular drive, I just use Disk Management and look up the HDD by name. That is much easier then trying to track all the S/N of the HDDs. I am not using Scanner, so I am not sure if that program requires drive letters to work. Is there some reason you need/want to keep any drive letters assigned to your pool HDDs? I found DrivePool was easier to work with when I removed all those drive letters from my pool HDDs. Just my thoughts to your initial question on how to not drive yourself crazy with numerous drives in DrivePool.
    1 point
  6. Hi gtaus, I can see that your account is following this thread, so hopefully you'll get notified about this response. Maybe check that https://community.covecube.com/index.php?/notifications/options/ is set to your liking?
    1 point
  7. After posting, I found an issue I had missed: the disk was marked as Read Only in disk management. After running DISKPART from cmd I managed to remove the read-only tag using the command attributes disk clear readonly and it appears to be OK now.
    1 point
×
×
  • Create New...