Windows 10: New HD unmounting itself / 2 Windows Boot Manager in the BIOS


  1. Posts : 15
    Windows 7 x64 UEFI + Windows 10 x64 UEFI
       10 Jan 2018 #1

    New HD unmounting itself / 2 Windows Boot Manager in the BIOS


    Hey, I corrupted my computer that was running perfectly for 7 years. The symptoms are:

    1/ A 2nd Windows Boot Manager appeared out of the blue in the BIOS and is interfering with the 1st WBM.

    2/ my 4TB Toshiba 7200rpm HD is randomly and frequently unmounting itself which creates sometimes a huge lag when accessing files (the files are not corrupted, I could back them up onto my spare Seagate 3TB 7200rpm HD and they are fine). It lags when I run chkdsk /f /r through cmd, and sometimes lags when copying large chunks of data: you can see Windows copying the files at normal speed (100MBps) and suddenly the speed drops to 0. You have to wait for 3 or 4 minutes before it continues the copy at a way slower speed than before (30MBps). It makes Windows lag as well, especially when shutting down, I have to wait forever until it shuts down completely. I sometimes have to hit and hold the power button to speed up the process.


    All the specs are in my profile but here are they anyway:

    OS: Windows 7 x64 (UEFI) + Windows 10 x64 (MBR)
    CPU: Intel i7 2600K @3.4 GHz
    Motherboard: Asus P8P67 B1
    Memory: 4x4GB Gskill PC3 12800 1600MHz
    Graphics Card(s): Gigabyte GTX 750
    Hard Drives:SSD: Samsung 840 Pro 256GB (System Win7 x64)
    HD: Seagate 2TB 7200rpm SATA3
    HD: Toshiba 4TB 7200rpm SATA3
    HD: Seagate 2TB 7200rpm SATA3 (Win 10 x64 + Backup) - unplugged

    HD: Seagate 3TB 7200rpm SATA3 (Spare) - unplugged
    PSU: Seasonics 650W 80+ Bronze
    Case: Antec Sonata III
    Cooling: Noctua NH-D14

    So what happened? Well... I wanted to make a WindowsToGo system on an external Sandisk SSD. I was on my main system (Windows 7 UEFI x64) and installed WinToUSB. WinToUSB created a bootable UEFI Windows install on my external SSD and I restarted the computer... without unplugging all my internal SSD/HDs.

    The WindowsToGo install went fine, well, I still have to troubleshoot why the internet speed is way slower than it should be but this is not the topic here so I may create a new post in the forum about that issue later. When I shutdown WindowsToGo and unplugged the drive, I booted the computer but instead of booting into my main system (W7), it went straight to the BIOS. That's when I saw a 2nd Windows Boot Manager in the Boot section.

    I decided to boot on my Windows install DVD to run a startup repair and I could hear one of my HD (probably the Toshiba) spinning although my W7 system is on an SSD. There is absolutely no system files on the Toshiba so I don't get why it would be sollicitated for a startup repair.

    After the startup repair I booted on W7 after fiddling the boot options again in the BIOS and trying the different Windows Boot Manager options. I tried to access my files, just to see if everything was fine. My files on my 2TB Seagate were ok but my files on the 4TB Toshiba were hard to access. I could open an Excel document (it opened slowly) but it was impossible to save the edits I made. I tried to open an video file but the player froze.

    I installed EasyBCD to remove the 2nd WBM in the BIOS but the soft only listed my W7 UEFI install... (My Win10 MBR system is on an unplugged SATA HD). I tried the repair BCD option but it didn't change anything. I decided to load a backup image I did with Macrium Reflect but even though W7 seems to run fine, there's still this 2nd WBM in the BIOS I can't remove.

    I restarted the computer and booted on my Win10 system. I ran all the Seatools tests on the Toshiba except the Long Generic Test and it passed all tests (SMART, Short Generic Test etc). After backing up all my data from the 4TB Toshiba to a spare 3TB Seagate, I ran diskpart to clean and format the Toshiba. And then I did a 1 pass secure wipe with CCleaner. The drive got wiped but it's still unmounting itself and giving me a hard time when I want to shutsown the computer (it hangs forever). I also noticed the drive was heating more than the Seagates (42C vs 32C) with CrystalDiskInfo.

    As I'm typing, I started a chkdsk /f /r on the Toshiba that was supposed to take about 6 hours but then the drive unmounted itself again and the chkdsk process is lagging... It hangs for 5 minutes then keeps going, then hangs again etc. The chkdsk should be complete tomorrow morning after 16 hours.

    Any help would be appreciated because I have no clue how to solve this. The Toshiba drive is only 1 month old but was working perfectly before the WindowsToGo install on the Sandisk. Do you have any idea why it is lagging like this, even after a full pass secure wipe and a diskpart clean?

    Why did a 2nd WBM appear? What make these appear in the BIOS in the first place?

    Click image for larger version. 

