Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

Hello,

I'm having problems with my Touchsmart PC I can't boot it up since it can't find the C drive. My PC has a Seagate 7200.11. Does this fix work in a HP Touchsmart PC?

0

Share this post


Link to post
Share on other sites

Hello,

I'm having problems with my Touchsmart PC I can't boot it up since it can't find the C drive. My PC has a Seagate 7200.11. Does this fix work in a HP Touchsmart PC?

If your PC has the faulty model and firmware, then yes, you will also have this problem. You can take the serial number of your seagate hdd and go to the seagate website and type in the serial number.

go here http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931&NewLang=en

and choose #2 "click here to use the serial number check utility"

it will tell you if it is one of the affected models. that is the sure way to know if it is this problem. btw, it doesn't matter the brand of your pc, if they used the faulty seagate hdd, then you will have this problem.

0

Share this post


Link to post
Share on other sites

Great job, Simba, that might be usefull for other members with your

type of drive/firmware :thumbup

Although I would like to emphasize that playing with the command-line

options of the firmware-updater is at the user's own risk.

Flashing a drive with incorrect/incompatible firmware will kill it.

Greetz,

Peter.

This is true, but the drive came from an Iomega enclosure. The model numbers matched, but because it was an LC firmware (not SD), it wouldn't flash. So, I had to force it.

It's been a couple weeks and haven't bumped into any issues.

0

Share this post


Link to post
Share on other sites
I am using a proper external power pack coupled upto the drive, a Nokia CA-42 cable to connect drive to the computer (a laptop) the three pins on the drive are all connected via the CA-42. I have also tried using a cmos/ttl serial port via a USB connection and that had the same trouble. I don't know what I'm dong wrong.

So don't we (to use Jaclaz' famous words: "I have my crystal ball at the shop for a retune") :whistle:

First make sure you've got a properly working TTL-RS232 connection before doing anything else.

  • Install the interface's (USB) drivers.
  • Check that a loopback-test can be performed at (at least) 38400 baud
    (Remember that not all CA-42 adapters are created equal; see other posts in this thread)

Once you've got that working, come back here and describe exactly what you've tried and done.

Unfortunately, when I connect this adapter to my computer the computer makes no indication that anything has been connected

Like most (if not all) USB-devices, you first have to install the drivers before you plug it in.

(Though Windows *should* respond and detect an "Unknown Device" once you've attached it) :unsure:

Possibility 2:

You *could* have received a DOA (Dead On Arrival), if so return the interface for a replacement.

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites
I am using a proper external power pack coupled upto the drive, a Nokia CA-42 cable to connect drive to the computer (a laptop) the three pins on the drive are all connected via the CA-42. I have also tried using a cmos/ttl serial port via a USB connection and that had the same trouble. I don't know what I'm dong wrong.

So don't we (to use Jaclaz' famous words: "I have my crystal ball at the shop for a retune") :whistle:

First make sure you've got a properly working TTL-RS232 connection before doing anything else.

  • Install the interface's (USB) drivers.
  • Check that a loopback-test can be performed at (at least) 38400 baud
    (Remember that not all CA-42 adapters are created equal; see other posts in this thread)

Once you've got that working, come back here and describe exactly what you've tried and done.

Unfortunately, when I connect this adapter to my computer the computer makes no indication that anything has been connected

Like most (if not all) USB-devices, you first have to install the drivers before you plug it in.

