VOGONS


SATA2PATA adapters experience

Topic actions

Reply 40 of 52, by jakethompson1

User metadata
Rank Oldbie
Rank
Oldbie
douglar wrote on 2023-06-28, 14:04:

I found this quote interesting: https://www.reddit.com/r/retrocomputing/comme … o_ide_adaptors/

The problem could be that the cheaper adapters just pass the commands through unchanged while the more expensive adapters bother to emulate ATA commands SATA drives are not mandated to support such as CHS commands. If a CHS-only BIOS is used to access the disk, this makes a difference.

I'm assuming the author was talking about the ubiquitous JMicron stata--pata bridges here when talking about the cheap ones. https://www.jmicron.com/products/list/17

Happen to know if there is a way using Linux hdparm or looking at the ATA IDENTIFY information, etc. whether a drive is one that doesn't support CHS access?
I assume if a drive "doesn't support CHS," that means it still supports PIO mode using LBA addresses?
You remind me that recently I tried a brand new 1TB WD drive through the JMicron converter, and it didn't work. I figured it was different revisions of SATA but maybe this is actually the issue. I went to my old standby drive (Toshiba HDWD110) and it worked just fine.

Reply 41 of 52, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie

Has anyone had success with Marvell-based adapters on the PIIX4 southbridge (BX chipset, for example)?

I tried three different motherboards, they all had the same issue, either a read error during Windows setup or other odd system hangs... Replaced with an old '06 datecode JMicron adapter and the problem disappeared completely.

SSD used is SanDisk U110.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 42 of 52, by darry

User metadata
Rank l33t++
Rank
l33t++
mockingbird wrote on 2023-08-03, 06:13:

Has anyone had success with Marvell-based adapters on the PIIX4 southbridge (BX chipset, for example)?

Yes, please see [1].

[1]
Re: Adding XT-IDE option ROM to Asus P3B-F BIOS [Thanks to DenizOezmen, it actually works!!!]

Reply 43 of 52, by ElectroSoldier

User metadata
Rank Oldbie
Rank
Oldbie

Its shameful Microsoft never added TRIM support to XP.

Ive found the most reliable over long periods of time are the Seagate SSHDs with a SATA to ATA adapter from Startech.
had at least 3 years of daily use and its most than fast enough.

Reply 44 of 52, by darry

User metadata
Rank l33t++
Rank
l33t++
ElectroSoldier wrote on 2023-08-03, 09:38:

Its shameful Microsoft never added TRIM support to XP.

Ive found the most reliable over long periods of time are the Seagate SSHDs with a SATA to ATA adapter from Startech.
had at least 3 years of daily use and its most than fast enough.

An occasional boot from a Linux LiveCD/LiveUSB will allow running TRIM from there, as long as you use a new enough version (mainly kernel) that supports NTFS, trimming NTFS and the disk controller used .

root@bob-VirtualBox:/tmp# dd if=/dev/urandom of=/tmp/ntfsdrive.raw count=1024 bs=1MB

1024+0 records in

1024+0 records out

1024000000 bytes (1.0 GB, 977 MiB) copied, 9.72184 s, 105 MB/s

root@bob-VirtualBox:/tmp# mkfs.ntfs -F /tmp/ntfsdrive.raw

/tmp/ntfsdrive.raw is not a block device.

mkntfs forced anyway.

The sector size was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 512 bytes.

The partition start sector was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 0.

The number of sectors per track was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 0.

The number of heads was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 0.

Cluster size has been automatically set to 4096 bytes.

To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set.

Windows will not be able to boot from this device.

Initializing device with zeroes: 100% - Done.

Creating NTFS volume structures.

mkntfs completed successfully. Have a nice day.

root@bob-VirtualBox:/tmp# mount -o loop /tmp/ntfsdrive.raw /tmp/ntfs

root@bob-VirtualBox:/tmp# lsblk -f /dev/loop18

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS

loop18 ntfs 04F2734611D0D9FC 971.2M 1% /tmp/ntfs

root@bob-VirtualBox:/tmp# fstrim -av

