Windows 10: Data partition inaccessible after Windows 10 Pro 20H2 upgrade

The laptop is a Dell E5570 with a Crucial MX300 CT525MX300SSD1, last Wednesday I upgraded Windows 10 Pro to the latest major version 20H2. The upgrade rebooted twice and when it finished - partition D, which was a 312GB NTFS, became RAW.

Examining the partition data shows it's totally random indicating encryption, the first and last sectors are identical probably indicating the NTFS boot sector is still there and data is intact. The OS partition C is ok, meaning D is Opal range-encrypted.


The upgrade created a new recovery partition by shrinking the OS partition C, probably due to insufficient free space according to the upgrade log but this happened only after the following Windows System logs.


Windows Logs -> System eventvwr shows the following right after the first reboot:


The operating system started at system time ‎2020‎-‎12‎-‎23T11:14:03.

11:14:05EnhancedStorage-EhStorTcgDrvThe following informational event has occurred 0x0, 0x5, 0x0, 0x0. D0Entry

11:14:05EnhancedStorage-EhStorTcgDrvA TCG Command has returned an error. Desc: AuthenticateSession Param1: 0x1 Param2: 0x60000001C Param3: 0x900000006 Param4: 0x0 Status: 0x12

11:14:05EnhancedStorage-EhStorTcgDrvA TCG Silo has returned the capabilities value of 0x7.

11:14:06EnhancedStorage-EhStorTcgDrvThe following informational event has occurred 0x0, 0x0, 0x0, 0x0. DeviceStart

11:14:08NtfsVolume D: \Device\HarddiskVolume5 is healthy. No action is needed.

11:14:49NtfsThe file system structure on volume D: has now been repaired.

11:14:49NtfsVolume D: \Device\HarddiskVolume5 requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.

11:14:53NtfsA corruption was discovered in the file system structure on volume D:. The Master File Table MFT contains a corrupted file record. The file reference number is 0x1000000000024. The name of the file is "<unable to determine file name>".


A few seconds earlier it seems KB4592438 was installed according to setupact.log, which has a documented issuehere, here and MS confirmed, regarding chkdsk which might have been executed automatically on boot. Yet this looks like a different issue surrounding SED.

TPM is enabled in the BIOS, I don't believe BitLocker was ever explicitly enabled on any of the partitions. It's possible to roll back the upgrade for 10 days, so I had to extend that setting to 30 days so not to lose the Windows.old folder. I tried rolling back on a clone disk, just to make sure it's successful, and it was. For now I can't go back since it's irreversible and I'm not sure if it'll help, the big question is whether Windows changed something in the SED/Opal subsystem, or simply giving the wrong credentials.

Here is sedutil output:


# sedutil-cli --scan

Scanning for Opal compliant disks

/dev/sda 2 Crucial_CT252MX200SSD1

/dev/sdb No

No more disk present ending scan

# sedutil-cli --query /dev/sda



/dev/sda ATA Crucial_CT252MX200SSD1

TPer function 0x0001

ACKNAK = N, ASYNC = N. BufferManagement = N, comIDManagement = N, Streaming = Y, SYNC = Y

Locking function 0x0002

Locked = N, LockingEnabled = Y, LockingSupported = Y, MBRDone = N, MBREnabled = N, MediaEncrypt = Y

Geometry function 0x0003

Align = N, Alignment Granularity = 1 512, Logical Block size = 512, Lowest Aligned LBA = 0

SingleUser function 0x0201

ALL = Y, ANY = N, Policy = N, Locking Objects = 16

DataStore function 0x0202

Max Tables = 16, Max Size Tables = 12582912, Table size alignment = 1

OPAL 2.0 function 0x0203

Base comID = 0x1000, Initial PIN = 0x0, Reverted PIN = 0x0, comIDs = 1

Locking Admins = 4, Locking Users = 16, Range Crossing = N



TPer Properties:

MaxComPacketSize = 131072 MaxResponseComPacketSize = 131072

MaxPacketSize = 129792 MaxIndTokenSize = 126976 MaxPackets = 1

MaxSubpackets = 1 MaxMethods = 1 MaxSessions = 1

MaxAuthentications = 21 MaxTransactionLimit = 1 DefSessionTimeout = 240000



Host Properties:

MaxComPacketSize = 2048 MaxResponseComPacketSize = 2048

MaxPacketSize = 2028 MaxIndTokenSize = 1992 MaxPackets = 1

MaxSubpackets = 1 MaxMethods = 1



# linuxpba



DTA LINUX Pre Boot Authorization



Please enter pass-phrase to unlock OPAL drives: *****

Scanning....

Drive /dev/sda Crucial_CT525MX300SSD1 is OPAL NOT LOCKED



I've read posts online regarding Windows "taking ownership" on SED/Opal for some reason, can this be the case here? This clearly seems like a severe upgrade bug. What does "Locked = N" actually mean? Is there a way to get the partition data back?


Thank you!

:)

 

Help! Data partition not showing under my computer

This is happening on a windows 2000 server. Our second partition of the system, for data is not showing under my computer. Here are the properties of it in disk management:





Now under logical drives its listed as F and shows free space available.

Suggestions on how to fix this?

 

W7 Hard drive partition issue

to get rid of that 100 meg windows partition that setup creates for you on a new install on a blank hdd:

- press shift+f10 when on the partition management screen in setup <-- this opens a command prompt
- diskpart <-- start the windows command line partition management tool
- list disk <--- list the installed hdds in this computer for the next step
- select disk 0 <- might have to replace 0 with the number of the correct disk
- clean <-- this will erase all data on the disk you selected one step up- dont use the wrong disk!
- create partition primary <- creates a primary partition taking up all space on the drive, adjust the command if necessary
- exit, exit to exit diskpart and the command prompt
- click refresh in partition manager and select your newly created partition and install to that

 

Windows 10 upgrade problem, no input accepted

I really hate having to come here and ask for help, but I really am stumped. It hurts my geek pride. I have a PC with fairly modern hardware in it. It has a p8p67 pro in it. I have tried upgrading windows 10 on it twice now. Both times I have had the same result.

After windows finishes upgrading it goes to the log in/set up screen. I can't do anything. No keyboard or mouse input is accepted.

I will list some, or hopefully all, of the troubleshooting steps I have tried:

• Move keyboard and mouse to different USB ports.
• Try different keyboard or mouse.
• Restart computer, repeatedly.
• Google for related issues.
• Update Bios, because why not.
• Create boot media and revert to windows 7.

The windows 10 system restore boot media works fine with keyboard and mouse. All USB ports work in windows 7. I don't know what is wrong. I suspect that windows 10 is lacking a driver of some sort, but since the computer accepts no input I have no way of checking for which driver let alone installing it.

Please help me figure this out. If I have to revert back to windows 7 again, I am not going to get it upgraded to windows 10. Thank you in advanced.