(problem) system freezes when trying to access hdd

[dstarfire]

I'm trying to replace the 20gb hard drive I've been using with a 100gb model. However, whenver an app tries to access the hard drive, the system seems to freeze (stays at same screen, doesn't respond to controller input, or soft-reset).

I've tried hdformat, hdloader (self-compiled v0.8c), codebreaker (9.3, retail disc) and ulaunchelf (3.9) to access the drive. hdloader freezes at the initial splash screen, ulaunchelf freezes at "loading hdd modules" and neither codebreaker nor hddformat make it to their splash screen.

The drive is recognized in windows and I've even formatted it with winhiip 1.7.6, with no problem. I tried reinstalled the original drive, and it still works just fine.

The drive I'm trying to install is a Seagate barracuda model #ST3120026A, with jumper set to master (I've tried switching to cable select with no luck). According to the compatibility list, this drive is supposed to be compatible. The old 2ogb drive is also a seagate barracuda (set to master), so I've had good luck with them.

I've even tried leaving hdloader at it's splash screen overnight, thinking it might just take a long time to recognize such a large drive for the first time, but no luck.

Can somebody please help me?? I'd really like to get this drive working, and I've tried everything I could think of or dig up.

[amp2006]

did you tried to use Another NA ( Network Adaptor ) ?

or check the connection between NA to PS2 or to HDD ..

also check the NA pins .sometimes it get broken

[dstarfire]

Unfortunately, I don't have access to another adaptor to test it with.

However, I did test the same adaptor with another hard drive and it works just fine.
It's the combination of this adaptor and the new hdd that doesn't work. Both of them will work just fine with other devices.

[Bootlegninja]

use a patched HDL from SKSApps. yours may not have the proper patches.

[dstarfire]

trying an 'official' patched version of did no good. Also, a messed up hdloader wouldn't account for the issues with ulaunchelf and codebreaker.

I guess maybe I'll have to look into going the usb route. I do have an external drive enclosure that connects via usb.

[dlanor]

trying an 'official' patched version of did no good. Also, a messed up hdloader wouldn't account for the issues with ulaunchelf and codebreaker.

That is true. But a problem that could account for all these problems is if there is something badly wrong with the low-level format of the HDD. A PC might ignore some such problems, because the PC HDD access routines work differently from those of the HDD drivers for a PS2.

I would suggest using the "Disk Management" console of a Windows system to format the entire drive to NTFS, avoiding the 'quick format' option to ensure that all sectors are renewed. Then use WinHiip to reformat that drive for use in a PS2. And then you should finally try that HDD in the PS2 again, with the same softwares as before. Hopefully it will then work, as all sectors on the entire disk surface should then be readable.

I guess maybe I'll have to look into going the usb route. I do have an external drive enclosure that connects via usb.

Unlike a PC the PS2 can not use the same software methods to access a USB drive and an IDE drive. So with a USB drive you can not use HDLoader at all, but will instead have to use other programs such as "USBAdvance" or "Open PS2 Loader" to run backup games. The latter is recommended, as it is a 100% freeware homebrew project currently being developed and improved at an impressive rate.

But the USB speed of a PS2 is horribly slow compared to what a modern PC uses. This is partly due to the PS2 having only USB 1.1 hardware and partly due to the driver system which seldom approaches the transfer speed limit even of USB 1.1 (slow as that is...).

So the quality of gameplay or video playback from any USB drive is limited on the PS2.

For some games it is fine, especially if they have no high-rez FMV movies, but games like FFX and FFXII will always stutter, freeze, or have other problems in the FMV scenes.

Best regards: dlanor

[dstarfire]

Thanks for the tips dlanor.

I tried your suggestion. I even did a full chkdsk /r on the drive and then a full format in winhiip, with no luck. I also tried the same steps with my 400 GB drive, also a seagate baracuda, but still get the same problems with both of them. I've even tried setting the 32GB limit jumper, and no luck.

[amp2006]

then the only thing you have not changed is the NA .

[dstarfire]

Ya know, with all the problems I've had, I'm wondering how long I should wait for hdloader to boot past it's initial splash screen when using a large drive (120gb or 400gb)?

As an update, I tried using an alternate NA with all three drives (the 20gb, 120gb, and 400gb) with no luck. Except, that when if I connect the 120gb, the NA with no drive, and then the 400gb drive, HDLoader will see and format the drive. (bizarre, I know, but I've succeeded with that process twice, without it: not at all).

However, after formatting the drive (using hdloader) and adding several games (using winhiip 1.7.6), hdloader still seems to freeze at the splash screen, even after repeating the drive shuffle process I described above.

I've kind of given up on the 120GB drive as bad, since I got it used. So, unless somebody can come up with another idea, I guess I'm stuck with with my old 20GB drive or blowing $40 on trying a new drive.

[djflexmaster79]

Just a quick thought, Do you have the jumper Setting correct on the HDD's?

DJ