Name:	Capture.PNG 
Views:	2 
Size:	9.2 KB 
ID:	171880

    Thanks in advance for your suggestions!
      My ComputerSystem Spec

  2.    10 Jan 2018 #2

    The chkdsk should be complete tomorrow morning after 16 hours.
    This is a big sign that the drive is failing. The Seatools Long test, is similar to chkdsk /R where it looks for bad sectors and tries to move the files to good sectors. The longer Check Disk and Seatools Long test take, the more bad sectors you have. If the Long test fails, then the drive should be replaced. What did Crystal Disk InfoSMART data say about the drive? If there is a yellow caution for too many bad sectors, then I would consider replacing the drive.
      My ComputerSystem Spec


  3. Posts : 15
    Windows 7 x64 UEFI + Windows 10 x64 UEFI
    Thread Starter
       11 Jan 2018 #3

    I don't know about the failing drive (remember it's only 1 month old, and I never had a problem in 1 month before the WindowsToGo/startup repair thing) because CrystalDiskInfo show any indication about a faulty drive, the HD passed all Seatools tests except the Generic Long Test I haven't selected and chkdsk /f /r didn't find anything.

    Code:
    Chkdsk was executed in read/write mode.  
    
    Checking file system on H:
    The type of the file system is NTFS.
    Volume label is New Volume.
    
    Stage 1: Examining basic file system structure ...
                                                                                           
                                                                                           
      256 file records processed.                                                         File verification completed.
                                                                                           
                                                                                           
      0 large file records processed.                                                                                                                           
                                                                                           
      0 bad file records processed.                                      
    Stage 2: Examining file name linkage ...
                                                                                           
                                                                                           
      282 index entries processed.                                                        Index verification completed.
                                                                                           
                                                                                           
      0 unindexed files scanned.                                                                                                                                
                                                                                           
      0 unindexed files recovered to lost and found.                     
    Stage 3: Examining security descriptors ...
    Cleaning up 2 unused index entries from index $SII of file 0x9.
    Cleaning up 2 unused index entries from index $SDH of file 0x9.
    Cleaning up 2 unused security descriptors.
    Security descriptor verification completed.
                                                                                           
                                                                                           
      13 data files processed.                                            
    Stage 4: Looking for bad clusters in user file data ...
                                                                                           
                                                                                           
      240 files processed.                                                                File data verification completed.
    
    Stage 5: Looking for bad, free clusters ...
                                                                                           
                                                                                           
      976646592 free clusters processed.                                                        Free space verification is complete.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
       3815317 MB total disk space.
        113748 KB in 9 files.
            76 KB in 15 indexes.
             0 KB in bad sectors.
        185435 KB in use by the system.
         65536 KB occupied by the log file.
       3815025 MB available on disk.
    
          4096 bytes in each allocation unit.
     976721407 total allocation units on disk.
     976646593 allocation units available on disk.
    Click image for larger version. 

Name:	Capture1.PNG 
Views:	2 
Size:	86.6 KB 
ID:	171959

    Anyway, while looking at the event log, I found literally a ton warning entries:
    Source: storeahci "Reset to device, \Device\RaidPort0, was issued."

    With a couple of :
    Source Disk "The IO operation at logical block address 0x5ebf41 for Disk 0 (PDO name: \Device\0000002c) was retried."

    These warning entries correspond to the HD lags I'm experiencing and are the reason why chkdsk took so long.
    What does this mean?

    Click image for larger version. 

Name:	Capture2.PNG 
Views:	2 
Size:	62.8 KB 
ID:	171960
      My ComputerSystem Spec


 

Related Threads
So I recently dual booted with Windows 10 and Ubuntu. I decided that I don't want Ubuntu at all anymore. I booted up my computer, was taken to the grub menu like usual, and I booted up using the Windows 10 Boot Manager. After that, I signed in,...
I was working on my laptop (Lenovo G505s, AMD A10, 10gb Ram, 1Tb HDD, Win 10 edu), suddenly I got a Blue screen error and Windows started collecting data regarding teh error. It went till 100% and got stuck there, after some time the screen started...
I need to put the Windows OS, that means Windows Boot Manager in BIOS at Boot option 2, but in this case it does not boot. I need to put at boot position 1 PXE boot and if that fails boot from Boot option 2 (Windows). How could I do that? My...
Hello, i was playing with disc partitions and i accidentally deleted something... The problem is, that when i start my computer, Windows boot manager error appears (with no options, nothing, just some text about how should i reinstall / repair...),...
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 15:06.
Find Us