Jump to content

VideoRipper

Member
  • Posts

    329
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Everything posted by VideoRipper

  1. As you might already have noticed, this thread is about 7200.11 drives running SD15 firmware. While the info *might* be useful on other drive-types and/or firmware-version, we have no experience with other drives/firmware, so you're completely on your own with them. It *may* be possible to use the SD15 procedure as a guide, but you really have to interpret what is done in the procedure here and transpose it to commands/steps for your drive. Since I'm not familiar with problems on your drive-type and firmware, it wouldn't surprise me if it actually suffers from an entirely different problem. Greetz, Peter.
  2. Since you already have an F-prompt (for "Failure"), I'm afraid the motor-driver or controler on the PCB is defective, which is not easy/possible to repair yourself. Greetz, Peter.
  3. Something in the back of my mind tells me you're not using "The official installation source" of the product... Anyway... did you install the .Net Framework version 3.x?
  4. I would say: uninstall and re-install the application. Apparantly it was unable to load some crucial libraries (like DLL's, etc.), but it's hard to tell, since this message doesn't say anything really... What does your system-log tell you? Greetz, Peter.
  5. In the BIOS, at the POST (the first thing you see when starting up your PC), what's the size reported for that drive?
  6. I'm a bit confused now... A little time later you wrote: Maybe you should check if the TX- and RX-wires to your RS232 <=> TTL interface are properly making contact (and be sure the ground is also connected). If that doesn't work... well, maybe your PCB indeed is fried, who knows? Greetz, Peter.
  7. Here's another PHP-script (which also shows you some other details): <?php $text='<html><head><title>PHP Environment</title></head><body>'. '<table style="border-collapse: collapse;" cellpadding="1">'; foreach ($_SERVER as $key => $val) $text.='<tr onMouseOver="this.style.backgroundColor=\'AAAABB\';" '. 'onMouseOut="this.style.backgroundColor=\'transparent\';">'. '<td style="font-weight: bold; border-right: 2px solid #000000;">'. $key.'</td><td style="width: 100%;">'. (is_array($val)?nl2br(print_r($val,true)):$val).'</td></tr>'; $text.='</table>'; echo $text.'</body></html>'; ?> ...and how it is executed can be seen by pressing this link
  8. How come I have the feeling I've read this question before? Why post requests ("Spam the board") when you're not using any of the information given and just start the same thing over and over again? It's getting a bit annoying
  9. Loop up This thread is for Seagate drives running SD15 firmware only Greetz, Peter.
  10. Yes... read the procedure to the letter Hint: you have to disconnect the motor and/or head-contacts from the PCB before powering up the unit. You'll get this message when the controller on the PCB was able to load the firmware off the drive (it is stored on the platters, that's why you have to put in a cardstock). Greetz, Peter.
  11. I don't think you can fix a defective drive with a software solution (I don't know SeDiv either) and that message is all gibberish to me
  12. Like already said: capacitors are used for all kinds of things and it's a bit hard to see from here where it "Fell off"... Just have a close look on that motherboard for any missing components (where it could fit); most likely it's somewhere near the CPU as part of its power regulation-circuit. Greetz, Peter.
  13. I've seen discs (not only DVD, but also CD) that we're not exactly centered, resulting in its sides "crashing" left and right inside the tray's sides. Of course it's also possible that the disc isn't flat, so it's oscillating up and down in the tray. Either way: if it's the disc, I would just make a backup of it and don't use it, cause it might damage the drive in the end (and it's pretty annoying to watch a movie with a rattling DVD-player). Greetz, Peter.
  14. Don't exaggerate, Jaclaz You know it's pretty easy to swap a BIOS chip on a PCB with the right tools...
  15. You should even be able to use the drive for, lets say, 18 months with the current SD15 firmware without problems and de-brick it again after that. The drive itself is not at fault, there's only a small problem with "Some overflow in the LBA/SMART/whatever table after nnn entries". The SD1A firmware update *should* have fixed this, but this hasn't been confirmed yet. You're free to update the firmware, but it's just as easy to start an RMA at Seagate and have the drive swapped for free. I did that a couple of months ago, only to set my mind at ease Just my 2 €-cents B) Peter.
  16. The F means "FAILURE", which is correct if the PCB is not connected to the drive or if the drive actually is defective.
  17. That's great news! Now have the drive swapped or if possible: refunded
  18. You might want to have a read in this Wiki The actually used private address-space doesn't matter much, you only might need to change some statically addressed device-settings inside your LAN. Greetz, Peter.
  19. Okay... now you've got communications with the drive working, you can try to unbrick it. But, since I've never had to unbrick a 7200.10 drive, you're on your own (you *could* try to use the procedure for 7200.11 drives, but as always: at your own risk) Keep us updated, Peter.
  20. You really should start a new thread for this... For us: yes For drive-recovery firms: no I can only tell for my older WD PATA-drives and they have a 2*5 pin header between the power- and the IDE-connector (for the master/slave, etc. jumpers) that might want to talk with the outside as well, though I've never tried... Other drives, might not even want to communicate (diagnostics-wise) using "Normal" RS-232 protocols; there are a lot of others (like JTAG), as well as non-disclosed ones. I highly double that, since that would mean drive manufacturers have to do the same to diagnose their own products, though a PCB *could* indeed have some pads for that purpose, who knows? Seagate 7200.7 (which is PATA) uses 9600 baud using these connections: (Remember: RX of drive go to TX of PC and vice-versa and are also using TTL-levels!) But... as said before, this actually belongs in a new thread Greetz, Peter.
  21. With my 7200.11 drive it only took a couple of seconds, but as seen in khobar's case it took a bit longer, so you might want to wait... If nothing happens after, let's say, an hour or so, you might want to give it another try after a "Drive reboot", but that's entirely at your own risk (as always). Good luck and keep us posted, Peter.
  22. See my reply in the 7200.11 topic first You should first get a working command-prompt from the PCB. To achieve this, do the following: Completely remove the PCB from the drive Connect a RS232 to TTL interface between your PC and the PCB (don't forget the GND, ground, pin) Open a new connection with HyperTerminal (or similar) with these settings:Speed: 9600 baud Databits: 8 Parity: None Stop bits: 1 Flow control: None[*]Apply normal power to the drive via the SATA-power connector [*]You should get a prompt after pressing CTRL+Z [*]If not: close the HyperTerminal connection and re-try at other speed settings (19200, 38400) Good luck, Peter.
  23. Electronically 7200.10, 7200.11 and probably a lot (all?) of other Seagate SATA drives are "Identical", so *in theory* the 7200.11 trick *could* work with the others. However, this thread is for 7200.11 drives in particular and while its procedure *could* be used on similar drives, you do it entirely at your own risk and your results may (WILL!) vary, so only do it when you're at least a bit comfortable with electronics. We cannot advise you on drives other than the 7200.11 ones here; you will have to start your own new thread or find a similar one for your specific drive. Having that said: the PCB on a Seagate drive houses a simple, but effective, diagnostics environment; even with no drive attached, it should give you a prompt when pressing CTRL+Z after having connected it to a RS232-TTL level port and applying power to the board. First get that working before proceding... Greetz, Peter.
  24. Yep, just give it a go Connect it to your PC the normal way and see if it's recognized in the BIOS (and as the correct size). Don't forget to update us on the progress Greetz, Peter.
  25. If connections are getting dropped because the network is getting overcrowded, I would urge the network/systems-administrator to invest in a network-upgrade or a network-redesign for the new situation.
×
×
  • Create New...