lvm2 boot failure

01-13-2009, 02:02 PM

Martin Kraus Ã*rta:

On Tue, Jan 13, 2009 at 02:16:45PM +0100, Kirï¿½ly Lï¿½szlï¿½ wrote:

Hi list,

My server doesn't boot after raid card faliure. I recreated the raid1
array, partitioned and copyed the whole system to it. Then executed lilo
-v .

and the error message or something that fails the boot? is it bios, or it
doesn't find lilo, or initramfs doesn't find root?

mk

The third, initramfs doesn't find root, but there is a screenshot link
in the end of my original message.

Screenshot from the boot screen: http://kiru.mikroweb.hu/IMG_1145.JPG

"init-bottom ... mount: mounting /dev on /root/dev failed: No such
file or directory"

--
Regards
----
kiru
----

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

01-13-2009, 02:24 PM

On Tue, Jan 13, 2009 at 04:02:41PM +0100, KirÃ¡ly LÃ¡szlÃ³ wrote:
> Martin Kraus Ã*rta:
>> On Tue, Jan 13, 2009 at 02:16:45PM +0100, Kirï¿½ly Lï¿½szlï¿½ wrote:
>>
>>> Hi list,
>>>
>>> My server doesn't boot after raid card faliure. I recreated the raid1
>>> array, partitioned and copyed the whole system to it. Then executed
>>> lilo -v .
>>>
>>
>> and the error message or something that fails the boot? is it bios, or it
>> doesn't find lilo, or initramfs doesn't find root?
>>
>> mk
>>
>
> The third, initramfs doesn't find root, but there is a screenshot link
> in the end of my original message.
> Screenshot from the boot screen: http://kiru.mikroweb.hu/IMG_1145.JPG
>
> "init-bottom ... mount: mounting /dev on /root/dev failed: No such
> file or directory"

according to this /dev/ on the root filesystem doesn't exist. boot from a live
media and check for the existende of /dev/ on the filesystem you're trying to
use as root.

mk

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

01-13-2009, 03:18 PM

Martin Kraus Ã*rta:

On Tue, Jan 13, 2009 at 04:02:41PM +0100, KirÃ¡ly LÃ¡szlÃ³ wrote:

Martin Kraus Ã*rta:

On Tue, Jan 13, 2009 at 02:16:45PM +0100, Kirï¿½ly Lï¿½szlï¿½ wrote:

Hi list,

My server doesn't boot after raid card faliure. I recreated the raid1
array, partitioned and copyed the whole system to it. Then executed
lilo -v .

and the error message or something that fails the boot? is it bios, or it
doesn't find lilo, or initramfs doesn't find root?

mk

The third, initramfs doesn't find root, but there is a screenshot link
in the end of my original message.

Screenshot from the boot screen: http://kiru.mikroweb.hu/IMG_1145.JPG

"init-bottom ... mount: mounting /dev on /root/dev failed: No such
file or directory"

according to this /dev/ on the root filesystem doesn't exist. boot from a live
media and check for the existende of /dev/ on the filesystem you're trying to
use as root.

mk

There is a dev directory and within the special files as I expected.
It's possible that initrd don't try to mount the right filesystem? My
lilo.conf:

---------------

ubuntu:/# grep -v ^# /etc/lilo.conf

lba32

boot=/dev/cciss/c0d0p1

root=/dev/vg/root

bitmap=/boot/sid.bmp
bmp-colors=1,,0,2,,0
bmp-table=120p,173p,1,15,17
bmp-timer=254p,432p,1,0,0

install=bmp

prompt
timeout=50

map=/boot/map

vga=normal

default=linux

image=/boot/vmlinuz-2.6.19.1
label="26191"
read-only
image=/vmlinuz
label=linux
initrd=/initrd.img
read-only
---------------

And the root filesystem:

--------------
ubuntu:/# ls -al /
Ã¶sszesen 4198528
drwxr-xr-x 22 root root 4096 jan 11 19.56 .
drwxr-xr-x 22 root root 4096 jan 11 19.56 ..
drwxr-xr-x 2 root root 4096 jan 9 21.43 backup
drwxr-xr-x 2 root root 4096 jan 12 14.04 bin
drwxr-xr-x 2 root root 4096 jan 12 17.40 boot
drwxr-xr-x 3 root root 4096 jan 9 22.34 boot.old
drwxr-xr-x 15 root root 20480 jan 7 17.02 dev
drwxr-xr-x 91 root root 12288 jan 13 14.03 etc
drwxr-xr-x 2 nobody nogroup 4096 2005 nov 9 ftp_feltolt
drwxr-xr-x 2 root root 4096 jan 9 21.45 home
lrwxrwxrwx 1 root root 28 jan 9 22.23 initrd.img ->
boot/initrd.img-2.6.26-1-686

