mr_yellow

Hey guys, I'm trying to do a drive removal and it gets about 50% and fails with the following error: Error Remove <DRIVE> from Pool <Pool> Error Duplicating File "\?\\GLOBALROOT\Device\Harddrivevolume21\<FILEPATH>", The system cannot find the path specified. However when I look in the pool, I see the file and when I dig into the drive's pool.part, I see the file as well. I can open the file, copy it, renaming it etc.. but I still get he same error with the same old path. Any ideas how to resolve this? The drive is perfectly fine and was scanned in the last 30 days with zero errors. Restarting the removal just errors out with the same file. Thanks!

Hi all, kind of a weird question but here goes... I'm planning to unceremoniously copy data direct from a drivepool's drive onto a new unraid array, then wipe the drive and add it to the array. How exactly will drivepool handle this when I eventually boot back into windows with the drives still attached (to do some housecleaning of the OS)? Will it not see the drives because they're no longer NTFS formatted (at which point I can do a forced removal)? or will it potentially do something dangerous to the drives trying to reconnect them and potentially harming the new xfs partitions that unraid built? Thanks!

Hey guys, Been running drivepool for many many years now and finally getting around to researching ways to avoid bitrot in my duplicated data.... As far as I can tell, SnapRAID seems to be one of the ways to do this but information seems to be scattered all over the place. Has anyone written an end to end guide on running SnapRAID with Drivepool? There seems to be some intricacies with how to best setup snapRAID as well as how to restore data in the event of a drive failure... Much appreciated,

Never heard of snapraid... googled it a bit and it seems like a good way to add parity checks to files stored on a disk... but I'm confused how it will work with drivepool. Do I run snapraid against the drivepool itself or do it point it to the individual drives and have it scan the files on the drives directly? Does this remove the need to duplicate any drivepool data? How would I go about running parity against only certain files in the drivepool that might be spread across various drives? Thanks,

That makes sense. Has there been any discussion on beefing up file integrity either through manual parity scanning or other means?

Hey Guys, Absolutely nothing against drivepool and have been a faithful drivepool user for at least a decade now but I've been worried about data integrity after discovering some corrupted photos probably from a damaged drive removal at some point over the years. I've contemplated migrating from windows + drivepool to something like unraid for a while but not sure what's the best way or if there are other options out there... Especially if there's any sort of a way to do an in place migration or reuse the existing hardware (HP ML310e + LSI SAS card + USB3 enclosures). I'm sure i'm not the first one to think about this... What have other members here done? Thanks!

Thanks for the tip with MultiPar.. I will definitely try this out because I've already discovered a few corrupted JPGs of my kids in my photo library and that's with not even trying so I'm definitely worried about data integrity about the rest of my "backups". I've been running drive pool for so many years now, I've had thoughts of going unraid and setting up a proper RAID pool for the sake of data integrity. I'm not too worried anymore about maximizing the space that I already have with the selective duplication. But I'm not sure what is the best migration path. I'm curious if anyone else here has transitioned from drivepool to windows spanned volumes (which contain their own parity volumes). The duplication errors eventually went away on their own after a few more reboots and rebalances. Maybe the migration question is best asked in it's own thread.

Hi! So I unfortunately had a drive throw SMART errors and eventually gave up it's ghost. While it was giving errors and I had a replacement on order, I did the following: 1) I setup new placement rules that moved some more "important" data off the drive and moved some more non-essential stuff only to that drive 2) My pool was pretty full (drives were well past their 95% limit) so rebalancing would complain of not being able to move X amounts of GBs 3) eventually the drive got worse (more and moreunreadable sectors) at which point I tried to remove the drive from the drive pool (but only checking off skipping duplication for faster drive removal) 4) in that process, the drive *really* died and is now not even mountable in windows. sometimes it'll spin up but the the drive name defaulted to "local disk" in windows and it complains that the drive is not readable. During this time, the drive showed up in drivepool with the generic label and I clicked "Remove" and it disappeared. It didn't even have a prompt on how to remove like before. Poof, it vanished. Okay, so the drive is dead and it took along with it a few TB of data. I can live with that since I managed to pull a list of files and nothing critical was amongst it. Now, the drive pool is giving a Duplication Warnings saying ~15 files are missing: 10:26:38.1: Warning: 0 : [FileDuplication] Error checking file \\?\GLOBALROOT\Device\HarddiskVolume15\[REDACTED] for duplication consistency. The system cannot find the path specified 10:26:40.3: Warning: 0 : [FileDuplication] Error checking file \\?\GLOBALROOT\Device\HarddiskVolume15\[REDACTED] for duplication consistency. The system cannot find the path specified 10:26:40.4: Warning: 0 : [FileDuplication] Error checking file \\?\GLOBALROOT\Device\HarddiskVolume15\[REDACTED] for duplication consistency. The system cannot find the path specified ... 10:27:03.6: Information: 0 : [FsControl] Set overall pool mode: PoolModeNoReportIncomplete (lastKey=FileDuplication, pool=4538dc0f-4f53-419c-a2bf-63406948c107) I've tried clicking "Duplicate now" but after it re-measures, I get the exact same error message. Afraid to click Rebalancing... What's also curious is when I spin up the drive and it mounts as "local disk", it DOES actually show up in Stablebit Scanner under the custom drive name I gave it and I can see there's a lot of activity (80-100+ MB/s at some points). What's going on here? Is the drive self scanning itself? SMART is showing a slew of realloc sectors (25k+) and the unreadable sector is 100+ now, vs 24-32 before... Should I leave the drive plugged in and let whatever is scanning it finish? From what I've read in earlier posts, I've enabled file system logging in troubleshooting but not sure where that log is. Any advice?

