Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Completely clean hard drive?


  • Please log in to reply
9 replies to this topic

#1 noz03

noz03

  • Members
  • 155 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 01 February 2013 - 06:20 AM

I have a hard disk with about 9 partitions or something on it (dont know why....) and the computer also had a lot of problems with the hard drive so I want to completely clean it and bring all these partitions together then defrag it and check for any errors. What is the best way to do this? Can I just use the windows install CD's partition management and delete them one by one to make a new one? Or might this still miss some stuff that should be cleaned?

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:09 PM

Posted 01 February 2013 - 08:38 AM

Go Start/Run...type diskmgmt.msc and hit Enter.

Press Print Screen key.

Post the edited photo and be sure that it fully reflects all partitions (lower part of the screen).

How To Capture And Edit A Screen Shot - http://www.bleepingcomputer.com/forums/topic43088.html/page__gopid__2493350

System manufacturer and model? Who created all these partitions?

Louis

Edited by hamluis, 01 February 2013 - 08:39 AM.


#3 noz03

noz03
  • Topic Starter

  • Members
  • 155 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 01 February 2013 - 09:54 AM

Well my computer never came with any OS so there isn't any setup partitions that I know of but anyway here is the screenshot.
Attached File  hd screen.jpg   118.92KB   9 downloads


I created c d and e and have already backed up all the files i want from them, the other system reserved and one without a name i have no idea who made...

So yeah, I wanna make it all just 100% unallocated or whatever and then make 2 new partitions C and D only. Might also be good to run some checks or special formatting during that time as well but I really have no idea about this stuff to be honest :/

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:09 PM

Posted 01 February 2013 - 12:52 PM

The 300MB partition...appears to be something I would expect to see in an OEM (HP, Dell, etc.) system.

The unallocated space is just space on the hard drive that is not being occupied used by any partition existing.

IMO, this drive looks like someone attempted to install Windows by cloning it to the drive, resulting in the odd array that exists.

The 2GB partition appears to be something I would find in an OEM system.

Not sure what "Unavailable" means to you...but I would interpret that as an indicator that something may be wrong with the hard drive.

If you do not have Microsoft Genuine Windows disks to use for reinstalling Windows...I'd think twice about deleting anything.

Louis

#5 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:09 PM

Posted 01 February 2013 - 01:00 PM

I agree with Louis.

If you want to check the physical health of the drive, try this...

Get a copy of GSmartControl for Windows
http://prdownload.berlios.de/gsmartcontrol/gsmartcontrol-0.8.7-win32.zip?download
Unzip it and run gsmartcontrol.exe

Double-click your drive and click the VIEW OUTPUT button and copy and paste the resulting report in your reply so we can look at it.

This way we can make sure that the drive itself is healthy. Then if you do have a Windows install disk as Louis mentioned, you can try removing all of the partitions during the install process like you mentioned :)

If it does not work at that point we can use a Linux LiveCD to clear the drive's partitions and prepare it for the install.

James

#6 noz03

noz03
  • Topic Starter

  • Members
  • 155 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 02 February 2013 - 08:43 PM

Ok here it is, seems there was some kind of fail on it but I really have no idea what I am looking at.

