Christopher (Drashna)

Yup, this is completely normal and expected in this case. The BIOS information is part of what we use to identify the system. When you change that, it will cause the licensing system to require you to "Transfer" the license to the new hardware. This just updates the information on our end, to make sure it's current. http://beta.stablebit.com/Support/Scanner/Licensing As for the forum software, yeah, there is something up with it, since we upgraded to the most current version. Also, giving the time frame, we were experiencing an issue and had rebooted the host that the site was on. This may have been the cause of issue you saw. If it happens again, let us know.

You should be able to delete the alert. If not, let us know. You can reset the status of the damaged sectors, which will rescan them: http://beta.stablebit.com/Support/Scanner/2.X/Manual?Section=Disk%20Scanning%20Panel Generally, not really. You may be able to "game the system" by doing the advanced replacement. But I wouldn't recommend it. Yes. If the drive is from an external enclosure (such as the Seagate Backup Plus, or Seagate Expansion externals), then removing the drive physically from the enclosure actually voids the warranty.

For licensing issues like this, we always recommend using the contact form: https://stablebit.com/Contact Though, it does appear that you've already done that. And yeah, if the pool is not properly licensed, it will do this until it is properly activated.

Well, if you're willing to spend the money on it, a better CPU will definitely serve you better! As for the memory, that's really odd. Newegg is pretty good about stock. And yeah, SSD prices have plummeted recently. It's really nice though. Can pick up a couple of 128GB SSDs for ~$100 now!

Ah, okay. If that's the case, then just make sure the DNS stuff is setup correctly. For the most part, all you'll want to do is change the DNS stuff on the router itself, so that it changes what it handed out to client devices. If you want, we can see about setting up a remote support session, and I can help with this, and make sure everything configured properly.

Okay. And when you check, the drive looks completely fine, correct? And the "Smart NoWmi" option doesn't help either, correct? If so, could you do this: http://wiki.covecube.com/StableBit_Scanner_Advanced_Settings In the logging Tab, find the "SmartDiskInfo" entry and click on it. Select the "Verbose" option and hit "OK". Let scanner run until it does this again (if you reboot the system, you'll need to redo this). Once it does, grab the contents of "C:\ProgramData\StableBit Scanner", open a ticket at https://stablebit.com/Contactand upload the contents there.

Okay, I've bumped the original ticket and have let Alex know about this issue.

If the issue does persist, let us know. And what does the email say exactly?

Okay, thanks for confirming that. I've let Alex know and hopefully, we can get this fixed for you soon. As for the Disk Management console, that's normal. This doesn't represent the size of the pool at all, in fact. It's just a place holder number. Literally, everywhere else, the size should be reported properly.