Hi, just wondering if there’s a newer beta to try? I’m on 2.5.4.3216 and I have this damaged file system issue on two drives. Thanks

If I could interject here, I have an HP Gen8 Server (ML310e) running the same B120i controller and it is possible to run that controller in straight ACHI mode. It allows all the SMART metrics to pass through with the default settings in Stablebit Scanner. I have 4 Drives plugged in right now and they all report back without issues. If OP is running a single drive RAID volume, maybe it's worth it to just switch to ACHI. I also had similar issues with getting SMART data from a USB enclosure. I just assumed it was a limitation of the USB. What's weird is that I can plug the same enclosure via eSATA and I can get SMART data coming back with that... I'm going to read through this thread a little closer and see if I can get SMART via USB again.

Hi Chris, Thanks for the suggestions. I did try taking ownership and it kept failing with the same error. really strange. what's stranger is that I recently moved the drive with the access is denied errors from a marvel 88SE9230 controller to an Intel controller while troubleshooting some SSD detection issues and after rebooting with the drive on the intel controller, all the folders I had issues taking ownership of disappeared. This allowed me to delete the entire old PoolPart folder. (yay!) I don't quite understand why but I wonder if the OS treats the drive differently if it's detected as a hard disk drive vs. a solid state drive... Anyways, Thanks for the suggestion to copy the other files in the old PoolPart directly into an existing PoolPart. My only worry is that some of these files are old or have been updated or moved to new locations. I think i'll have to set aside a few hours and manually verify that the files already exist in the Drive Pool before I go ahead and straight up delete them. Thanks,

Hi, 2 issues i was hoping to get some advice on: 1) I recently removed and re-added a drive from my drive pool while juggling some file placement issues and it's left behind an old PoolPart.GUID directory that I can't seem to delete. There are no files and all the "leaf" directories (directories that don't have anything in them) report back as "access is denied" whenever I try to access/delete/change permissions. I'm running with admin privilages as well. reboots haven't cleared up the broken folders either. CHKDSK is clean as well... this is on a w2k2012 r2 OS. 2) I've also noticed i have another old PoolPart.GUID directory on another drive. This time, it *does* contain files (~2.8GB's worth 1000's of files). Last touched more than a year ago.. This was probably from another drive removal and then re-add. The files are still readable and directories are accessible (unlike issue #1). Anyone know of a way to easily validate the files in this old PoolPart are safe to delete? It's a lot of directories and a lot of files. thanks,

Hi Chris, Thanks for the help, I've currently left my 1TB SSD as an archive drive and forced the VMDK's to live only on the SSD. Everytime I set the 1TB SSD as an SSD drive, the SSD Optimizer does seem to want to start moving stuff off the SSDs right away. so for now, I've left it as an archive drive. Is there a way to set the amount of unduplicated files on an SSD drive besides zero? Thanks,

Now I have some strange behaviour... It looks like the new SSD is not respecting the file placement rules i have. I've excluded the SSD from the video share yet I see a lot of duplicated videos being stored on the SSD I've included ONLY the SSD for my VMDK's, yet I only see ~50% of the actual VMDK's being stored on the SSD. What exactly is going on here? Is there a way to force drivepool to reshuffle the files around? Thanks,

I noticed another weird behaviour with the way the SSD Optimizer Balancer works... So I've setup a bunch of file placement rules to force some VMware VM's onto the new 1TB SSD I have. Drivepool says it's out of balance, and I initiate a rebalance and it happily moves all my VMDK's onto the new SSD. Then, it says it's out of balance afterwards, so I click to rebalance and then it starts moving files OFF the SSD. I suspect this is because of the SSD Optimizer Balancer because it's marked the drive as an "SSD" drive and sets the unduplicated target to zero. The balancer then goes back and forth between moving stuff onto the drive and off... Any way I can force files onto the SSD first, and while still allowing other 'archived' files to remain on the drive? thanks