Please perform in this order:
a) HD Tune
b) Sea Tools
c) TestDisk
d) Chkdsk
The recovery partition was labeled with W: earlier in the thread.
Other partitions can be labeled after completing the other tests.
oh crap, you were looking at that incorrectly.
I had the windows recovery drive I was attempting to make (that started this whole thing) inserted at the time with the label RECOVERY and drive letter W lol.....
might have been looking at that? The recovery partition never had one until now.
- - - Updated - - -
yea i dont know whats going on with windows. (maybe it was the assigning and removing of the drive letter to the recovery partition...) but now it shows . Or maybe it was the doing a chkdsk against it when it had the letter. weiiird
in disk management. at least its seeing it not 100% free.
- - - Updated - - -
and just like that
- - - Updated - - -
im now going to test it, with EXTREME trepidation. this all has just about given me heart palpitations.... will BBS
1) Please upload V2 and DM:
BSOD - Posting Instructions
2) Make a new restore point:
Create System Restore Point in Windows 10
3) Open administrative command prompt and type or copy and paste (all at one time)
When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the threadCode:bcdedit /enum all reagentc /info diskpart lis dis sel dis 0 det dis lis vol lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel par 5 det par
yep, restore point/macrium image is first order of business assuming this actually works (creating recovery drive illustrating partition is back in practice)
will report back with the rest after that!
whelp, with the slew of things im trying to address right now - i figured id circle back to this one.
recovery partition is all fine n dandy if i assign a drive letter to it. the minute i remove the drive letter POOF. reagentc /info shows disabled again.
defeated.
- - - Updated - - -
in place upgrade time.. its my understanding that doesnt disturb your current environment, akin to what happens when you do a version upgrade via windows update. sounds like the way to go.
When available please update the progress with the steps in post #33.
will do. just got home from the gym. the windows in place upgrade has it back as enabled and i can create a recovery drive meaning its working.
problem was, that was the case before as well. Disk management still sees it as empty so whatever it is, its still not completely fixed.
beginning to think the partition itself is bad. However as a test I deleted the recovery partition and did the in place upgrade, as i expected windows to create a new one. It did not.
sigh.
Here are the results, with little idea what im looking it, it looks like it isnt identifying the file system of the recovery partition properly? All other tools see it as ntfs, windows isnt however. How can i assign it a file system?
actually it shows as offline too? perhaps thats why it doesnt see the file system. how can i bring it online is probably the right question to be asking
Dropbox - new 1.txt - Simplify your lifeCode:C:\Users\klepp\Desktop>bcdedit /enum all Firmware Boot Manager --------------------- identifier {fwbootmgr} displayorder {bootmgr} {58e9184c-5725-11ea-bdcd-806e6f6e6963} timeout 1 Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume13 path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI description Windows Boot Manager locale en-US inherit {globalsettings} flightsigning Yes default {current} resumeobject {8ede3a8a-6c5c-11ea-b1b7-b09a3595dfd8} displayorder {current} {3966804d-5726-11ea-bdcd-646e6960ca16} toolsdisplayorder {memdiag} timeout 0 Firmware Application (101fffff) ------------------------------- identifier {58e9184c-5725-11ea-bdcd-806e6f6e6963} device partition=U: description UEFI: SanDisk, Partition 1 Windows Boot Loader ------------------- identifier {0cb3b571-2f2e-4343-a879-d86a476d7215} path \EFI\Microsoft\Boot\SecConfig.efi description DebugTool loadoptions DISABLE-LSA-ISO,DISABLE-VBS nx OptIn Windows Boot Loader ------------------- identifier {2c3ff6bc-5aec-11e9-b9e2-baab820f4185} device ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{2c3ff6bd-5aec-11e9-b9e2-baab820f4185} path \windows\system32\winload.efi description Windows Recovery Environment locale en-US inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{2c3ff6bd-5aec-11e9-b9e2-baab820f4185} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Windows Boot Loader ------------------- identifier {3966804d-5726-11ea-bdcd-646e6960ca16} device ramdisk=[C:]\boot\macrium\WA10KFiles\media\sources\boot.wim,{ramdiskoptions} path \windows\system32\boot\winload.efi description Macrium Reflect System Recovery osdevice ramdisk=[C:]\boot\macrium\WA10KFiles\media\sources\boot.wim,{ramdiskoptions} systemroot \Windows nx OptIn detecthal Yes winpe Yes Windows Boot Loader ------------------- identifier {608d0a96-642c-11ea-a6cf-adf1414b54a8} device ramdisk=[\Device\HarddiskVolume16]\Recovery\WindowsRE\Winre.wim,{608d0a97-642c-11ea-a6cf-adf1414b54a8} path \windows\system32\winload.efi description Windows Recovery Environment locale en-US inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[\Device\HarddiskVolume16]\Recovery\WindowsRE\Winre.wim,{608d0a97-642c-11ea-a6cf-adf1414b54a8} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Windows Setup ------------- identifier {7254a080-1510-4e85-ac0f-e7fb3d444736} device ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{465c1954-6c39-11ea-be4d-2cfda1e1fe1c} bootstatdevice partition=C: custom:11000083 partition=C: path \windows\system32\winload.efi description Windows Rollback locale en-US bootstatfilepath \$WINDOWS.~BT\Sources\SafeOS\bootstat.dat inherit {bootloadersettings} restartonfailure Yes osdevice ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{465c1954-6c39-11ea-be4d-2cfda1e1fe1c} custom:21000152 partition=C: systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Windows Boot Loader ------------------- identifier {current} device partition=C: path \WINDOWS\system32\winload.efi description Windows 10 locale en-US inherit {bootloadersettings} recoverysequence {8ede3a8e-6c5c-11ea-b1b7-b09a3595dfd8} displaymessageoverride Recovery recoveryenabled Yes isolatedcontext Yes flightsigning Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \WINDOWS resumeobject {8ede3a8a-6c5c-11ea-b1b7-b09a3595dfd8} nx OptIn bootmenupolicy Standard Windows Boot Loader ------------------- identifier {8ede3a8e-6c5c-11ea-b1b7-b09a3595dfd8} device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{8ede3a8f-6c5c-11ea-b1b7-b09a3595dfd8} path \windows\system32\winload.efi description Windows Recovery Environment locale en-US inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{8ede3a8f-6c5c-11ea-b1b7-b09a3595dfd8} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Resume from Hibernate --------------------- identifier {608d0a94-642c-11ea-a6cf-adf1414b54a8} device partition=C: path \WINDOWS\system32\winresume.efi description Windows Resume Application locale en-US inherit {resumeloadersettings} recoverysequence {608d0a96-642c-11ea-a6cf-adf1414b54a8} recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 filedevice partition=C: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Resume from Hibernate --------------------- identifier {8ede3a8a-6c5c-11ea-b1b7-b09a3595dfd8} device partition=C: path \WINDOWS\system32\winresume.efi description Windows Resume Application locale en-US inherit {resumeloadersettings} recoverysequence {8ede3a8e-6c5c-11ea-b1b7-b09a3595dfd8} recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 filedevice partition=C: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Windows Memory Tester --------------------- identifier {memdiag} device partition=\Device\HarddiskVolume13 path \EFI\Microsoft\Boot\memtest.efi description Windows Memory Diagnostic locale en-US inherit {globalsettings} badmemoryaccess Yes EMS Settings ------------ identifier {emssettings} bootems No Debugger Settings ----------------- identifier {dbgsettings} debugtype Local RAM Defects ----------- identifier {badmemory} Global Settings --------------- identifier {globalsettings} inherit {dbgsettings} {emssettings} {badmemory} Boot Loader Settings -------------------- identifier {bootloadersettings} inherit {globalsettings} {hypervisorsettings} Hypervisor Settings ------------------- identifier {hypervisorsettings} hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Resume Loader Settings ---------------------- identifier {resumeloadersettings} inherit {globalsettings} Device options -------------- identifier {2c3ff6bd-5aec-11e9-b9e2-baab820f4185} description Windows Recovery ramdisksdidevice unknown ramdisksdipath \Recovery\WindowsRE\boot.sdi Device options -------------- identifier {465c1954-6c39-11ea-be4d-2cfda1e1fe1c} description Windows Setup ramdisksdidevice partition=C: ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi Device options -------------- identifier {608d0a97-642c-11ea-a6cf-adf1414b54a8} description Windows Recovery ramdisksdidevice partition=\Device\HarddiskVolume16 ramdisksdipath \Recovery\WindowsRE\boot.sdi Device options -------------- identifier {8ede3a8f-6c5c-11ea-b1b7-b09a3595dfd8} description Windows Recovery ramdisksdidevice partition=C: ramdisksdipath \Recovery\WindowsRE\boot.sdi Setup Ramdisk Options --------------------- identifier {ramdiskoptions} description Macrium Reflect System Recovery ramdisksdidevice partition=C: ramdisksdipath \boot\Macrium\boot.sdi C:\Users\klepp\Desktop>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: 8ede3a8e-6c5c-11ea-b1b7-b09a3595dfd8 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. C:\Users\klepp\Desktop>diskpart Microsoft DiskPart version 10.0.19041.1 Copyright (C) Microsoft Corporation. On computer: DESKTOP-KEVIN DISKPART> lis dis Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 931 GB 1024 KB * Disk 1 Online 9 TB 0 B * Disk 2 Online 9 TB 0 B * Disk 3 Online 9 TB 0 B * Disk 4 Online 9 TB 0 B * Disk 5 Online 9 TB 0 B * Disk 6 Online 9 TB 0 B * Disk 7 Online 9 TB 0 B * Disk 8 Online 114 GB 0 B * Disk 9 Online 9 TB 0 B * Disk 10 Online 9 TB 0 B * Disk 11 Online 9 TB 0 B * Disk 12 Online 9 TB 0 B * DISKPART> sel dis 0 Disk 0 is now the selected disk. DISKPART> det dis Samsung SSD 970 EVO Plus 1TB Disk ID: {C13D80F3-7AE3-48E0-97DD-FAFA2DBC1916} Type : NVMe Status : Online Path : 0 Target : 0 LUN ID : 0 Location Path : PCIROOT(0)#PCI(1D00)#PCI(0000)#NVME(P00T00L00) Current Read-only State : No Read-only : No Boot Disk : Yes Pagefile Disk : Yes Hibernation File Disk : No Crashdump Disk : Yes Clustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C Windows NTFS Partition 930 GB Healthy Boot Volume 1 Partition 516 MB Healthy Offline Volume 2 FAT32 Partition 100 MB Healthy System DISKPART> lis vol Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C Windows NTFS Partition 930 GB Healthy Boot Volume 1 Partition 516 MB Healthy Offline Volume 2 FAT32 Partition 100 MB Healthy System Volume 3 E Emulation NTFS Partition 9 TB Healthy Volume 4 Q Plex Media NTFS Partition 9 TB Healthy Volume 5 R Plex Media NTFS Partition 9 TB Healthy Volume 6 S Single-play NTFS Partition 9 TB Healthy Volume 7 F Emulation NTFS Partition 9 TB Healthy Volume 8 G Emulation NTFS Partition 9 TB Healthy Volume 9 H Emulation NTFS Partition 9 TB Healthy Volume 10 I Emulation NTFS Partition 9 TB Healthy Volume 11 O Other Data NTFS Partition 9 TB Healthy Volume 12 D Dock NTFS Partition 9 TB Healthy Volume 13 U USB Drive NTFS Removable 114 GB Healthy Volume 14 P Plex Media NTFS Partition 9 TB Healthy DISKPART> lis par Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 System 100 MB 1024 KB Partition 2 Reserved 16 MB 101 MB Partition 3 Primary 930 GB 117 MB Partition 4 Recovery 516 MB 931 GB DISKPART> sel par 1 Partition 1 is now the selected partition. DISKPART> det par Partition 1 Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b Hidden : Yes Required: No Attrib : 0X8000000000000000 Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 2 FAT32 Partition 100 MB Healthy System DISKPART> sel par 2 Partition 2 is now the selected partition. DISKPART> det par Partition 2 Type : e3c9e316-0b5c-4db8-817d-f92df00215ae Hidden : Yes Required: No Attrib : 0X8000000000000000 Offset in Bytes: 105906176 There is no volume associated with this partition. DISKPART> sel par 3 Partition 3 is now the selected partition. DISKPART> det par Partition 3 Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 Hidden : No Required: No Attrib : 0000000000000000 Offset in Bytes: 122683392 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 0 C Windows NTFS Partition 930 GB Healthy Boot DISKPART> sel par 4 Partition 4 is now the selected partition. DISKPART> det par Partition 4 Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac Hidden : No Required: Yes Attrib : 0X8000000000000001 Offset in Bytes: 999662026752 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 15 RAW Partition 516 MB Healthy Hidden DISKPART> sel par 5 The specified partition is not valid. Please select a valid partition. There is no partition selected. DISKPART> det par
- - - Updated - - -
ok, so preliminary results are in.
a diskpart list disk. select disk 0. list vol. select vol 1. online vol. seems to have brought it online. diskpart now shows it as ntfs.
after thinking eureka i backed out only to do a reagentc /info and see disabled. Aaaargh.
I followed with a reagentc /enable which said "cant find recovery" or whatever that special line we all know and love is.
so, just before literally banging my head in defeat - i closed out. re-opened the prompt, and ran /enable a second time. Success it says.
huh? So i do a reagentc /info again. Sure as garbagee. There it is in all its glory. I check disk management. Shows the proper sizing information.
Now.. im going to restart. and pray with all of my soul it persists and is working on the other side. If so - i think the crux of the issue has been identified - and resolved.
Again, preliminarily it seems the volume was offline and needed to be broughten online.
After a few probably un necessary restores and a windows in place upgrade that at least taught me how that behaves (so wasnt a waste) i think we may have it.
BBS!
- - - Updated - - -
and defeated. a restart and reagentc /info shows it as disabled again.
reagentc /enable shows "the windows RE image is not found"
a list vol shows it as offline again.
so NOW the question becomes. why does the volume keep going offline and how can i fix THAT?
argh.
- - - Updated - - -
mmmmm.
when the problem turns out to be something so simple and the wrong trees have been barked up the entire time.
again preliminary.
automount seems to have been disabled. no idea why. or how. never did it myself as i didnt know it was a thing. Not to mention you'd think the in place upgrade would have reset something like that to the default.
so its re-enabled, im going to bring the volume online, and im going to restart. (in a few, got a download going)
assuuuuming its going to be fixed this time for real though.
occams razor they call it right?
- - - Updated - - -
Well, thats a wrap! problem solved. and a saga of a thread ending with a tidbit of info for people at future peril.
waaaay more satisfying that it should be!
thank you for getting me on the right track @zbook
You're welcome.
Please make free backup images:
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect
If you upload V2 and DM they can be scanned for problems (post#33).
Quote
