Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Can't mount system drive - error 0x000000ED

09 Apr 2017   #1
Gi1919

Windows 7 Home Premium 64 bits
 
 
Can't mount system drive - error 0x000000ED

Hello,

I'm having issues with my HP Pavilion g6-1331sf laptop.

I've had 3 BSODs recently:
  • one about 2 weeks ago, code 0x0000007A: "KERNEL_DATA_INPAGE_ERROR".
  • then another, the same one, a few days ago.
  • then a 0x000000ED, "UNMOUNTABLE_BOOT_VOLUME", later that day.

I have this about the second BSOD:
Quote:
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036

Informations supplémentaires sur le problème :
BCCode: 7a
BCP1: FFFFF6FC500E5180
BCP2: FFFFFFFFC0000185
BCP3: 00000001B06BC880
BCP4: FFFFF8A01CA30000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\033117-29172-01.dmp
C:\Users\Me\AppData\Local\Temp\WER-1823324-0.sysdata.xml
And some stuff had happened between the 2nd and 3rd BSODs:
  • it did a CHKDSK with only 3 steps; when I looked into the Event Observer later, the log was truncated, stopping halfway through a word ("Répara"...) in the middle of step 2
  • when my session opened, I was informed that Comodo couldn't start, the install was damaged. Seven's own firewall wouldn't start either, with an error code 0x80070422
  • I restarted the laptop, everything was normal until the login screen, then it stayed on "welcome" for ages, then showed a "neutral" session, said something about not being able to access user profiles, that the identity was incorrect... The LED was lit continously for about an hour, and then when it finally went out, I was able to display the Task Manager, close that session, and open my own, which looked normal. I planned a CHKDSK on C: and ticked both boxes in the hope of fixing the firewall problems
  • I restarted the laptop, but it did not do the CHKDSK, and again, took a while to open a neutral session; I had to wait one more hour to redo the whole thing (log in to my own session, plan a CHKDSK)
  • I restarted it again, and this time, it displayed the "Windows" screen longer than usual and then: UNMOUNTABLE_BOOT_VOLUME!

It kinda felt like it had been going worse and worse with every restart, so I have not booted on the drive since.

****************************************************************************

The laptop has a dual boot (Windows 7 / Ubuntu, though I'm not sure I can remember the Linux password...) and a bunch of partitions:
  • sda1 SYSTEM 200 MB
  • sda2 C: (Windows 7 and some data too) 70 GB
  • sda3 extended partition (sda5, 6, 7,8)
  • sda4 E: (HP_TOOLS) 3,97 GB
  • sda5 Ubuntu (boot) 500 MB
  • sda6 Ubuntu (root) 40 GB
  • sda7 Ubuntu (swap) 3,91 GB
  • sda8 D: (my data) 348 GB

All I have handy currently is:
  • a SystemRescueCD from 2009, which I used to copy all the data from D: to an external hard drive
  • the old XP laptop I'm typing from, which I fear is compromised, so I'm not sure I can download/burn ISOs from it
  • a Windows 7 repair disk which I hope works, I've never had to use it so far

While in the SystemRescueCD session, Gparted displays warning signs next to sda2 and sda8.
  • About sda8 (D: ), it says: "This software has detected that the disk has at least 7 bad sectors". I was able to copy all my files but 2 to the external hard drive.
  • About sda2 (C: ), it says: "Failed to calculate number of free clusters: input/output error. Failed to mount /dev/sda2: input/output error. NTFS is inconsistent. Run chkdsk /f on Windows then reboot TWICE!" (it may say more stuff, but I can't scroll all the way down)

I haven't tried the other tools included on the live CD yet ("Show Filesystems" and "TestDisk"). Should I?

Any idea of what the issue is, first? I hope it's a Windows problem and not a hard drive failure... There's a little bit of data on C: I'd like to be able to save too...

And then: is the next step booting on the Windows 7 repair disk? Will that play nice with my dual boot? And preserve all the data too?

Thank you...


My System SpecsSystem Spec
.
09 Apr 2017   #2
Layback Bear

Windows 7 Pro. 64/SP-1
 
 

Hi Gi1919 and welcome to our forum.

I'm not a BSOD Expert but I do know some information is needed by them.

Please complete this and post the info as per the tutorial.

By Brink.

Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Help Forums

Jack
My System SpecsSystem Spec
09 Apr 2017   #3
Gi1919

Windows 7 Home Premium 64 bits
 
 

Thanks, Jack.

I did read those instructions, but it seems you need to be able to be logged in a Windows 7 session to provide all that information. I currently cannot even mount the drive! So I'm afraid I can't provide the info requested either...

ETA: but if this isn't the right forum as I currently cannot boot, please feel free to move this topic to the right place, mods!
My System SpecsSystem Spec
.

09 Apr 2017   #4
axe0

Windows 10 Pro
 
 

Hi Gi1919,

This is clearly a failing hard drive, your best bet is to replace it.
Reinstalling or using the repair disk probably won't help enough to completely get rid of the problem.
My System SpecsSystem Spec
09 Apr 2017   #5
Gi1919

Windows 7 Home Premium 64 bits
 
 

Really?? Seven bad sectors on a 350 GB partition didn't look that bad to me, and I had hoped the C: partition wasn't much worse off... Ah, crap!

Ok, let me rephrase my question then: before I bin the laptop and buy a new one, what's my best bet to recover the data I still had left on C: ? I'm mostly thinking of my Thunderbird and Firefox profiles, plus tons of music, plus the odd file that had saved under My Documents by default... That's gonna be my number 1 priority, even if I can't save the laptop itself!
My System SpecsSystem Spec
09 Apr 2017   #6
axe0

Windows 10 Pro
 
 

Bad sectors are not the only thing that could cause a hard drive to die. OTH, every hard drive can change at least a few bad sectors (marking the sector as bad, move the data to a backup sector), but how many varies a lot and usually it is only just a couple.

You don't have to trash the laptop, only replace the hard drive. Usually with laptops, the RAM and hard drive are the only parts that can be replaced (besides the battery) without trashing the laptop.

You may be able to recover your data with a WinPE, Windows 10 Recovery Tools - Bootable Rescue Disk - - Windows 10 Forums
My System SpecsSystem Spec
27 Apr 2017   #7
Gi1919

Windows 7 Home Premium 64 bits
 
 

Hi,

Is it okay if I pop back up here? Sorry I was away for so long...

I think I managed to recover everything I needed to.

Now I'd like to try to resuscitate the laptop! (I won't change the hard drive, as the laptop itself is 5 years old... But if I could squeeze a few more weeks out of it, that'd be great, as I have some important work to turn in soon and don't have the time to buy and configure a new computer right now!)

I booted on the Windows 7 repair disk and launched a CHKDSK /f /r that's running at the moment.

I'd like to know:

1) is it okay if I run it twice in a row? Since that's what Gparted recommended... I think. It says "Run chkdsk /f on Windows then reboot TWICE!". Not sure if I should run chkdsk once, reboot twice, or run chkdsk, reboot, run chkdsk again, reboot again... Thoughts?

