[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

non-recognition of hard drive(s) in AMD Athlon w/KT7A-RAID mb running RAID 0 (striping) w/2 Quantum Fireball 30 G hard drives on IDE 3 & 4 controllers



Hello,
 
I am doing something for my first time:  building my own system and install Debian Linux 2.2r3.  Everything seems to work fine until I reach the part in dbootsrap where I need to partion my hard drive(s).  At that point in time, the installer pgm basically says "you don't have any disks."  I physically do, but it doesn't see them. 
 
This is the system I have put together:
    OS:                   Debian Linux 2.2r3 (only)
    Motherboard:    ABIT KT7A-RAID.  I have set this up in the BIOS to use RAID 0 (striping) for performance enhancement.
    CPU:               AMD Athlon 1.0 Gig
    CD-ROM:        I/O Magic
    CD-Burner:      Pacific Digital
    ZIP Drive:        Iomega 100
    Floppy:           Generic
    Hard Drives:    Quantum Fireball 30 Gig (2).  Bought as "Bare" drives.
 
I have installed all the hardware, checked that all cables were secure, power supplied to devices, etc.  I put the CD-ROM disc of the OS into my CD-ROM drive and it begins the boot process.
 
I assume the CD-ROM drive is recognized correctly (it wouldn't have started the boot process if not).  Everything except the hard drives seems to be recognized.  The two CD-ROM devices are IDE. One is mounted on the m.b. IDE 1 controller.  The other, along with the ZIP drive, is on the IDE 2 controller.  The m.b. has 2 more controllers (IDE 3 & IDE 4) for UDMA-100:  on each I have connected a Quantum drive.  
 
Note that I have not formatted nor partitioned the hard drives.  Without an OS, it's tough to do that!  I have, after the dbootstrap program started, "alt'd" into the linux prompt.  I ran the following commands:
    e2fsck /dev/hda  -> read only file system.  not ext2 format.
    e2fsck /dev/hdb  -> device not configured
    e2fsck /dev/hdc  -> device not configured
    e2fsck /dev/hdd  -> read only file system
    e2fsck /dev/mdo -> attempt to read block for filesystem resulted in short read while trying to open /dev/md0.  Could this be a
                                 0-length partition?
I also ran cfdisk.  It defaulted to /dev/hda and was read only.  I did get some practice on how to use the cfdisk.
 
 
My initial thought is that I somehow need to format the Quantum drives that are RAID0'd together to be seen as one unit. ( I don't, however, know the exact syntax to do that.) If the Linux system saw them as one unit and I knew that name, like /dev/md0, I think the dbootstrap installer would allow me to partition it/them and proceed.
 
I would certainly appreciate any help that could be provided in getting over this hurdle.
 
Thanks,
Rob
    

Reply to: