Bizarre HD Problem

[Dead_Dad]

OS: Win98/Mandrake 9.1

I just installed a new 80GB Maxtor HD (6Y080L0) and, while my BIOS sees it
and it shows up in dmesg as 'hdd',

a) It doesn't show up in dev, mnt, /etc/fstab, or /etc/mtab.

b) /dev/ide/host0/bus1/target1/lun0 is empty.


Here is the relevent(?) dmesg output:

Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 90432D3, ATA DISK drive
hdb: MAXTOR 6L080J4, ATA DISK drive
blk: queue c03cb420, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03cb55c, I/O limit 4095Mb (mask 0xffffffff)
hdc: FUJITSU MPB3032ATU, ATA DISK drive
hdd: Maxtor 6Y080L0, ATA DISK drive
blk: queue c03cb86c, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03cb9a8, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: host protected area => 1
hda: 8440992 sectors (4322 MB) w/256KiB Cache, CHS=525/255/63, UDMA(33)
hdb: host protected area => 1
hdb: 156355584 sectors (80054 MB) w/1820KiB Cache, CHS=9732/255/63, UDMA(33)
hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }
hdc: 6335280 sectors (3244 MB), CHS=6704/15/63, UDMA(33)
Partition check:
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 >
/dev/ide/host0/bus0/target1/lun0: p1
/dev/ide/host0/bus1/target0/lun0:<6> [PTBL] [785/128/63] p1 p2 < p5 p6 p7 >
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.


Here is what Harddrake2 has to say about my hard drives:

Model: 90432D3
Vendor: Maxtor
Bus: ide
Channel: primary
New devfs device: /dev/ide/host0/bus0/target0/lun0/disc
Old device file: /dev/hda
Media class: hd

Model: 6L080J4
Vendor: Maxtor
Bus: ide
Channel: secondary
New devfs device: /dev/ide/host0/bus0/target1/lun0/disc
Old device file: /dev/hdb
Media class: hd

Model: MPB3032ATU
Vendor: Fujitsu
Bus: ide
Channel: secondary
New devfs device: /dev/ide/host0/bus1/target0/lun0/disc
Old device file: /dev/hdc
Media class: hd

Model: 6Y080L0
Vendor: Maxtor
Bus: ide
Channel: secondary
New devfs device: /dev/ide/host0/bus1/target1/lun0/disc
Old device file: /dev/hdd
Media class: hd

I installed MD 9.1 on the Fujitsu - the first two are Win98/FAT32.

I thank you for any help you can offer me. I'm sorry for taking up so much
bandwidth, but I am somewhat new to Linux, and don't know exactly what
information you need.

Keith Olson

[Steve Martin]

Dead_Dad wrote:

> OS: Win98/Mandrake 9.1
>
> I just installed a new 80GB Maxtor HD (6Y080L0) and, while my BIOS sees it
> and it shows up in dmesg as 'hdd',
> a) It doesn't show up in dev, mnt, /etc/fstab, or /etc/mtab.
> b) /dev/ide/host0/bus1/target1/lun0 is empty.

Looks from dmesg like the kernel did in fact detect it, so
that much is okay. Let me ask the stupid questions...
Did you partition the drive after you installed it using
fdisk (or some such)? After you partitioned it, did you
make filesystems on the new partition(s) (i.e. did you
format them)?


--
Steve Martin, CPBE CBNT

[Ken Kauffman]

"Steve Martin" <ecprod@bellsouth.net> wrote in message
news:229Ta.2523$nL2.1192@fe05.atl2.webusenet.com.. .
| Dead_Dad wrote:
| > OS: Win98/Mandrake 9.1
| >
| > I just installed a new 80GB Maxtor HD (6Y080L0) and, while my BIOS sees
it
| > and it shows up in dmesg as 'hdd',
| > a) It doesn't show up in dev, mnt, /etc/fstab, or /etc/mtab.
| > b) /dev/ide/host0/bus1/target1/lun0 is empty.
|
| Looks from dmesg like the kernel did in fact detect it, so
| that much is okay. Let me ask the stupid questions...
| Did you partition the drive after you installed it using
| fdisk (or some such)? After you partitioned it, did you
| make filesystems on the new partition(s) (i.e. did you
| format them)?
|
|
| --
| Steve Martin, CPBE CBNT

I agree with Steve. Adding the drive to an existing system will only allow
the system to recognize its existance. It will not add the relevant entries
to /etc/fstab and will not set the drive up for you. I'm assuming you are
adding to an existing system as hdd is typically a slave drive on the second
IDE controller in your system.

fdisk/parted the disk to set up partition(s)
man mkfs
man fstab

ken k

[felmon davis]

In article <zdeTa.16748$zd4.6739@lakeread02>, "Ken Kauffman"
<kkauffman@nospam.headfog.com> wrote:

> I'm assuming
> you are adding to an existing system as hdd is typically a slave drive
> on the second IDE controller in your system.

I may be reading this wrong but it looks to me like the OP has both hdc
and hdd set up as 'secondary'. hdc should be set as 'primary' and hdd as
'secondary', right? maybe check the jumpers on the hard-drives and the
cable sequence.

Felmon

[Ken Kauffman]

"felmon davis" <davisf@punzel.ditmar> wrote in message
news:ysSdnTkA6t-SsYOiRTvU2Q@giganews.com...
| In article <zdeTa.16748$zd4.6739@lakeread02>, "Ken Kauffman"
| <kkauffman@nospam.headfog.com> wrote:
|
| > I'm assuming
| > you are adding to an existing system as hdd is typically a slave drive
| > on the second IDE controller in your system.
|
| I may be reading this wrong but it looks to me like the OP has both hdc
| and hdd set up as 'secondary'. hdc should be set as 'primary' and hdd as
| 'secondary', right? maybe check the jumpers on the hard-drives and the
| cable sequence.
|
| Felmon

I don't think that is the case. I think they just need to set the drive up.
I'd like to hear back from the Op on what is going on though.

ken k