2) what should I do after that? Try to reboot the regular way? Try the "fix boot" option in the console? Run some other command at the prompt?

Thank you!
My System SpecsSystem Spec
27 Apr 2017   #8
axe0

Windows 10 Pro
 
 

Download an ISO from Windows 10 Recovery Tools - Bootable Rescue Disk - - Windows 10 Forums and boot from the Win10PE, open HDTune and post a screenshot or proper photo of the health tab.
We'll need the status of the hard drive to determine if it's worth it to run chkdsk.


Please note, if I don't reply within a short notice (exception for night hours), do not bump your thread. I've recently lost my mother on a rare kind of cancer. I will respond back, but it may take time.
My System SpecsSystem Spec
27 Apr 2017   #9
Gi1919

Windows 7 Home Premium 64 bits
 
 

Hi Axe0!

Sorry to hear that... Hope you're doing ok... or as ok as can be... Internet hug!

I can't burn a CD right now, but I can tell you that using Linux, the overall health of the drive is displayed as green. There are 116 bad sectors: 76 reallocated, 40 pending. Those were the only lines displayed in red. Here's the full smartmontools output:
Code:
ubuntu@ubuntu:~$ sudo smartctl --smart=on --offlineauto=on --saveauto=on /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
SMART Attribute Autosave Enabled.
SMART Automatic Offline Testing Enabled every four hours.

ubuntu@ubuntu:~$ sudo smartctl -H -i /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 5400.6
Device Model:     ST9500325AS
Serial Number:    S2WELMNR
LU WWN Device Id: 5 000c50 04af23b30
Firmware Version: 0005HPM1
User Capacity:    500 107 862 016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Apr 23 20:51:33 2017 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