I have the windows cd but actually planning to install a windows 8 trial for now to see if a different os might also help with the problem. Btw the problem, which several computers shops and many forum posts could never exactly work out was that the OS keeps suddenly not working, a fresh install fixes it up fine, then a week, a month, sometimes a few months later.... bam, cant boot the OS again.... the only suggestion people keep giving me is that it is HD related but no one is sure of anything. Maybe a certain part of the disk that when it gets accessed makes the OS go crazy? Or I have no idea.

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 5400.6
Device Model:     ST9320325AS
Serial Number:    6VE4W1G7
LU WWN Device Id: 5 000c50 01ef4d74e
Firmware Version: 0002SDM1
User Capacity:    320,072,933,376 bytes [320 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:    Sat Feb 02 17:18:54 2013 PST
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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 109) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103b)	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   097   076   006    Pre-fail  Always       -       79836545
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1907
  5 Reallocated_Sector_Ct   0x0033   071   071   036    Pre-fail  Always       -       613
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       47246727
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       -       2757
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   037   020    Old_age   Always       -       1835
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       65535
188 Command_Timeout         0x0032   100   097   000    Old_age   Always       -       38655295530
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   070   045   045    Old_age   Always   In_the_past 30 (Min/Max 21/30)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       511
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       74
193 Load_Cycle_Count        0x0032   075   075   000    Old_age   Always       -       51395
194 Temperature_Celsius     0x0022   030   055   000    Old_age   Always       -       30 (0 9 0 0 0)
195 Hardware_ECC_Recovered  0x001a   063   058   000    Old_age   Always       -       79836545
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       10
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       10
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 44993 (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 44993 occurred at disk power-on lifetime: 2755 hours (114 days + 19 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 d9 c0 03 00  Error: WP at LBA = 0x0003c0d9 = 245977

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 30 62 63 40 00      02:05:21.667  WRITE FPDMA QUEUED
  61 00 08 58 1c 5f 40 00      02:05:21.667  WRITE FPDMA QUEUED
  61 00 08 10 62 63 40 00      02:05:21.666  WRITE FPDMA QUEUED
  60 00 08 28 3e b0 40 00      02:05:21.665  READ FPDMA QUEUED
  61 00 28 28 a3 5f 40 00      02:05:21.665  WRITE FPDMA QUEUED

Error 44992 occurred at disk power-on lifetime: 2755 hours (114 days + 19 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 d9 c0 03 00  Error: WP at LBA = 0x0003c0d9 = 245977

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 e0 61 63 40 00      02:05:19.070  WRITE FPDMA QUEUED
  61 00 08 60 1c 5f 40 00      02:05:19.070  WRITE FPDMA QUEUED
  61 00 18 a0 61 63 40 00      02:05:19.069  WRITE FPDMA QUEUED
  60 00 00 c8 c0 03 40 00      02:05:19.069  READ FPDMA QUEUED
  60 00 08 d8 12 01 40 00      02:05:19.068  READ FPDMA QUEUED

Error 44991 occurred at disk power-on lifetime: 2755 hours (114 days + 19 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 d9 c0 03 00  Error: WP at LBA = 0x0003c0d9 = 245977

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 78 61 63 40 00      02:05:16.489  WRITE FPDMA QUEUED
  61 00 08 58 1c 5f 40 00      02:05:16.489  WRITE FPDMA QUEUED
  61 00 08 60 61 63 40 00      02:05:16.488  WRITE FPDMA QUEUED
  61 00 08 0f a6 80 41 00      02:05:16.487  WRITE FPDMA QUEUED
  61 00 10 48 61 63 40 00      02:05:16.487  WRITE FPDMA QUEUED

Error 44990 occurred at disk power-on lifetime: 2755 hours (114 days + 19 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 d9 c0 03 00  Error: WP at LBA = 0x0003c0d9 = 245977

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 30 98 60 63 40 00      02:05:13.907  WRITE FPDMA QUEUED
  60 00 80 68 29 bd 40 00      02:05:13.907  READ FPDMA QUEUED
  61 00 08 58 1c 5f 40 00      02:05:13.906  WRITE FPDMA QUEUED
  60 00 08 a0 86 b2 40 00      02:05:13.906  READ FPDMA QUEUED
  60 00 08 78 1f b0 40 00      02:05:13.905  READ FPDMA QUEUED

Error 44989 occurred at disk power-on lifetime: 2755 hours (114 days + 19 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 d9 c0 03 00  Error: WP at LBA = 0x0003c0d9 = 245977

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 78 60 63 40 00      02:05:11.213  WRITE FPDMA QUEUED
  61 00 08 60 1c 5f 40 00      02:05:11.212  WRITE FPDMA QUEUED
  61 00 08 68 60 63 40 00      02:05:11.212  WRITE FPDMA QUEUED
  61 00 08 f0 a2 5f 40 00      02:05:11.211  WRITE FPDMA QUEUED
  60 00 08 78 1f b0 40 00      02:05:11.210  READ FPDMA QUEUED

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%      2757         245977
# 2  Short offline       Completed: read failure       90%      2501         13358318

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.


#7 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:09 PM

Posted 02 February 2013 - 09:59 PM

Hi

Unfortunately, the drive is bad. It needs to be replaced.

It has some permanent damage from past experiences (which may have been overheating).

The reallocated sectors is really high and soon it will run out of reserve sectors...
5 Reallocated_Sector_Ct   0x0033   071   071   036    Pre-fail  Always       -       613

and it appears to be growing more bad sectors...
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       10

Some of the other attributes also show evidence that there were serious problems with the drive in the past.

1   Raw_Read_Error_Rate     0x000f   097   076   006    Pre-fail  Always       -       79836545
7   Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       47246727
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       65535
188 Command_Timeout         0x0032   100   097   000    Old_age   Always       -       38655295530
195 Hardware_ECC_Recovered  0x001a   063   058   000    Old_age   Always       -       79836545


I wish I had better news but at least now you know that this drive was probably the cause of your problems.

Did you ever suspect it of overheating in the past?

James

#8 noz03

noz03
  • Topic Starter

  • Members
  • 155 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 03 February 2013 - 09:01 AM

Yes this is very bad news, especially as it had these problems since the day I bought it and I have wasted countless hours trying to fix it :( I don't think overheating could be the problem though as its just a netbook and is usually cold even after an hour or hard use.

Anyway I actually just bought a new laptop and just want to fix the old one for travelling and so on. Is there any cheap fix for this problem? Like can I isolate the bad sectors in the unallocated space so they wont cause the OS to mess up again? I obviously wont be using it for any important data ever again (like I was before), thanks for checking the log for me. You are right, its so good to finally know what the problem was.

#9 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:09 PM

Posted 03 February 2013 - 11:10 AM

Hi

It is the kind of problem that you can't avoid because the bad sectors are spreading. What will often happen in cases like this is that you can install and run things without a problem but then all of sudden the files that were fine before start having bad sectors and things begin to crash.

The error log has 44993 errors in it so there have been lots of problems that you probably did not even notice.

James

#10 noz03

noz03
  • Topic Starter

  • Members
  • 155 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 03 February 2013 - 12:11 PM

Hi

It is the kind of problem that you can't avoid because the bad sectors are spreading. What will often happen in cases like this is that you can install and run things without a problem but then all of sudden the files that were fine before start having bad sectors and things begin to crash.

The error log has 44993 errors in it so there have been lots of problems that you probably did not even notice.

James


oh :( That kind of explains my problems exactly. Well right now I cant afford to replace the hard drive, also when I barely use it it usually lasts a few months so I will just have to reinstall the OS each time it messes up :) Is there anything I can do to help it to last as long as possible, apart from just not using it so often? Maybe I could make the OS files read only or something? Or maybe put the OS on a very small partition in the middle of the drive or something? Just throwing random ideas out there to be honest :)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users