Red Hat Bugzilla – Bug 77237
new hdb harddrive only "findable" as hdd device?
Last modified: 2007-04-18 12:48:07 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
I first double checked to see that the drive was slave and on ide0
chain. Having done that and scratched my head I found this in my syslogger:
hda: QUANTUM FIREBALLP LM20.5, ATA DISK drive
hdb: QUANTUM FIREBALL EX6.4A, ATA DISK drive
hdc: Pioneer DVD-ROM ATAPIModel DVD-105S 011, ATAPI CD/DVD-ROM drive
hdd: SONY CD-RW CRX175E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
But when trying to fdisk the drive I can only seem to find it when I do a fdisk
(I was not sure where to post this - I thought it mounting related though.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. installed the drive as slave on ide0
2. boot up
3. no drive @ hdb
Actual Results: I tried accessing the drive but get the error:
# ./fdisk /dev/hdb
Unable to open /dev/hdb
but curiously I tried hdc and hdd and hdd was willing to be fdisked!?!? despite
that is is technically my CDRW.
Expected Results: hdb = hdb, fdisk, write fs, happy.
Tried posting to comp.os.linux.hardware and psyche-listserv. Without resolution.
To follow this up - I could not fdisk the hdd partition - as I came to surmise
that it is the write buffer on my CDRW.
So - I used pqmagic to clean and make my new 6GB drive into an ext3 system - yet
I cannot see/mount/fdisk/etc....anything to my hdb - I would think the drive
messed up - but I can see it with windows.
Sorry, this is one of those "call support because you have a totally weird hardware setup"
type of bugs. :\ Those symptoms are really strange.
If you have a way for me to reproduce the problem on any random system, it'll be easier
for me to try solving it.
Well I sorted this one out - forgot about the bug report - I had the burner in
the hdb slot before - so the grub.conf still pointed the scsi=ide thing to hdb.
After I changed that to point to hdd (where the burner is) - no problems!
Everything works great now.