hdb when no hdb attached in 2.1.36

Curtiss Cicco (cmc@ipgeek.com)
Wed, 30 Apr 1997 23:34:41 -0700


Today I installed a new Quantum Fireball hard drive and now
i'm getting messages about hdb at boot up. The thing is that
nothing is attached as a slave on the primary IDE interface;
it's even disabled in my bios. Here's some output of my syslog.

kernel: hda: Maxtor 71626 AP, ATA DISK drive
kernel: hdb: non-IDE drive, CHS=935/128/63
kernel: hdc: QUANTUM FIREBALL_TM3840A, ATA DISK drive
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: ide1 at 0x170-0x177,0x376 on irq 15
kernel: hdb: DMA disabled
kernel: hdb: INVALID GEOMETRY: 128 PHYSICAL HEADS?
kernel: hdc: DMA disabled
kernel: Started kswapd v 1.23
kernel: Partition check:
kernel: hda: hda1 hda2 hda3
kernel: hdc: hdc1 hdc2

What could be causing a phantom drive to be showing up?

On another note with the Quantum. No matter which two partition
sizes I use for the drive, fdisk keeps warning me of partition 1
overlapping partition 2. Here's my partition printout.

Device Boot Begin Start End Blocks Id System
/dev/hdc1 1 1 2084 1050304+ 83 Linux native
/dev/hdc2 2048 2085 7480 2719584 83 Linux native

In this output it looks like partition 2 is overlapping into partition
1 opposite of what fdisk reports. In this instance when I partitioned
the drive I explicitly chose 1-2084 for partition 1 and 2085-7480
for partition 2. So somehow partition 2 is beginning before the start
of what I specified. After writing the partition table, rebooting,
and running mke2fs on the partitions I'm able to mount and access
these partitions with no apparent problems. My only concern is when
I start writing files to these partitions I might eventually lose data
due to these overlaps.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Curtiss Cicco             =
=   1cmc3466@ibm.mtsac.edu  =
=   cmc@ipgeek.com          =
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=