Well, Windows 7 Professional and up supports up to 192GB of memory (I didn't realize that it was THAT much!), so that's more than plenty. Well, at least 75% of what the board can hold. https://msdn.microsoft.com/en-us/library/aa366778(VS.85).aspx#physical_memory_limits_windows_7 I'd recommend checking the QVL for the board, just in case. However, usually most anything that's "compatible" (right speeds and voltage) should work

You are very welcome. And thank you for the kind words! If you need anything else or have any more questions, don't hesitate to ask!

Okay. When this happens, could you run "devmgmt.msc" and see if the "Covecube Virtual Disk" device is present in the "Disk drives" group? If it is, try disabling it and and re-enabling it, to see if that helps.

Very close, in fact. As for the duplication grouping, that is one of the top priorities after StableBit CloudDrive is released.

Ah, that will do it. These prevent the scans from taking place automatically. Disabling these options should allow the disks to be scanned properly now. As for manual scans, under the "sector map" section, you can start a scan manually for each disk. http://beta.stablebit.com/Support/Scanner/2.X/Manual?Section=Disk%20Scanning%20Panel Notice on the left side of the sector map, there is a start and stop arrow? This is how you'd start the scan manually for the disk. As for scheduling the scans individually, we don't have a method to do that, and it's by design. Specifically, we have throttling options that will avoid scanning or throttle the scan of the drives in a number of circumstances : if they're being used (an active load on the disk), if there is a large load on another disk on the same controller, if the disks are too warm overall, if any one disk is significantly warmer than the rest. These are there to help prevent any issues that could be caused by scanning the drives. Additionally, we scan using a background I/O to help minimize the impact of the scans, as well. These options can be configured in the Scanner Settings page, under the "Throttling" tab, and under the "Heat" tab, as well.

Tod, I've flagged the files that you've posted recently so Alex can take a look at them. When this happens, try restarting the "StableBit DrivePool Service" and see if that fixes it, at least temporarily. If it does, let us know.

Probably is the best bet, unfortunately. And a better CPU and more RAM is always nice. And that's a lot of memory. Just make sure your OS can support all of it.

That would definitely mean that no new files are allowed to be placed on that drive. Actually, there is a "duplicate files later" option when you remove the disk. This will only move unduplicated data off of the pool, and then rescan the pool after the drive is removed and reduplicate as needed (if possible). After it's removed, you could replace it with a new drive and it should rebuild the duplicate files on the new disk. However, this may only work if you only have duplicated files on the "bad" drive.

You should be able to do an inplace upgrade, without any issues. If you're concerned about that at all, then please uninstall the old version and install the new version. Though, there have been a few changes (such as with the theme/UI), but nothing too major.

If the only drive that you have free space is on that damaged drive, then most likely. Check the DrivePool UI. Chances are that you will see a Red/orange arrow above the drive in question, at the left side. If this is the case, this arrow is the "real time placement limiter" indicator. meaning that new files can only be put on the drive up to that point. And in this case, that would be no drives. So if there is no more free space on any of the other drives, it could block you from adding new files.

From the looks of the uploaded dump, it looks corrupted. Which would indicate the the file didn't finish uploading, or a serious hardware issue. Given everything, it's most likely hardware related, unfortunately.

Due to how StableBit Scanner current works, there are some known limitations. Stable Release: 2.5.1.3062 Public Beta Release: 2.5.2.3146 SMART data from RAID Arrays. Because most controllers hide the contents of the RAID array, we're not able to access information about them from inside the OS. There are ways to access the data about the drives, but this usually requires implementing 3rd party code, or by accessing data through the controller's management software (such as HighPoint's Web Management software). We are looking into implementing this feature in the future, but there is no ETA. SMART Data from Storage Spaces array. Because of the low level implementation of Storage Spaces, the disks in the array are hidden from access normally. This makes getting information about the disk (including SMART data) significantly more difficult. We are looking into implementing this feature in the future, but there is no ETA. Repairing Damaged Sectors. Right now, we only identify and flag damage (unreadable) sectors on disks. Repair is up to the disk or the user to manually repair these issues. Temperature or Max Temperature shows a 0C, Disk capacity is mis-reported, or Drive Reports significantly number of unreadable sectors (Especially newer USB drives) This is a known issue with the way that the drive is reporting disk information, up to and including sector sizes. This has been resolved in the latest internal beta build (2.5.2.3121). Dynamic Disks are not reported properly. Due to the added complexity of how dynamic disk operate, they were not being shown properly in the disk lists. This has been resolved in the latest public beta build (2.5.2.3100) Disk List issues with a lot of disks. Fixed in internal beta build (2.5.2.3107 and up) Pushover notifications fail. This is due to an API change. Fixed in latest internal betas (2.5.2.3122) File system repair fails This is a known issue, and has been fixed in the Public beta (2.5.2.3103) File system comes back as unhealthy, consistently. ?If you are running Windows 8 or up, this may be an issue with the command you use. Please run "chkdsk x: /f" to verify. Adding the "/scan" command actually misses a number of issues as it skips a number of checks. The main one is MFT corruption. Stablebit Scanner is not misreporting info, but CHKDSK isn't checking everything. If there is no corruption (verified by CHKDSK) and you're seeing this come back constantly (and it disappears on a recheck), there is a known issue where the data comes back incorrectly. It's on the "to do list" to fix. Disk list is empty over Remote Desktop Connection. This is an issue with the 3rd party controls that we use for StableBit Scanner. This is been fixed in the Public Beta version (2.5.2.3103). Non-NTFS file system (ReFS) Support. This is a newer file system, and not currently supported. While surface scans will occur, we have no way to identify files or recover them. This means that we need to reverse engineer the file system and build a custom ReFS parser (much like we did for NTFS). The same would need to be done for exFAT and other file systems. However, we will probably only target NTFS and ReFS, as these are the primary file systems in use. No WSSX (Windows Server Essentials) installer exists. Starting with 2.5.2.3132, we have stopped producing the WSSX (WHS/WSE) installer. Now, the EXE installer will install both the stand alone UI and the dashboard tab, so the EXE should be used for all installations. This allows for more unified changes, and installation. And it allows for both the dashboard and stand alone UI to be used. This list is by no means comprehensive, and it's contents may change as these issues are investigated. Internal Beta builds can be found here: The latest, safe build is 2.5.2.3146 General Windows: http://dl.covecube.com/ScannerWindows/beta/download/?C=N;O=D Don't download the latest build unless it's been checked out or you've been instructed to. If it's not a build numbered in the change log, then it's an interim development build and may not be stable.

Due to how StableBit DrivePool and certain software works, there are some known limitations. Stable Release: 2.2.3.1019 Public Beta Release: N/A VSS Support. This includes anything that strictly requires VSS support to work. This includes (but is not limited to): Windows Backup You can back up the pooled drives, but not the pool directly. Windows Server Backup You can back up the pooled drives, but not the pool directly. Previous Versions System Restore Dynamic Disks. Because of the added complexity of Dynamic disk, we don't support them being added to a pool. Specifically, we take into account the physical disk when determining where duplicates reside, and that adds a lot more complexity and overhead when you start dealing with Dynamic Disks due to the complex arrays that you can create with them. Plex Media Server's database. This database relies on hard linking files together, instead of using the database to point to the same file for redundant files. Because we don't support hard links on the Pool, you may notice missing images in Plex if the database is being stored on the pool. OneDrive for Windows 8.X. Windows 8 uses a new type of file system link to link the files to the cloud (and locally), in a seamless way. Unfortunately, we don't support this file system link only the pool current. USN Journaling . This may affect how certain apps detect changes on the pool. NOTE: Issues with "Change notifications" has been resolved in the beta builds (2.2.0.651 and up). This affects apps like DropBox. Antivirus Scanners. This is a broad generalization. But due to how they work, they can adversely affect the pool and it's performance, and can even cause some pretty bad behavior (eg, locking the system up). If you suspect that this is the case, version 2.2 and up has the option to disable the "bypass file system filters" feature (located in "Performance", under Pool Options), which may fix this. Otherwise, we recommend completely uninstalling any antivirus program that you suspect is causing issues (disabling isn't enough as the real time scanner is actually still active). Data Deduplication. This mainly applies to the Windows Server role, rather than 3rd party software. This feature works by identifying identical blocks of data. It converts the files into a special kind of reparse point, and carves out the duplicate data. This duplicate data is placed into the "System Volume Information" folder (and may be handled as part of VSS). When you access the data, a file system filter splices the data back together. While not officially supported, it should work on the underlying disks. The public beta build (2.2.0.651 and up) add some handling for Deduplication, so that the data is detected "intact". Deduplication is NOT supported on the pool, and because it appears to use the same data structure as VSS, it may never be supported. TrueCrypt/VeraCrypt. This software bypasses the normal disk API, meaning that it does not show up for StableBit DrivePool, and cannot be used. ReFS. At this time, full support does not exist. By "Full support", we mean registering the Pool drive as ReFS instead of NTFS, integrity stream support, and potentially additional handling for ReFS (such as checking integrity streams, and reduplicating files for "bad" files). It should be noted that ReFS only enables integrity streams for drive metadata. If you want to enable it for all files, you need to run "Set-FileIntegrity X:\ -enable $true" from a powershell prompt Long File Paths. StableBit DrivePool doesn't have a problem with log paths, and actually supports long paths (up to 64k character paths, I believe). Explorer, however uses win32 API and does not support long paths. There is, however an issue where file names (not paths) longer than 200 characters cause issues. This is resolved in 2.2.0.684. Pool is Removable. This is default behavior, but causes issues with some software, and may be a problem for some people. The Public Beta build (2.2.0.651) disables this behavior by default, and introduces an advanced setting that can be used to toggle the setting. Files not showing up in directory list. If you are experiencing this issue, then the issue may be network related. By default, Windows caches network information, such as directory searches. This can cache the incomplete list. In this case, the fix is a simple registry tweak: http://wiki.covecube.com/StableBit_DrivePool_Q7420208 This will increase network usage slightly, but should not adversely affect the network. Cannot add VHD(X) based disks to the pool. Errors out when trying to add a drive that is a mounted VHD(X) file to the pool. Error or long delay when renaming folders on the network. This applies to Windows 10 Anniversary update (version 1607) as the client, and Windows Server 2012R2, Windows 8.1 and up as the share server. There is an issue when the share has been indexed locally on the server by Windows Search. This is NOT a StableBit DrivePool bug, but a bug with Microsoft code. For now, the solution is to disable the Windows Search service. However, if you're using Windows Server Essentials, this will adversely affect the built int streaming options, as well as the file list for the Remote Access Website. Microsoft KB Article: https://support.microsoft.com/en-us/kb/3198614 You can "fix" this issue here: Q542215 Cumulative update that addresses this issue is available here: Link Microsoft Store Apps have issues with the pool. This is most likely due to some feature not supported by the Pool. In particular, VSS, USN Journaling, or some other file system command/check. Windows Subsystem for Linux. The file system commands cause issues when navigating the pool. This applies to both v1 and v2 of WSL. This list is by no means comprehensive, and it's contents may change as these issues are investigated. Internal Beta builds can be found here: http://dl.covecube.com/DrivePoolWindows/beta/download/ The latest, safe build is 2.2.3.1019 Full change log can be found here: changes.txt Don't download the latest build unless instructed to, especially if it's not a listed numbered build in the change log, as these are interim development builds and may not be stable.

Ah, okay. In that case, could you update the version to the latest? Either the latest stable version: http://dl.covecube.com/ScannerWhs2/release/download/StableBit.Scanner_2.5.1.3062_Release.wssx Or ideally, the newest version (there is some newer handling for issues akin to this) http://dl.covecube.com/ScannerWhs2/beta/download/StableBit.Scanner_2.5.2.3097_BETA.wssx

Well, if this is for Forefront Client Security, it looks like it's not officially supported for anything past Vista/Server 2008. And if that is the case... then any OS past that pushes the limit of compatibility. Specifically, since there are significant kernel changes in Windows 8, the produce may not be compatible with recent versions of Windows. Additionally, with HyperV, do you have the VPN stuff installed as well (Routing and Remote Access)? If so, make sure you're using a dedicated NIC.

If you don't have six disks, then it may be that the disk 6 issues are related to the pool problems directly. In fact, if the volume is having issues, then it could cause issues. And if this is the case, could you do a clean reinstall of StableBit DrivePool? http://wiki.covecube.com/StableBit_DrivePool_Q3017479 This will remove the driver and and all the files. As for the frequent reboots, these are not graceful shutdowns. These are hitting the reset button or the like. And these can cause further issues. In fact, I'd recommend running "chkdsk c: /r" and "sfc /scannow".