Problems with 3.5" - 2.5" connector

[Tempesta]

Hi, I've bought the adapter DT-327A from a local store in Barcelona because
I need to connect the hard disk of my IBM ThinkPad 750E to my desktop's
computer to format it because my laptop came with no floppy nor cdrom drive.

The problem is that my desktop's BIOS detects the hard disk but when I enter
windows, linux or ms-dos, it says it's not present. I can't access it with
fdisk nor fdisk /mbr. The adapter has 2 jumpers but there're no instructions
so I don't know where's the problem.

Thank you in advance for your help!

PS: I've tried to put it as master in the first and the second IDE cable but
didn't work :-(

 

[Arno Wagner]

Hi, I've bought the adapter DT-327A from a local store in Barcelona because
I need to connect the hard disk of my IBM ThinkPad 750E to my desktop's
computer to format it because my laptop came with no floppy nor cdrom drive.

The problem is that my desktop's BIOS detects the hard disk but when I enter
windows, linux or ms-dos, it says it's not present. I can't access it with
fdisk nor fdisk /mbr. The adapter has 2 jumpers but there're no instructions
so I don't know where's the problem.

Thank you in advance for your help!

PS: I've tried to put it as master in the first and the second IDE cable but
didn't work :-(

How does the "not present" manifest itself with Linux? Is it in
the kernel boot-up messages? What kernel version? What HDD model?

On Linux you could try "fdisk -l", to see whether it is listed.
Also as master on the second cable, it should show up as /dev/hdc,
which you can verify with

cat /proc/ide/hdc/model

which should print the hdd model.

Arno

 

[Tempesta]

Arno Wagner va escriure:

How does the "not present" manifest itself with Linux? Is it in
the kernel boot-up messages? What kernel version? What HDD model?

On Linux you could try "fdisk -l", to see whether it is listed.

This is the output when connected as master on the second cable:

[root@unit0 tempesta]# fdisk -l

Disc /dev/ide/host0/bus0/target0/lun0/disc: 40.0 GiB, 40020664320 octets
255 capçals, 63 sectors/pista, 4865 cilindres
Unitats = cilindres de 16065 * 512 = 8225280 octets

Dispositiu Arrenc. Comença Acaba Blocs
Id. Sistema
/dev/ide/host0/bus0/target0/lun0/part1 * 1 1256 10088788+
b Win95 FAT32
/dev/ide/host0/bus0/target0/lun0/part2 1257 4865 28989292+
f Win95 Estesa (LBA)
/dev/ide/host0/bus0/target0/lun0/part5 1257 2512 10088788+
7 HPFS/NTFS
/dev/ide/host0/bus0/target0/lun0/part6 2513 3768 10088788+
b Win95 FAT32
/dev/ide/host0/bus0/target0/lun0/part7 3769 4404 5108638+
83 Linux
/dev/ide/host0/bus0/target0/lun0/part8 4405 4467 506016
82 Intercanvi Linux
/dev/ide/host0/bus0/target0/lun0/part9 4468 4865 3196903+
83 Linux

Also as master on the second cable, it should show up as /dev/hdc,
which you can verify with

cat /proc/ide/hdc/model

This is what I get:

[root@unit0 tempesta]# cat /proc/ide/hdc/model
IBM-DARA-206000

which should print the hdd model.

But if i do "fdisk /dev/hdc" it says:

[root@unit0 tempesta]# fdisk /dev/hdc

No es pot obrir /dev/hdc

Which in catalan means that it can't open /dev/hdc

The adapter I use has some jumpers but I don't know where the problem is, it
came with no instructions :-?

Is seems as it recognizes it but I can't access /dev/hdc. Any idea?

Thank you very much in advance!

 

[Arno Wagner]

Arno Wagner va escriure:

In comp.sys.ibm.pc.hardware.storage Tempesta <[email protected]>
wrote:

[...]
This is the output when connected as master on the second cable:

Disc /dev/ide/host0/bus0/target0/lun0/disc: 40.0 GiB, 40020664320 octets

^^^^^
But what is this??? Looks like an IDE disk with SCSI-addressing!
And it is not the IBM disk, but likely your primary ide, since
the IBM has only 12GB. Maybe fdisk cannot find the corret device?

255 capcals, 63 sectors/pista, 4865 cilindres
Unitats = cilindres de 16065 * 512 = 8225280 octets
[...]
But if i do "fdisk /dev/hdc" it says:

[root@unit0 tempesta]# fdisk /dev/hdc
No es pot obrir /dev/hdc

Which in catalan means that it can't open /dev/hdc

Maybe fdisk does not access /dec/hdc, because it is not there. I think
with the above device sheme it would be something like

/dev/ide/host0/bus0/target1/lun0/disc
or
/dev/ide/host0/bus1/target0/lun0/disc
or
/dev/ide/host1/bus0/target0/lun0/disc

or the like. Do you use SCSI-emulation for your IDE disks? In addition
this seems the scsi-addressing-variant, where every partition gets
its own device. Usually this is done in order to avoid them shifting
around when SCSI targets are added or removed. But with SCSI-emulation
on ide it makes less sense, since IDE-devices do not move around
when others are added or removed.

If so, just switch the emulation off for hdc or try a
"rescan-scsi-bus.sh -c" to find out under which device device the
IBM disk can be found.

You can also post your kernel-commandline here ("cat /proc/cmdline")
to shed some light on this.

I don't think jumpers will help. If the kernel can get the model
number, then the interface is working.
At the moment I think the disk is used with SCSI-emulation. If so,
it is not accesable as /dev/hdc.

Arno