Nested-V Dedup corruption 26100.1742 and Insider 26296.5001 (and Server 2022) is still there.
Nested-V, host can be Server 2019, Server 2022, Windows 10, Windows 11. Can be Intel or AMD. SSD recommended, 32 GB minimum. 1st level guest is Server 2022, 2025 or the newest vNext, dedup on drive D : active where the nested VMs reside. And they experience data corruption, and in some rare cases even on the D : drive of the 1st level guest. Does not happen if 1st level guest is Server 2019, rock solid then. (I have to use D : with a space, because that over-eagerness of office products to force auto-guess and auto-correct things crept into this forum too, converting it to a smiley!) The video, in that case Server 2022 on Win11 as host:https://www.joumxyzptlk.de/tmp/microsoft/S2022-Nested_Deduplication_VDI-Hyperv_profile_kills_filesystem_v2.mp4 See here my previous posts: https://techcommunity.microsoft.com/t5/windows-server-insiders/server-vnext-26040-and-server-2022-deduplication-data-corruption/m-p/4047321 Here: https://techcommunity.microsoft.com/t5/windows-server-insiders/server-2025-hyper-v-deduplication-corruption-is-still-there/m-p/4136286 Here: https://techcommunity.microsoft.com/t5/windows-server-insiders/26063-deduplication-data-corruption-is-still-there/m-p/4067827 Still perfectly reproducible, in this case the host was just upgraded to Win11 24h2.What is new and different? I know you (i.e. Microsoft) not only does have a bug entry, it got reproduced, and in one case I even know the CPU type to be an E5-1650 where this bug got reproduced (though with ~50% chance there since that CPU is old and slow). I even know it got sorted into "existing features fixed" category this bug belongs since deduplication is not a new feature. Here the two screens from todays re-test: Happy fixing! I am lucky I never used deduplication on a CSV in a Hyper-V Cluster - I was just about to do in 2023, but then this happened. kind regards, Joachim Otahal
Windows Server Preview Build 25997 - How to Activate NVMe/TCP?
Hello all, NVMe/TCP preview support for Windows Server v.next was announced during MSFT Ignite a couple of weeks ago. Should it already be inside the current build? If so, I can't find anything in the registry to activate the feature. Has anyone activated it yet? If so, how is it done? Any help is much appreciated! -Felix
Storage Spaces Direct bug?
Does anyone know if Microsoft monitors this forum for bug reports? Or is there a better way to report them? I'm thinking there may be a bug in Windows Server 2025 Data Center when detecting supported drives for Storage Spaces Direct (S2D). I'm using Micron 7450 Pro drives, which have Power Loss Protection (PLP) and should be supported, but the cluster report is incorrectly reporting they don't have PLP and will not let them be used. I posted this same issue a few weeks back on this forum, but didn't get a response, so I'm thinking this is the wrong place to report the bug.Windows Server 2025 + S2D (Storage Spaces Direct) + Micron 7450
Hi, I've been trying about a thousand different combinations of Windows Server Datacenter 2025 preview with Micron 7450 Pro NVMe SSD drives, and I just can't get Windows to report these correctly. I'm starting to think it's a bug in Windows. So first off, these drives definitely have PLP (power loss protection). They're enterprise NVMe SSD drives. And as far as I can tell, they are compatible with S2D. But no matter what configuration I do from both hardware and software, the "Cluster Validation Report" for S2D says the"Disk does not have non-volatile cache." Here's two screenshots - one using Window's driver, and one using Micron's driver: I'm at a loss. Is this a Windows 2025 bug?26063 deduplication data corruption is still there.
From Server 2022 up to this newest 26063 build, they all have the same problem, as described here:https://techcommunity.microsoft.com/t5/windows-server-insiders/server-vnext-26040-and-server-2022-deduplication-data-corruption/m-p/4047321 I am out of energy for today and give up for today. It seems to be impossible to get Microsoft to care for actual OS bugs instead of marketing.Server 2025 Hyper-V deduplication corruption is still there
I can still reproduce this with 100% confidence on two VERY different machines and hosts with my "easy to reproduce" package: - AMD Ryzen 5950 with Windows 11 23H2 (self built) - Dual Xeon 6226R with Server 2019 (HP Proliant DL 380). As I posted quite often now: If you use deduplication for Hyper-V, i.e. where the virtual machines reside, you will get data corruptions, your virtual machines will crash, and you may even get a filesystem corruption on the drive hosting the machines. For more details see here:26063 deduplication data corruption is still there. - Microsoft Community Hub As for now: If you used deduplication in Hyper-V scenario, like you used it with Server 2012 up to server 2019, don't bother with Server 2022 and Server 2025 until that bug is fixed. My offer still stands for a live demonstration how I reproduce and talk about the differences how Microsoft tried to reproduce this and how I reproduce this. This is the result for "right about now" albeit without "funk soul brother"...b25951 - ReFS 3.10 volume became RAW, REFSUtil not compatible with v 3.10
Dear WS Insider Team, community I have upgraded lab instance my WS 2022 to WS vNext b25xxx. Everything went fine. I did a second IPU as the vNext version was about to expire. the server has physical disks Samsung 990 Pro - driveletter H, ReFS 3.10, 64k Samsung 990 Pro - mounted as directory on driveletter H, ReFS 3.10, 64k ( now changed to d: ) Samsung 860 Evo - driveletter C, NTFS, 4k, WS vNext. After IPU from WS a former vNext to b25951 the ReFS volume H became in a RAW state. The one that was linked is still healthy (but did not contain data) ReFSutil salvage does not work as it throws it is incompatible with this ReFS version 3.10 both volumes have. since this is a lab, other than loosing some not productive data but time, I would like to ask for two things 1. how can I salvage this drive? 2. is it expected that refsutil is not yet ready with the latest version of ReFS? Thank you for your time. Otherwise no backup, no mercy 😐b26063 - Bug Bash - Enabling the new ReFS Dedup will fail - not enough space on the disk
Tried to follow the instructions on non CSV ReFS drive but ReFSDedup with Dedup or DedupandCompression will fail on non CSV drives with ReFS. ReFS Version is 3.14, Clustersize 64k what I have tried: emptied the drive reformatted the drive, still 3.14. expected behaviour: since the new dedup is going to replace the old dedup I hoped that this would work with any types of ReFS drives, not eventually limited to CSV, as the bug bash task requests.