(Though Windows *should* respond and detect an "Unknown Device" once you've attached it) :unsure:

Possibility 2:

You *could* have received a DOA (Dead On Arrival), if so return the interface for a replacement.

Greetz,

Peter.

Hi,

I can communicate with the drive, so I think the connection is correct, I can enter commands into hyperterminal ok unitl it comes to switching off the power at the HDD, once I connect it again I cannot enter anything into hyperterminal,(i've tried ctrl-z) the only way I can do that is by disconnecting the HDD power source again, but when I do that I can enter commands again but the process has been interupted and won't work

The CA-42 cable is connected to a laptop via a USB connection, I have got a connection on all the three prongs that are used on the HDD (gnd, tx,rx) and I am using a external power supply like the picture in videoripper's post.

I don't know what else I can try.

Regards

Ian

0

Share this post


Link to post
Share on other sites

At what step in the process did you remove the power (and most important: when)?

After each step, you should wait until you've receive (any) response from the drive.

This is where some people do things wrong: they issue the "Format Partition"-command:

F3 T>m0,2,2,0,0,0,0,22 (enter)

but don't wait until this (or an error-) message is returned:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000

User Partition Format 5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 05 secs

User Partition Format Successful - Elapsed Time 0 mins 05 secs

It's highly unlikely (but not impossible) that you're only able to get a command-prompt

back after 2 power-cycles, instead of just 1.

In any case, this wouldn't make much different; you could even do a power-cycle 10 times

if you'ld like or continue un-bricking two days later...

...if it's done at the correct point in the un-bricking sequence :unsure:

So why it isn't responding as expected... I really don't know :no:

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

hi again finaly cleaned the contacts now on trying to spin up i get

Elapsed Time 8.618 secs

R/W Status 2 R/W Error 84150180

please help

0

Share this post


Link to post
Share on other sites
Unfortunately, when I connect this adapter to my computer the computer makes no indication that anything has been connected

Like most (if not all) USB-devices, you first have to install the drivers before you plug it in.

(Though Windows *should* respond and detect an "Unknown Device" once you've attached it) :unsure:

Possibility 2:

You *could* have received a DOA (Dead On Arrival), if so return the interface for a replacement.

Greetz,

Peter.

The first possibility seems unlikely to me, since all USB devices I have used to date are immediately detected at least as an "unknown device". Also, the drivers I have are not .exe, they require manual install. Is it possible the TTL side of the device must be connected to something (TX, RX, GND, & VCC) before the device is connected to the computer? Does this thing need external power? I would think not, given it should be powered via USB.

Edited by bigleg
0

Share this post


Link to post
Share on other sites

The device *should* at least be recognized when plugged in.

It also doesn't need an external power supply to get recognized.

You don't always need to have a "Real" (exe) installer to install drivers, though...

Didn't the device come with an installtion manual by any chance?

Hmmm, I've found the (XP) installation manual myself :whistle:

2 Installing CDM Drivers

2.1 Installing Via The Found New Hardware Wizard

To install CDM drivers for an FTDI device under Windows XP, follow the instructions below:

  • [some introduction text about old drivers here...]
  • Connect the device to a spare USB port on your PC. If the device is based on the FT2232, the
    Microsoft composite device driver is automatically loaded in the background. Once the composite
    driver has been installed Windows Found New Hardware Wizard will launch.
  • [The standard procedure to install a driver follows...]
  • Open the Device Manager (located in "Control Panel\System" then select the "Hardware" tab and
    click "Device Manger") and select "View > Devices by Connection", the device appears as a "USB
    Serial Converter" with an additional COM port with the label "USB Serial Port" (Figure 2.13). If the
    device is based on the FT2232, two ports will be available from a composite USB device.

So indeed... it *should* be detected by Windows as new hardware (offering to install its drivers). :unsure:

Have you tried to connect the interface directly to a mobo's USB-port?

Some USB devices don't like to be connected through an (external) hub.

Have a look with a magnifying glass to see if all solder-joints are good.

(Sorry... couldn't come up with better ideas at the moment) :blushing:

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

The device *should* at least be recognized when plugged in.

It also doesn't need an external power supply to get recognized.

You don't always need to have a "Real" (exe) installer to install drivers, though...

Didn't the device come with an installtion manual by any chance?

Hmmm, I've found the (XP) installation manual myself :whistle:

2 Installing CDM Drivers

2.1 Installing Via The Found New Hardware Wizard

To install CDM drivers for an FTDI device under Windows XP, follow the instructions below:

  • [some introduction text about old drivers here...]
  • Connect the device to a spare USB port on your PC. If the device is based on the FT2232, the
    Microsoft composite device driver is automatically loaded in the background. Once the composite
    driver has been installed Windows Found New Hardware Wizard will launch.
  • [The standard procedure to install a driver follows...]
  • Open the Device Manager (located in "Control Panel\System" then select the "Hardware" tab and
    click "Device Manger") and select "View > Devices by Connection", the device appears as a "USB
    Serial Converter" with an additional COM port with the label "USB Serial Port" (Figure 2.13). If the
    device is based on the FT2232, two ports will be available from a composite USB device.

So indeed... it *should* be detected by Windows as new hardware (offering to install its drivers). :unsure:

Have you tried to connect the interface directly to a mobo's USB-port?

Some USB devices don't like to be connected through an (external) hub.

Have a look with a magnifying glass to see if all solder-joints are good.

(Sorry... couldn't come up with better ideas at the moment) :blushing:

Greetz,

Peter.

I have already read through the manual, as well as a lot of other troubleshooting documentation found on the website. One of the documents directed me to Microsoft's "USBView" application. According to one of FTDI's documents, if the device doesn't show up in USBView with at least a Product and Vendor ID, it is extremely likely the there is a hardware fault Document link: see page 14. Interestingly, the seller wrote back to me saying they talked to the factory, and it DOES need +5V. I am skeptical, but will try this to appease them.

Yes, I have tried connecting to mobo USB ports as well as my PCI port.

This is irritating as I've already tried two CA-42 cables, both having their own particular problems.

0

Share this post


Link to post
Share on other sites
Interestingly, the seller wrote back to me saying they talked to the factory, and it DOES need +5V.

I find that very weird, to say the least :unsure:

A USB-port already carries a solid 5V power supply, why need an external one?

I am skeptical, but will try this to appease them.

Well I'm curious, so keep us updated on your progress.

Peter.

0

Share this post


Link to post
Share on other sites

This is true, but the drive came from an Iomega enclosure. The model numbers matched, but because it was an LC firmware (not SD), it wouldn't flash. So, I had to force it.

It's been a couple weeks and haven't bumped into any issues.

Could you please explain how exactly you proceed to FORCE the flashing? I'm having this same problem.

0

Share this post


Link to post
Share on other sites

@qwertyu: Just scroll back a couple of pages for the answer :whistle:

Ahh.. Finally fixed the LC15 Firmware issue and successfully upgraded my drive to SD1B Firmware..

What you do is download the Firmware Upgrade ISO.. Then exit the tutorial and hit CTRL-C at the menu (yes, abort the .bat file).

Enter this command:


sf.exe -m BRINKS -f 6HBXR1B.LOD -s -x -b

After that, it'll come back to you as FW SD1B instead of FW LC15.

Also take a note of my reply!

Although I would like to emphasize that playing with the command-line

options of the firmware-updater is at the user's own risk.

Flashing a drive with incorrect/incompatible firmware will kill it.

Greetz,

Peter.

Edited by VideoRipper
0

Share this post


Link to post
Share on other sites
Interestingly, the seller wrote back to me saying they talked to the factory, and it DOES need +5V.

I find that very weird, to say the least :unsure:

A USB-port already carries a solid 5V power supply, why need an external one?

I am skeptical, but will try this to appease them.

Well I'm curious, so keep us updated on your progress.

Peter.

Not surprisingly, applying 5Volts didn't work.

0

Share this post


Link to post
Share on other sites

Obviously... :unsure:

Well... the only thing I can think of is that the device is broken (or they've

forgot to program its EEPROM/firmware) :no:

I suggest you just return it and ask for a refund or a working one.

...and there's really no way to get those CA-42's working?

What are the issues with those two?

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.