-
August 13th, 2010, 11:55 PM
#1
Repairing MBR on HD with bad clusters.
Okay, the un-thinkable happened to me. Probably a simple endeavor for most of you, but for me I never encountered this problem so theres a jackass first for everything right ? .. heh.. I was installing Open SuSE live on my box, which i planned to dually partition with XP home. The monitor that I have, flickers quite a bit, it's an old piece of trash. So that led me to unplugging it more than once and plugging it back in (the monitor).. The result was nil. So i physically shut off the box during the install, **YES I KNOW**, dumb....... So i'm guessing that I caused some cross linkage problems with the hdd, and messed up the MBR altogether, and when i fire up the machine now, I get "No active OS Partition !, insert cd or reboot" .. [I really hope you guys don't break out the flame throwers on this thread ]
Things i've tried thus far:
1.) Seeing as I have a Vista recovery disk only, and not an XP disk, I fired up the Vista disk and skipped the install, went to recovery mode and got the command prompt open. I first tried fixboot, and fixmbr, which were to no avail, I thought they were available on vista too but i guess i was wrong. I tried scandisk, which didn't work either.. So finally, I ran chkdsk /f /r and let that run. It had alot of listings of bad sectors on which it claimed it repaired when that finished.
2.) I had a system suite recovery disk which came with my laptop (vista), but it stated dually compatible with XP, vista, 7. So I went to the partition table, and on my hdd (79.6 GB), it states that 7.9 GB have bad sectors. "Wow". Even after running chkdsk and repairing all the bad sectors, I still have 7.9 GB of nil sectors ? I tried toggling the NTFS partition as "active" on the MBR, but it will *NOT* allow me to because of the bad sectors.. Now I have no problem stating myself as a Newbie on here. This problem I thought i could fix easily, but i'm leaving my ego at the door on this one. It took me a lot of hours of playing around before deciding to write this thread.. Help AO
"Serenity is not the absence of conflict, but the ability to cope with it."
-
August 14th, 2010, 04:40 AM
#2
You need to get a Windows XP disk then run a FIXMBR and FIXBOOT.....I fear you may have made it worse with the Vista disk......especially if it's an OEM version which it sounds like it is......
and the 7.9 gigs of bad sectors must be related to the XP\Vista File System\Architecture incompatibility.......ZOIKS!
and.......the Vista Home disk repair could be formatting for FAT......EEK....I don't even wanna think about it! Good luck my friend, hope you can get her back up!
Last edited by Wazz; August 14th, 2010 at 04:45 AM.
"It is a shame that stupidity is not painful" - Anton LaVey
-
August 14th, 2010, 12:18 PM
#3
I am going out so I shall be quick.
1. I don't think that turning off the machine did any harm..........hell! I have turned off windows machines at the power supply hundreds of times with no ill effects. All you usually get is the "windows did not shut down properly" message and the bootup mode options screen. All I would expect is that Linux would not work because it hadn't loaded completely.
2. Are your Vista recovery disk and your system suite recovery disk the same thing?
I will post later about the screen issue.
Right now I do not hold out much hope as I think your HDD has been marked as having bad sectors.
There is software that will probably fix that, but it costs as much as 3 or 4 HDDs and you have to buy it up front.
Cheers for now
Last edited by nihil; August 14th, 2010 at 12:23 PM.
-
August 14th, 2010, 01:27 PM
#4
Hiya'h Bud..
http://www.ambience.sk/fdisk-master-...ilo-fixmbr.php
you ow me a cold Beer.
you want to grab this util
-
August 14th, 2010, 11:42 PM
#5
HYBR|D: Listen man, i'll buy you a cold beer anyway, cause this is such a handy app. But I got some crappy news. I don't have a floppy drive on my laptop, so I threw the utility on a disk, and ran it as such: <quote> fixmbr.exe /drive 0 listpartitions:
1.)NTFS
2.)Win95 # Hmmmm. Possible conversion from the vista rescue disk ?
</quote>
So then I proceeded. <quote>E:\fixmbr.exe /drive 0 fixmbr</quote>
Rebooted the machine and got <quote>Reboot and select proper boot device or insert boot media in selected boot device</quote>
I then, go back into the recovery suite utility, into the manual partitioner, and it sais that there are still 7.9 gb of bad sectors, and that the primary partition is damaged. Yank the HDD or what folks ? <quote>Nihil: 2. Are your Vista recovery disk and your system suite recovery disk the same thing?</quote> Negative, they're different. As far as the monitor, garbage day is monday .. Any hope guys ?
-
August 14th, 2010, 11:47 PM
#6
HYBR|D: Listen man, i'll buy you a cold beer anyway, cause this is such a handy app. But I got some crappy news. I don't have a floppy drive on my laptop, so I threw the utility on a disk, and ran it as such: e:\fixmbr.exe /drive 0 listpartitions:
1.)NTFS
2.)Win95 # Hmmmm. Possible conversion from the vista rescue disk ?
So then I proceeded. E:\fixmbr.exe /drive 0 fixmbr
Rebooted the machine and got
"Reboot and select proper boot device or insert boot media in selected boot device"
I then, go back into the recovery suite utility, into the manual partitioner, and it sais that there are still 7.9 gb of bad sectors, and that the primary partition is damaged. Yank the HDD or what folks ?
Nihil: 2. Are your Vista recovery disk and your system suite recovery disk the same thing?
Negative, they're different. As far as the monitor, garbage day is monday .. Any hope guys
"Serenity is not the absence of conflict, but the ability to cope with it."
-
August 14th, 2010, 11:56 PM
#7
-
August 15th, 2010, 12:32 AM
#8
-
August 15th, 2010, 01:31 AM
#9
Updates off topic a bit
Hi, I promised a bit more info so here goes:
1. chkdsk
This utility will fix file system errors but can be very dangerous, as it will tag any sector it cannot understand as "bad". This is a problem as it does not apply to Windows systems only.
Please be aware that it does not repair bad sectors, it just marks them as such. This can cause big problems.
2. Flickering Screen
As a general principle you should not run a system with known failing hardware.
The probable causes are:
1. Refresh rate set too low.......60 MHz for example.....72,75,85 are what you should be looking for with a CRT. If you have an LCD then 60 is just fine....they don't flicker they just crap out
2. You are running in safe mode or installing an OS.............they default to the lowest "safe" settings..... which would be 60 MHz.
3. Defective VGA cable or ports (screenside or MoBo) Try a different cable. If it is the ports then you need to replace the equipment, if you do not have an alternative connection.
4. The screen is dying. You should replace it immediately, as it can cause untold damage to your system.
5. Heat. With the screen unplugged from the power run a vacuum cleaner over its ventilation slots.
DO NOT REMOVE THE CASING UNLESS YOU ARE A QUALIFIED TV ENGINEER
Three months after you last used it, there are capacitors in there that will kill you
-
August 15th, 2010, 12:04 AM
#10
Hmm.. I have never thought of trying it either lol, but you & I will be the creators of this new found glory eh ? lol.. Atleast it will ease my troubleshooting pain in the mean time.. Yes, I am USA, east coast, new england . (Ripping hair out, due to system) .. Hehe, can't help it folks.
"Serenity is not the absence of conflict, but the ability to cope with it."
Similar Threads
-
By brokencrow in forum Tips and Tricks
Replies: 17
Last Post: January 24th, 2007, 10:41 PM
-
By brokencrow in forum Security News
Replies: 31
Last Post: April 14th, 2006, 03:37 PM
-
By slinky2004 in forum Hardware
Replies: 2
Last Post: January 22nd, 2006, 05:00 PM
-
By Capt Whatever in forum General Computer Discussions
Replies: 2
Last Post: November 22nd, 2004, 02:16 AM
-
By smirc in forum AntiOnline's General Chit Chat
Replies: 2
Last Post: February 25th, 2002, 01:07 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|