Bad blocks on Toshiba HDD & Win10 OS probs

Page 3 of 3 FirstFirst 123

  1. Posts : 19,535
    W11+W11 Developer Insider + Linux
       #21

    You could use Macrium Reflect to make backup and if it verifies than you can just restore image to new drive and it will be just as good as cloning if not better. MR rescue disk/USB contains programs for dealing with bad BOOT and other problems and can also optimize for SSD if you use it.
      My Computers


  2. Posts : 16,338
    W10Prox64
       #22

    ohante said:
    They mention ddrescue in that 7 thread.. Folks over at hddguru suggested starting with either that or hddsuperclone to do an identical sector by sector clone for drives that exhibit evidence of hardware failure. I've just finished 2 & 1/2 hours of cloning the notebook's internal HDD minus all it's bad blocks to the new drive connected to the notebook via this Sabrent docking station, with the notebook booted into Linux Mint off an USB stick. So far so good.

    Tomorrow I'll see if I can pull the Toshiba case apart, swap drives, run the Windows 10 installer from a flash drive, select the Repair option and see if the installer can repair the cloned copy of 10.

    Someone also reminded me that Toshibas have a keyboard shortcut that can restore the notebook to its factory fresh software condition using system recovery I think from a hidden partition.

    http://support.toshiba.com/sscontent?docId=98082971

    That may be another option if the W10 installer can't repair the HDD clone.

    Data recovery I've dealt with a bit in the past using various software. The "magical' one was Testdisk that was able to recover a deleted NTFS partition table from a backup few seem to be aware exists at the very end of the drive. I'd mistakenly deleted the drive's one primary partition with the wrong diskpart command. But after hours of deep scanning, Testdisk fixed the useless drive in a second by copying the backup table back to the beginning of the drive.
    Good luck and let us know how it goes.
      My Computer


  3. Posts : 85
    Windows 7 Ultimate 64-bit SP1
    Thread Starter
       #23

    It's all fixed :)
    @Samuria - Other methods of cloning corrupted HDDs might not have been successful, but the Linux hddsuperclone folks on hddguru suggested did the trick. Last night I booted the Toshiba to Linux Mint from a flash drive, and ran hddsuperclone to clone the internal HDD to a new one in a USB connected docking station. Tonight I cracked the case open and dropped in the clone. After that it was pretty simple. Booted Windows 10, and ran Check Now from the C: drive's Properties > Tools menu. It had me reboot to run chkdsk I assume it was, found and fixed system file errors, and finally booted to a working desktop after repairs.

    I'm glad it was that quick and easy. But now I still don't know if my old Acronis True Image backups could have been restored successfully. I am tempted though to delete hundreds of gigabytes worth of backed up video & audio files and run Acronis to image the new drive. And maybe look the free Macrium Reflect program @CountMike mentioned for imaging.
    Last edited by ohante; 06 Sep 2017 at 05:43.
      My Computer


  4. Posts : 16,338
    W10Prox64
       #24

    ohante said:
    It's all fixed :)
    @Samuria - Other methods of cloning corrupted HDDs might not have been successful, but the Linux hddsuperclone folks on hddguru suggested did the trick. Last night I booted the Toshiba to Linux Mint from a flash drive, and ran hddsuperclone to clone the internal HDD to a new one in a USB connected docking station. Tonight I cracked the case open and dropped in the clone. After that it was pretty simple. Booted Windows 10, and ran Check Now from the C: drive's Properties > Tools menu. It had me reboot to run chkdsk I assume it was, found and fixed system file errors, and finally booted to a working desktop after repairs.

    I'm glad it was that quick and easy. But now I still don't know if my old Acronis True Image backups could have been restored successfully. I am tempted though to delete hundreds of gigabytes worth of backed up video & audio files and run Acronis to image the new drive. And maybe look the free Macrium Reflect program @CountMike mentioned for imaging.
    That's great news! I'll second the Macrium recommendation. Cheers!
      My Computer


  5. Posts : 85
    Windows 7 Ultimate 64-bit SP1
    Thread Starter
       #25

    simrick said:
    That's great news! I'll second the Macrium recommendation. Cheers!

    Indeed @simrick - I want to thank you and everyone who took some time to contribute their thoughts on this issue. I learned a lot along the way. It's really great that support forums like these are still chocked full of knowledgeable folks willing to help work out other peoples' issues... just like the pre-www gui days.

    Happy to have my lappy no longer so wacky.

    Cheers all!
      My Computer


  6. Posts : 16,338
    W10Prox64
       #26

    ohante said:
    Indeed @simrick - I want to thank you and everyone who took some time to contribute their thoughts on this issue. I learned a lot along the way. It's really great that support forums like these are still chocked full of knowledgeable folks willing to help work out other peoples' issues... just like the pre-www gui days.

    Happy to have my lappy no longer so wacky.

    Cheers all!
    Glad we could be of help.
      My Computer


  7. Posts : 85
    Windows 7 Ultimate 64-bit SP1
    Thread Starter
       #27

    Post recovery corrupted file isuues


    I'm still in need of help on this issue folks. After cloning this drive to a new HDD and successfully booting the working clone, I later ran sfc /scannow. It found and repaired corrupted files, but reported it was not able to fix some. I ran it a second time the next day with the same message at the end of the scan. The cbs.log is over 31000 lines and is a bit beyond me. Here's most of the error I can spot:

    * 12 instances: .... - ERROR_FILE_NOT_FOUND
    * 25 instances: 0000xxxx - Couldn't mark for pending delete:
    * Many: 0000xxxx - Error - Overlap: Duplicate ownership for directory
    * Many: [Path to file] is not owned but specifies SDDL in component in component [Component]
    * Very many: 0000xxxx Error - Overlap: Duplicate ownership for directory [Path to directory]
    * Many: Cannot repair member file [File info] in the store, file is missing
    * 4 instances: Could not reproject corrupted file [File info] source file in store is also corrupted
    * Several: Warning - Overlap: Directory [Path] is owned twice or has its security set twice

    The system hasn't given me any problems. But it's been suggested that I download the latest ISO of 1703 (I'm still on 1607 build 14393.1715), install Windows 10 over the existing one, and the installer ought to repair the existing file issues. Does this sound like the best path forward? I can upload the cbs.log if it's of any help.

    Last night I got an Windows Update alert saying the new creators update has been downloaded and is ready to install. I opted to delay the update for a week, and am wondering if there might be any conflicts with this if I go ahead and run a full re-installation of Windows 10 & update to 1703 from a flash drive.

    Thanks for any input on all this. :)
      My Computer


  8. Posts : 43,201
    windows 10 professional version 1607 build 14393.969 64 bit
       #28

    When scannow is unable to complete or displays that it found integrity violations that it was unable to fix the next step that typically fixes what scannow could not fix are the dism commands.

    Run these commands using administrative command prompt:
    dism /online /cleanup-image /checkhealth
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth

    Sometimes the dism commands above fail. An if the above commands fail there are additional dism commands:
    Use DISM to Repair Windows 10 Image Windows 10 Performance Maintenance Tutorials

    Create a bootable windows 10 iso:
    Download Windows 10
      My Computer


  9. Posts : 85
    Windows 7 Ultimate 64-bit SP1
    Thread Starter
       #29

    zbook said:
    When scannow is unable to complete or displays that it found integrity violations that it was unable to fix the next step that typically fixes what scannow could not fix are the dism commands.

    Run these commands using administrative command prompt:
    dism /online /cleanup-image /checkhealth
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth

    Sometimes the dism commands above fail. An if the above commands fail there are additional dism commands:
    Use DISM to Repair Windows 10 Image Windows 10 Performance Maintenance Tutorials

    Create a bootable windows 10 iso:
    Download Windows 10

    Thanks for that zbook. Will give run those and report back.
      My Computer


  10. Posts : 85
    Windows 7 Ultimate 64-bit SP1
    Thread Starter
       #30

    Fantastic @zbook. Those commands seem to have done the trick:

    /checkhealth - Found no corruption
    /scanhealth - Completed successfully
    /restorehealth - Completed successfully

    Re-ran sfc /scannow which reported corrupt files found and successfully repaired - this time with no mention of any corrupt files found that couldn't be repaired.

    Thanks ever so much for your input on this bit of digital magic @zbook. :)
    Last edited by ohante; 18 Sep 2017 at 05:48.
      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 01:39.
Find Us




Windows 10 Forums