Boot failure after chkdsk /r No bootable image found

Page 9 of 15 FirstFirst ... 7891011 ... LastLast

  1. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #81

    The Users folder was copied from D: > F: but when it was done there was a prompt for a huge number for files.
    These files may have the same name but different dates.
    They were not viewed.
    The whole users folder could be copied again an may take 12 to 18 hours to get to the prompt for the duplicate files and then complete the file transfer.

    The files on the computer were disorganized with many failed windows upgrades, boot loops, etc.
    Somehow a Microsoft store had place the RAID 0 folders/files onto another drive in windows RE, then clean install, and restore the folders and files. This service had been performed multiple times and this was before learning about making images.
    The Macrium image that was initially made was on a non-corrupt operating system but an operating system that was not able to be upgraded.
    There were default updated Macrium backup images and those images are likely with a problematic operating system (problems with scannow and restorehealth, but bootable)
    If necessary losing several months of the most recent saved files could work if that could simplify things to where the drive could be cleaned and restored quickly (for example may, june and july). A lot of time has passed and I would like to use the files on the problematic computer with a working operating system.
    The latest Macrium image should have an operating system that cannot be upgraded to 1803 and cannot be repaired with an in place upgrade repair. It may be able to boot but was never tested. It did have recurrent chkdsk repairs and all of the drive hardware tests passed. The HD and RAM were tested again last night with the HP on board UEFI diagnostics.

    Drive G: New Volume has a backup Users folder and the Macrium backup image.
    Should this users folder be compared to the others? If so how for the duplicate file names that may have different dates?
    Macrium is not yet installed on D: drive.
    Should it be installed using Kyhi boot rescue?
    Macrium could be installed on another computer?....... and then G: drive moved to the other computer.


    When the additional files are copied to the F: drive how should the new folder(s) be labeled so that it works smoothly for the restoration? How will the duplicate problem be addressed? These additional copies would be backup2 with the file name or something similar?

    The files that were copied to F: I am not able to determine whether they are complete or incomplete. There were files in prior User folder transfers in which long files names were blocked and may have been lost. There were too may files that were duplicates and I don't remember the selection that had been made in the past.

    When the Users folder was restored it was first moved from the external drive to the desktop. For some reason the Microsoft technician was concerned that an interruption could cause problems and preferred a transfer to the desktop first. The Users folder was never separated restoring the individual folders before the next computer problem so that may be the source of some of the problems.
    Last edited by zbook; 07 Sep 2018 at 04:16.
      My Computer


  2. Posts : 30,189
    Windows 11 Pro x64 Version 23H2
       #82

    sorry zbook so many questions. Lets try this.

    Where are the critical files you created between July 18/2018 and the time it crash. Specifically what files are they, are they pictures, documents. Do you know the path to these files?

    I suggested you start Macrium and browse the C: drive within the image you created. I asked if you could navigate down through aaaaaa\documents and open My Music (or My pictures) to see if this folder has data.
      My Computer


  3. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #83

    Using Macrium there were no MyPictures seen on C:\users\aaaaaaa\documents.
    The Macrium images should now be on drives F: (4TB) and G: (1TB)
    Images are below of what was seen using G:

    Viewing the Macrium desktop items reminded me of a prior Users restoration.
    Before Macrium was in use the computer had had a Windows defender offline and Windows driver verifier bootloop with Windows 1607.
    At a Microsoft store they had backed up the Users folder, clean installed 1607, and placed the Users folder back on the desktop using owner. Then two weeks later they performed another backup to fix an upgrade failure to 1703.
    These could be related to the duplicate backup images prompt displayed at the end of copy and paste of C: (750 GB) to F: (4 TB)
    Opening the owner users folder there are mypictures however these are old, from 2016.

    Boot failure after chkdsk /r  No bootable image found-macrium-open-image-part-1.png

    Boot failure after chkdsk /r  No bootable image found-macrium-open-image-part-2.png

    Boot failure after chkdsk /r  No bootable image found-macrium-open-image-part-3.png

    Boot failure after chkdsk /r  No bootable image found-macrium-open-image-part-4.png


    This was from a users folder (owner) that had been placed on the desktop.
    Boot failure after chkdsk /r  No bootable image found-macrium-open-image-part-5-pictures.png
      My Computer


  4. Posts : 152
    Windows 10 Pro/Education x64
       #84

    Ok, I had to read the last few posts twice to make sure I didn't miss anything. @zbook, You mentioned you were trying to reinstall the Intel RST driver, from within Kyhi's winpe book disk. That said, I'm inferring from your actions, you are trying to access and reinitialize the RAID 0 cache from winpe. Have I got everything correct so far?
      My Computer


  5. Posts : 30,189
    Windows 11 Pro x64 Version 23H2
       #85

    Since the Raid was a Raid 0 from what I understand it cannot be rebuilt. Is this your understanding.

    So back a few posting this is how c:\users\aaaaaa\documents appeared

    Boot failure after chkdsk /r  No bootable image found-image.png

    And then when you looked in Macrium f:\users\aaaaaa\documents

    Boot failure after chkdsk /r  No bootable image found-image.png

    So we are not looking at the same thing. Yes drive letters are different but that is just Macrium mounting drive.

    You showed a great deal of administrator which I think we agreed has none of your work.

    Could you post entire users\aaaaaa\documents from Macrium image. Please nothing else.
      My Computer


  6. Posts : 152
    Windows 10 Pro/Education x64
       #86

    Caledon Ken said:
    Since the Raid was a Raid 0 from what I understand it cannot be rebuilt. Is this your understanding.
    Yes, exactly my understanding.

    As for the files in the Macrium image, I'd copy those to the new drive as we know those files are good.
      My Computer


  7. Posts : 30,189
    Windows 11 Pro x64 Version 23H2
       #87

    Agree but I'm just trying to determine what are the critical files on the old 750GB that were created on July 18/18 and then subsequently until it crashed.
      My Computer


  8. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #88

    This is what is seen now:

    Boot failure after chkdsk /r  No bootable image found-macrium-1.png

    How do you reopen what was seen earlier?
    Is a reboot necessary?
      My Computer


  9. Posts : 30,189
    Windows 11 Pro x64 Version 23H2
       #89

    Third option down left, Open an Image or backup folders in Windows explorer.

    zbook, without giving out to much personal information what files were created from July 18 to crash point, the critical files?

    Are we looking for pictures, or documents?
      My Computer


  10. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #90

    Cannot find the same images as in post 83.

    Instead Macrium is now drive H: or I:

    There were no audio, pictures, video in this location

    Boot failure after chkdsk /r  No bootable image found-macrium-1.png

    Boot failure after chkdsk /r  No bootable image found-macrium-2.png


    Boot failure after chkdsk /r  No bootable image found-macrium-3.png

    Boot failure after chkdsk /r  No bootable image found-macrium-4.png

    Boot failure after chkdsk /r  No bootable image found-macrium-5.png
    Last edited by zbook; 09 Sep 2018 at 02:17.
      My Computer


 

  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 11:32.
Find Us




Windows 10 Forums