? Maxtor disk problem
Before I get any egg on my face by returning this disk, I am asking the IDE gurus opinion. I'm also sorry for bothering lkml.
I'm running FedoraCore 2 on a Alpha LX164 box with 512M RAM. The on board IDE chip won't handle current IDE so I purchased a HighPoint Rocket133 and a Maxtor 120G drive. On boot, the kernel panics after probing the drive reporting "INVALID HEADS" etc. I then gave the kernel hde=noprobe option via SRM to boot the system after adding "alias block-major-33 ide-probe" to /etc/modprobe.conf. While fsdisk /dev/hde reports "unable to read /dev/hde", hdparm -I reports the following:
/dev/hde:
ATA device, with non-removable media
Model Number: Maxtor CALYPSO
Firmware Revision: YAR43KJZ
Standards:
Likely used: 1
Configuration:
fixed drive
Logical max current
cylinders 0 0
heads 0 0
sectors/track 0 0
--
device size with M = 1024*1024: 0 MBytes
device size with M = 1000*1000: 0 MBytes
Capabilities:
IORDY not likely
Cannot perform double-word IO
R/W multiple sector transfer: not supported
DMA: not supported
PIO: pio0
I'm not familiar with IDE at all. I have always used SCSI. However, my SCSI disk is full and I'm short of money.
My current opinion is the disk is bad. Could an expert please confirm this or please tell me how to fix it? Sorry, printed on the disk is: LBA 240121728 which, I presume, is the total sectors.
Thanks in advance.
More data:
cat /proc/devices (edited)
Block devices:
1 ramdisk
2 fd
8 sd
9 md
11 sr
33 ide2
65 sd
ls -l /proc/ide
-r--r--r-- 1 root root 0 May 28 10:32 cmd64x -r--r--r-- 1 root root 0 May 28 10:32 drivers lrwxrwxrwx 1 root root 8 May 28 10:32 hde -> ide2/hde -r--r--r-- 1 root root 0 May 28 10:32 hpt366 dr-xr-xr-x 3 root root 0 May 28 10:32 ide2
Signature · 1 line
Bob R. Taylor <[email protected]>
Don't you have at least a PC in which you could test your card+disk ? it may be possible that your card does not work in your alpha, I've already had problems with some PCI cards in alpha (most probably because of the drivers, or poorly designed PCI interfaces).
Just for reference, here is what hdparm sees on my maxtor 120GB on my alpha (integrated ALI controller). Perhaps there's really a problem with your disk, but it seems rather strange. Generally, IDE disks with bad identification stop spinning and do not respond to any further command.
If it comes that it's your IDE controller which is wrong, perhaps you would be interested in trying a SCSI->IDE adapter, which would allow you to turn your IDE disk into an SCSI-like one and connect it to your motherboard ?
Regards,
Willy
/dev/hdc:
non-removable ATA device, with non-removable media
Model Number: Maxtor 6Y120L0 Serial Number: Y410P3CE Firmware Revision: YAR41BW0 Standards: Supported: 1 2 3 4 5 6 7 Likely used: 7 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 bytes/track: 0 (obsolete) bytes/sector: 0 (obsolete) current sector capacity: 16514064 LBA user addressable sectors = 240121728
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 2048.0kB ECC bytes: 57 Queue depth: 1
Standby timer values: spec'd by standard, no device specific minimum
r/w multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* NOP cmd
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* look-ahead
* write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
SET MAX security extension
Advanced Power Management feature set
* DOWNLOAD MICROCODE cmd
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- below Vih
Device num = 0 determined by the jumper
Checksum: correct
Quoted 71 lines · Bob R. Taylor
Before I get any egg on my face by returning this disk, I am asking the IDE gurus opinion. I'm also sorry for bothering lkml.
I'm running FedoraCore 2 on a Alpha LX164 box with 512M RAM. The on board IDE chip won't handle current IDE so I purchased a HighPoint Rocket133 and a Maxtor 120G drive. On boot, the kernel panics after probing the drive reporting "INVALID HEADS" etc. I then gave the kernel hde=noprobe option via SRM to boot the system after adding "alias block-major-33 ide-probe" to
/etc/modprobe.conf. While fsdisk/dev/hdereports "unable to read/dev/hde", hdparm -I reports the following:
/dev/hde:ATA device, with non-removable media
Model Number: Maxtor CALYPSO
Firmware Revision: YAR43KJZ
Standards:
Likely used: 1
Configuration:
fixed drive
Logical max current
cylinders 0 0
heads 0 0
sectors/track 0 0
--
device size with M = 1024*1024: 0 MBytes
device size with M = 1000*1000: 0 MBytes
Capabilities:
IORDY not likely
Cannot perform double-word IO
R/W multiple sector transfer: not supported
DMA: not supported
PIO: pio0I'm not familiar with IDE at all. I have always used SCSI. However, my SCSI disk is full and I'm short of money.
My current opinion is the disk is bad. Could an expert please confirm this or please tell me how to fix it? Sorry, printed on the disk is: LBA 240121728 which, I presume, is the total sectors.
Thanks in advance.
More data:
cat
/proc/devices(edited)Block devices:
1 ramdisk
2 fd
8 sd
9 md
11 sr
33 ide2
65 sdls -l
/proc/ide(quoted diff) +0
-2-r--r--r-- 1 root root 0 May 28 10:32 cmd64x -r--r--r-- 1 root root 0 May 28 10:32 driverslrwxrwxrwx 1 root root 8 May 28 10:32 hde -> ide2/hde -r--r--r-- 1 root root 0 May 28 10:32 hpt366 dr-xr-xr-x 3 root root 0 May 28 10:32 ide2Signature · 6 lines
Bob R. Taylor <[email protected]> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
For the archives. I received an email from a Maxtor user. He had a drive with the exact same symptoms recently. He contacted Maxtor and confirmed the drive was bad.
Thanks to all who replied!
Signature · 1 line
Bob R. Taylor <[email protected]>