Jump to content
Covecube Inc.

thepregnantgod

Members
  • Content Count

    178
  • Joined

  • Last visited

  • Days Won

    5

thepregnantgod last won the day on March 29

thepregnantgod had the most liked content!

About thepregnantgod

  • Rank
    Advanced Member

Recent Profile Visitors

441 profile views
  1. Nope. And I just rebuilt the pool and it's still doing it.
  2. So, I'm using the newest beta and this started happening. I get two new drives in Disk Management that need to be initialized (I haven't for fear of jacking something up) but they are exactly 2048GB and I don't have any 2TB drives (plus 2TB drives don't read as 2048gb). Then I see some covecubecoveFS to add to my pools. Is there something wrong? Screenshot attached.
  3. Okay, an update. For the record, it's not Drivepool, exactly. I switched to Storage Spaces with a x3 mirror (BAD DECISION). Everything was perfect and then woke up and the entire drive was not formatted. Lost about 6TB of data. Not happy. Had to go back to Drivepool. Now, my previous pool (which was still on the drives) had some funky folder sizes - like over 8gb for a coves folder (I'm guessing where DP maps everything). And, everytime I would install DP no matter the version, it would hang on loading service, it would wonk out my Norton, it would lock up my system from uninstalling, etc. Very annoying. So, on a clean system, I took my previous drives and then via Treesize went in and deleted all traces of the PoolPart folders/covevs while leaving my data there. Did that for about 10 drives or so. Installed DP, loaded perfectly, did nothing to Norton. Rebooted cleanly, etc. So, as far as I can tell, somehow my previous pool got corrupted and then any new pool would jank everything up. (as an example, multiple coveFS folders had over 1,000,000 separate files in them and were stubborn to delete) To Chris/Drashna, a neat option (that to a non-programmer seems easy) would be to have Drivepool prompt, "Previous Pool detected, would you like to import?" Then we can say NO!
  4. Nope. And I dont want to dog you guys out. Two things possible...win ver 1809 or maybe a x3 duplication over 10+ drives. My coves folder on some drives was 8gb!
  5. Anyone have experience with this? I can't get Drivepool (the release version or any of the betas) to load the service without hanging the entire system. I've installed Windows 47 times now over the past 8 days. Patched, unpatched, loaded Drivepool at the beginning or after the patches, still - once I import my existing pool everything hangs. Checked all the drives for errors - can access them perfectly if Drivepool isn't installed - Drivepool just has "starting services for hours and hours"
  6. First, I'm sorry this happened because it's happened to me...more than once. Don't format it. Programs like Recuva and Reclaime can help you scrub the drive for anything recoverable. I'm hoping you didn't use Windows new format ReFS because when that one gets hosed you get nothing back. At all. I'm sticking with NTFS simply for fear of a RAW drive. And if you're using Drivepool duplicate duplicate duplicate (I usually set it to x3 but if I get enough space maybe even x4)
  7. As a follow up, I must have reloaded Windows 35 times in the past few days. On this go round this is what I did: 1. Clean Install of Windows, fully patched 2. Install Norton - run scan - no hang/clean 3. Install Chipset drivers - run scan - no hang/clean 4. Insert each of 10 drives individually, scan for errors (chkdsk) then scan via Norton - no hang/clean 5. Finally, after all 10 drives are scanned, clean and error free, I install DrivePool beta (latest). It hangs on install (see image) and now Norton hangs on scan. What gives?
  8. I'm late to the convo but from my personal experience... I got a 1600W Titanium EVGA PSU that powers a Zenith ROG extreme mobo with a 2950x OC'd to 4.1ghz. It also powers 2xTitan XP (SLI) Nvidia cards. Attached, I have 2 SSDs, 3 NVME drives, 6 Bluray drives, and various fans. Three HBA cards (a LSI 9201-16i and two Intel expanders). I also have 37 Green drives from 3TB-12TB and 3 SAS drives. My PSU is able to support all that. Now...that being said, I can't plug the vacuum into the wall in that loft because that'll trip the switch since my system is likely pulling max from the wall.
  9. So, this is new. System starting hanging quite a bit and I don't have a problem reinstalling windows so I did. But despite about 15 different installs now, Drivepool is still causing my Norton Antivirus to hang on scans as well as all basic Explorer functions. Here's how I've isolated it (over the past few days) 1. Clean install Windows 10 fully patched to 1809 2. Install Norton, updated - clean scan without hang 3. Install Chipset drivers - clean scan without hang 4. Connect all drives - clean scan without hang 5. Individually, chkdsk each drive, individually scan each drive and all files - no hang 6. Install Drivepool, won't actually load services and then Norton hangs on various files (it changes each time) 7. Now reboots are not clean (it won't reboot or shutdown without a hard turn off the power). 8. Uninstall Drivepool or disconnect all the drives that Drivepool is trying to read - clean reboot and Norton doesn't hang. So I can only surmise it's something in the driver/software that Drivepool is using to connect the drives that causes this. (Oh and I've tested both the released version and the beta - which BTW, the beta numbering is odd - you are normally sequential and this time you jumped quite a bit) Any ideas would be greatly appreciated.
  10. Yep, that's how it would work but things get a little more complicated likely because of my setup and individual experiences. I have 40 drives (previously all in one pool). The idea is that with everything triple duplicated, I could lose up to two drives at once and still have one copy of all my data. But...sometimes my drives will throw up errors and then go missing? I pull up Disk Management, the drive is there, so I add a letter, use Treesize to find the files that are somehow so hidden that Windows Explorer won't even show them with the Hidden Files toggled. Treefile size shows giant directories under found.000 and found.001 which are created by chkdsk automatically. The metadata showing it as a Pooled drive is gone or corrupted and most (fingers crossed) of my data is contained in haphazardly organized folders because they never seem to have the same folder heirarchy after this. Now my pool is jacked and I have to go through manually and rebuild. (I'm doing this now but have decided to break them into 2 x 20 pools so ideally it'll go faster). Point is, perhaps I don't trust the duplication or when it takes more than a day to remove a drive, it would take me 40 days to rebuild my pool. Maybe I'm just impatient. If I could find a way to stop having my drives randomly throw errors that cause chkdsk to jack everything...
  11. 1. Yes, I have duplication. 2. It starts over, I believe, because it has to go through all the contents on that disk and compare it against the contents on 39 other 3-10TB disks (all green so not super speedy). 3. And if I simply remove the disk myself without using Drivepool, then I have 2 million files on it that have to be compared anyway manually by copying them back to the main pool and then telling windows to skip those that have the same name/size. Tedious.
  12. I've been trying to remove a drive for days now. It's stuck on 92.3% and I don't want to reboot because it'll have to start over. If I just hard remove it, then I have to copy over nearly 8TB of data and wait for Explorer to tell me that most of it is already on the drive... Any ideas on how to expedite this?
  13. Is it possible to add a striped drive (two NVME drives in Raid 0 via Windows) to a Pool?
  14. So, I have 4, 8 bay enclosures with their own PSU to support my Pool. Lately, I've been paying more attention to Event viewer and realized that all the errors are coming from one port/drive bay not a drive (as I originally thought). The error is : The IO operation at logical block address 0x15461528 for Disk 5 (PDO name: \Device\000000a5) was retried. Now...I'm not getting any NTFS errors that say there's corruption on the drive or anything. But can someone smarter than me tell me if this is something I should worry about? Should I remove the drive from that bay and leave it empty? Or can it be ignored like some Distributed Com errors that I see on every single computer build I do?
  15. So, for future reference, I did take the following steps. 1. As Spider99 suggested, I mounted each disk to a folder on my C drive. Now, in Event Viewer any NTFS drive errors show which volume (i.e. disk) so I can add a letter to it and then scan. 2. I'm still unable to simply scan within windows without actually adding a letter to it. I've not tried using CMD/Diskpart then chkdsk volume because that's actually more tedious then just adding a letter and going to properties/scan.
×
×
  • Create New...