Laptop SSD Failed Start Up - "Cannot be Repaired"

Page 1 of 3 123 LastLast

  1. TJR
    Posts : 10
    10/7 Pro 64
       #1

    Laptop SSD Failed Start Up - "Cannot be Repaired"


    This Dell Precision 5510 was purchased 5 years ago and I added a Samsung 950 Pro 256GB SSD following Kari's excellent tutorial to put Users folder on 1TB HDD. Also was configured to dual boot when upgraded from W7 to W10 Pro 64. No problems until last week when startup failed to a blue screen "Your PC/Device needs to be repaired". (I am still able to boot into W7.)

    I created a bootable repair USB with Rufus and got "...cannot be repaired..." message. Searched TenForums for similar situations and attempted the following diagnostics/repairs: earlier restore point (none found), sfc /scannow /offbootdir etc (Windows Resource Protection could not perform the requested operation), backed up BCD and used Macrium Reflect to repair boot (error 0xc000000e), chkdsk (no problems found), DISM /image.../cleanup-image /revertpendingactions (error 3, DISM & CBS logs attached), created scratch directory, BCD -s -h -r ren...etc... bootrec /rebuildbcd (nothing changed), tried DISM with /checkhealth (error 2, component store cannot be repaired), ran DISM with source pointed to USB ISO of exactly the same version as installed version - W10 Pro 1903 18362 (error 0x800F080 DISM failed).

    I have a backup image of the OS partition, but it also fails when restored, so I assume the corruption/error is in the System Reserved partition, of which I have no backup.

    I purchased an M.2 enclosure, tested the SSD on my desktop and imaged all partitions on the SSD - just in case. From W7 in the laptop and when plugged into my desktop externally, the SSD appears to be fully functional. Before wiping it and re-installing everything, I thought I'd post a help request here.

    I've uploaded log files to this dropbox folder:

    Dropbox - LKP Laptop Logs - Simplify your life

    I had to use the DM log collector, because V2 doesn't appear to work in W7....

    Many thanks in advance for your advice!

    Tom

    Laptop SSD Failed Start Up - "Cannot be Repaired"-diskmgr.jpg
      My Computers

  2. FreeBooter's Avatar
    Posts : 4,045
    Windows 10 Pro 64-bit
       #2

    If you open the log file, you’ll be shown details of all the tests performed by Startup Repair, with any errors discovered detailed. We can use this information to help diagnose and get to the root cause of the problem.



    To open log file from the Windows Recovery Environment, click and open the Command Prompt. When the Command Prompt is open, type Notepad and press Enter key to open the Notepad application. The Startup Repair log file is located at:



    Code:
    C:\Windows\System32\Logfiles\Srt\SrtTrail.txt


    You will need to navigate to the drive on which you have Windows installed (usually the C: drive) to see the SrtTrail.txt log file.
      My Computer


  3. TJR
    Posts : 10
    10/7 Pro 64
    Thread Starter
       #3

    FreeBooter,

    Thanks for your prompt reply. I was looking for this log earlier, but could not find it in the usual places. It was in a Recovery folder in an unnamed 533 MB partition on the SSD - perhaps an earlier System Reserved?? It is not a partition that I created. Here are the results:

    Startup Repair diagnosis and repair log
    ---------------------------
    Number of repair attempts: 1

    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory =
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 266 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 31 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code = 0x0
    Time taken = 31 ms

    Root cause found:
    ---------------------------
    Boot configuration is corrupt.

    Repair action: Partition table repair
    Result: Failed. Error code = 0x20
    Time taken = 4734 ms

    ---------------------------
    ---------------------------

    I recall an earlier version of an SrtTrail log showed a metadata error, but that logfile is no longer in the W10 Sys32 location.

    Is this a fixable problem? I believe both of these drives are MBR.

    Thank you
    Tom
      My Computers

  4. FreeBooter's Avatar
    Posts : 4,045
    Windows 10 Pro 64-bit
       #4

    Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

    Please type below commands into Command Prompt and press Enter key.

    Following commands will repair Master Boot Record (MBR), Boot Sector and BCD Store.


    Code:
    Bootrec /FixMbr
    
    Bootrec  /FixBoot
    
    Bootrec /scanos
    
    Bootrec  /RebuildBcd
      My Computer


  5. TJR
    Posts : 10
    10/7 Pro 64
    Thread Starter
       #5

    FixMBR completed successfully, but FixBoot failed, so I did not RebuildBCD. ScanOS found the SSD W10, but did not find the W7 installation that I've been running successfully on the HDD:

    Laptop SSD Failed Start Up - "Cannot be Repaired"-diskpart.jpgLaptop SSD Failed Start Up - "Cannot be Repaired"-fixboot-fail.jpg
      My Computers

  6. FreeBooter's Avatar
    Posts : 4,045
    Windows 10 Pro 64-bit
       #6

    Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

    Please type below command into Command Prompt and press Enter key.

    Following command will fixes errors on the disk and locates bad sectors and recovers readable information.


    Code:
    Chkdsk D: /r


    Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.
      My Computer


  7. TJR
    Posts : 10
    10/7 Pro 64
    Thread Starter
       #7

    I ran Chkdsk on all of the drives. Here are the results from the two OS partitions:

    Microsoft Windows [Version 10.0.18362.356]
    (c) 2019 Microsoft Corporation. All rights reserved.

    X:\Sources>diskpart

    Microsoft DiskPart version 10.0.18362.1

    Copyright (C) Microsoft Corporation.
    On computer: MININT-2KRRUAL

    DISKPART> list vol

    Volume ### Ltr Label Fs Type Size Status Info
    ---------- --- ----------- ----- ---------- ------- --------- --------
    Volume 0 G OS 7 NTFS Partition 99 GB Healthy
    Volume 1 F User Profil NTFS Partition 822 GB Healthy
    Volume 2 H System Rese NTFS Partition 500 MB Healthy
    Volume 3 D OS 10 NTFS Partition 213 GB Healthy
    Volume 4 I NTFS Partition 533 MB Healthy
    Volume 5 E Cruzer_Win1 NTFS Removable 14 GB Healthy
    Volume 6 FAT Partition 101 MB Healthy Hidden
    Volume 7 C RECOVERY NTFS Partition 8 GB Healthy Hidden

    DISKPART> exit

    Leaving DiskPart...

    X:\Sources>chkdsk d: /r
    The type of the file system is NTFS.
    Volume label is OS 10.

    Stage 1: Examining basic file system structure ...
    940032 file records processed.
    File verification completed.
    12123 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    278 reparse records processed.
    1184944 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    278 reparse records processed.

    Stage 3: Examining security descriptors ...
    Deleting an index entry with Id 47E from index $SDH of file 9.
    Cleaning up 8669 unused index entries from index $SII of file 9.
    Cleaning up 8669 unused index entries from index $SDH of file 9.
    Cleaning up 8669 unused security descriptors.
    CHKDSK is compacting the security descriptor stream
    Security descriptor verification completed.
    122457 data files processed.
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ...
    940016 files processed.
    File data verification completed.

    Stage 5: Looking for bad, free clusters ...
    16216332 free clusters processed.
    Free space verification is complete.
    Correcting errors in the Volume Bitmap.

    Windows has made corrections to the file system.
    No further action is required.

    224107804 KB total disk space.
    157792056 KB in 801800 files.
    433000 KB in 122460 indexes.
    0 KB in bad sectors.
    1017416 KB in use by the system.
    65536 KB occupied by the log file.
    64865332 KB available on disk.

    4096 bytes in each allocation unit.
    56026951 total allocation units on disk.
    16216333 allocation units available on disk.
    Failed to transfer logged messages to the event log with status 50.
    __________________________________________________________________________________

    Microsoft Windows [Version 10.0.18362.356]
    (c) 2019 Microsoft Corporation. All rights reserved.

    X:\Sources>chkdsk g: /r
    The type of the file system is NTFS.
    Volume label is OS 7.

    Stage 1: Examining basic file system structure ...
    230912 file records processed.
    File verification completed.
    1064 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    213 reparse records processed.
    284864 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    213 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    26977 data files processed.
    CHKDSK is verifying Usn Journal...
    36923232 USN bytes processed.
    Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ...
    230896 files processed.
    File data verification completed.

    Stage 5: Looking for bad, free clusters ...
    8702208 free clusters processed.
    Free space verification is complete.

    Windows has scanned the file system and found no problems.
    No further action is required.

    104856671 KB total disk space.
    69596600 KB in 194324 files.
    113684 KB in 26978 indexes.
    0 KB in bad sectors.
    337555 KB in use by the system.
    65536 KB occupied by the log file.
    34808832 KB available on disk.

    4096 bytes in each allocation unit.
    26214167 total allocation units on disk.
    8702208 allocation units available on disk.
    Failed to transfer logged messages to the event log with status 50.
    ________________________________________________________________________________

    I then re-ran Bootrec and once again Fixboot failed. Here are the results:

    Microsoft Windows [Version 10.0.18362.356]
    (c) 2019 Microsoft Corporation. All rights reserved.

    X:\Sources>bootrec /fixmbr
    The operation completed successfully.

    X:\Sources>bootrec /fixboot
    The volume does not contain a recognized file system.
    Please make sure that all required file system drivers are loaded and that the volume is not corrupted.

    X:\Sources>bootrec /scanos
    Scanning all disks for Windows installations.

    Please wait, since this may take a while...

    Successfully scanned Windows installations.
    Total identified Windows installations: 1
    [1] D:\Windows
    The operation completed successfully.
    ________________________________________________________________

    Thank you for your help!

    Tom
      My Computers

  8. Steve C's Avatar
    Posts : 6,482
    Windows 10 Pro 64 bit
       #8

    You could also try installing Macrium Reflect Free on a working PC, create the Reflect USB boot drive, boot to that USB drive on the problem PC then run the option Fix windows boot problems - see Use Macrium Reflect Rescue Media to Fix Windows Boot Issues

    This is a situation where it's good to have a system backup to recover from e.g. using Macrium Reflect.
      My Computers


  9. TJR
    Posts : 10
    10/7 Pro 64
    Thread Starter
       #9

    Steve C

    Thanks for your suggestions! I do make backups using DriveImage XML and store them on a 'swap drive' at a friend's house. Unfortunately, I've only imaged the OS partition and not the System Reserved partition. My booting problem did not go away after restoring the W10 OS backup, hence my request for help. I've also attempted MR boot repair with no success (error 0xc000000e?). I may have time later to try it again.
    ________________________________________________________________________________

    Following directions on some earlier FreeBooter threads, I've run SFC Scannnow again with the same 'Resource Protection' error:

    Microsoft Windows [Version 10.0.18362.356]
    (c) 2019 Microsoft Corporation. All rights reserved.

    X:\Sources>diskpart

    Microsoft DiskPart version 10.0.18362.1

    Copyright (C) Microsoft Corporation.
    On computer: MININT-SQUJO47

    DISKPART> list vol

    Volume ### Ltr Label Fs Type Size Status Info
    ---------- --- ----------- ----- ---------- ------- --------- --------
    Volume 0 G OS 7 NTFS Partition 99 GB Healthy
    Volume 1 F User Profil NTFS Partition 822 GB Healthy
    Volume 2 H System Rese NTFS Partition 500 MB Healthy
    Volume 3 D OS 10 NTFS Partition 213 GB Healthy
    Volume 4 I NTFS Partition 533 MB Healthy
    Volume 5 E Cruzer_Win1 NTFS Removable 14 GB Healthy
    Volume 6 FAT Partition 101 MB Healthy Hidden
    Volume 7 C RECOVERY NTFS Partition 8 GB Healthy Hidden

    DISKPART> exit

    Leaving DiskPart...

    X:\Sources>sfc /scannow /offbootdir=h:\ /offwindir=d:\windows

    Beginning system scan. This process will take some time.


    Windows Resource Protection could not perform the requested operation.
    ___________________________________________________________________________________

    I'm stuck here and would appreciate any other suggestions....

    Tom

    - - - Updated - - -

    I ran Macrium Reflect boot repair from USB, selected the OS10 partition (not the System Reserved), then saved the configuration for booting. It appears that there is still some corruption:

    Laptop SSD Failed Start Up - "Cannot be Repaired"-mr-failed-boot-os10.jpg

    Any thoughts for next steps?

    Tom
      My Computers

  10. FreeBooter's Avatar
    Posts : 4,045
    Windows 10 Pro 64-bit
       #10

    You will need to execute following commands to repair boot error message.

    Code:
    Bootrec /scanos
    
    Bootrec  /RebuildBcd
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:30.
Find Us




Windows 10 Forums