keinreis

Somehow, the PoolPart folder on one of my pooled drives was renamed "Documents" and it has the icon for, and displays contents per the view of a Windows "Documents" folder. Other than that, the drive is functioning fine, and all files are accessible. My actual Windows "Documents" folder is on an entirely different drive, and fortunately, Windows is not confusing the two "Documents" folders with each other. I did try to fix this by unhiding protected operating system files in that folder, and looked for a desktop.ini that might be telling Windows to call that folder "Documents" instead of "PoolPart.guid". But there was no desktop.ini file to delete or rename in that folder. When I pull up the properties on the pooled drive "Documents" folder (the one that should be a PoolPart folder), I can see the long alphanumeric name in the "Type" - i.e. .b04cc995-92c6-4325-a981-7f9e32866201 Can I just rename that folder "PoolPart.b04cc995-92c6-4325-a981-7f9e32866201"?

Done. Seems to have worked. After installing that version of Scanner, I am no longer getting File System Damage warnings on all the drives in my pool. Though I'm not certain these were all "false positives". Throughout my many rounds of testing the drives, CHKDSK /F had reported what appeared to be legitimate MFT Mirror Corruption and/or Bitmap Errors. But those have likely been resolved/repaired, and no new warnings have been triggered. So I think (hope) I'm good. I am now in possession of 5 new Seagate 8TB External USB 3 drives. My plan was to shuck those, and install the drives in some sort of external enclosure. I prefer to avoid USB 3, and I've had plenty of issues with eSATA in the past. My server mobo has USB 3.1 Gen 2 ports (10Gbps) on it (1 Type A and 1 Type C). I see that there are a few enclosures with USB 3.1 Gen 2 connections. The speed of USB 3.1 Gen 2 is appealing, but would it also be prone to the same kinds of disconnection issues as USB 3.0/3.1 Gen 1? Next month, I will get two more 8TB internal (NAS) HDD's, which will finally allow me to turn on duplication on my entire pool. This has been a process, but progress is being made. Thanks for all the help!

2.2.1.922_x64_RC has been installed. But I have not been noticing any file access issues lately. My main issue now is the multitude of File System Damage warnings I am getting on every drive in my pool, even after repeated repairs via CHKDSK /F. I also took Jaga's advice and tested every one of these drives in another PC. I ran CHKDSK /F on each drive. No file system issues were found on any drive. But just to be sure, I also used the drive manufacturer's diagnostic software to test each drive. No SMART warnings, no file system errors, no bad sectors. I then reinstalled these drives back in my server, and reset the "File System Health" status to "unchecked". The status changed Immediately to "File System Damaged" on each drive as soon as I did that. I ran CHKDSK /S on each drive again, and it found MFT Mirror and bitmap errors on every drive in my pool. They had been installed for less than 5 minutes. Not enough time (even for me) to cause an unexpected shutdown or BSOD. Any additional suggestions would be appreciated.

Thank you for the suggestions. I plan to test the drives in another machine - starting with the brand new Ironwolf drive. Unfortunately all my other desktop PC's are very old - having only SATA II. I do still have my trusty HP EX495 MSS up and running. This is not the server with File System Damage issues. The HP doesn't even have DP on it, and there's an open drive bay. Anyone remember if those have SATA III?

Update 4/29: I thought I was out of the woods and could move on with the recovery process, but it appears something is corrupting the file system on nearly every drive on my PC. This morning, upon booting up, I was greeted with whole new round of File System Damage warnings in Scanner. At this point all five of the drives in my pool have File System Damage warnings, including the brand new 8TB Seagate Ironwolf drive I just installed yesterday. I ran CHKDSK /F on all five of the drives, and only one reported any issues that needed to be corrected - "MFT Mirror Corrupted". This was supposedly fixed by CHKDSK /F. The other four drives didn't report any file system issues at all. I don't think I can disregard these warnings as false alarms. I did discover one folder that contains a large number of files is no longer accessible. File Explorer won't shows any of the files in that folder, let alone allow me to open, or move them. So far, I've only found one folder with that issue, but there could be others. Hardware-wise, I should mention that I have made some changes recently - after the first round of File System Damage and Bad Sector warnings earlier this month. I installed a brand-new, more powerful power supply, and all new SATA power and data cables. I am certain the physical cable connections are solid, but I have not run any Burst tests to see if there are SATA controller issues. Would that be a logical next step to take in the troubleshooting process? I also run a quality 1500-sized UPS which is not showing any "events", so I'm not apt to blame power issues for this.

