lionelhutz

It's an HP B120i controller. I have partially solved this issue. I noticed that the controller had a logical volume of only 3GB on my 8GB drive. Not sure how that happened. Perhaps it thought the old 3GB drive was still there. Anyway, I had to delete the 3GB logical volume and put a new 8GB logical volume on the 8GB drive. Drivepool is currently reduplicating my data to the new logical volume, so I'll let that happen before I do anything else. Scanner still says the remaining 3GB drive and one of the 4GB drives is "File System Damaged". Trying to repair doesn't work.

I'm using an HP Gen8 Microserver running Windows Server 2012 R2. Until recently, I had a Drivepool of five storage drives: 2 x 3TB, 2 x 4TB and an external 8TB. One of the 3TB drives showed damaged sectors, so I removed it from the Drivepool and then physically removed it. (I shut down the server first.) Then I shucked the external 8TB and installed that where the 3TB had been. I did some reading and it seemed that Drivepool should be okay with this. The drives all seem okay but Scanner has two issues. Firstly, Scanner is reporting 2 x 3TB and 2 x 4TB drives. When I expand the "> file system health" section for the 8TB, that section does list it as 8TB, but the "size" section still calls it 3TB. Secondly, Scanner is reporting that all four drives have "File System Damaged". Attempting to repair didn't work, and as long as Scanner doesn't seem to have identified the drive properly, I'm almost afraid to try in case it tries to wipe data to make it a 3TB! Drivepool is seeing the 8TB drive okay. It has marked 10TB of data as "other" but I assume this is because Scanner is telling it there are file system issues.

I have resolved this problem so I thought I would post the resolution. It wasn't a disk issue, it was a folder permissions issue. At some point, all my Shared Folders' permissions got totally messed up. Not sure of the original cause. Possibly my attempts to fix things made it worse, permissions are really complicated. I fixed it by removing each drive from the drivepool, copying any remaining data off the drive, reformatting, then adding the clean drive to a new pool. Then I created new Shared Folders in the new pool and gradually copied all my data into them, checking permissions as I went. I suspect this is a lesson for any new Windows Server installation: create new shared folders and then copy data into them. Don't try and point straight at your old shared folders. The fix took ages because I had more data than space on any one drive, so I had to keep shifting data around. Permissions were so messed up there was some data I simply couldn't move off a drive, luckily nothing important. I suspect there could have been file system level problems, because I wasn't able to reformat the drives until I deleted the old partition using disk management. Since the fix I have moved my Client Computer Backups shared folder back to the drivepool and it seems to be working fine. So I don't think there is any inherent problem with having that folder in a drivepool.

I have recently had problems with Windows Server Essentials R2 client backup, and my best guess is that it is something to do with having the "Client Computer Backup" folder in a Drivepool. This is new: I have been running the server for about 18 months with client backups going to "Client Computer Backup" folder in a Drivepool and everything was fine until the last month or so. The backup service kept stopping itself and if I manually restarted it, it would stop again almost immediately. The logs showed regular WriteFile and EOF errors. I scanned all my drives with StableBit Scanner but found no errors. I reinstalled the server OS (again with the "Client Computer Backup" folder in a Drivepool) to no avail; the same errors kept happening. Then I got the bright idea to move the "Client Computer Backup" folder to my system drive (temporarily) and the errors stopped. I then moved it to a separate drive outside the Drivepool to give it a bit more room and it still appears to work fine. So I can only conclude it is a problem with Drivepool, or at least with how backup deals with Drivepool. Searching on old posts, I see quite a few reports of similar issues from around 2012. Is this still an ongoing issue? Or is there a way to get my "Client Computer Backup" folder back to the Drivepool?