Hello Friends
I was making a bootable usbpen drive for installing RHEL5.
I made a blunder by typing a command
dd if=diskboot.img of=/de/sda (I should have typed sdc1 instead of sda)

Now My production server is in mess now.
When I give
fdisk -l
It shows following

Disk /dev/sda:220.2 GB, 220219834368 bytes
255 heads,63 sectors/track,26773 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks ID System
/dev/sda1 ? 188019 188051 253319 e4 Speedstor
Partition 1 does not end on cylinder boundary
/dev/sda2 ? 62656 186401 993984023 98 Unknown
Partition 2 does not end on cylinder boundary
/dev/sda3 ? 105611 225119 959953209 7d Unknown
Partition 3 does not end on cylinder boundary
/dev/sda4 ? 331 849 4161536 0 Empty
Partition 4 does not end on cylinder boundary

Partition table entries are not in disk order
_________________________________________________________


Pl help how to retrive the situation.
I have a RAID in my server.
Pl email me the solution.
Pawan

Why anyone would use a production server for this??? Why one would be running as root for this is also very questionable.

Restore from backup, no backup then you learned a very valuable lesson.

No I will not email you any solution, post here read here.

You might be lucky, try booting from a LiveCD version of say Scientific Linux or CentOS 5 and maybe use parted/gparted to recover the partition table, but this just might be a waste of time depending on what type of RAID you are speaking of. Hardware or software RAID??? RAID0, 1, 4 or 5??

You will have to a least know the starting points for each partition used (at least the very first one).