Some folks have gotten RH 6.0 up and running?! Yesterday I purchased an
AMD K6-2/400 and get a kernel panic on the net install. Details are ASUS
P5A, 100Mhz bus, 128M, Adaptec 2940, 3 * Fujitsu 4.5g. RH 5.2 runs fine.
On Fri, 7 May 1999, m. allan noah wrote:
> you made raid support as a module. go back and re-make kernel. but in the
> stuff you actually need directly, not a module.
>
> allan
>
> "so don't tell us it can't be done, putting down what you don't know.
> money isn't our god, integrity will free our souls" - Max Cavalera
>
> On Fri, 7 May 1999, Aaron Bush wrote:
>
> > ----- Original Message -----
> > > fd is not defined as an official partition type, yet, in fdisk. Change
> > > the type to fd anyway - it will be listed as an unknown type. Reboot and
> > > it should auto recognize the array.
> > >
> > > Kevin
> >
> > Thanks,
> > I have set the filesystem type of the partitions on sda and sdb
> > (excluding /) to 'fd'. I then did a umount /dev/sda5 then mkraid for my
> > /dev/md0. When I boot the machine now I get this as the output of dmesg:
> > <--- begin cut -->
> > autodetecting RAID arrays
> > autorun ...
> > ... autorun DONE.
> > VFS: Mounted root (ext2 filesystem).
> > (scsi0) <Adaptec AHA-294X Ultra2 SCSI host adapter> found at PCI 9/0
> > (scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs
> > (scsi0) Downloading sequencer code... 374 instructions downloaded
> > scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.15/3.2.4
> > <Adaptec AHA-294X Ultra2 SCSI host adapter>
> > scsi : 1 host.
> > (scsi0:0:1:0) Synchronous at 80.0 Mbyte/sec, offset 15.
> > Vendor: IBM Model: DRVS09V Rev: 0140
> > Type: Direct-Access ANSI SCSI revision: 03
> > Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
> > (scsi0:0:2:0) Synchronous at 80.0 Mbyte/sec, offset 15.
> > Vendor: IBM Model: DRVS09V Rev: 0140
> > Type: Direct-Access ANSI SCSI revision: 03
> > Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
> > SCSI device sda: hdwr sector= 512 bytes. Sectors= 17928698 [8754 MB] [8.8
> > GB]
> > sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 >
> > SCSI device sdb: hdwr sector= 512 bytes. Sectors= 17928698 [8754 MB] [8.8
> > GB]
> > sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 >
> > autodetecting RAID arrays
> > (read) sda5's sb offset: 6144704 [events: 00000002]
> > (read) sdb5's sb offset: 6144704 [events: 00000002]
> > autorun ...
> > considering sdb5 ...
> > adding sdb5 ...
> > adding sda5 ...
> > created md0
> > bind<sda5,1>
> > bind<sdb5,2>
> > running: <sdb5><sda5>
> > now!
> > sdb5's event counter: 00000002
> > sda5's event counter: 00000002
> > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2
> > do_md_run() returned -22
> > unbind<sdb5,1>
> > export_rdev(sdb5)
> > unbind<sda5,0>
> > export_rdev(sda5)
> > md0 stopped.
> > ... autorun DONE.
> > <-- end cut -->
> >
> > This looks good except for the md0 stopped message. Once the boot is
> > complete a cat /proc/mdstat shows nothing about md0? What is the kmod
> > error?