/tmp/ntfs: 971.2 MiB (1018388480 bytes) trimmed on /dev/loop18

Reply 46 of 52, by ElectroSoldier

User metadata
Rank Oldbie
Rank
Oldbie
darry wrote on 2023-08-03, 19:00:
An occasional boot from a Linux LiveCD/LiveUSB will allow running TRIM from there, as long as you use a new enough version (main […]
Show full quote
ElectroSoldier wrote on 2023-08-03, 09:38:

Its shameful Microsoft never added TRIM support to XP.

Ive found the most reliable over long periods of time are the Seagate SSHDs with a SATA to ATA adapter from Startech.
had at least 3 years of daily use and its most than fast enough.

An occasional boot from a Linux LiveCD/LiveUSB will allow running TRIM from there, as long as you use a new enough version (mainly kernel) that supports NTFS, trimming NTFS and the disk controller used .

root@bob-VirtualBox:/tmp# dd if=/dev/urandom of=/tmp/ntfsdrive.raw count=1024 bs=1MB

1024+0 records in

1024+0 records out

1024000000 bytes (1.0 GB, 977 MiB) copied, 9.72184 s, 105 MB/s

root@bob-VirtualBox:/tmp# mkfs.ntfs -F /tmp/ntfsdrive.raw

/tmp/ntfsdrive.raw is not a block device.

mkntfs forced anyway.

The sector size was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 512 bytes.

The partition start sector was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 0.

The number of sectors per track was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 0.

The number of heads was not specified for /tmp/ntfsdrive.raw and it could not be obtained automatically. It has been set to 0.

Cluster size has been automatically set to 4096 bytes.

To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set.

Windows will not be able to boot from this device.

Initializing device with zeroes: 100% - Done.

Creating NTFS volume structures.

mkntfs completed successfully. Have a nice day.

root@bob-VirtualBox:/tmp# mount -o loop /tmp/ntfsdrive.raw /tmp/ntfs

root@bob-VirtualBox:/tmp# lsblk -f /dev/loop18

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS

loop18 ntfs 04F2734611D0D9FC 971.2M 1% /tmp/ntfs

root@bob-VirtualBox:/tmp# fstrim -av

/tmp/ntfs: 971.2 MiB (1018388480 bytes) trimmed on /dev/loop18

Yeah but its a lot of work for so little pay off when you consider the actual performance benefits over a Seagate SSHD.

Page file on an SSD could have some utility though.

Reply 47 of 52, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie
darry wrote on 2023-08-03, 06:38:

Thanks, I had no idea that existed! Unfortunately, it halved the write performance (also tested with the Marvell though not shown here):

Default Intel (Microsoft) Driver:

JMicron - VMM32.png
Filename
JMicron - VMM32.png
File size
11.79 KiB
Views
568 views
File license
Public domain

IAA Driver:

JMicron - IAA.png
Filename
JMicron - IAA.png
File size
11.98 KiB
Views
568 views
File license
Public domain

I confirmed UDMA was enabled with the IAA app (you also have to get that from the extracted data cab because IAA 2.3 will not install the usual way for the BX chipset).

So I guess I'll just stick with the JMicron for this combo.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 48 of 52, by Comos

User metadata
Rank Newbie
Rank
Newbie
douglar wrote on 2023-06-28, 14:04:
I found this quote interesting: https://www.reddit.com/r/retrocomputing/comme … o_ide_adaptors/ […]
Show full quote

I found this quote interesting: https://www.reddit.com/r/retrocomputing/comme … o_ide_adaptors/

The problem could be that the cheaper adapters just pass the commands through unchanged while the more expensive adapters bother to emulate ATA commands SATA drives are not mandated to support such as CHS commands. If a CHS-only BIOS is used to access the disk, this makes a difference.

I'm assuming the author was talking about the ubiquitous JMicron stata--pata bridges here when talking about the cheap ones. https://www.jmicron.com/products/list/17

What do you suppose the "expensive" adapters are?

I have one of these bi directional devices and it doesn't seem to support CHS. https://www.startech.com/en-us/hdd/pata2sata3

What about the Marvell 88SA8052 PATA to SATA Bridge - https://www.marvell.com/content/dam/marvell/e … ief-2015-09.pdf
Or the Genesis Logic GL831 - https://www.arrivalelectronics.co.uk/uploads/ … tasheet_103.pdf

Are there other ones?

Probably depends also on which chipset are they used. So far I never had an issue with JMicron or Marvel.

Reply 49 of 52, by darry

User metadata
Rank l33t++
Rank
l33t++
Comos wrote on 2023-09-18, 11:52:
douglar wrote on 2023-06-28, 14:04:
I found this quote interesting: https://www.reddit.com/r/retrocomputing/comme … o_ide_adaptors/ […]
Show full quote

I found this quote interesting: https://www.reddit.com/r/retrocomputing/comme … o_ide_adaptors/

The problem could be that the cheaper adapters just pass the commands through unchanged while the more expensive adapters bother to emulate ATA commands SATA drives are not mandated to support such as CHS commands. If a CHS-only BIOS is used to access the disk, this makes a difference.

I'm assuming the author was talking about the ubiquitous JMicron stata--pata bridges here when talking about the cheap ones. https://www.jmicron.com/products/list/17

What do you suppose the "expensive" adapters are?

I have one of these bi directional devices and it doesn't seem to support CHS. https://www.startech.com/en-us/hdd/pata2sata3

What about the Marvell 88SA8052 PATA to SATA Bridge - https://www.marvell.com/content/dam/marvell/e … ief-2015-09.pdf
Or the Genesis Logic GL831 - https://www.arrivalelectronics.co.uk/uploads/ … tasheet_103.pdf

Are there other ones?

Probably depends also on which chipset are they used. So far I never had an issue with JMicron or Marvel.

JMicron ones (or at least some chip models) have issues with VIA 686B and Intel ICH4 based IDE ports. (there may be others) Oherwise, they work well.

Mavell ones are reputed to be the most compatible, but there is at least one thread here about a newer chip revision or maybe a counterfeit chip having issues.

Sunplus also makes chips for such adapters. At least one Startech model uses those.

Reply 50 of 52, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie
darry wrote on 2023-09-18, 23:10:

Mavell ones are reputed to be the most compatible, but there is at least one thread here about a newer chip revision or maybe a counterfeit chip having issues.

Sunplus also makes chips for such adapters. At least one Startech model uses those.

Yes, I will have to follow up on the newer, unlabeled chips supposedly not being the same as the older Marvell chips with the logo. I tried to transplant one on my mSATA adapter, but I think I received a non-functioning chip. I'm waiting for my next chip to arrive to test.

Sunplus isn't good either.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 51 of 52, by douglar

User metadata
Rank Oldbie
Rank
Oldbie
darry wrote on 2023-09-18, 23:10:

JMicron ones (or at least some chip models) have issues with VIA 686B and Intel ICH4 based IDE ports. (there may be others) Oherwise, they work well.

I've had trouble using the Jmicron bridges with the Promise PDC-20630 based VLB controllers, which was disappointing because it's been the fastest VLB IDE controller that I've looked at, but my fastest IDE devices are Sata based.

Reply 52 of 52, by darry

User metadata
Rank l33t++
Rank
l33t++
douglar wrote on 2023-09-21, 12:05:
darry wrote on 2023-09-18, 23:10:

JMicron ones (or at least some chip models) have issues with VIA 686B and Intel ICH4 based IDE ports. (there may be others) Oherwise, they work well.

I've had trouble using the Jmicron bridges with the Promise PDC-20630 based VLB controllers, which was disappointing because it's been the fastest VLB IDE controller that I've looked at, but my fastest IDE devices are Sata based.

That's interesting. My experience with PCI Promise controllers
(Ultra 100 and 133, AFAICR) and JMicron has been positive .

So, newer Promise ones sarted working whereas newer Intel ones stopped working, 🤣. We need a compatibility table/reference.