Hi Bene
Many thanks for the reply.
At 12:47 22/04/01, you wrote:
>This looks like the typical output for the "raid module not in
>kernel" problem; I'd say raid5 is compiled as a module and not
>included in an initrd.
You are correct. In the first instance, I compiled a new kernel 2.4.3 for
the new cpu, etc., & inadvertently compiled raid as a module. Since then I
have compiled various kernels, all with raid built in. The current state is
shown in the previous complete dmesg. Relevant extract follows. This is one
of three Linux systems I have running currently. Unfortunately my network
was largely reliant on the 10 GB of data stored on the raid array!
Sorry if I misled you.
dmesg extract:
md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md.c: sizeof(mdp_super_t) = 4096
autodetecting RAID arrays
(read) hdc1's sb offset: 20089152 [events: 00000080]
(read) hde1's sb offset: 20089152 [events: 00000080]
(read) hdg1's sb offset: 20089152hdg: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
[events: 00000082]
autorun ...
considering hdg1 ...
adding hdg1 ...
adding hde1 ...
adding hdc1 ...
created md0
bind<hdc1,1>
bind<hde1,2>
bind<hdg1,3>
running: <hdg1><hde1><hdc1>
now!
hdg1's event counter: 00000082
hde1's event counter: 00000080
hdc1's event counter: 00000080
md: superblock update time inconsistency -- using the most recent one
freshest: hdg1
md: kicking non-fresh hde1 from array!
unbind<hde1,2>
export_rdev(hde1)
md: kicking non-fresh hdc1 from array!
unbind<hdc1,1>
export_rdev(hdc1)
md0: former device hdc1 is unavailable, removing from array!
md0: former device hde1 is unavailable, removing from array!
md: md0: raid array is not clean -- starting background reconstruction
request_module[md-personality-4]: Root fs not mounted
do_md_run() returned -22
md0 stopped.
unbind<hdg1,0>
export_rdev(hdg1)
Thanks for your time
Mike Parsons
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
