Thanks guys! I need to save these instructions, really helpful!

First of all, here's the output pvscan:
PV /dev/sda2 VG VolGroup00 lvm2 [232.69 GB / 32.00 MB free]
Total: 1 [232.69 GB] / in use: 1 [232.69 GB] / in no VG: 0 [0 ]

For me this appears LVM does not see the big SATA in any way.

Secondly, to follow the instruction of using pvcreate, I need to find out the uuid of that big SATA at the time it was in LVM or right now?

And thirdly, I need to check the BIOS options for SATA disks. At least this one is easy for me!

Thanks, at least there is a little hope now!

It saw the first time right? You mentioned that you moved that data to big SATA disk and that is what you are trying to recover. I am not sure what you mean by this?

I think this is the UUID for your big SATA disk:

And thirdly, I need to check the BIOS options for SATA disks. At least this one is easy for me!

You are on your own here

I thought pvscan would mention the SATA disk, if it sees it. But of course, since it has been removed, why should the command mention it. It is just that I am not too familiar with these commands.

Ok, can I see the current uuid with some command?

I checked the BIOS and there two settings I am not sure...
"Extended IDE drive [Auto]"
"Access Mode [Auto]"

These are current settings. The other option is "Disabled".

The UUID (which is the same as I posted in my instructions) comes from the archived VolGroup00 metadata that you posted (Thank you for that, BTW.) back in #10.

The partition does not currently have a UUID, since the PV header was wiped by pvremove. That is why you have to identify the device (very carefully) by its /dev/xxxx name. The UUID is just to tell pvcreate which entry to use from that metadata.

The BIOS settings in question would be for SATA ports. If those are on an add-on card rather than on the motherboard, then you would have to find out how to access the settings for that card.

Thanks! Splendid information! I was glad to find this after a relaxing stay in my sauna...

I suppose I have to arrange everything so that the device name would be the same as in that LVM config file in question?

How about when and if this pvcreate command succeeds, what is the next step to get the disk visible?

I went through all BIOS menus, but I didn't find anything else related to SATA interfaces.

It doesn't matter, but you do have to use the current device in place of that red "{X}" in my instructions (along with the correct path to the archive file, of course). Whatever device you specify is going to get a PV header written to it, so be sure it's right. You will get a warning that the device does not currently have a PV header. Of course not -- you wiped it. Enter the requested uppercase "YES" at that prompt.
The next step would be the vgcfgrestore command that I gave:The correct path to the archive file is the only thing you need to supply there.

1 members found this post helpful.

Superb!
Then I can try those commands right away!

Just to add, after running vgcfgrestore the lv will be in inactive state, you should run:

Once done check the output of lvs and mount the lv.

This is based on the testing I did yesterday.

1 members found this post helpful.

I am thrilled! Thanks guys!
Everything has worked so far!!

lvs shows now:
LV VG Attr LSize Origin Snap Move Log Copy% Convert
LogVol00 VolGroup00 -wi-ao 229.69G
LogVol01 VolGroup00 -wi-ao 2.97G
LogVol02 VolGroup00 -wi-a- 1.82T

Currently, the size of the volume is 82.3GB and nothing is visible. How to mount the LV?

Create new directory (just to make sure that you don't mount it on a directory containing stuff).

1 members found this post helpful.

Due to my OS version, I need to supply also the file system type. Is it LVM specific in this case or ext3 as I remember having it?

If at the time of creating lv you have used ext3 then that is what you have to use. Command will look something like:

Ok, now I again bumped against that same old issue of not being able to mount that disk:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol02,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

dmesg says:
VFS: Can't find ext3 filesystem on dev dm-2.

As if the disk has anyway been written over in some phase...

Interestingly, pvscan already knows this:
PV /dev/sda2 VG VolGroup00 lvm2 [232.69 GB / 0 free]
PV /dev/sdb1 VG VolGroup00 lvm2 [1.82 TB / 0 free]
Total: 2 [2.05 TB] / in use: 2 [2.05 TB] / in no VG: 0 [0 ]

The old directory I used for this disk shows the initial volume size 82.3GB. Somehow I feel I am so close...

Check the filesystem on the lv using: