Dan,

On Sat, 4 Nov 2000, Dan Browning wrote:
>       '/' mounted on RAID-5

IIRC, lilo cannot deal with RAID-5 partitions at boot time - only RAID-1
(and maybe RAID-0?)

> * When booting with newly created '/dev/md0' as '/', it is reported
> corrupt and needs a manual fsck
> * The manual fsck reports millions (almost) of:
> inode 12156 is in use, but has dtime set.  Fix?
> inode 12156 has imagic flag set, clear?
> ...
> And various other sundry errors.
> * After fsck'ing it (holding the enter key down for an hour), and

I'm guessing that this is because it is treating one disc of the RAID-5
array as a horribly broken ext2 partition. Fixing these errors completely
trashes the RAID-5 array.

> - mkraid /dev/md0
> - mke2fs -b 4096 -R stride=8 /dev/md0
> - init 1

I've never tried it like this - does the raid5syncd thread continue
running OK when you take it down to runlevel one?

> - cp -xa / /mnt/md0
> (During the cp I get a bunch of errors like the following:)
> "EXT2-fs error (device md(9,0)): ext2_new_block: Allocating block in
> system zone - block = 416"
> "EXT2-fs error (device md(9,0)): ext2_free_blocks: freeing blocks in
> system zones - Block = 419, count = 5"

These may be harmless, but I haven't seen them before. Maybe try waiting
for raid5syncd to finish syncing the array before mke2fs and cp.

> - cp finishes.  So I edit the /mnt/md0/etc/fstab and set
>       "/dev/md0               /               ext2    defaults        1 1"
> - then I edit /mnt/md0/etc/lilo.conf to set:
>       image=/boot/vmlinuz-2.4.0-test10
>               label=2.4.0-t10md0
>               read-only
>               root=/dev/md0

Are you also setting boot=/dev/md0? This installs the boot block in the
MBR of each disk which is part of the array.

> - '/sbin/lilo -v' runs fine

You are doing 'lilo -r /mnt/md0', aren't you? Just running lilo will use
/etc/lilo.conf instead of /mnt/md0/etc/lilo.conf.

This is what I do:

mkraid /dev/md0
  /* wait for raid5syncd to complete */
mke2fs -b 4096 -R stride=8 /dev/md0
mount /mnt/md0
find / -mount -print | cpio -pm /mnt/md0
cd /mnt/md0
vi etc/lilo.conf
  /* change 'boot' and 'root' lines to '/dev/md0' */
vi etc/fstab
  /* change root fs to '/dev/md0' */
vi etc/mtab
  /* change root fs to '/dev/md0', delete all other lines */
lilo -r .
  /* run lilo, treating '/mnt/md0' as the root */
reboot

> * Two are on the Intel i815 Mobo (onboard LAN / vid)

Just out of interest, is this the D815EEA? What do you think of it, and
the Solano2 Chipset?

> * Two are on the Promise Ultra66 controller (2.00b18 firmware) <--
> that's why I use the ide patches when using 2.2.17
> * raidtools-.90-13.rpm (plus .90 in the kernel)

Shouldn't be a problem with this. Give the above a try, and see if it
helps...

Corin

/------------------------+-------------------------------------\
| Corin Hartland-Swann   | Direct: +44 (0) 20 7544 4676        |
| Commerce Internet Ltd  | Mobile: +44 (0) 79 5854 0027        |
| 22 Cavendish Buildings |    Tel: +44 (0) 20 7491 2000        |
| Gilbert Street         |    Fax: +44 (0) 20 7491 2010        |
| Mayfair                |    Web: http://www.commerce.uk.net/ |
| London W1K 5HJ         | E-Mail: [EMAIL PROTECTED]        |
\------------------------+-------------------------------------/

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]

Reply via email to