Amiga and 'new age' HDDs
 

Well, here is some strange question i think, becouse i lost some time for google about problem kind of this. So, i have a1200 board. Board is worked. If i attached any 'OLD' HDDs (i mean on 800mb of size,or on 1.2gb, on 4gb) as MASTER (as MASTER by jumpers and as MASTER by cabble). It is OK. BootMenu give me name of partitions, and can boot from it if partition bootable. Or, can boot from floppy disk and can view this HDD by HDDTOOLBOX. Well, standard situation.

Well, next stage. If i try to put as MASTER any 'new age' HDDs (on 40gb, on 20gb, on 80gb (samsung basically) ). Amiga just can't watch it. HDDTOOLBOX said 'no disk', bootmenu said 'no disk'. And nothink about normally detect of harddrive. But, here is not all problem :)

If i put up as MASTER old hdds (any, 800mb,4.gb) and put as SLAVE 'new age' HDD, amiga detect perfectly botch drivers ! And i can disable from bootmenu, old hdd, and boot from new. So, here is problem. Why i can't and how i can setup only ONE 'new age' HDD.

But, here is not all agayn. Some times i was using it (i do not know agayn how it possible, and what it's can be or can't be). For example, i put 'old' hdd as MASTER, 'new age' HDD as SLAVE, boot from master, setup by hddtoolbox 'new age' hdd, put off 'old' hdd , and 'new age' hdd work ! boot is good and bla bla bla. But it's not all the time. If i start to try put CD-DRIVE (40x speed) as SLAVE, agayn nothink to work. If i put as SLAVE 'old' CD-DRIVE (2x speed) it is work !

But of course, i do not want using old monsters for solve this problem. What is it ? New hardware so fast that amiga can't detect it ? (but why is detect possible with old drives ?).

Anyway, any ideas will good. Maybe someone already know how it solve. Will good to know.

Thanks all for answers.

I think first of all you have to tell us about your system set up.
- Kickstart version
- Workbench version
- type of Hard disk / CD-Rom(name of the company)
- do you use a buffered IDE interface?
It will help us to find the problem much quicker.

Well, it is not standart situation ?
Kikstart version 3.0 (harware) and i rekick it on 3.1 by blizkick. But, i want to said, that some times, 'new age' hdds work alone as master (i mean that 3.0 kickstart some time detect hdds, so, i think it is not kickstart problem (i hope).

Workbench version .. i want to said, that this hdds have already installed system (3.9 bb2), and already bootable. Bot bootmenu do not see it (so, i hope wb problem not here too ?) Anyway, i try and from wb3.0, and from 3.1, anyway. I think is hardware problem like fast wakeup ..

Type of disks :
new age hdd - segate baracuda 40gb
new age cd-rom - LG cd-r/rw drive (52/24/52)
old hdd - Conner 540-mb (i think is western Digital)
old cd-rom - (2x speed) - just can't read (all words is unreadable for time), but if i remember correctly - it is MITSUMI.

What about buffered IDE's . I try only from standard amiga interface , and witch Fast ATa Mk3. In botch case - the same problem.

Are you running the OLD Fast File System [FFS] or have you formated your disks with SFS[smart file sysytem].

As even under workbench 3.9 with BB2 installed problems in the constant recognition of larger HD's and partitions beyond the 4gig mark have been noticed before by other users....unless a different file system is being used.

File System here is not a problem i think, becouse HDDTOOLBOX can't detect drive. So, all what i want, put up drive as Master, and hddtolbox said me 'here is hdd, yes'. After detect, will time of filesystems.

I think probelm not in file system, amiga on hardware level can't detect it.
(of course hdd is worked)

But anyway, i have on my 40gb drive - 3 partition: system(3gb,sfs), work (3.5gb,sfs), test - (2gb, ffs)

If as you say you have already managed to install a system partition on the 40gb drive with workbench 3.9 , which I take you have made a bootable partiton.

And since you say your using a fast ata IDE interface is this problem about basic ide detection as different drives are recognised by ther position in the chain ??

woody57:
yes, as i said it can be detected by 2 hdds on cable, but per one can't.
anyway, i think i found problem - bad cabble for me.

so, thanks to all for time, i hope problem is solved :)