Comments on: Samsung HD753LJ SATA HDD 750 GB

By: Wim Bervoets

Wim Bervoets — Mon, 23 Nov 2009 10:11:59 +0000

If you can’t get your BIOS to recognize your HDD, you could try asking for help at http://www.wimsbios.com/forum/my-hard-drive-isn-t-recognized-f26.html, maybe there is a patched BIOS available.

Wim

By: Marvin

Marvin — Fri, 20 Nov 2009 08:59:50 +0000

AFAIK drive size is independent of SATA speed setting. Have you checked Samsung’s ES Tool for a drive size setting? Checked in another friend’s PC that can handle larger sizes what your drive shows up as there? If there’s no BIOS update for your mainboard it just won’t detect more than that, I’m afraid.

By: Freak

Freak — Fri, 20 Nov 2009 02:53:13 +0000

Yo i got the same prob with my Samsung HD753LJ SATA HDD 750 GB but 2 things are really odd.1st in the bios it only shows 131gb but its a 750gb i got it off a friend that told me he set it down so it could work on his old pc.How can i get the 750gb back? iv tried switching it a couple of times from 1.5 to 3.0 and back but still kinda screws me in HSTools i cant set the umda it hangs or kicks me back out 2 dos.Otherwise the harddrive works fine,drag n drop install everything just 131gb im so frustrated.I think once as i tried 2 erase the drive it said somthing bout SA out of stacks and a service code=AJ36 can anybody help or has whitnessed the same?

By: Matthias

Matthias — Mon, 16 Feb 2009 22:36:25 +0000

Thank’s a lot, the procedure works really fine.
I had the same issue with a HD502HI and VIA8237 controller. Updating the BIOS and so on was without any effect. After following your instruction the drive was detected by the controller and is running well.
I was in contact with Samsung support for two times cause of this problem, -> save your time and let them sleep.

By: Marvin

Marvin — Thu, 12 Feb 2009 17:19:42 +0000

D’oh! Why don’t you try yourself? Obviously the tool’s functions has mixed up labels. So 1.5 -> 3.0 is 3.0 -> 1.5 and the other way round. If you set it now to 1.5 it should be 3.0 and not work in a board that supports only 1.5.

By: moesfeld

moesfeld — Thu, 12 Feb 2009 17:03:14 +0000

shure but will it really switch to 3.0 since it did not when I used it the first time it actually switched to 1.5 even when selecting 1.5 -> 3.0

By: Marvin

Marvin — Thu, 12 Feb 2009 06:02:16 +0000

On a board that can handle 3.0 you can of course switch back to the higher speed with the same tools.

By: moesfeld

moesfeld — Wed, 11 Feb 2009 17:13:00 +0000

WOW!!!!
This really worked out! I selected the WRONG 1.5 -> 3.0 and now my Spinpoint F1 320 Gb works on my Asrock K7VT4A Pro.

But what if I upgrade to SataII board will the drive be stuck @ 1.5. I´m asking because doing 1.5 – 3.0 again might not work since it switched my drive from 3.0 to 1.5. Or is it a kind of “toggle” Mode?

By: Marvin

Marvin — Wed, 21 Jan 2009 14:51:07 +0000

Nice this one worked for you. But on my board the drive would not even show up in the BIOS.

By: Richard

Richard — Tue, 20 Jan 2009 09:20:30 +0000

OK, after having the same problem as you guys, i followed all instructions i found on the problem. I am using an older foxconn motherboard 945G series. I followed Kens tutorial at first with no success, not saying it was wrong, but it didn’t work for me. I struggled for a week before i decided to buy an external enclosure for it to run through USB, as another site had suggested. Still no success in the caddy. By now my head is spinning, so i thought the drive was faulted, so i made a return request on Ebuyer, and had to phone them. Boy am i pleased i did. The nice tech chap ran me through some questions and i explained it all. It shows up in bios, and when windows boots it installs the device driver, but no drive appears. So he said, click start, go to computer and right click and press manage, this opens up a drive manager, in there you should see the hard drive, right click on the drive which should be unallocated space and format, simple as that. If you can’t format, restart your system and follow the steps again, that’s how i did it. Apparently this drive has an issue with older chipsets where the drive installs but does not initialise. That’s all it was for me, so maybe anyone out there who is still having problems can combine this with kens tutorial and hopefully you will sort it out. Thanks for all the info, helpful or not.