On friday i've finished movind my data to a new hard drive supplied with my ODW. Drive type is Samsung SV4002H 40 GB.
I am unable to use the new drive in my machine. There i have also second hard drive in mobile rack, CDRW (also shipped with ODW) and ZIP drive. The problem is that the Samsung HDD DOES NOT WORK together with any device on one bus. It's no matter whether it's master or slave. Pegasos does not start up for a while, when at last openfirmware prompt comes up i see that there are no devices on IDE bus to which i connected the drive. HDD led is constantly on.
This is not first problem with Samsung HDDs on Pegasos. Previously when i migrated from Amiga i had another problem with 20GB Samsung. It didn't detect reliably, i had to press Reset several times for it to come up. This problem is known as long spinup time. I raised this topic on MorphZone, you can find it there as soon as MZ is up and running.
2 Genesi: PLEASE NOTE THIS! Never use Samsung drives any more!
This problem is even more strange because Samsung drives utilize Marvell chips. This means that Marvell's products are incompatible...

We don't ship Samsung hard disks with the ODW yet? You bought this yourself or..?
Have you tried cable select mode? Are you using the cables we supplied, or some of your own? Are you sure to connect it, when forced set to master/slave, to the correct end of the cable (note the final connector is always master, the middle one is always slave.. you should never ever have to set a jumper since 80-core cables came into existance. Cable select is a mind-numbingly simple technology to implement)

If they are your own make sure they are 80-core, and use flat ones if possible. I know we shipped rounded ones unfortunately with a lot of systems.

Are you sure it does not work even in tandem with the Samsung combo drive? We rely on those being configured for cable select from the factory and thrown at the end of the cable.
The Pegasos will stall during boot if it's looking for devices and they at least attempt or seem to respond to the standard ATA reset. It might be that the drive really does not spin up fast enough (even 5400rpm disks can be a little slow to do that) in the first place, and therefor it would do this like your 20GB did. This is a known firmware "problem" which we could solve in the next update possibly.
Marvell's chips are incompatible with what exactly? Please don't make rash gestures like this.

Neko

Well, I have Samsung SV3064D drive (30 GB) working on one cable together with Samsung CD-ROM (SC-148, 48x). There is a problem of reset needed after power up, but it is not Samsung specific (had the same problem with Seagate 8GB drive). There are no other problems.

> This is not first problem with Samsung HDDs on Pegasos. Previously when
> migrated from Amiga i had another problem with 20GB Samsung. It didn't

When I switched from Pegasos-I to Pegasos-II I wanted to use my
Seagate ST380021A (80GB, Barracuda4) that worked fine in Pegasos
I on the II. But this did not work either. No OF-start with the HD
plugged in. I did a bugreport and included serial debug.

Now a SAMSUNG SV1604N (160GB) works very good on my PegasosII.

So this is not about a brand but more likely about special models.


Regards,
Peter

Now i've replaced my drive with Seagate Barracudda 7200.7 (the same as usually ships with ODW, there are plenty of them at my work) and everything went pretty fine. It works with all devices in all combinations.
So i still think it's some firmware problem. I already told about it to Sven, he said he'll look at it.