drwxr-xr-x 14 root root 4096 jan 12 14.04 lib
drwx------ 2 root root 16384 jan 8 11.53 lost+found
drwxr-xr-x 4 root root 4096 jan 7 16.58 mnt
drwxr-xr-x 3 root root 4096 2007 jan 10 opt
drwxr-xr-x 2 root root 4096 nov 26 19.56 proc
drwxr-xr-x 20 root root 4096 jan 12 17.41 root
drwxr-xr-x 2 root root 4096 jan 12 14.04 sbin
drwxr-xr-x 2 root root 4096 nov 26 19.56 selinux
-rw------- 1 root root 4294967296 nov 27 09.02 swap
drwxr-xr-x 2 root root 4096 nov 26 19.56 sys
drwxrwxrwt 5 root root 4096 jan 13 14.03 tmp
drwxr-xr-x 13 root root 4096 nov 24 16.40 usr
drwxr-xr-x 16 root root 4096 2005 jÃºn 17 var
lrwxrwxrwx 1 root root 25 jan 9 22.30 vmlinuz ->
boot/vmlinuz-2.6.26-1-686

------------

--
Regards
----
kiru
----

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

01-13-2009, 06:05 PM

On Tue, Jan 13, 2009 at 05:18:34PM +0100, Király László wrote:
> There is a dev directory and within the special files as I expected.
> It's possible that initrd don't try to mount the right filesystem? My
> lilo.conf:
>
> ubuntu:/# grep -v ^# /etc/lilo.conf
>
> lba32
>
> boot=/dev/cciss/c0d0p1
>
> root=/dev/vg/root
>
>
> bitmap=/boot/sid.bmp
> bmp-colors=1,,0,2,,0
> bmp-table=120p,173p,1,15,17
> bmp-timer=254p,432p,1,0,0
>
> install=bmp
>
>
> prompt
> timeout=50
>
> map=/boot/map
>
> vga=normal
>
> default=linux
>
> image=/boot/vmlinuz-2.6.19.1
> label="26191"
> read-only
> image=/vmlinuz
> label=linux
> initrd=/initrd.img
> read-only

instead of that root=/dev/vg/root you may try root=/dev/mapper/vg-root if your
volume group is called vg. otherwise i'm not suer what the problem could be.
you may try to use apped="root=/dev/mapper/vg-root" in the image declaraction.

mk

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

01-14-2009, 08:49 AM

instead of that root=/dev/vg/root you may try root=/dev/mapper/vg-root if your
volume group is called vg. otherwise i'm not suer what the problem could be.
you may try to use apped="root=/dev/mapper/vg-root" in the image declaraction.

mk

I tryed it with root=/dev/mapper/vg-root but didn't help.
The error message is the same: "mount: mounting /dev on /root/dev
failed: No such file or directory"

What's now?
How can I debug the problem?
There is an easy way?
Which mailing list is for me?

--
Regards
----
kiru
----

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

01-14-2009, 11:14 AM

On Wed, Jan 14, 2009 at 10:49:32AM +0100, Király László wrote:
>
>>
>> instead of that root=/dev/vg/root you may try root=/dev/mapper/vg-root if your
>> volume group is called vg. otherwise i'm not suer what the problem could be.
>> you may try to use apped="root=/dev/mapper/vg-root" in the image declaraction.
>>
>> mk
>>
>>
>>
>
> I tryed it with root=/dev/mapper/vg-root but didn't help.
> The error message is the same: "mount: mounting /dev on /root/dev
> failed: No such file or directory"
> What's now?
> How can I debug the problem?
> There is an easy way?
> Which mailing list is for me?

assuming you have the correct initramfs for your kernel with correct driver
for raid, you may try to pass "debug=y" to the kernel command line. initramfs
should pick it up and maybe output some interesting information before it
panics. most notably what device it tries to use for /root/.
otherwise you'll have to go through initramfs-tools scripts
(/usr/share/initramfs-tools) and add this info yourself, regenerate initrafs
and try again.
One problem I had once upon a time is, that for some reason initrafs couldn't
detect my root filesystem, so I had to add "rootfstype=ext3" to the kernel
command line.

mk

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org