The main hard drive (the one C:\ is on) is showing as raw
OS: Windows 10 Enterprise The main hard drive (the one C:\ is on) is showing as raw. I got a bluescreen (wish I had recorded what it said on it before I restarted, but it's probably a moot point now) and tried to restart, but the laptop froze before Windows loaded. I did some diagnostic stuff using a recovery drive and it became apparent that something had happened to C (it was showing as a Raw drive named D). I reassigned the drive letters back to the correct ones but I can't find any way of indicating that the drive is not raw. The partitions are all there according to DISKPART (Recovery 300mb, System 100mb, Reserved 128mb, Primary 237gb, Recovery 663mb), and the System partition is still formatted, as when I list the volumes, I get a FAT32 with 100MB, but everything else is raw. Much of the drive is Bitlocker encrypted. I know there are 3rd party tools that claim to be able to recover things, but I am wary that it will render the drive inoperable, even if it will get my data back. I have most of my data backed up, I just want a functioning OS that has all of my applications.Direct Mode didn’t work on ReFS formated Cluster Shared Volumes
Hi, why is direct access not possible with a ReFS format CSV volume? Instead of direct access, all reFS formatted CSVs that are provided by a SAN runs with "FileSystemRedirected". This behavior is critical because the "FileSystem Redirected" mode, compared to direct access, has up to 90% or more performance losses depending on the environment. Neither the fact that ReFS formatted CSV only run in "FileSystem Redirected" mode nor the associated performance penalties are mentioned in any official Microsoft statement. On the contrary, Microsoft actively recommends using ReFS for VHDX files. That is why, like many others, I have formatted the CSV with ReFS since the server in 2016, because I hoped that this would be an advantage for the customer systems. Unfortunately, this procedure led to the opposite and it was not easy to find the reason for it. Mainly because Microsoft has absolutely nothing documented about this behavior. I personally had to postpone more than 100 TB of data on various customer systems over the past few months in order to eliminate this problem and to bring the CSV formatted with ReFS back to NTFS. This action cost my company a considerable amount and also led to massive annoyance of the customer. However, if you know what to look for, you can now find a lot of posts on the Internet that confirm this behavior. Here are a few examples. https://github.com/MicrosoftDocs/windowsserverdocs/issues/2051 https://www.hyper-v-server.de/hypervisor/performance-probleme-hyper-v-cluster-mit-san-storage-und-csvs-mit-refs-formatiert/ https://techcommunity.microsoft.com/t5/failover-clustering/understanding-the-state-of-your-cluster-shared-volumes/ba-p/371889 https://www.windowspro.de/marcel-kueppers/refs-ntfs-vor-nachteile-dateisysteme-server-2016 https://www.wowrack.com/blog/microsofts-latest-system-refs-compared-to-ntfs/ https://4sysops.com/archives/windows-server-2019-cluster-shared-volumes-best-practices/ https://social.technet.microsoft.com/Forums/ie/en-US/6b2dcc4f-e735-4700-81f3-df45d94e7e01/refs-for-a-hyperv-csv-volume?forum=winserverhyperv https://forums.veeam.com/veeam-backup-replication-f2/latest-veeam-community-forums-digest-oct-2-oct-8-t46019.html Therefore, I now spare myself any further details and come directly to my demand. If ReFS does not fundamentally support direct mode, then I also expect Microsoft to publicly clarify it accordingly and also clearly indicate which disadvantages could arise if the CSVs are formatted with ReFS. If it should work and there is only a bug in between, please finally fix it. This problem has existed since Server 2016, so enough time should have passed to fix the problem. Best Regards from Germany Alex
Azure File Share - NTFS Permission Extremely Slow
Recently moved file server data to Azure File Share. No issue with mapping, opening files. The issue is when managing the permission. When updating/adding NTFS permission per folder, it is EXTREMELY slow. Any advise or workaround that you could share please. Thank you.
