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? > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >