DTL-H10000 Boot issues

I've made some little progress but I think to have discovered only bad things.
I've tried to log on the linux side using the credetials you suggested me and the first one worked (root:Administr)
tryed to launch DSEDB with no luck:
http://imgur.com/a/nZGmQ
after that I've tried to run the complete test from the web interface and it reported a lot of issues(sw in TOOL and DVD position):
https://drive.google.com/open?id=0B_3-8mst-fI7cHkwYkdRdGp4YTA

I'm beginning to believe that there's no way to get this tool properly working.

What do you think guys?

thank you

 

It looks like it couldn't run "eeload" and "iopload", and so everything after that probably depended on those two. It seems alarming, but your TOOL is undoubtly still working to a certain extent.
I don't know why you couldn't connect dsedb to dsnetm on the TOOL itself, but you aren't actually the first to have this problem. Anyway... the tests have shown that dsedb can be used to run software.

Given that it appears to be fine when the switch is in the WS mode position, there should be something different about the path taken when the switch is in the TOOL mode. Probably related to the DVD emulator because that is the only thing unique about your TOOL.

I'm no guru on TOOL repairs because I don't specialize on hardware. But I would take a look at the installation of the T14000. And probably image the HDDs as the same time.
unclejun uploaded the T14000 manual, which shows how it is connected.
Maybe even try the TOOL without the T14000 connected.

 

I've tried to remove the T14000 from the tool and turn it on again without it, but unfortunately it has always same behaviour.
Another strange thing I've noticed (ir maybe it's normal) is that on the linux's side boot screen the second hdd is not found:
http://imgur.com/a/6xvyL

 

The second HDD isn't connected to the Linux SBC iirc, it's connected somewhere else. I don't think it would relate to the issues you're having.

 

Did you attempt to put it back afterwards?

Yeah, the 2nd HDD is connected to your T14000. On other TOOLs, it would be connected to the AIF.

 

From watching your video, it fails to load the dvdserv driver psxss.o due to a busy device or resource, maybe the emu hdd is failing...
Then it fails to load the psxss62.o driver, complaining that it was compiled for the 2.2.14-5 kernel while you're running 2.0.36, which is the correct kernel version for the Pentium233 SBC model.

It loads dsnetm without errors, so dsedb should work...was that in Tool or WS mode?
What happens if you run dsidb?
You should dump both hdd as soon as possible.

 

Unless I was mistaken, he ran two diagnostic tests; one in WS mode that had nearly all passes. The later one was in TOOL mode, which oddly couldn't have iopload and eeload run. As tests could be run via dsedb, surely that means that the TOOL's main functions are fine?

I guess that because the T14K couldn't be initialized, the TOOL is left in a half-booted state.

 

His rom version seems quite old, in both test logs.
We had some old threads with similar issues, in the first one a chat between a user and scea dev support about reflashing the rom,which includes some info about the back dipswitches:
http://assemblergames.com/l/threads/the-max-parris-faulty-ps2-tool-tread.15498/page-6#post-231922
http://assemblergames.com/l/threads/tool-drives.14887/page-2#post-220371
http://assemblergames.com/l/threads/tool-dsedb-help.45522/#post-666811
http://assemblergames.com/l/threads/dtl-t-10000-appear-to-fails-during-play-dvd-games.22593/

 

Sorry for the late reply but today I was very busy unfortunately.
I'm not an expert of this particular hardware but I was thinking to try to clone the HDDs in 2 other ice HDD I have, could it be useful?
Do I have to use a particular sw to clone those HDDs?
If for example one of them is already corrupted is there a way to do some sort of new installation?

Thank you everyone for the help, those last messages let me hope a bit to see this tool to work again

 

No, you don't need the switch to be in any special position. Just clone both HDDs if possible, with your favourite tool. Personally, I used Clonezilla, but you could use other tools as well. Using the Linux DD tool would do as well, but inappropriate use of it is dangerous.

