Running RHEL6.4 on a Dell. Previously had 1 2TB drive running the OS and 1 2 TB drive being used as scratch space. Wanted to add 2 more HDs to the scratch space, upping it to 6TB. Realized that i didn't partition the initial scratch space properly so my plan was to add drives 3 and 4, partition and volume them correctly, move the data off of the improperly initialized drive onto the new scratch space (drives 3 and 4) and then initialize it and add it to the new pool space.

I've got drives 3 and 4 working properly and you can mount that drive and copy files to it and life is good. Now, when I tried to initialize the first scratch drive, the volume manager hung and crashed while initializing the space. Now it crashes every time with a "badalloc" error from the command line, even when I run it with --sync like it asks me to. I can't get to the 2nd drive space and am not sure how else I can get to it to make this work. When I restarted it, it didn't boot properly because of an entry still in fstab that wasn't removed. I was able to edit that file and get it to boot, but can't manage this last drive. any ideas?

Thank you.

Attached Thumbnails

 

When you tried to run the "pvs" command it told you that you were not root so you did a "sudo" to run it as root.

However, I don't see where you did that when you ran the system-config-lvm which suggests you tried to run it as a non-root user as well and that is probably the main issue.

Another issue is that it is trying to run in an X environment. Are you doing this from a console GUI such as Gnome or are you doing it from one of the character consoles or a separate session such as PuTTY? If not in a console GUI you may need to setup your X environment (e.g. DISPLAY and XAUTHORITY variables) after you switch users.

1) The Logical Volume Management app was running fine before these changes were made. I typically just ran it from the System -> Administration menu. When it started crashing, I ran it from the command line so I could actually get an error message (see attached where I ran it with sudo).

2) The screenshots are just being taken of a terminal window inside of my VNC client. I'm on a macbook remoting into the server in another room in my building. These same errors happen when i'm sitting at the computer or VNC'd in.

3) It was working as a non-root user before (it just prompts for the root password when it opens), so I can't believe that that's the problem. The window comes up like it's going to open and I get the "Reloading LVM. Please wait" bar and it acts like it's going to load fully and then simply closes with only the error message attached in the terminal window. It seems to me like it's a configuration problem where I screwed something up, but I'm just not sure how to tell what I screwed up nor how to fix it. I can run whatever other commands I need to run and post screenshots if that would be helpful.

Thanks.

Attached Thumbnails