Hi
Here's the latest saga. I took the view that the disk was about to fail so I bought another (80GB Seagate Barracuda) I have also taken the opportunity to upgrade the memory to 1.5Gb.I did not think there would be a problem but here is an extract of "dmesg"
17179570.832000] SIS5513: IDE controller at PCI slot 0000:00:02.5
[17179570.832000] SIS5513: chipset revision 0
[17179570.832000] SIS5513: not 100% native mode: will probe irqs later
[17179570.832000] SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
[17179570.832000] ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda

MA, hdb

MA
[17179570.832000] ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc

MA, hdd

MA
[17179570.832000] Probing IDE interface ide0...
[17179571.120000] hda: Maxtor 6Y080L0, ATA DISK drive
[17179571.400000] hdb: ST380011A, ATA DISK drive
[17179571.456000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[17179573.056000] hdb: max request size: 1024KiB
[17179573.056000] hdb: Host Protected Area detected.
[17179573.056000] current capacity is 66055248 sectors (33820 MB)
[17179573.056000] native capacity is 156301488 sectors (80026 MB)
[17179573.056000] hdb: Host Protected Area disabled.
[17179573.056000] hdb: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
[17179573.056000] hdb: cache flushes supported
[17179573.056000] hdb: hdb1
[17179602.340000] hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
[17179602.364000] hdb: drive_cmd: error=0x04 { DriveStatusError }
[17179602.376000] ide: failed opcode was: 0xef
[17179603.280000] hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
[17179603.292000] hdb: drive_cmd: error=0x04 { DriveStatusError }
[17179603.304000] ide: failed opcode was: 0xef
I don't know what "Host Protected Area" is but I am assuming it's because most of the disk was unpartitioned. I have since created a partition hdb2.
The strange thing is that hdb1 is a linux swap area which IS CURRENTLY MOUNTED and is BEING USED as a swap. My current instalation; Mepis 6; saw two swap areas hda2 and hdb2 and activate them.
I have been adviced it may be the cable but why only the slave drive? The other alternative is the ide on the M/B but it appears to read it OK.
Any Clues will be helpful.
grabro