The reason why we are suggesting that you clone your disks, is because there is no way to make a clean installation onto a new disk; until today, the only way is to write somebody's image.
I don't know if the T14000 HDD must contain anything. But if it can be managed with the T14k tools alone, then it will probably work if you replaced it with a new disk.

 

Ok thank you, just another question to be sure.
I've read that the HDDs must be at least 30gb to contain all the data and sometimes the tools have 2 40gb HDDs. I have a friend that works with ATM and he can still find me some brand new ide HDDs but the smallest size he can find is 80gb is that a problem?

 

not at all.

But for the PS2 side (the HDD PS2 games can see as the PS2 own HDD, which attaches to the PCMCIA card slot outside the tool) it need to be a official SONY harddrive.

http://assemblergames.com/l/threads/for-sale-new-dtl-h20400-ps2-hdd.29744/ This has the HDD but is missing the PCMCIA card. It used to come as a kit (hdd + powersupply + pcmcia card) in a white box, but for some weird reason a lot of those kits were parted of their pcmcia cards and are being sold as HDD + power supply now. That HDD will work on the PS2 TOOL and on PCMCIA debugs (PS2 TEST).

The internal HDDs are not visible to the games at all.

 

Ok, I removed the HDDs today but at the moment at home I have only one ide hdd..so for now I'll dump one of them in this ide I've got and the other one in a sata hdd just to store the data (I don't think that trying the sata hdd with a converter like I do for the retail consoles could be a good idea). So for the moment do you suggest to change the new ide with the actual master hdd or with the slave hdd (the one connected with the T14000)?

 

Connect those HDDs to a PC with OS which can read S.M.A.R.T. attributes and have the HDDs checked for health. Any which is bad, have it replaced. It's that simple.

 

The T14000's HDD makes a lot of noise but it seems to be still OK from the tests, the main HDD instead has some problems, I hope to be in time to clone it
http://imgur.com/a/h9x0A

 

The fastest method I had to clone the main HDD was with Easeus (did not have a pendrive with clonezilla ready). Anyway the cloning process went good but even with the new HDD I have the same error in the boot sequence

 

What model are them? The MAXTOR "ROMULUS" (4D040H2) isn't that horribly noisy but the SEAGATE ST340823A is horribly noisy. There's also a IBM Deskstar type which I don't recal the model number right now.

After those SONY switched to MAXTOR models in the Fireball 3 range or a member of that SEAGATE model family which was used on classic XBOX units. Those are much, much quieter than the early PS2 HDDs.

Regarding the boot up error, you might have the PS2 side flash corrupted.

It's partitioned in two 2MB windows. You can boot the unit in WS mode and issue a flash command with a parameter which tell the flasher to write to the inactive portion of the flash (the flash region is 4MB big but the PS2 side only uses half of the area on each mode, toggling the TOOL/WS switch toggle the swap of the two flash regions within the 4MB window.).

These commands are meant to be issued on the development PC, not on the PS2 TOOL linux terminal.

 

The T14000's hdd (the louder one) is a IBM deskstar, the main hdd is a Sony branded hdd 4D040H2.

About trying to reflash the TOOL rom that sound very interesting but I still have to figure out how to do that.
I need to have the proper SDK (that matches with the rom version) on the PC but the only 2 procedures I've found are that linked from unclejun here:
http://assemblergames.com/l/threads/the-max-parris-faulty-ps2-tool-tread.15498/page-6#post-231922
Seems to be a little different from the one you suggested to me.

Are those the same that you was referring?
I apologise for my noob questions but I'm trying to learn as as fast as possible (and trying to make less questions as possible)

Thank you guys for all your patience

 

You're confused. The point of flashing the TOOL is actually make it match the SDK you're trying to use. Get SDK 3.0.x here on the forum, install it and flash the tool with the image which comes with it.

You don't need to find a SDK that matches the TOOL as it is now.

 

Yeah, a lot!

Ok I'll try to do that, thank you a lot for now, and again thanks for the patience