Note to moderator - If this question would be better answered in the Scanner forum, please feel free to move it. Admittedly, I'm more of a "casual user". Ignorance was bliss in my case... until it wasn't. I had been on an older version of DrivePool for a long time by the time I finally got the memo, and installed the update to 2.20.906 - which was around the beginning of the April. Almost immediately afterwards, I started having file access issues on some of the drives in my pool. I was unable to move files from certain folders on certain drives in File Explorer. That prompted me to open Scanner for the first time in a long time to see if there was something wrong with those drives. At that point, I noticed that Scanner was stuck at 57% on one of my drives, and that it had never completed a full surface scan on that drive, which had been in my system for months. I contacted support, and Christopher recommended I upgrade to the latest version of Scanner, which I did. I also ran the Troubleshooter on both DrivePool and Scanner, and uploaded the log files. He didn't see anything that stood out in my logs, but he did point out that having both MalwareBytes and Acronis installed could be the cause of my problems. To quote him, "These use file system filters that intercept and can modify all file access. It could be that one, both or the combination of these filters is causing this issue." He recommended uninstalling one of both of them, to see if the file access problem went away. Has anyone else had any issues with these two programs? I've come to rely on both of them, and don't want to get rid of them unless it is really necessary. Well, before I could even try Christopher's recommendation of uninstalling MB or Acronis, the newer version of Scanner I'd installed started alerting me to all sorts of issues on my drives. Something must have really nailed me, because pretty much all five internal drives in my pool, and my OS drive, plus three 8TB Seagate External USB drives ended up with File System Damage (errors in the MFT bitmap, or MFT mirror corrupted). I ran CHKDSK /R on all the drives, but it didn't fix the MFT issues. A few of the drives, including my OS drive, also had damaged sectors - just one sector per drive. I was able to recover the files that were affected. All my data was backed up to the 3 8TB Seagate Externals, but two of those also had MFT Bitmap errors, and the third one had a bad sector. So I knew I had to work out a recovery plan. That's where I could use some help. I purchased a new SSD for the OS drive, and one new Seagate 8TB Ironwolf HDD for my pool. I also purchased three new Seagate 8TB External drives for backup. I am now in the process of moving data off the drives with issues, and on to new drives. I will also be purchasing a couple more 8TB drives as soon as I can to get enough capacity to start using duplication - which I have never used before. So far, I have removed one of the old HDD's from the pool, and installed the new 8TB Seagate Ironwolf HDD, which has been added to the pool. Installing the new 8TB Drive has given me enough free space to remove another one of my old internal HDD's which has MFT bitmap errors. That drive which will be removed next only has MFT bitmap errors, and no bad sectors. It's only been in service for few months. I'd like to reuse it, if possible. Would simply reformatting that drive resolve the MFT bitmap error issues? If reformatting the drive will work, then I'll probably do the same thing with the rest of my internal and external drives which only have MFT bitmap errors. Again, those drives aren't throwing any SMART errors. They don't appear to have any physical damage/bad sectors. Ideally, then I would be in a position to re-purpose some of the old Seagate 8TB external drives for local backup again. I would have a total of 5 of them, which would match the capacity of my internal drives in my pool. Dealing with that many external USB drives is a bit of a pain, though. I was thinking of shucking the external drives and putting them in some sort of external enclosure. Are there any good external enclosures on the market? Thanks for the help.

Appreciate the reply. Though they don't refer to it as USN Journalling, I think this is the setting you were talking about:. Propagate modifications Files and folders modified on the source side are overwritten on the target side during synchronization. I now have that one un-checked, and it isn't trying to create all new files unnecessarily. DrivePool is working great. Glad I decided to give it a try. Thanks,. . - Rob

I recently had to migrate data from 5 X 4TB HDD's that were in an old WHS 2011 setup when my eSATA enclosure's power supply died. I was basically just using WHS 2011 as a file server, so I decided just to move on from WHS 2011 and build a Win10-based PC in a case with a lot of 3.5" drive bays instead. Before I built the new PC, I backed up all the data on the 5 X 4TB HDD's to external USB drives. I wasn't using DrivePool on WHS 2011. Upon completing the build of the new PC, I decided to give DrivePool a try. I purchased the 2.0 version, and installed it. I then installed three brand-new 4TB drives, and created a new pool - adding those three drives to the pool. I copied over as much data to those three drives from the external USB drives to the three HDD in the pool as would fit. I still had two drives from the old WHS setup, which were less than a year old, and checked out healthy -so I decided to re-use them at least temporarily. Having read that drives with existing data could be added to a pool, I just installed those old 4TB drives and added them to the pool. I moved the data out of the old WHS 2011 ServerFolders into new folders, and added those folders to the pool. I ended up with exactly what I set out to have - five 4TB drives, and their data, in a pool. I know DrivePool offers file duplication, but I just don't have enough free space on my drives to duplicate everything that I would need to. I also prefer to have an offline backup, so I set up Allway Sync to sync all the data in my pool back to the same external USB drives that I had previously used to back up that data in the first place. I have added no new data to the drives in the pool yet. Even the folder structure is identical between what's in the pool, and what's on the external USB drives. I am now attempting to set up a one-way sync from the pooled drives back to the external USB drives in Allway Sync. When Allway Sync "analyzes" the data between the pooled drives and the external USB drives, it doesn't recognize that any of the existing files are already on the USB drives. It wants to copy everything over again - which shouldn't be necessary. I'm new to the pooled drive thing, so maybe I'm missing some elementary understanding of how it works. Any idea what I need to do to set up the sync properly so I don't have to copy all the files over again? Thanks!