DaveJ

I have a similar setup on my backup NAS. All non-Drivepool drives are mounted to folders at c:\mount and I can access the drives directly from there if needed.

Weird. I physically removed the two 8TB drives (the ones replaced by the 16TB drive) and now my drive sizes show as normal. I have two more 8TB drives to replace this weekend, so we'll see if the same issue recurs.

I am seeing this issue as well. I replaced two 8TB drives with one 16TB using the normal drive removal procedure. Prior to the drive removal all of my drives reported the correct sizes. As with the OP, Windows and Scanner report the correct drive sizes. [edit] If I hover over a specific drive I'm also seeing an asterisk next to the space used (see screenshot). I don't recall seeing that before either.

A few months ago I rebuilt my backup setup. Previously I had a pool connected locally to my server, but as part of the backup setup rebuild I physically moved that set of drives to a different machine. I kept the pool intact and migrated it to the new machine without issue. Now apparently I am getting Missing Disk notifications for the former local pool, which no longer exists. How do I reset the notifications so I no longer receive messages for the non-existant pool? The wiki article on resetting notifications appears to reference a command that is no longer available in DP 2.x.

I've been upgrading my storage this week and had installed the latest available beta from the website (2.2.0.881) so I could swap disks without the pool going into read-only mode. Since installing the beta I've noticed an occasional error in my system log - Event ID 153, logged to "disk", with the following: "The IO operation at logical block address 0x2 for Disk 10 (PDO name: \Device\00000045) was retried." In this case Disk 10 is the drive hosting the pool. I hadn't seen this come up with the previous DrivePool install. Is this anything to be concerned about? It seems to happen after a reboot but not always.

I've had Drivepool running for a long time and haven't had any issues up until last weekend. On my primary server I have a single 4-disk pool with folder duplication enabled for all folders. I had been backing it up to two locations - a single locally-connected external drive, and a separate backup NAS with a second Drivepool with folder duplication enabled for one path. Last week I expanded my external drive backup to two drives in a USB enclosure. Both drives were pooled to provide a single backup target, and folder duplication was not enabled. Despite that, I noticed that when I copied data from the primary pool to the new backup pool, duplication had been enabled on one folder. I disabled duplication on that folder and verified it was turned off on the rest as well. Last night my server warned me that several of my drives were running low on space - upon checking I found duplication had been enabled on the folders I had previously verified it was turned off. So now to my question - if I have a primary pool with folder duplication enabled, and I copy data from that pool to a secondary local pool that does not have folder duplication enabled, are the duplication settings for the source folders copied to the secondary pool as well? I should note that I've never seen this issue when copying data to my backup NAS.