Jump to content
Covecube Inc.

fleggett1

Members
  • Content Count

    13
  • Joined

  • Last visited

  1. That's excellent to hear, as I was thinking of replacing my two stone-age Supermicro HBAs: https://www.supermicro.com/en/products/accessories/addon/AOC-SASLP-MV8.php With this Broadcom/LSI controller since it supports 16 ports on just the one card: https://www.broadcom.com/products/storage/host-bus-adapters/sas-nvme-9500-16i Any problems I might run into?
  2. Outstanding. Thanks a bunch for the quick reply.
  3. Sorry for the threadnecro, but due to some Best Buy sales, I was able to replace the four low-capacity drives with four 16TB monsters. However, because of the way my enclosure is put together (insufficient airflow), it looks like I'm going to have to separate them due to heat issues (as reported by Scanner). As such, I'll be repositioning these drives in my bays so that they're not immediately next to any other drives (they're low-capacity, so I'll probably just pull and retire them). This isn't gonna screw anything up, will it? Is Drivepool's drive identification bay-dependent or inde
  4. Well, there have been some pretty unfortunate incidents since I last posted. I sent the drive off to RRG. They said it was either a firmware or platter issue. $400 for the former, around $900 for the latter. And they couldn't tell me which one it is without delving into the drive, which means a repair commitment. I told them that I'd have to think it over. That's just the tip of the iceberg, though. I think my system is trying to suicide itself. That 6 TB drive that had the bad sectors finally gave up the ghost. I was able to evacuate it via the Scanner plugin, but it might've
  5. Sorry for the late reply. Some real-life stuff got in the way. Thanks for all the feedback. I wound-up sending the drive to RRP for possible recovery. I mailed it last Friday, so I don't expect to hear anything for at least a few more days. I put an unofficial limit of $300, but because the drive can be read for about a minute after the OS loads, I'm hoping that it'll be less than that and that it's something relatively simple, like maybe an overheating or otherwise marginal, but not 100% failed, part, like you see with a lot of RRP's Macbook repairs. Regarding which drive to get
  6. Huh, I didn't know DP could perform per-folder duplication. I'll definitely check that out once I can get the system settled. I should probably go ahead and purchase another 10+ TB drive while I'm at it. Just as a follow-up, I put the drive in my fridge overnight and just tried reading it. It worked for about two more minutes than before, then died again. The motor still spins, but there's a spanner in the works somewhere. Through some teeth gnashing, I also went ahead and contacted RRP to explore my options. I'm now just waiting to hear back. If RRP can recover, say, 90% o
  7. Okay, I deslected those options within DP. When I next rebooted, in the nick of time, I managed to assign a drive letter, do a dir /s /b on the drive, and capture the output. Lotsa stuff that can be replaced, but predictably, there was more than a few files that will be exceedingly difficult to re-source. It's a good thing I didn't keep my banking records on that drive. One thing I thought I noticed were directory entries with no associated files. Can DP store directory markers on one drive, but the files in that directory on another drive? - nvm, I confirmed that when I put the d
  8. Here's a thought - could I simply just assign a drive letter to the troublesome drive and, while it's still being recognized, do a simple dir /s, capture the output, and go from there?
  9. Thanks for the quick reply. I kinda/sorta get what you're saying on an abstract level, but not on a nitty-gritty one. I suppose it comes down to the age-old question of where exactly are the files stored on a pooled system, especially and critically if they're not duplicated on other drives. From what I recall when I installed DP some years ago, I chose to NOT have a software RAID-style setup, instead opting for a simple JBOD configuration since I didn't have many drives at the time and, therefore, almost no storage space to spare. I figured if I needed to do any drive replacements in
  10. Yesterday, I got the dreaded notice from DP that a disk had dropped out of the pool. After a reboot, the drive reappeared, so I started the removal process. About 10% in, the drive dropped out again. Rebooting seems to revive the drive, but now it only gets to 0.3% before it drops out. Only the percentage figure shows progress (up to the aforementioned 0.3%) - the actual byte report remains static, which makes me suspicious that any data is genuinely being transferred. What really sucks is that this drive (a 4 TB WD Red) was almost full. I didn't RAID anything, so it's just a simple
  11. Okaydoke. I just removed the letter manually. Thanks for the replies.
  12. Okay, but just to be crystal clear, Drivepool will still be able to access and use the drive once the letter is removed? And that's all that's needed? Nothing off-the-wall, like doing some registry tinkering?
  13. My apologies if this has already been discussed, but I recently added a 10 TB WD drive to my Windows 10 pool using 2.2.3.1019. Drivepool rebalanced everything just fine, but Windows Explorer can still see the new drive as an individual disk with its own drive letter. This has me a bit weirded-out, as my other pooled drives are invisible to Explorer, which seems like "normal" behavior. Do I need to manually go into disk management and remove the drive letter? Or does Drivepool do more than that to hide pooled drives?
×
×
  • Create New...