surfyogi

I lost my C: SSD drive some time ago. I seem to have lost a good working backup of it as well... So I installed a new Windows 7 on a new SSD. I now have the pool back up and running, with 1 difference. I don't know how to restore my Folder Duplication settings precisely as they were. I have a few questions regarding how drivepool will act for me, so please follow, and I'll be brief: 1) Can I save my folder duplication config file (or, where is it and what's it called?) so that I can reload it sometime later if I lose my Windows C drive? (assuming I am using same version of drivepool on new configuration? ) 2) What happens to my backed up folders if I lose my C drive, have to re-install Windows 7? Will the original duplicated folders still be duplicated across 2 or more drives (for example, if I have 10 drives pooled)? 3) If for any reason I don't set up backup folders immediately after a Windows re-install, will those duplicate folders/files stay as is, or will they be deduplicated over time by DrivePool? I have used this forum many times before, and I don't remember these questions ever being addressed, it may be a special situation. Please point me to other threads if this is a duplicate question.

I am recovering a drive I pulled out of a hot swap box ( the drive lost the drivepool partition because I didn't unmount the drive from Windows first). I now have all the recovered folders/files sitting on a spare drive (thanks to WonderShare Data Recovery) and am slowing copying them back to the pool. My questions is this: Is there some difference between using Windows 7 copy, vs Win7 move? (as far as the drivepool emulation is concerned?) What I have noticed is this: (I know how to force Windows to copy or move, as I need to of course) a) If I use "copy", I may or may not get a "merge folders" dialog, and a "these files are already present, replace or no?) dialogs. If I use copy, it will often times just look like its copying, I will come back after some time, expecting to see a merge dialog up, and I see nothing. No copy going on, no dialogs, nothing. Like it just copied the first few folders and then stopped? If I use "move" on the other hand, it seems to always do a reliable deep transfer of files all the way down the tree, across all folders, very reliably. I was not aware to expect different behaviors between these 2 operations, except of course, files that are moved will be deleted from the source drive. I am of course, copying from a spare recovered filed drive, to the emulated pooled drive. I assume this is not a bug in windows. I'm thinking it's a bug in DrivePool filesystem emulation? I'm on version: 2.1.1.561 Anyone else ever notice this behavior?

I've moved it around, that's standard procedure. This is such a strange problem, I doubt anyone has seen it before me. I've tried it in 2 different external docs, vs the internal desktop bay, and various internal bays. Identical behavior, even when I use a different disk drive with a cloned filesystem of the original. 1 drive of 16, one drive only. It's taken me a while to isolate it, and never really have been able to.. - The drive is a problem regardless of drivepool service is running, or not. Windows 7 not happy.. - The drive is a problem even if I clone the drive (with cloning dock) to a new identical clone of the drive. - The drive is a problem and constantly dismounts, remounts, even if I plug it into an external e-sata enclosure, or have it on board my desktop pc internally. - The drive will not remove from the drivepool; it will dismount before operation can finish. I've been pulling the files off the drive, in anticipation of not being able to use the filesystem that's on it (which I have attempted to scan and fix several times). Something with the filesystem, and Windows 7 does not like it. I can use the drive in a dock, and read the files fine with a Mac.. and copy them to a new disk, new filesystem, and that works just fine. So I assume once files are rescued, then I can just format the drive(s) and they will work again. Can you please point me to the most recent documentation, on how to replace a drive that will not Remove in the normal fashion, from the drivepool?

I have been using StableBit DiskPool for several years. I'm a true believer. I rarely have to touch it, sometimes it goes a year at a time without much attention. But recently, I see something I don't understand. My U: drive, is up and down, on and off the pool. It gets reported as off, and within a few seconds it has reconnected. I have installed a power supply I think is big enough, since most of the disks are in an external enclosure with it's own power. I don't see this same problem with any other drive. I have moved the drive to different location in the cabinet, to test wires, power, etc. When I put it in an external dock, still does same thing.. So I cloned it to an identical new drive, and put it back in the main cabinet. New drive, still does same thing. I have run dskchk on it, and it has a few problems, then it should be ok. Every time I reboot, dskchk wants to give it some attention, but not that much, so I'm not sure what to do now. I've moved the data to a new drive, same issue; I'm thinking filesystem problems.. This may be a Windows thing, but still, it's got exclusively DiskPool files on it. And I have attempted to remove and add it back to the pool. No help. I am a veteran windows user, and I have tried everything I can think of (so far) to isolate this to a disk, or filesystem, or something I can deal with directly to fix it. I'm seriously thinking of adding a new drive to the pool, then migrate files off the new U: drive, and see what that does for me, but I can't imagine that should really be necessary. Any suggestions?