MBR Woes - Error 255/Error 8255 Error writing master boot record

[pressafrica]

Hi
I am receiveing the following error message and am at a loss to repair it: Error 255/Error 8255 Error writing master boot record

I was installing Redhat Linux 8.0 when it came up with an error during the install. It then shutdown and rebooted the machine. It is unable to reinstall as it can not access the MBR again. When you reboot and use FDISK/MBR it says : "Error writing fixed disk. The master boot code has NOT been updated"

When I run fdisk without the /MBR Switch I can see three partitions as listed:
partition: 1 status: a type: Non-DOS Volume label: (blank) Mbytes: 103 System: (blank) Usage: 1%
partition: 2 status: (blank) type: Non-DOS Volume label: (blank) Mbytes: 18206 System: (blank) Usage: 95%
partition: 1 status: (blank) type: Non-DOS Volume label: (blank) Mbytes: 768 System: (blank) Usage: 4%

I can not delete any of these partitions using fdisk. When I use the Partition Magic rescue disks I can see the following three Partitions:
*./boot Linux Ext3 103.3MB Used 12.1MB Unused 91.2MB Active Primary
*./ Linux Ext3 18206MB Used 708.3MB Unused 17496.8MB None Primary
*./ SWAPSPACE2 Linux Swap 767.8MB Used 0.0MB Unused 767.8MB None Primary

Again when I try resize, delete etc when I press the apply button I get the following error: Error#58 Unable to write to the boot sector. Virus protection software may be running. I do not have any virus protection software running nor is there a virus protection option in the BIOS.

When I run the check partition for errors I get the following report
Error #993 Partition contains open files. Use the operating system check utility.

It does not enable the fix button and obviously I am unable to run the operating system check utility.

I am unable to give you the part info other than the drive is an IBM20GB thinkpad drive.

I have tried using programs such as bootcontrol to try and write a new MBR - no go. I have tried reprogramming the MBR using debug and a set of assembler commands.

I have tried using windows 2000 server in recovery mode from the CD with the FIXBOOT and FIXMBR command, no joy!

I have tried disksave from a MS-DOS 6.22 disk and diskprobe -still no luck

I have tried everything I can think of to rectify this error. I am now desperate as I live on a little island in the caribbean and have no access to anything other than internet.

Many thanks,

Mike

 

[wolluf]

binary zero fill utility? IBM did have one called wipe (I say did have, because I have a copy but couldn't find it on IBM's site last time I looked - nor a replacement for it), but its only for drives up to 8GB.

You could try another manufacturer's utility, but most only work on their own drives (ironically, wipe works on any drive type).

There's a utility called wipeout on this page

http://www.lurkhere.com/~nicefiles/index.html

- recommended by jmatt in another thread, which might be worth trying.

 

[pressafrica]

Thanks, I have tried wipeout but it is unable to read the boot sector for Drive C:

I have already tried wipe from IBM which now seems to belong to Hitachi same results.

I have even tried using debug and programming in assembler to wipe the sector. It tells me the program executes successfully but still have these same three partitions.

I have run the powerquest and seaget disk tools which show me the drive is working correctly but neither of them can wipe or access the MBR.

Still at a complete loss, trying to figure out what the f@%! happened and how to fix it.

Thanks

Mike

 

[wolluf]

As the problem seems to be writing to the MBR, this probably won't help either. But,

http://www.boot-us.com

has a dos utility which will read and write track0. You could try producing a binary zero filled file & see if boot-us can write it to your disk.

 

[evildoughboi]

if all fails, send the drive back if its under warranty, if you dont mind it being shipped off for about 2 weeks. most likely they would just send you a new one and sell it as refurb. it happened to me a few times.

another option would be getting another hard drive, setting up the bad 1 as slave and use partition magic on it, then wipe it clean. hopefully u have another drive. good luck!

 

[KimLeece]

You say that you have tried debug and reprogramming but it didn't work? I used debug with the instructions from:-

http://www.winntmag.com/Articles/Index.cfm?ArticleID=5327&pg=1

It was the same problem as you had - also caused by a Redhat install - and luckily it worked fine. If the code here is different to what you tried then you might be lucky!

Kim Leece.