Emergency UNIX and Linux Support

There must to more to what you did besides do a normal power off, install a single disk, and reboot; then shutdown, remove the new disk, and reboot.

Files don't corrupt themselves.

Something is missing from your story.

Believe or not this is the whole story , no more nor less
1- Power off the server
2- add a new disk to increase the space ( the disk already formated with windows NTFS )
3- power on the server
4- the server won't boot and the

Code:

Bad BPR sig

appeared at the bottom of screen
5- powered off the server ( unplugged power cable )
6- unplug the new the disk
7- Power on the server with solaris boot hd only
8- the server won't boot anymore
9- finally I'm stuck with the courrpted solaris disk

after all and a final word is my data still recoverable or should i let it go and give up

Hmm, you should face the reality. You scenario doesn't make sense. This isn't a corrupted Solaris disk. This is a disk with no Grub but a Windows bootloader. A disk corruption doesn't replace a partition table by another still correct one. You should find out who else messed with your disk or swapped it with another one.

What might have happened is your mbr was already broken when you last shutdown your OS. When did you last successfully reboot that box ?

PS: I'll came back later with a command to find out is a ZFS signature exists on your disk.

few minutes before adding the new disk
okay i'm waiting for the command

Normally I would agree but I have seen Solaris x86 do some really weird stuff when unexpectedly encountering a new disk if you did not touch the /reconfigure file prior to installing the new disk.

For those you are not familiar with the /reconfigure file, it causes Solaris to check for the presence of any newly installed devices the next time the system is booted.

Like installing a Windows boot loader ?

---------- Post updated at 23:31 ---------- Previous update was at 17:35 ----------

Try this:

Code:

dd if=/dev/rdsk/c0d0p0 bs=1024k skip=30 count=512 | od -X | grep 00bab10c | head

Was this disk previously used by Windows before you installed Solaris 10 on it ?
Are you sure there was no other storage device connected to your machine (a third disk, USB key, whatever ?)

Questions:

Is the disk you added for more space the same kind of disk as the one Solaris is installed on?

If so is it possible you got the two disks mixed up?

Did you use ESD protection?

If you have another disk with the same geometry, boot off of a linux CD, and run:

Code:

dd if=/dev/sdx of=/dev/sdy bs=512k

Replace x with the letter of the bad disk and y with the known good and try to boot off of them. This will work only if the disks have the same geometry. To be sure of the device files from the linux environment, boot with the known good disk first, put a file system on it, and create a file. Reboot, put the bad disk in, mount the filesystem you just created so you can be certain of the device files. Unmount it, then do the dd. This will produce a known good disk to work with that will have all of your data on it. At least you will have two copies in case you make a mistake in your recovery.