Out of curiosity (and since, I've just noticed this thread), what does
the output of "dmesg | grep hd" show you?
Emmanuel
Thanks. The dmesg approach was mentioned last Friday, I did it but
didn't get a chance to post it. Here it is:
[Brandon@localhost Brandon]$ dmesg | grep hd
Kernel command line: initrd=initrd.img hdd=ide-scsi root=/dev/hdf1
BOOT_IMAGE=vmlinuz
ide_setup: hdd=ide-scsi
ide1: BM-DMA at 0x14a8-0x14af, BIOS settings: hdc:pio, hdd:DMA
ide2: BM-DMA at 0x1440-0x1447, BIOS settings: hde:DMA, hdf:DMA
ide3: BM-DMA at 0x1448-0x144f, BIOS settings: hdg:DMA, hdh:DMA
hdc: MATSHITADVD-ROM SR-8584A, ATAPI CD/DVD-ROM drive
hdd: ZIPCD 4x650, ATAPI CD/DVD-ROM drive
hde: ST380021A, ATA DISK drive
hdf: WDC WD400BB-00CFC0, ATA DISK drive
hde: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63,
UDMA(66)
hdf: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=77545/16/63,
UDMA(66)
hde: [PTBL] [9729/255/63] hde1 hde2 < hde5 >
hdf: [PTBL] [4865/255/63] hdf1 hdf2 hdf3 < hdf5 hdf6 hdf7 hdf8 hdf9 >
hde9: bad access: block=0, count=1
end_request: I/O error, dev 21:09 (hde), sector 0
hde8: bad access: block=0, count=1
end_request: I/O error, dev 21:08 (hde), sector 0
hdc: ATAPI 32X DVD-ROM drive, 512kB Cache
hde9: bad access: block=0, count=1
end_request: I/O error, dev 21:09 (hde), sector 0
hde8: bad access: block=0, count=1
end_request: I/O error, dev 21:08 (hde), sector 0
I used to have those parts of hde mounted as partitions (one for all
pictures, one for all documents, etc. so it was really easy to upgrade)
Thanks!
--
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