ubuntu@ubuntu:~$ sudo smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 5400.6
Device Model:     ST9500325AS
Serial Number:    S2WELMNR
LU WWN Device Id: 5 000c50 04af23b30
Firmware Version: 0005HPM1
User Capacity:    500 107 862 016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Apr 23 20:51:51 2017 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
Total time to complete Offline 
data collection:         (    0) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 144) minutes.
SCT capabilities:            (0x103f)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   078   077   006    Pre-fail  Always       -       86143218
  3 Spin_Up_Time            0x0002   099   098   000    Old_age   Always       -       0
  4 Start_Stop_Count        0x0033   098   098   000    Pre-fail  Always       -       2640
  5 Reallocated_Sector_Ct   0x0033   097   097   036    Pre-fail  Always       -       76
  7 Seek_Error_Rate         0x000f   089   060   030    Pre-fail  Always       -       905571090
  9 Power_On_Hours          0x0032   077   077   000    Old_age   Always       -       20399
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0033   098   098   020    Pre-fail  Always       -       2582
183 Runtime_Bad_Block       0x0032   100   253   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       26351
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       4295032834
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   062   048   045    Old_age   Always       -       38 (Min/Max 22/38)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       36
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   075   075   000    Old_age   Always       -       50433
194 Temperature_Celsius     0x0022   038   052   000    Old_age   Always       -       38 (0 13 0 0)
195 Hardware_ECC_Recovered  0x001a   051   043   000    Old_age   Always       -       86143218
196 Reallocated_Event_Count 0x0033   097   097   036    Pre-fail  Always       -       76
 197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       40
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 22333 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 22333 occurred at disk power-on lifetime: 20399 hours (849 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 c4 3d 66 00  Error: UNC at LBA = 0x00663dc4 = 6700484

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 01 c4 3d 66 40 00      00:03:05.016  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:03:04.986  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      00:03:04.953  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:03:04.859  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:03:04.836  SET FEATURES [Reserved for Serial ATA]

Error 22332 occurred at disk power-on lifetime: 20399 hours (849 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 c4 3d 66 00  Error: UNC at LBA = 0x00663dc4 = 6700484

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 01 c4 3d 66 40 00      00:03:02.509  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:03:02.499  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      00:03:02.498  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:03:02.485  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:03:02.443  SET FEATURES [Reserved for Serial ATA]

Error 22331 occurred at disk power-on lifetime: 20399 hours (849 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 c4 3d 66 00  Error: UNC at LBA = 0x00663dc4 = 6700484

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 01 c4 3d 66 40 00      00:03:00.022  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:03:00.012  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      00:03:00.011  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:02:59.997  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:02:59.956  SET FEATURES [Reserved for Serial ATA]

Error 22330 occurred at disk power-on lifetime: 20399 hours (849 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 c4 3d 66 00  Error: UNC at LBA = 0x00663dc4 = 6700484

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 01 c4 3d 66 40 00      00:02:57.546  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:02:57.536  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      00:02:57.534  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:02:57.521  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:02:57.479  SET FEATURES [Reserved for Serial ATA]

Error 22329 occurred at disk power-on lifetime: 20399 hours (849 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 c4 3d 66 00  Error: UNC at LBA = 0x00663dc4 = 6700484

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 01 c4 3d 66 40 00      00:02:55.027  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:02:55.017  SET FEATURES [Reserved for Serial ATA]
  ec 00 00 00 00 00 a0 00      00:02:55.015  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:02:54.967  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:02:54.876  SET FEATURES [Reserved for Serial ATA]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     20397         126243962
# 2  Short offline       Completed: read failure       90%     20397         126243962
# 3  Short offline       Completed: read failure       90%     20397         126243962
# 4  Short offline       Completed: read failure       90%     20397         126243962
# 5  Extended offline    Completed: read failure       90%     20395         126243962
# 6  Short offline       Completed: read failure       90%     20395         126243962
# 7  Extended offline    Completed: read failure       90%     20381         126243962
# 8  Short offline       Completed: read failure       90%     20380         126243962
# 9  Short offline       Completed: read failure       90%     20349         6700481
#10  Short offline       Completed: read failure       90%     20349         6700481
#11  Short offline       Completed: read failure       90%     20349         6700481
#12  Short offline       Completed: read failure       90%     20349         6700481
#13  Short offline       Completed: read failure       90%     20349         6700481

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

ubuntu@ubuntu:~$ sudo smartctl -t short /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Sun Apr 23 20:54:32 2017

Use smartctl -X to abort test.

ubuntu@ubuntu:~$ sudo smartctl -l selftest /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     20399         6700481
# 2  Extended offline    Completed: read failure       90%     20397         126243962
# 3  Short offline       Completed: read failure       90%     20397         126243962
# 4  Short offline       Completed: read failure       90%     20397         126243962
# 5  Short offline       Completed: read failure       90%     20397         126243962
# 6  Extended offline    Completed: read failure       90%     20395         126243962
# 7  Short offline       Completed: read failure       90%     20395         126243962
# 8  Extended offline    Completed: read failure       90%     20381         126243962
# 9  Short offline       Completed: read failure       90%     20380         126243962
#10  Short offline       Completed: read failure       90%     20349         6700481
#11  Short offline       Completed: read failure       90%     20349         6700481
#12  Short offline       Completed: read failure       90%     20349         6700481
#13  Short offline       Completed: read failure       90%     20349         6700481
#14  Short offline       Completed: read failure       90%     20349         6700481

ubuntu@ubuntu:~$ sudo smartctl -t long /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 144 minutes for test to complete.
Test will complete after Sun Apr 23 00:35:07 2017

Use smartctl -X to abort test.

ubuntu@ubuntu:~$ sudo smartctl -l selftest /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 20381 126243962
# 2 Short offline Completed: read failure 90% 20380 126243962
# 3 Short offline Completed: read failure 90% 20349 6700481
# 4 Short offline Completed: read failure 90% 20349 6700481
# 5 Short offline Completed: read failure 90% 20349 6700481
# 6 Short offline Completed: read failure 90% 20349 6700481
# 7 Short offline Completed: read failure 90% 20349 6700481
And I'd already launched the CHKDSK before posting, which ended with this message (roughly translated from French):
Quote:
Adding 26 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap.
Correcting errors in the volume map.
Windows has made corrections to the file system.
(...)
116 KB in bad sectors.
There were also 2 "Windows replaced bad clusters in file xxx" messages during step 4 (about a file in a Firefox profile and another in a FeedDemon profile).

Then I tried restarting, and it said more or less: "Windows couldn't start, could be due to a recent software or hardware change". I chose "Launch the system restart tool".

Then it said "insert an installation CD". Well, I inserted the repair CD, was that it? It's all I have... (on that page, it also said: "status: 0xc0000225")

I rebooted. This time, the console started very fast and displayed the partition size accurately. Earlier today, before the CHKDSK, it had taken an hour before I could reach the prompt, and it said "Partition size: 0 MB".

So after selecting my OS, I clicked "Next" and a different window popped up, with a progress bar. It said "Identifying problems..." and then "Attempting repairs...", and then, it opened HP Recovery Manager, which only offered options I didn't like (restoring, resetting...)

So I turned it off, and that's where I'm at.

What should I do now?


[Edited to add: I know the drive is likely dying, but again, it would save my life if I could make this laptop work for just a few more weeks... That's all I need, really!]
My System SpecsSystem Spec
27 Apr 2017   #10
axe0

Windows 10 Pro
 
 

Given the current state, I doubt it could go on for another 3-4 more weeks. If the data is correct, the bad sector count isn't the only issue with the drive.

A safe(r) bet could be a docking station. I understand you don't have the time to get another laptop and configure it, but the longer you continue with this hard drive the higher the risk your work becomes corrupted!
I don't know what you're doing, what software you're using and how much time it takes to get everything configured, but if I was in this situation I would do either of the following
- get a new system and give up some sleep to get it configured
- configure a proper backup system and use it to move and save work on until it is done.

TBH, configuring a backup system and keep using the dying drive could eventually take more time than configuring a new system.
This, because, as mentioned, the longer you work the higher the risk of issues. There is a possibility your work doesn't get corrupted, but the software you're using to work does.
My System SpecsSystem Spec
Reply

 Can't mount system drive - error 0x000000ED




Thread Tools




Similar help and support threads
Thread Forum
BSOD at startup, error 0x000000ED
Hi, I have a Dell Inspiron N5110 with Windows 7 Home Premium 64bit pre-installed. When I try to startup, it gets past the Windows logo then goes to the BSOD, error 0x000000ED. I've tried booting in the Last Known Good Configuration, and Safe Mode. The 'Repair Your Computer' option doesn't do...
BSOD Help and Support
BSOD 0x000000ED STOP error.
I have a laptop and it has been working fine for the most of time. Just recently, after a restart, my laptop doesn't boot. I had to disable automatic restart to see the BSOD: a STOP error 0x000000ED Unmountable_Boot_Volume (specifically: 0xFFFFFA80080468C0, 0xFFFFFFFFX0000185, 0x0000000000000000,...
BSOD Help and Support
BSOD when booting computer, error 0x000000ed
Hi guys, I have been encountered a problem of my windows 7 (Windows 7 Ultimate x64). The problem is when I try to boot my windows 7, it fails and a blue screen appears, stating that the error message "Stop: 0xed". I try to repair windows, but it fails. So, I reinstall my windows 7. And it works...
BSOD Help and Support
BSOD startup loop, error 0X000000ED
I am getting an unmountable boot volume error for my Win 7 64 bit Acer Aspire 5750-6627. I have tried all the safe mode options, but those do not work. Windows cannot startup normally. And I cannot get to startup repair either. I tried using a Win 7 disc to get to the recovery options, which got me...
BSOD Help and Support
Error 0x000000ED blue screen
Hi guys I am using window 7 32 bit home premium and facing a problem about which I did some research and everywhere I found the same solution ie is using chkdsk from recovery using recovery discs This is my problem STOP 0x000000ED(0x877959C0,0xC0000185,0x00000000,0x00000000)...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 08:37.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App