Question I Hex edited my disk and now it's not working anymore ?

For anyone else reading this:

This right here is why you never, ever screw around with partitions, doubly why you don't dick around with registry entries, and triply why you do not dick with a Hex editor on the boot sector if you do not know exactly what you are doing, on a drive that contains the one and only copy of your critical data.

if you have time, try the tools in
http://www.hiren.info/pages/bootcd

As far as the hardware? Probably not. For the data that was on that drive? No idea, but if I were a betting man, I'd say yes, it is toast.

This is when you reinstall the OS etc, and bring your critical data up from the backup.

How to fix that drive, with the existing data? Maybe someone else has an idea. I don't.

I doubt that would do anything beneficial. The actual data/boot sector on the hard drive, modified by your hex editor changes, is what is screwed....not the drive circuit board.

Is there any absolutely cannot do without, critical data on this drive?
If not.....toss it and move on.
If there is, toss it and move on.

This is where a good backup factors in.

Five points before you do more:

1. I agree with USAFRet - you do NOT need to start replacing pieces of hardware. The problem entirely is in the data written on the HDD unit.

2. I am concerned that you say, "My hard disk is NOT recognized by the bios. I can't see it." The tale you tell should NOT prevent the BIOS for detecting the HDD. Are you sure it cannot be detected in BIOS?

3. There is no tool built into BIOS to allow you to edit HDD sectors. However, many such software tools exist on bootable CD's (maybe on hiren referenced by rgd1101?) If you are SURE you can restore data to all the places you made changes, you could try that. To use such tools you must have the CD in your optical drive, of course, and you must set your BIOS to boot ONLY from that optical drive, so it does not get stuck trying to access other storage units - specifically, the failed HDD it gets stuck on! Then it can boot from and run the OS on the bootable CD.

4. IF you can get your machine to a state where it can boot normally with the faulty HDD connected, but still not accessible, then you really need to do a data recovery operation. In almost all cases the tools used will make a COPY of all the data it can find from that "bad" drive" onto another spare HDD. So, to do this, you need that empty spare HDD to put the copied data onto. One such software tool is GetDataBack NTFS, but there are many others. You must pay for GetDataBack, but it has an interesting process. From their website you can run it on your failed HDD and it will do all its analysis, even to the point of showing you a "directory" of all the files it got (hopefully all of the drive's data) and allow you to open some of those files to verify that they are valid. IF you are satisfied that the tool is doing all you need, you THEN must pay for the software, and it is installed on your machine and finishes the recovery process by writing its recovered data to your spare HDD. ON the other hand, if you don't think the tool is doing things right, you do NOT pay, and it leaves your faulty HDD untouched - it has operated in read-only mode. The HDD is untouched and available for analysis by any other software. Whether you use this tool or another, in this manner you can retrieve (hopefully) all of the data on the HDD to another drive. THEN you can use diagnostic and repair tools, like the Seatools for DOS suite, to completely wipe that faulty unit clean with a Zero Fill, then Partition and Format it and start fresh.

5. You REALLY should read up on the MAJOR differences between RAID1 and true backups. In a RAID1 system, EVERY change you make is done to BOTH HDD units instantly. If you foul up one with odd operations, the other also is just as bad! I doubt very much that a RAID1 system would have prevented your current problem.

If you can't see the HDD in BIOS, then this would suggest that it has a physical problem, not a logical one. Editing sector 0 CANNOT create a physical problem.

What fzabkar said ^.

I know, my point #1 says you don't need to replace hardware. BUT fzabkar is right. If you confirm that BIOS cannot detect the hardware, then you DO have a hardware problem. And it is NOT caused by the sector editing you did.

Right. I think the hardware fail came first, then the Hex editing, which probably made things worse.

RAID 1,5, is really used for a drive failure so you can get the system up and running quickly if one drive fails and to prevent data loss if a drive physically fails, not data backup to restore if you accidentally formatted or deleted something.

