parted. grrr. I'm in dire need of help.
 

Long story short, I have a 4TB array under FC6 that I configured using parted (one gpt partition) and lvm. I started moving data onto the array, and the server hung
after having MOVED (not copied) about 3TB of data onto the array. I rebooted to
find I can no longer mount, or even print the partition!

[root@hondaserver1 backup]# parted /dev/sdb print
Error: Unable to open /dev/sdb - unrecognised disk label.
Information: Don't forget to update /etc/fstab, if necessary

I dont know what to do. Could someone please see if they could guide me through
at least getting access to the partition, therefore the data again so I can move
everything back off the array?

Thank you.

Is /dev/sdb the device holding the logical volume you created?

What, if anything, does pvscan tell you? Is the lv active?

Is the lv listed in /dev/mapper?

Have you added the device to /etc/fstab? If so, is the line correct? If not, can you mount the /dev/mapper/ entry for the logical volume?

Have you used the lvm tools to investigate your logical volumes?

Were you aware that a logical volume uses a different partition number from standard linux file systems, and that running fschk on the actual physical device (/dev/sdb in your case) would destroy the logical volume and any data stored on it. (Running fschk on /dev/mapper/<lvname>/ should work.) (I mention this only because I burned myself on this issue.)

Thank you for the reply.

I was getting anxious last night and decided to roll the dice. It just wasnt sitting well with me doing nothing while hoping someone could help bail me out of my self-inflicted mess. This is what I did:

parted would crash and give the "Youve found a a bug!" error message if I tried to do mklabel. I checked parted's website and noticed a newer version of of the softare (1.8.2, FC6 has 1.8.1-something) I went ahead and installed the FC7 rpms which were the ones that had the latest version of parted.

Now, parted worked without crashing. I did mklabel, created a new gpt partition, then did rescue. It immediatley found the missing partition, and I was able to mount it then. I have since moved the data back off that array, intact, so I am safe!

Dodged a bullet that time, however it still bothers me why it happened in the first place.