Umfriend

OK, so it is a bit scary to advise on this. Best may be to wait for Christopher. You could try to run a CHKDSK but as these won't have a drive letter I am not sure how. To be honest, I fear that something went wrong, seriously wrong and it may have to do with the use of USB. I think Chris is no fan of USB for DP. I would guess that this is not really a DP issue but perhaps someone here can help. Probably best to not do anything at all until you had advice you trust.

In your case I would do both. I hope it works out. Have you tried attaching one of these drives to another PC? How are they attached? How did you affect the reboot and do you see anything weird in Event Viewer?

Look here:

lmgtfy: https://www.pcworld.com/article/2047513/fragging-wonderful-the-truth-about-defragging-your-ssd.html?page=2 https://www.pcgamer.com/should-i-defrag-my-ssd/ TL;DR - No.

AFAIK, all you need to do is / how I would do this: 1. De-activate license on current PC (write down the license key somewhere) 2. Disconnect the Pooled HDDs (I am assuming that none of the HDDs also have the OS partition on it BTW) 3. Build the new PC and install Windows 4. Download and install DrivePool 5. Shut down PC, connect the Pool HDDs and boot. Presto! DP should recognise the Pool. Do NOT make a new Pool. There may be an issue with access rights on the Pool. For that use http://wiki.covecube.com/StableBit_DrivePool_Q5510455

The only way I think this works is if you use hierarchical pools where the cache runs on each lower-level non-duplicated pool. To my surprise, someone claimed in another thread it works and it may well be.

AFAIK, Stablebit is a small company and forum support may be out for a bit. Having said that, Hyper-V Server 2019, or any other 2019 Server, is not listed on https://stablebit.com/DrivePool/Download so even though it may run (I suspect it will) it is not officially supported as such. On Server 2019 with Essentials Role, there is no such thing. 2019 Essentials does not have the dashboard, anywhere access, client backups etc. at all. Basically, 2019 Essentials is a Foundation type edition. IMHO, it is worthless. Server 2019 does not come with the Essentials Experience / Role at all.

Well then it would be the THD - LHD in case of x2 duplication. I am sure if I take a bit of time I can get to an actual general formula but it is rather simple and why bother.

The latter so 1.5GB. As long as the largest HDD (LHD) is less then or equal to the total HDD (THD) size divided by the duplication factor (DF), the net available space (NAS) is THD / DF.

I don't really know but I would have tried moving the files left manually or to find out what kept the files locked.

Frankly, I do not know...Sry.

So my guess is, the HDD is simply toast. Again, look at Event Viewer. If the data is valuable, consider not messing with it and finding a professional to recover whatever can be recovered.

I have cloned OS drives on a number of occasions. Never had an issue. That is assuming, of course, that the OS is not on a HDD of which another partition is part of the Pool (should work as well but you'll have two bootable drives until you delete the old partition and that may be somewhat confusing).

I am new to WSE2016 but I have noticed this too. I think it happened more when I ran bitlocker. In any case, typically, with me, the dashboard finds them a bit later and the health message disappears. More often than not, closing and restarting the dashboard itself suffices.

What data recovery software have you tried and what did it say? Can you have a look at Event Viewer and see if there are DISK/ATAPI/IDE/NTFS errors? Have you tried attaching the HDD to another PC using a different cable (or another port using a different cable)?

Is it even connected to the interweb? If not then a move to WSE2016 might be a bit expensive (I got a really cheap 2nd hand license, still more expensive than WHS2011 at the time). Yeah, 120GB is enough although I am never sure about how much it needs at install time (that was a thing with WHS2011). I got a 240GB. Maybe may advice was not that sensible after all, it does depend on your use case. If it is basically cold storage/archiving _and_ you only backup the OS HDD (which I would not like but he, 24 TB is hard to backup and rotate offline), then I would also consider keeping it as is, don't bother with 2TB partitions and replace one at a time once in a while with the largest HDD you can get.

Yes, once you get past the 20GB and a bit, you'd need to leave them idle for a bit to get decent writes again. If you keep throwing data at them, once the non-SMR cache is full, it'll be slow without recovery. SSD with optimizer may help but then the write must still be less than your SSD + 20GB and a bit. I have had great sustained writes on the SMR drives but that was in cases of real sequential nature. You got 4 SMR HDDs? I might be interested. 4 would allow fast writes of 80GB in one go already!

I assume the 8TB is attached through USB. My advice: 1. "Remove drive from pool" one of the 2 TB non-system disks; 2. Replace it with actual 8TB HDD (I am always suspicious of USB-connected HDDs for longer periods) 3. "Remove drive from pool" the (data partition on) a 2 TB system disks; 4. That HDD, really, replace it with an SSD. Not only does the system become way snappier, I would never use OS and Data from the same HDD. Do a Server Recovery for the OS partition to that SSD (I always disconnect the other HDDs when I do a system recovery). 5. "Remove drive from pool" another 2TB HDD, replace with an 8TB HDD and so on. Do you backup your data as well? Remember, WHS2011 does not support backups of _volumes_ in excess of 2TB, so if you want to backup an 8TB HDD with WHS 2011 Server Backup, you MUST partition the HDD in 2TB partitions. THis has a performance cost that is real. Consider moving to WSE2016. I just did. I fumbled a lot but it it worth it IMO.

Duplication just means two copies stored on different physical HDDs. And all files are stored in plain NTFS format, that does not change with duplication. If you transferred the Pooled HDDs to a system not running DP you'd be able to read them. It might be a bit of a mess working out that you have duplicates though. I run x2 duplicates for continuity and Server Backup for Backup. So if you ever transfer to a non-DP running machine (perhaps a linux-based NAS?) then I would consider to first go back to x1 duplication. Hope this helps.

It is actually easy. Let's start with your starting position: 1. You had a Pool of local HDDs, say Pool A (or Local). On these HDDs you have a hidden PoolPart.* folder in which the data of Pool A is stored. 2. You created a CloudDrive (possibly added it to a new Pool, Pool B (or CloudPool), I'll assume that) 3. You created a new Pool C (or HYbridPool) and added Pool A and Pool B to it. Now on HDDs of Pool A, there will be another hidden PoolPart.* folder (say level 2) _within_ the earlier PoolPart.* ( level 1) folder. Anything stored in level 1 is in Pool A ONLY. When you look at Pool C, the data in level 1 will show up as Other. This is in fact very similar to storing data on a HDD of Pool A in the root folder or outside of the level 1 PoolPart.* folder: It will show up in Pool A as Other. So, for each HDD in Pool A, _move_ the contents of the level 1 folder to the level 2 folder (stopping DrivePool service first and restarting it when done). The that data is in Pool C, unduplicated and the re-measure pass will duplicate Pool C (by storing a duplicate in Pool B). There is no need for Fileplacement rules (that is assuming you have x2 for everything in the Pool). And you cannot have files only on Local _and_ have x2 duplication.

Uhm, it's back.... no clue what changed

Running WSE2016 and Scanner 2.5.4.3216. I've had quite a few mishaps and issues, will probably do a clean install soon but... Scanner runs but the Performance column is empty. Used to show a graph and number. Tried repair and uninstall/install. No fix. Any ideas?

Anyway I can see/prove/diagnose that settings are getting corrupted?

I am using 3220 BETA but I've had to press the reset button on my Server a few times (it became unresponsive and the power button did not shut it down, wonder how I can analyze/diagnose this...). After boot, Scanner lost all settings and scan history. Each time. Edit: In Event Viewer, I do see Scanner throwing an Event after each such reboot. Want me to submit an error report somehow/where? Edit2: I wonder whether it could have something to do with using Bitlocker? DP waits a while, right? Maybe Scanner tries to access the disks to early?

Alternatively, if the HDD had been scanned in the past, you could expand the HDD, choose the bottom small drop down box and select Mark All Readable Blocks Unchecked.