The best DATA backup plan is to a second drive using a copy program. That COMBINED with a RAID setup (not RAID 0) will give you a proper and pretty safe backup strategy. I like to keep the OS and programs on a separate hard drive from my files (movies, email folders, etc...), image the OS drive, and run backups of the data drive. You can image the data drive, but that takes longer and it's easier to just run a copy overnight to get the file differences.

What I do when I setup system is to create an image of the drive after setting everything up, updates, drivers, programs to make restoring it easy. Then do a restore of the data. If re-building a system I almost never re-use the drive, the old drive gets yanked and put aside as another backup drive, a new drive gets put in, image is dumped on it, and files restored from the backup.

I have about 4 drives with my files on it now from doing drive upgrades, and I can restore any of my computers including games, MS Office, etc... in a few hours from the images, then can simply plug in a backup drive and copy the files over. If one of my backup drives goes bad, at most I would lose a few weeks of stuff and can go back to an older drive. I try to keep my backups on two different hard-drives in addition to the main data drive, for 3 copies of most of my files.

Don't bother with different partitions. I am guessing your programs and OS will be on the SSD, and data will live on the regular drives.

Get an external drive and use something like clonezilla to image the SSD onto it after it's setup. Put that away.

Use one HDD for data and the second for a backup (MS Backup in the operating system works just fine, or you can just copy the full directory with your files manually). Keep in mind partitions in a drive will do NOTHING for you if the drive goes bad, it's just there to logically separate things to make it easier to work with, not to hold backups of the other partition. If a drive goes bad, all the partitions on it will be gone.

As an IT student you have learned so far the power and danger of Hex editors, and something about data recovery tools and processes. Now you're starting to learn the major differences between various RAID systems and a true backup system. You definitely need to learn more in this area so you can decide how best to set up your own. You're making progress, whilst experiencing the pain of mis-steps.

Some simple principles for backups:

The backup should always be made to a physically different HDD unit.

Ideally, that HDD unit should be connected to the system being backed up only when the backup copy is being made. Thereafter it should be disconnected from the computer AND from a power source to keep it safe electrically.

Ideally, the HDD containing the backup should be stored at a physically separate safe site.

At one large business where worked, their IT staff had backups made automatically during the nights and stored in TWO places - on tapes stored at the site, with the second backup sent electronically to a service in a different part of the country. They needed them when TWO of the HDD's in their RAID5 system failed almost simultaneously, so the RAID system could not repair itself.

Hi everyone, I know it's been 10 years since this topic was last discussed, however history tends to repeat itself.
I also messed around with a Seagate 1500GB hdd. More specifically I messed with the hex values of its partition, in basically the same way. "edited line 1c0 changing 42 to 07" . I did this because I was accessing the drive via a linux OS, and without my knowledge windows had turned the drive into a RAID one(alongside a 1TB WD drive).
Now something went wrong during the edit and now the drive has become completely unusable. it needs to be connected either via USB, or if using a SATA interface then AHCI. No recovery software can do anything with it though. Can't initialize it in windows, and everywhere it says 0KB, even the hex editor only shows 1 line with 0 value.

I don't care that much about the data inside(it would be cool to recover them though). What I care is just to get the HDD back to be able to use it as a storage device. the bios correctly recognizes it as a 1500GB drive.

Any advice?

dragonilly said:

Hi everyone, I know it's been 10 years since this topic was last discussed, however history tends to repeat itself.
I also messed around with a Seagate 1500GB hdd. More specifically I messed with the hex values of its partition, in basically the same way. "edited line 1c0 changing 42 to 07" . I did this because I was accessing the drive via a linux OS, and without my knowledge windows had turned the drive into a RAID one(alongside a 1TB WD drive).
Now something went wrong during the edit and now the drive has become completely unusable. it needs to be connected either via USB, or if using a SATA interface then AHCI. No recovery software can do anything with it though. Can't initialize it in windows, and everywhere it says 0KB, even the hex editor only shows 1 line with 0 value.

I don't care that much about the data inside(it would be cool to recover them though). What I care is just to get the HDD back to be able to use it as a storage device. the bios correctly recognizes it as a 1500GB drive.

Any advice?

Click to expand...

Please start a NEW thread for your particular situation.
This one is over a decade old.