Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Joey L <mjh2000@xxxxxxxxx>
- Date: Thu, 2 Apr 2009 21:29:05 -0400
On Thu, Apr 2, 2009 at 8:13 PM, thveillon@xxxxxxxxx <thveillon@xxxxxxxxx>wrote:
thveillon.debian wrote :I understand that it is getting late in the UK - I will wait till you wake
I see nothing that strikes me as odd in your conf, outside of the fact
that you only have a single user entry for your new kernel.
I think you need to add lvm mapper module to the initrd, echo dm-mod to
/etc/initramfs-tools/modules like you did for md-mod and raid's modules,
and rebuild an initrd.
Also, are your raided partitions identified as "fd" filesystem ? Maybe
the output of
fdisk -l
and
mdadm --detail --scan --verbose
would help us understand your layout better.
Tom
Sorry, please ignore my advice to load dm-mod in the initrd, reading the
whole thread I saw you are running on software raid only, so it's not
needed at all, only md-mod.
It's getting late in UK time zone...
or unless anybody on this listserv can lend a helping hand.
I think i did everything and this is a standard configuration - I did not do
anything too crazy !
Again - all this is software raid --- the /boot is raid1 and the other
volumes are software raid5 The Raid5 has LVM filesystems.
here is fdisk -l :
thor:/home/mjh#
thor:/home/mjh#
thor:/home/mjh# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 36 289138+ fd Linux raid
autodetect
/dev/sda2 37 60801 488094862+ fd Linux raid
autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 36 289138+ fd Linux raid
autodetect
/dev/sdb2 37 60801 488094862+ fd Linux raid
autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 36 289138+ fd Linux raid
autodetect
/dev/sdc2 37 60801 488094862+ fd Linux raid
autodetect
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 36 289138+ fd Linux raid
autodetect
/dev/sdd2 37 60801 488094862+ fd Linux raid
autodetect
Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 * 1 36 289138+ fd Linux raid
autodetect
/dev/sde2 37 60801 488094862+ fd Linux raid
autodetect
Disk /dev/md0: 295 MB, 295960576 bytes
2 heads, 4 sectors/track, 72256 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 1499.4 GB, 1499427176448 bytes
2 heads, 4 sectors/track, 366071088 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/dm-0: 536.8 GB, 536870912000 bytes
255 heads, 63 sectors/track, 65270 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 6442 MB, 6442450944 bytes
255 heads, 63 sectors/track, 783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 536.8 GB, 536870912000 bytes
255 heads, 63 sectors/track, 65270 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3: 419.1 GB, 419191324672 bytes
255 heads, 63 sectors/track, 50963 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-3 doesn't contain a valid partition table
On the mdadm --detail --scan --verbose :
thor:/home/mjh#
thor:/home/mjh#
thor:/home/mjh#
thor:/home/mjh# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 spares=3
UUID=8a435040:c6f27178:02026e74:21deb7ac
devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1,/dev/sde1
ARRAY /dev/md1 level=raid5 num-devices=4 spares=1
UUID=f60a4f26:891a29c2:8dbe0712:bd7a69ac
devices=/dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd2,/dev/sde2
- Follow-Ups:
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: thveillon.debian
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Alex Samad
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- References:
- upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Joey L
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Kumar Appaiah
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Joey L
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: thveillon.debian
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Joey L
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Joey L
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: thveillon.debian
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: Joey L
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: thveillon.debian
- Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- From: thveillon@xxxxxxxxx
- upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- Prev by Date: Re: problem with apt
- Next by Date: Re: translator tool
- Previous by thread: Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- Next by thread: Re: upgrading the kernel in debian etch from 2.6.18 to 2.6.29
- Index(es):
Relevant Pages
|