@Archer57

Yes, I appreciate Startech is overpriced - they somehow gives me a little quality assurance. For personal projects Ali is fine of course.

Ok, I'll try a JM as well - I'd imagine Linux is probing the HDDs in a different way and somehow it fails to detect the proper speed - as this works with the original HDD, the process "somehow" works 🙂

I've mounted the HDD on my Linux, this is Fedora 2.6.15 and I modded the menu.lst file into /boot/grub

Apologies for the screen photo - this is a live version of linux.

If this works, I'd like to check whether I can amend the actual installer that is provided by the manufacturer - after all it's a big script installing Linux.
I'd also need to make sure the system doesn't restore the original defaults - following a crash or something similar. There is a update-revert partition (which I am not concerned about) and a "home-backup" partition.

Let me check if this works first. Then, I'll try the other Startech adaptor and maybe an Aliexpress JM based one. If none work, well the software trick is the only thing.

Edit
The parameter is read, this is from MESSAGES

1Aug  7 15:02:59 xd10 kernel: Kernel command line: ro root=LABEL=/ rhgb quiet noapic libata.force=80c

However the parameter is not recognised

1Aug  7 15:02:59 xd10 kernel: Kernel command line: ro root=LABEL=/ rhgb quiet noapic libata.force=80c
2Aug  7 15:03:00 xd10 kernel: Unknown boot option `libata.force=80c': ignoring

I've looked online and libata.force doesn't seem to be available with 2.6.15. It this the end of the line??? 😳

update2

I've tried connecting the HDD directly to the MB's SATA controller and it works with ATA133

1	Line 179: Aug  7 09:25:01 xd10 kernel: ata1: dev 0 ATA-10, max UDMA/133, 1953525168 sectors: LBA48
2	Line 180: Aug  7 09:25:01 xd10 kernel: ata1: dev 0 configured for UDMA/133

Why am I using PATA?

Three reasons:
1. Revision 1 of these boxes have a PATA only motherboard, so I'll have to find a solution there too. And yes, Linux runs at UDMA/33 there too with the adaptor.
2. Not all SATA HDDs work on this board and my concern is that the manufacturer just didn't validate the SATA controller/driver combo. So I thought that keeping it via PATA was a better route
3. In the logs, Linux is unable to log the status of SATA drives. So if something happens and I extract logs, well I wouldn't be able to determine the health of the HDD

At least I have a feasable route for the SATA boards (Asus). Now need to find a working one for the PATA-only ones (Aopen)

Hmm, yeah, did not think of that. If older kernel does not have such parameter (which was probably added because people were having this exact issue) i am not sure what can be done, other than updating the kernel which likely is not acceptable.

You could try a solution from here, may be that will work: https://www.linuxquestions.org/questions/debi … p-741950-print/

If that does not work the issue may have no solution as this is basically a kernel bug.

tony359 wrote on 2025-08-07, 13:25:

@darry […]
Show full quote

@darry

Startech made two, the current model has a Marvell chip which is the one I am using.

The attachment ide2sat2.b.jpg is no longer available

The MB is indeed detecting the HDD as UDMA mode 5 which is UDMA/100. So somehow Linux is probably probing the drive and decides it's a UDMA/33 one.

The attachment WhatsApp Image 2025-08-07 at 14.31.03_e08ca579.jpg is no longer available

The attachment WhatsApp Image 2025-08-07 at 14.31.03_533ec0a1.jpg is no longer available

So tweaking Linux is my only option?

Where do I find that file, @Archer57 ?

Startech made and still makes a few. FWIW, someone mentioned issues with are apparently newer rev. Marvell chips. I have no idea if this might be one such issue.

At least some JMicron based adapterd seem to have isssues running in DMA modes on Intel ICH4 (and possibly newer) and Via 686B (and possibly other Via IDE controllers). JMicron and Micron pass TRIM, the Pericom Sunplus ones do not (AFAICR, but I posted about it somewhere here previously).

Marvell :
https://www.startech.com/en-ca/hdd/ide2sat
https://www.startech.com/en-ca/hdd/ide2sat2

JMicron :
https://www.startech.com/en-ca/hdd/ide2sat25

Pericom Sunplus (mine at least) :
https://www.startech.com/en-ca/hdd/pata2sata3

Archer57 wrote on Yesterday, 01:40:

You could try a solution from here, may be that will work: https://www.linuxquestions.org/questions/debi … p-741950-print/

Thanks A LOT for that, I did some search yesterday but because the kernel is very old it's almost impossible to find relevant information.

I'd love to try that option. However, I do not have credentials for the running linux so I can only do that "offline" from another computer running linux. I can edit that file and save it but can I rebuild the initrd image from an offline console?

From the looks of things, I believe you're going about it the correct way; adding it to the GRUB kernel line should be OK, and is correct.
You might want to try giving the full parameter, instead of omitting the [ID] section (see bold text above) and see if that helps?

I was also about to try this before I realised the whole code was not supported - but maybe I should try that anyways.: libata.force=0:80c
But neonsignal there seems to suggest it won't work via GRUB, which is a shame.

darry wrote on Yesterday, 05:08:

Startech made and still makes a few. FWIW, someone mentioned issues with are apparently newer rev. Marvell chips. I have no idea if this might be one such issue.

Thanks. I've got the ide2sata2 which is the current model. The ide2sat25 is discontinued and I cannot find it anywhere. In any case, it has ports on the sides and I have a power connector just adjacent to the IDE ports so no luck.

The pata2sata3 is the "SUNPLUS" chip I was talking about, not sure if they've changed it since you got it. This is the one I've ordered and I'll test it later.

tony359 wrote on Yesterday, 08:53:

Thanks. I've got the ide2sata2 which is the current model. The ide2sat25 is discontinued and I cannot find it anywhere. In any case, it has ports on the sides and I have a power connector just adjacent to the IDE ports so no luck.

The pata2sata3 is the "SUNPLUS" chip I was talking about, not sure if they've changed it since you got it. This is the one I've ordered and I'll test it later.

Sorry for my brain fart about that last one, it is indeed a Sunplus chip.

EDIT: Fixed my broken quote.

ahah no worries.

I don't need TRIM - my old Linux doesn't support it anyways, it was the whole point of going for an adaptor - so happy days.

I should get that adaptor today, I am really hoping it just works or I'm in a lot of Barney. 😀

SUCCESS!

The new adaptor from Startech works, Linux now sees the drive as UDMA(100). I am so happy!

1Aug  8 17:10:37 xd10 kernel: hda: WDC WD10EZEX-00BBHA0, ATA DISK drive
2Aug  8 17:10:37 xd10 WatchDog[1874]: Starting
3Aug  8 17:10:37 xd10 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
4Aug  8 17:10:39 xd10 kernel: hdc: SONY DVD-ROM DDU1615, ATAPI CD/DVD-ROM drive
5Aug  8 17:10:40 xd10 kernel: hdd: SONY DVD-ROM DDU1615, ATAPI CD/DVD-ROM drive
6Aug  8 17:10:40 xd10 kernel: ide1 at 0x170-0x177,0x376 on irq 15
7Aug  8 17:10:41 xd10 kernel: hda: max request size: 512KiB
8Aug  8 17:10:41 xd10 kernel: hda: 1953525168 sectors (1000204 MB), CHS=65535/255/63, UDMA(100)
9Aug  8 17:10:41 xd10 kernel: hda: cache flushes supported

Thank you SO MUCH to all for the help.

Now, that being said, the HDD I used to start the player for this test showed the same errors at boot. The 200GB drive I was using directly via SATA until earlier on, seemed happy.
So I still feel that the size of the partition is the main issue - but of course I couldn't consider the job done if the drives were running at 1/3 of the speed.

I've noticed that the partitions are all sized the same except "contents" which is "the rest of the HDD" basically.
I'll see if I can spot where in the installation script the drive gets partitioned, Ideally I'd like to make a custom installer.

Failing that, I'll buy a 200GB drive, install the SW on it and then clone it on the 1TB one.

But right now I am happy, if this adaptor didn't work, it was a problem. Also, Kudos to Startech, the box contains the power adaptor AND the sata cable which I thought I'd have to buy myself.

I'll update with the partition size 😀

tony359 wrote on Yesterday, 16:18:

SUCCESS! […]
Show full quote

SUCCESS!

The new adaptor from Startech works, Linux now sees the drive as UDMA(100). I am so happy!

Copy code to clipboard

1Aug  8 17:10:37 xd10 kernel: hda: WDC WD10EZEX-00BBHA0, ATA DISK drive
2Aug  8 17:10:37 xd10 WatchDog[1874]: Starting
3Aug  8 17:10:37 xd10 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
4Aug  8 17:10:39 xd10 kernel: hdc: SONY DVD-ROM DDU1615, ATAPI CD/DVD-ROM drive
5Aug  8 17:10:40 xd10 kernel: hdd: SONY DVD-ROM DDU1615, ATAPI CD/DVD-ROM drive
6Aug  8 17:10:40 xd10 kernel: ide1 at 0x170-0x177,0x376 on irq 15
7Aug  8 17:10:41 xd10 kernel: hda: max request size: 512KiB
8Aug  8 17:10:41 xd10 kernel: hda: 1953525168 sectors (1000204 MB), CHS=65535/255/63, UDMA(100)
9Aug  8 17:10:41 xd10 kernel: hda: cache flushes supported

Thank you SO MUCH to all for the help.

Now, that being said, the HDD I used to start the player for this test showed the same errors at boot. The 200GB drive I was using directly via SATA until earlier on, seemed happy.
So I still feel that the size of the partition is the main issue - but of course I couldn't consider the job done if the drives were running at 1/3 of the speed.

I've noticed that the partitions are all sized the same except "contents" which is "the rest of the HDD" basically.
I'll see if I can spot where in the installation script the drive gets partitioned, Ideally I'd like to make a custom installer.

Failing that, I'll buy a 200GB drive, install the SW on it and then clone it on the 1TB one.

But right now I am happy, if this adaptor didn't work, it was a problem. Also, Kudos to Startech, the box contains the power adaptor AND the sata cable which I thought I'd have to buy myself.

I'll update with the partition size 😀

EDIT: Glad it works.

You could try something like this to artificially cap the drive to a smaller size using hdparm and setting an HPA, as mentioned in this post.
Re: Here's an idea: using high endurance (micro)SD cards meant for continuous video recording as storage for retro gear

Thanks!

The installer from the manufacturer completely wipes the drive, partition and format it - if I understand right, changing the geometry won't survive that? Or am I mistaken?

I'm confident a 2004 install script for Linux is not going to be rocket science, I'm hopeful to find the line where the partitions are created and just amend that. That would also mean: no need to clone and anybody could re-install the machine without having to do anything.

Let me check the installation ISO - I might need some help again!

On the adaptor subject, I think I'll also buy a JMicron one from Ali, just for my own curiosity. Is there a recommended chip model?
That said, I really like the one I am testing now: it plug in the motherboard which means: NO UGLY FLAT CABLE! 🙂

tony359 wrote on Yesterday, 17:42:

Thanks! […]
Show full quote

Thanks!

The installer from the manufacturer completely wipes the drive, partition and format it - if I understand right, changing the geometry won't survive that? Or am I mistaken?

I'm confident a 2004 install script for Linux is not going to be rocket science, I'm hopeful to find the line where the partitions are created and just amend that. That would also mean: no need to clone and anybody could re-install the machine without having to do anything.

Let me check the installation ISO - I might need some help again!

On the adaptor subject, I think I'll also buy a JMicron one from Ali, just for my own curiosity. Is there a recommended chip model?
That said, I really like the one I am testing now: it plug in the motherboard which means: NO UGLY FLAT CABLE! 🙂

Setting an HPA is persistent. This is done at a low level within the drive. An installer script, OS installation, partitioning tool, etc, will not change that.

ah interesting I misunderstood! That would be amazing!

I see from hdparm manual that the "p" is for permanent. Absolutely amazing. I'll try that.

How do I calculate the number of sectors? How big is a sector?

tony359 wrote on Yesterday, 18:41:

ah interesting I misunderstood! That would be amazing!

I see from hdparm manual that the "p" is for permanent. Absolutely amazing. I'll try that.

How do I calculate the number of sectors? How big is a sector?

Sectors are 512 bytes in size.

Assuming the disk is /dev/sdb (adjust as appropriate) when connected to a modern Linux PC (I don't recommend doing this on that old custom Linux), you can get the current sector count by running [1] and assuming you want to reduce the capacity to 1/2 less than 127GB, you could run [2] and power cycle the system and drive (not strictly necessary) and run [3] to verify. Then you can repartition the drive or wipe it. See [4] for more examples.

Be careful, take your time and take notes. While this is nominally reversible (I have done so several times), you should always be mindful when using hdparm for things like this.

Potential caveats:
- I have in motherboard whose BIOS does not like this and misdetects the drive as 8GB
- Doing this over a USB to SATA adapter was not recommended when I last read about it. I still did it this way and it worked for me.

[1]

1root@bob-VirtualBox:~# hdparm -g /dev/sdb
2
3/dev/sdb:
4 geometry      = 30401/255/63, sectors = 488397168, start = 0

[2]

1sudo hdparm --yes-i-know-what-i-am-doing  -Np268435456  /dev/sdb

[3]

1root@bob-VirtualBox:~# hdparm -g /dev/sdb
2
3/dev/sdb:
4 geometry      = 16709/255/63, sectors = 268435456, start = 0

[4]
http://blog.asiantuntijakaveri.fi/2012/07/res … isk-on.html?m=1
https://www.tobsan.se/update/2014/08/16/hdparm.html

Thanks for taking the time to put that together for me, I appreciate it!

I can test with an old drive I have - in any case it's not the end of the world if I brick it! 😀
I'm planning to use a USB adaptor too, mainly because I don't want to fiddle with Linux and the 7 HDDs I have in my own desktop! Hopefully it'll work.

Fingers crossed it works as this would be the simplest solution. And most importantly, it fixes those "errors" I see on the player which seem to be only happening when a large HDD is installed.

Next drives will be 500GB though, I didn't realise WD still sell them through their website. It feels a bit less wasted as I plan to downgrade them to 160GB, the largest drive I've seen installed in those boxes from the factory.

Will update soon, thanks for now! 🙂

tony359 wrote on Yesterday, 16:18:

SUCCESS! […]
Show full quote

SUCCESS!

The new adaptor from Startech works, Linux now sees the drive as UDMA(100). I am so happy!

Copy code to clipboard

1Aug  8 17:10:37 xd10 kernel: hda: WDC WD10EZEX-00BBHA0, ATA DISK drive
2Aug  8 17:10:37 xd10 WatchDog[1874]: Starting
3Aug  8 17:10:37 xd10 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
4Aug  8 17:10:39 xd10 kernel: hdc: SONY DVD-ROM DDU1615, ATAPI CD/DVD-ROM drive
5Aug  8 17:10:40 xd10 kernel: hdd: SONY DVD-ROM DDU1615, ATAPI CD/DVD-ROM drive
6Aug  8 17:10:40 xd10 kernel: ide1 at 0x170-0x177,0x376 on irq 15
7Aug  8 17:10:41 xd10 kernel: hda: max request size: 512KiB
8Aug  8 17:10:41 xd10 kernel: hda: 1953525168 sectors (1000204 MB), CHS=65535/255/63, UDMA(100)
9Aug  8 17:10:41 xd10 kernel: hda: cache flushes supported

Thank you SO MUCH to all for the help.

Now, that being said, the HDD I used to start the player for this test showed the same errors at boot. The 200GB drive I was using directly via SATA until earlier on, seemed happy.
So I still feel that the size of the partition is the main issue - but of course I couldn't consider the job done if the drives were running at 1/3 of the speed.

I've noticed that the partitions are all sized the same except "contents" which is "the rest of the HDD" basically.
I'll see if I can spot where in the installation script the drive gets partitioned, Ideally I'd like to make a custom installer.

Failing that, I'll buy a 200GB drive, install the SW on it and then clone it on the 1TB one.

But right now I am happy, if this adaptor didn't work, it was a problem. Also, Kudos to Startech, the box contains the power adaptor AND the sata cable which I thought I'd have to buy myself.

I'll update with the partition size 😀

Glad it worked and good to know there are differences between different chips/adapters here and it is not simply broken with all of them. This is not a big deal with normal linux installs as those are easy to add the parameter to, but still.

Also regarding access to running linux - if you really wanted to - you could reset root password and gain access, given you have filesystem access. This may make some things easier to troubleshoot...

Yes, great to know some are working - though also disappointing to know that not everything works and I believe none is perfect!! But I like this more than the other one so happy days.

Root password: oh is that possible? How? 🙂

Yeah, resetting root password in linux when you have physical access is not hard, there are many ways.

Take a look at this: https://wiki.archlinux.org/title/Reset_lost_root_password

The easiest option probably is the last one, or you could just do this: https://unix.stackexchange.com/questions/7631 … c-shadow#533599

Thanks! It’s simpler than windows! 😂

It would definitely help having live access to the system for diagnostic purposes.

Cheers!