|
Hi,
I'm using the mdraid with standard redhat 9.
Installation was all fine (choosing lilo too) - I have two boxes and I
tried to do them identical.
df, fstab and mtab show the same things on each
box, apart from device specific stuff. /proc/mdstat shows the same
-
Personalities : [raid1]
read_ahead 1024 sectors md1 : active raid1 hda6[0] hdc6[1] 818880 blocks [2/2] [UU] md2 : active raid1 hda5[0] hdc5[1] 2048128 blocks [2/2] [UU] md4 : active raid1 hda3[0] hdc3[1] 11606848 blocks [2/2] [UU] md3 : active raid1 hda2[0] hdc2[1] 44033856 blocks [2/2] [UU] md0 : active raid1 hda1[0] hdc1[1] 104192 blocks [2/2] [UU] df shows on each box
Filesystem
1K-blocks Used Available Use% Mounted
on
/dev/md4 11424496 1580176 9263980 15% / /dev/md0 100890 14222 81459 15% /boot /dev/md3 43342848 32828 41108328 1% /export none 515436 0 515436 0% /dev/shm /dev/md1 805996 85108 679944 12% /var fs.private.network:/export 65512476 245832 61938788 1% /u1 The strange thing is, I'm upgrading the kernel on
each box. I ran lilo -v on one box, and it gave
LILO version 21.4-4, Copyright (C) 1992-1998 Werner
Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman boot = /dev/hda, map = /boot/map.0301
Reading boot sector from /dev/hda Merging with /boot/boot.b Mapping message file /boot/message Boot image: /boot/vmlinuz-2.4.20-20.9 Mapping RAM disk /boot/initrd-2.4.20-20.9.img Added linux * Boot image: /boot/vmlinuz-2.4.20-8 Mapping RAM disk /boot/initrd-2.4.20-8.img Added linux2.4.20-8 /boot/boot.0300 exists - no backup copy made. Writing boot sector. boot = /dev/hdc, map = /boot/map.1601 Reading boot sector from /dev/hdc Merging with /boot/boot.b Mapping message file /boot/message Boot image: /boot/vmlinuz-2.4.20-20.9 Mapping RAM disk /boot/initrd-2.4.20-20.9.img Added linux * Boot image: /boot/vmlinuz-2.4.20-8 Mapping RAM disk /boot/initrd-2.4.20-8.img Added linux2.4.20-8 /boot/boot.1600 exists - no backup copy made. Writing boot sector. Which looks fine to me. Indeed it works - I
rebooted and it came straight up with the new kernel.
However, when I run lilo -v on the other box, I
get
LILO version 21.4-4, Copyright (C) 1992-1998 Werner
Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman boot = /dev/hda, map = /boot/map.0301
Reading boot sector from /dev/hda Merging with /boot/boot.b Mapping message file /boot/message Boot image: /boot/vmlinuz-2.4.20-20.9 Mapping RAM disk /boot/initrd-2.4.20-20.9.img Added linux * Boot image: /boot/vmlinuz-2.4.20-8 Mapping RAM disk /boot/initrd-2.4.20-8.img Added linux2.4.20-8 /boot/boot.0300 exists - no backup copy made. Writing boot sector. which looks to me like it 'missed' a disk. My
lilo.confs are identical. and look like this:
prompt
timeout=50 default=linux boot=/dev/md0 map=/boot/map install=/boot/boot.b message=/boot/message linear image=/boot/vmlinuz-2.4.20-20.9
label=linux initrd=/boot/initrd-2.4.20-20.9.img read-only root=/dev/md4 image=/boot/vmlinuz-2.4.20-8 label=linux2.4.20-8 initrd=/boot/initrd-2.4.20-8.img read-only root=/dev/md4 I don't know if I shoudl be worried about this, but
I decided not to reboot. The only difference I noticed between the /boot dirs is
that the first one has two boot and map files thus:
-rw-r--r-- 1
root
root 512 Aug 11 19:02
boot.0300
-rw-r--r-- 1 root root 512 Aug 11 19:02 boot.1600 -rw------- 1 root root 31744 Aug 26 18:40 map.0301 -rw------- 1 root root 31744 Aug 26 18:40 map.1601 whereas the second box has only one of
each:
-rw-r--r-- 1
root
root 512 Aug 9 01:41
boot.0300
-rw------- 1 root root 31744 Aug 26 18:44 map.0301 Should I be worried? Anyone know what's going
on?
many thanks for any help.
regards
Dave
|
