On Tue, Mar 26, 2013 at 1:35 AM, Joakim Ziegler <joakim at terminalmx.com> wrote: > Yes, I ran that immediately after getting dropped to the shell. I can > take a look at the device nodes tomorrow, but if I remember correctly, > /dev/mapper contained only the file "control" before running vgchange > -ay, that is, there was no "vg_resolve02-lv_root" device there. That > device only shows up after I run vgchange -ay. > > I did not check whether /dev/vg_resolve02 exists, I can do that tomorrow. > > -- > Joakim Ziegler - Supervisor de postproducción - Terminal > joakim at terminalmx.com - 044 55 2971 8514 - 5264 0864 > > On 25/03/13 23:26, Gordon Messmer wrote: >> On 03/25/2013 06:35 PM, Joakim Ziegler wrote: >>> That's the output of, like you suggested: >> >> And you ran that before you ran "vgchange -a y"? That doesn't make any >> sense. The commands show the volume group active. I can't see any >> reason why the system wouldn't boot. >> >> I hate for you to keep rebooting your server, but do the device nodes >> look correct in both /dev/mapper and /dev/vg_resolve02 at that point? Apologies if someone mentioned this already ( don't have the whole thread in my mailbox), but whenever I've had to re-name a root lvm volume, I also had to recreate initrd. I haven't done it on 6.X, but I assume it applies to initramfs as well. The notes in my corp wiki link back to this redhat bugzilla post, https://bugzilla.redhat.com/show_bug.cgi?id=230190 try that maybe? Patrick