On 01/04/13 16:53, Joakim Ziegler wrote:
On 30/03/13 7:18, Joakim Ziegler wrote:
On 29/03/13 10:38, Gordon Messmer wrote:
On 03/29/2013 01:23 AM, Joakim Ziegler wrote:
Immediately after getting dropped to rdshell, I looked around in /dev,
which brought me a few surprises...
/dev/mapper
On 30/03/13 7:18, Joakim Ziegler wrote:
On 29/03/13 10:38, Gordon Messmer wrote:
On 03/29/2013 01:23 AM, Joakim Ziegler wrote:
Immediately after getting dropped to rdshell, I looked around in /dev,
which brought me a few surprises...
/dev/mapper contains only control, that is,
On 29/03/13 10:38, Gordon Messmer wrote:
On 03/29/2013 01:23 AM, Joakim Ziegler wrote:
Immediately after getting dropped to rdshell, I looked around in /dev,
which brought me a few surprises...
/dev/mapper contains only control, that is, vg_resolve02-lv_root is
missing.
Did you get to look
Recreating initrd made no difference.
Immediately after getting dropped to rdshell, I looked around in /dev,
which brought me a few surprises...
/dev/mapper contains only control, that is, vg_resolve02-lv_root is
missing.
/dev/root is a symlink to /dev/dm-0
Which is a bit surprising, since,
On 03/29/2013 01:23 AM, Joakim Ziegler wrote:
Immediately after getting dropped to rdshell, I looked around in /dev,
which brought me a few surprises...
/dev/mapper contains only control, that is, vg_resolve02-lv_root is
missing.
Did you get to look at or for /dev/vg_resolve02 as well?
On Tue, Mar 26, 2013 at 1:35 AM, Joakim Ziegler joa...@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,
I haven't actually renamed the root LVM volume, it's had the same name
since install. I just moved some drives around on the SATA ports. Is it
still worth recreating initrd?
--
Joakim Ziegler - Supervisor de postproducción - Terminal
joa...@terminalmx.com - 044 55 2971 8514 - 5264
On 03/26/2013 01:52 PM, Joakim Ziegler wrote:
I haven't actually renamed the root LVM volume, it's had the same name
since install. I just moved some drives around on the SATA ports. Is it
still worth recreating initrd?
I wouldn't expect it to make a difference, but it probably wouldn't hurt
Thanks, will try.
--
Joakim Ziegler - Supervisor de postproducción - Terminal
joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864
On 26/03/13 18:47, Gordon Messmer wrote:
On 03/26/2013 01:52 PM, Joakim Ziegler wrote:
I haven't actually renamed the root LVM volume, it's had the
On 03/24/2013 10:43 PM, Joakim Ziegler wrote:
I haven't actually tried writing anywhere in the rescue shell before
vgchange and mount. I'll give it a try, that would simplify things.
If nothing else, you probably can fit most or all of that in the shell's
environment. In case it's ever
Hi, Gordon, this was indeed a very good idea. I'm attaching that file
here, as it's a bit large. Thanks in advance for help and ideas.
--
Joakim Ziegler - Supervisor de postproducción - Terminal
joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864
On 25/03/13 0:21, Gordon Messmer
On 25/03/13 19:26, Joakim Ziegler wrote:
Hi, Gordon, this was indeed a very good idea. I'm attaching that file
here, as it's a bit large. Thanks in advance for help and ideas.
Hm, it seems the list strips attachments, and just pasting it makes the
mail too big to go through, so, pastebin to
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
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
On 03/22/2013 08:27 PM, Joakim Ziegler wrote:
So, after all this, my question is, how do I make Dracut (I'm assuming)
understand that this LVM volume is my root device and pick it up
automatically?
I've looked through Dracut trying to spot circumstances that might cause
the problem that
Thank you, I will do this tomorrow. It'll take me a little time, since I
need to transcribe everything manually, but I'll get it done. It's just
a very weird problem all in all.
--
Joakim Ziegler - Supervisor de postproducción - Terminal
joa...@terminalmx.com - 044 55 2971 8514 -
On 03/24/2013 10:38 PM, Joakim Ziegler wrote:
Thank you, I will do this tomorrow. It'll take me a little time, since I
need to transcribe everything manually, but I'll get it done. It's just
a very weird problem all in all.
You should be able to pipe the output into a file and copy it to the
I haven't actually tried writing anywhere in the rescue shell before
vgchange and mount. I'll give it a try, that would simplify things.
--
Joakim Ziegler - Supervisor de postproducción - Terminal
joa...@terminalmx.com - 044 55 2971 8514 - 5264 0864
On 24/03/13 23:41, Gordon
Grub (in the menu) has the following commands:
root (hd0,1)
kernel /vmlinuz-2.6.32-279.el6.x86_64 ro
root=/dev/mapper/vg_resolve02-lv_root rd_NO_LUKS LANG=en.US.UTF-8
rd_NO_MD crashkernel=128M rd_LVM_LV=vg_resolve02/lv_root
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb
Oh, and the exact Dracut error I get is:
dracut Warning: No root device block:/dev/mapper/vg_resolve02-lv_root
found
dracut Warning: LVM vg_resolve02/lv_root not found
But then:
# lvm vgscan
Found volume group vg_resolve02 using metadata type lvm2
# lvm vgchange -ay
1 logical volume(s)
I have an 8-core SuperMicro Xeon server with CentOS 6.3. The OS is
installed on a 120 GB SSD connected by SATA, the machine also contains
an Areca SAS controller with 24 drives connected. The motherboard is a
SuperMicro X9DA7.
When I installed the OS, I used the default options, which creates
When I booted the box after this, I got a kernel panic, the typical
Can't find root device.
Reading https://fedoraproject.org/wiki/How_to_debug_Dracut_problems , I
did the following:
# lvm vgscan
# lvm vgchange -ay
And then
# ln -s /dev/mapper/volumegroup-root_volume /dev/root
# exit
22 matches
Mail list logo
