Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

The Solution for Seagate 7200.11 HDDs

- - - - -

  • Please log in to reply
4721 replies to this topic

#476
cmburns

cmburns

    Newbie

  • Member
  • 12 posts

>>>>>>>>>>>>>> User Partition Format Successful

is this complete? is this i need to try? is there any error, did i forget anything?


I should be done. You can try spin down and spinup drive (from level 2>Z and then U) after it spins go back to T ( with /) then type F3 T>F712



i tried this on my TESTING DRIVE, since i will do all of this on my RAID drive after all possible 'pitfalls' are excluded.

if i type: 'F712' i get this:
===============================================================================
Byte:05A1: Expansion =
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
''

F3 T>
=============================================================================

which was the mistake in your last command?


so would this be all ok?

may i use the the 'path' of commands AS I WROTE in my last posting??

thank you again!

regards,

cmburns


How to remove advertisement from MSFN

#477
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag

>>>>>>>>>>>>>> User Partition Format Successful

is this complete? is this i need to try? is there any error, did i forget anything?


I should be done. You can try spin down and spinup drive (from level 2>Z and then U) after it spins go back to T ( with /) then type F3 T>F712



i tried this on my TESTING DRIVE, since i will do all of this on my RAID drive after all possible 'pitfalls' are excluded.

if i type: 'F712' i get this:
===============================================================================
Byte:05A1: Expansion =
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
''

F3 T>
=============================================================================

which was the mistake in your last command?


so would this be all ok?

may i use the the 'path' of commands AS I WROTE in my last posting??


it seems that you testing on ES.2 (probably SN05) drive not on 7200.11, try just F without any numbers

just 2 things:

connect to terminal before you power up drive.

second:

- N1 (Enter)

- / <- you need to go back into T> (you are on 1>) level before sending next command

- m0,2,2,,,,,22 (Enter) >>>>>>>>>>>>>> User Partition Format Successful


that should be all.

If you have critical/sensitive/important data on your raid you really should consider visit in a professional DR company. Poland is not so far from you :) You were warned.

Edited by aviko, 02 February 2009 - 03:30 PM.

Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#478
htpc

htpc

    Newbie

  • Member
  • 15 posts
aviko, from your experience is it safe to swap pcbs and run the firmware for those of us who are not good with electronics/coding?

#479
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag

aviko, from your experience is it safe to swap pcbs and run the firmware for those of us who are not good with electronics/coding?


If you mean 7200.11/ES.2/Diamondmax22 series it will not work. Connect only pcb without hda to pc and recognize it in bios or any other software. there will be capacity 0mb but serial number should be visible. What is that mean? It means that individual for any single hdd data are stored on its own pcb. Unless you do some work (sorry i cant tell you in simple words how exactly you need to do) it will not work. Use your brain/google/help someone and consider do you really have experience and proper tools to do that.

@edit:

as I underestand you mean swap pcb from another hdd right? Or by swapping you mean removing its own and put back together due all above steps in solution.

Edited by aviko, 02 February 2009 - 03:41 PM.

Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#480
cmburns

cmburns

    Newbie

  • Member
  • 12 posts

it seems that you testing on ES.2 (probably SN05) drive not on 7200.11, try just F without any numbers


i am on a ST3500320AS with firmware SD1A (it is already updated, since it is my experimenting-drive, on which i try all out to see if it works BEFORE i use it on my RAID drive.....

i typed only F

check this:
(it is too long to post it, not all is visible in the hyperterminal window!)
===============================================================================
Byte:0362: TraceBufferControlFlags1_18 = 00
Byte:0364: MinimumAllocationInTraceBlocksMSB_19 = 00
Byte:0365: MinimumAllocationInTraceBlocksLSB_19 = 00
Byte:0366: TraceBufferControlFlags1_19 = 00
Byte:0368: MinimumAllocationInTraceBlocksMSB_20 = 00
Byte:0369: MinimumAllocationInTraceBlocksLSB_20 = 00
Byte:036A: TraceBufferControlFlags1_20 = 00
Byte:036C: MinimumAllocationInTraceBlocksMSB_21 = 00
Byte:036D: MinimumAllocationInTraceBlocksLSB_21 = 00
Byte:036E: TraceBufferControlFlags1_21 = 00
Byte:0370: MinimumAllocationInTraceBlocksMSB_22 = 00
Byte:0371: MinimumAllocationInTraceBlocksLSB_22 = 00
Byte:0372: TraceBufferControlFlags1_22 = 00
Byte:0374: MinimumAllocationInTraceBlocksMSB_23 = 00
Byte:0375: MinimumAllocationInTraceBlocksLSB_23 = 00
Byte:0376: TraceBufferControlFlags1_23 = 00
Byte:0378: MinimumAllocationInTraceBlocksMSB_24 = 00
Byte:0379: MinimumAllocationInTraceBlocksLSB_24 = 00
Byte:037A: TraceBufferControlFlags1_24 = 00
Byte:037C: MinimumAllocationInTraceBlocksMSB_25 = 00
Byte:037D: MinimumAllocationInTraceBlocksLSB_25 = 00
Byte:037E: TraceBufferControlFlags1_25 = 00
Byte:0380: MinimumAllocationInTraceBlocksMSB_26 = 00
Byte:0381: MinimumAllocationInTraceBlocksLSB_26 = 00
Byte:0382: TraceBufferControlFlags1_26 = 00
Byte:0384: MinimumAllocationInTraceBlocksMSB_27 = 00
Byte:0385: MinimumAllocationInTraceBlocksLSB_27 = 00
Byte:0386: TraceBufferControlFlags1_27 = 00
Byte:0388: MinimumAllocationInTraceBlocksMSB_28 = 00
Byte:0389: MinimumAllocationInTraceBlocksLSB_28 = 00
Byte:038A: TraceBufferControlFlags1_28 = 00
Byte:038C: MinimumAllocationInTraceBlocksMSB_29 = 00
Byte:038D: MinimumAllocationInTraceBlocksLSB_29 = 00
Byte:038E: TraceBufferControlFlags1_29 = 00
Byte:0390: MinimumAllocationInTraceBlocksMSB_30 = 00
Byte:0391: MinimumAllocationInTraceBlocksLSB_30 = 00
Byte:0392: TraceBufferControlFlags1_30 = 00
Byte:0394: MinimumAllocationInTraceBlocksMSB_31 = 00
Byte:0395: MinimumAllocationInTraceBlocksLSB_31 = 00
Byte:0396: TraceBufferControlFlags1_31 = 00
Byte:0398: MinimumAllocationInTraceBlocksMSB_32 = 00
Byte:0399: MinimumAllocationInTraceBlocksLSB_32 = 00
Byte:039A: TraceBufferControlFlags1_32 = 00
Byte:039C: MinimumAllocationInTraceBlocksMSB_33 = 00
Byte:039D: MinimumAllocationInTraceBlocksLSB_33 = 00
Byte:039E: TraceBufferControlFlags1_33 = 00
Byte:03A0: MinimumAllocationInTraceBlocksMSB_34 = 00
Byte:03A1: MinimumAllocationInTraceBlocksLSB_34 = 00
Byte:03A2: TraceBufferControlFlags1_34 = 00
Byte:03A4: MinimumAllocationInTraceBlocksMSB_35 = 00
Byte:03A5: MinimumAllocationInTraceBlocksLSB_35 = 00
Byte:03A6: TraceBufferControlFlags1_35 = 00
Byte:03A8: MinimumAllocationInTraceBlocksMSB_36 = 00
Byte:03A9: MinimumAllocationInTraceBlocksLSB_36 = 00
Byte:03AA: TraceBufferControlFlags1_36 = 00
Byte:03AC: MinimumAllocationInTraceBlocksMSB_37 = 00
Byte:03AD: MinimumAllocationInTraceBlocksLSB_37 = 00
Byte:03AE: TraceBufferControlFlags1_37 = 00
Byte:03B0: MinimumAllocationInTraceBlocksMSB_38 = 00
Byte:03B1: MinimumAllocationInTraceBlocksLSB_38 = 00
Byte:03B2: TraceBufferControlFlags1_38 = 00
Byte:03B4: MinimumAllocationInTraceBlocksMSB_39 = 00
Byte:03B5: MinimumAllocationInTraceBlocksLSB_39 = 00
Byte:03B6: TraceBufferControlFlags1_39 = 00
Byte:03B8: MinimumAllocationInTraceBlocksMSB_40 = 00
Byte:03B9: MinimumAllocationInTraceBlocksLSB_40 = 00
Byte:03BA: TraceBufferControlFlags1_40 = 00
Byte:03BC: MinimumAllocationInTraceBlocksMSB_41 = 00
Byte:03BD: MinimumAllocationInTraceBlocksLSB_41 = 00
Byte:03BE: TraceBufferControlFlags1_41 = 00
Byte:03C0: MinimumAllocationInTraceBlocksMSB_42 = 00
Byte:03C1: MinimumAllocationInTraceBlocksLSB_42 = 00
Byte:03C2: TraceBufferControlFlags1_42 = 00
Byte:03C4: MinimumAllocationInTraceBlocksMSB_43 = 00
Byte:03C5: MinimumAllocationInTraceBlocksLSB_43 = 00
Byte:03C6: TraceBufferControlFlags1_43 = 00
Byte:03C8: MinimumAllocationInTraceBlocksMSB_44 = 00
Byte:03C9: MinimumAllocationInTraceBlocksLSB_44 = 00
Byte:03CA: TraceBufferControlFlags1_44 = 00
Byte:03CC: MinimumAllocationInTraceBlocksMSB_45 = 00
Byte:03CD: MinimumAllocationInTraceBlocksLSB_45 = 00
Byte:03CE: TraceBufferControlFlags1_45 = 00
Byte:03D0: MinimumAllocationInTraceBlocksMSB_46 = 00
Byte:03D1: MinimumAllocationInTraceBlocksLSB_46 = 00
Byte:03D2: TraceBufferControlFlags1_46 = 00
Byte:03D4: MinimumAllocationInTraceBlocksMSB_47 = 00
Byte:03D5: MinimumAllocationInTraceBlocksLSB_47 = 00
Byte:03D6: TraceBufferControlFlags1_47 = 00
Byte:03D8: MinimumAllocationInTraceBlocksMSB_48 = 00
Byte:03D9: MinimumAllocationInTraceBlocksLSB_48 = 00
Byte:03DA: TraceBufferControlFlags1_48 = 00
Byte:03DC: MinimumAllocationInTraceBlocksMSB_49 = 00
Byte:03DD: MinimumAllocationInTraceBlocksLSB_49 = 00
Byte:03DE: TraceBufferControlFlags1_49 = 00
Byte:03E0: MinimumAllocationInTraceBlocksMSB_50 = 00
Byte:03E1: MinimumAllocationInTraceBlocksLSB_50 = 00
Byte:03E2: TraceBufferControlFlags1_50 = 00
Byte:03E4: MinimumAllocationInTraceBlocksMSB_51 = 00
Byte:03E5: MinimumAllocationInTraceBlocksLSB_51 = 00
Byte:03E6: TraceBufferControlFlags1_51 = 00
Byte:03E8: MinimumAllocationInTraceBlocksMSB_52 = 00
Byte:03E9: MinimumAllocationInTraceBlocksLSB_52 = 00
Byte:03EA: TraceBufferControlFlags1_52 = 00
Byte:03EC: MinimumAllocationInTraceBlocksMSB_53 = 00
Byte:03ED: MinimumAllocationInTraceBlocksLSB_53 = 00
Byte:03EE: TraceBufferControlFlags1_53 = 00
Byte:03F0: MinimumAllocationInTraceBlocksMSB_54 = 00
Byte:03F1: MinimumAllocationInTraceBlocksLSB_54 = 00
Byte:03F2: TraceBufferControlFlags1_54 = 00
Byte:03F4: MinimumAllocationInTraceBlocksMSB_55 = 00
Byte:03F5: MinimumAllocationInTraceBlocksLSB_55 = 00
Byte:03F6: TraceBufferControlFlags1_55 = 00
Byte:03F8: MinimumAllocationInTraceBlocksMSB_56 = 00
Byte:03F9: MinimumAllocationInTraceBlocksLSB_56 = 00
Byte:03FA: TraceBufferControlFlags1_56 = 00
Byte:03FC: MinimumAllocationInTraceBlocksMSB_57 = 00
Byte:03FD: MinimumAllocationInTraceBlocksLSB_57 = 00
Byte:03FE: TraceBufferControlFlags1_57 = 00
Byte:0400: MinimumAllocationInTraceBlocksMSB_58 = 00
Byte:0401: MinimumAllocationInTraceBlocksLSB_58 = 00
Byte:0402: TraceBufferControlFlags1_58 = 00
Byte:0404: MinimumAllocationInTraceBlocksMSB_59 = 00
Byte:0405: MinimumAllocationInTraceBlocksLSB_59 = 00
Byte:0406: TraceBufferControlFlags1_59 = 00
Byte:0408: MinimumAllocationInTraceBlocksMSB_60 = 00
Byte:0409: MinimumAllocationInTraceBlocksLSB_60 = 00
Byte:040A: TraceBufferControlFlags1_60 = 00
Byte:040C: MinimumAllocationInTraceBlocksMSB_61 = 00
Byte:040D: MinimumAllocationInTraceBlocksLSB_61 = 00
Byte:040E: TraceBufferControlFlags1_61 = 00
Byte:0410: MinimumAllocationInTraceBlocksMSB_62 = 00
Byte:0411: MinimumAllocationInTraceBlocksLSB_62 = 00
Byte:0412: TraceBufferControlFlags1_62 = 00
Byte:0414: MinimumAllocationInTraceBlocksMSB_63 = 00
Byte:0415: MinimumAllocationInTraceBlocksLSB_63 = 00
Byte:0416: TraceBufferControlFlags1_63 = 00
Byte:0418: MinimumAllocationInTraceBlocksMSB_64 = 00
Byte:0419: MinimumAllocationInTraceBlocksLSB_64 = 00
Byte:041A: TraceBufferControlFlags1_64 = 00
Byte:041C: MinimumAllocationInTraceBlocksMSB_65 = 00
Byte:041D: MinimumAllocationInTraceBlocksLSB_65 = 00
Byte:041E: TraceBufferControlFlags1_65 = 00
Byte:0420: MinimumAllocationInTraceBlocksMSB_66 = 00
Byte:0421: MinimumAllocationInTraceBlocksLSB_66 = 00
Byte:0422: TraceBufferControlFlags1_66 = 00
Byte:0424: MinimumAllocationInTraceBlocksMSB_67 = 00
Byte:0425: MinimumAllocationInTraceBlocksLSB_67 = 00
Byte:0426: TraceBufferControlFlags1_67 = 00
Byte:0428: MinimumAllocationInTraceBlocksMSB_68 = 00
Byte:0429: MinimumAllocationInTraceBlocksLSB_68 = 00
Byte:042A: TraceBufferControlFlags1_68 = 00
Byte:042C: MinimumAllocationInTraceBlocksMSB_69 = 00
Byte:042D: MinimumAllocationInTraceBlocksLSB_69 = 00
Byte:042E: TraceBufferControlFlags1_69 = 00
Byte:0430: MinimumAllocationInTraceBlocksMSB_70 = 00
Byte:0431: MinimumAllocationInTraceBlocksLSB_70 = 00
Byte:0432: TraceBufferControlFlags1_70 = 00
Byte:0434: MinimumAllocationInTraceBlocksMSB_71 = 00
Byte:0435: MinimumAllocationInTraceBlocksLSB_71 = 00
Byte:0436: TraceBufferControlFlags1_71 = 00
Byte:0438: MinimumAllocationInTraceBlocksMSB_72 = 00
Byte:0439: MinimumAllocationInTraceBlocksLSB_72 = 00
Byte:043A: TraceBufferControlFlags1_72 = 00
Byte:043C: MinimumAllocationInTraceBlocksMSB_73 = 00
Byte:043D: MinimumAllocationInTraceBlocksLSB_73 = 00
Byte:043E: TraceBufferControlFlags1_73 = 00
Byte:0440: MinimumAllocationInTraceBlocksMSB_74 = 00
Byte:0441: MinimumAllocationInTraceBlocksLSB_74 = 00
Byte:0442: TraceBufferControlFlags1_74 = 00
Byte:0444: MinimumAllocationInTraceBlocksMSB_75 = 00
Byte:0445: MinimumAllocationInTraceBlocksLSB_75 = 00
Byte:0446: TraceBufferControlFlags1_75 = 00
Byte:0448: MinimumAllocationInTraceBlocksMSB_76 = 00
Byte:0449: MinimumAllocationInTraceBlocksLSB_76 = 00
Byte:044A: TraceBufferControlFlags1_76 = 00

Congen Mode Page
Congen Group
Byte:0450: NumDefaultATCyls = FF 3F
Byte:0452: NumDefaultATHeads = 10 00
Byte:0454: NumDefaultATSectors = 3F 00
Byte:0456: NumECCBytesForLongCmds = 04 00
Byte:0458: MaximumMultipleSize = 10
Byte:0459: LogicalSectorAlignment = 00
Byte:045A: PIOModeTiming = 00 02
Byte:045C: DMAModeTiming = 00 02
Byte:045E: NumCurrentATCyls = FF 3F
Byte:0460: NumCurrentATHeads = 10 00
Byte:0462: NumCurrentATSectors = 3F 00
Byte:0464: CurrentMultipleSize = 10 00
Byte:0466: MultiwordDMAModesSupported = 07
Byte:0466: Bit:0, MULTIWORD_DMA_MODE_0_SUPPORTED = 1
Byte:0466: Bit:1, MULTIWORD_DMA_MODE_1_SUPPORTED = 1
Byte:0466: Bit:2, MULTIWORD_DMA_MODE_2_SUPPORTED = 1
Byte:0467: UltraDMAModesSupported = 7F
Byte:0467: Bit:0, ULTRA_DMA_MODE0_SUPPORTED = 1
Byte:0467: Bit:1, ULTRA_DMA_MODE1_AND_BELOW_SUPPORTED = 1
Byte:0467: Bit:2, ULTRA_DMA_MODE2_AND_BELOW_SUPPORTED = 1
Byte:0467: Bit:3, ULTRA_DMA_MODE3_AND_BELOW_SUPPORTED = 1
Byte:0467: Bit:4, ULTRA_DMA_MODE4_AND_BELOW_SUPPORTED = 1
Byte:0467: Bit:5, ULTRA_DMA_MODE5_AND_BELOW_SUPPORTED = 1
Byte:0467: Bit:6, ULTRA_DMA_MODE6_AND_BELOW_SUPPORTED = 1
Byte:0468: AdvancedPIOModesSupported = 03 00
Byte:0468: Bit:0, PIO_MODE_3_SUPPORTED = 1
Byte:0468: Bit:1, PIO_MODE_4_SUPPORTED = 1
Byte:046A: MinimumMultiwordDMACycleTime = 78 00
Byte:046C: RecommendedMultiwordDMACycleTime = 78 00
Byte:046E: MinimumPIOTimeWithoutFlowControl = 78 00
Byte:0470: MinimumPIOTimeWithFlowControl = 78 00
Byte:0472: QDepth = 1F 00
Byte:0474: SATACapabilities = 0E 05
Byte:0475: Bit:0, SATA_NCQ_SUPPORTED = 1
Byte:0475: Bit:1, HOST_INITIATED_PHY_POWER_MANAGEMENT_SUPPORTED = 0
Byte:0475: Bit:2, SATA_PHY_EVENT_COUNTERS_SUPPORTED = 1
Byte:0475: Bit:3, UNLOAD_WHILE_NCQ_CMDS_OUTSTANDING_SUPPORTED = 0
Byte:0475: Bit:4, NCQ_PRIORITY_SUPPORTED = 0
Byte:0478: SATAFeaturesSupported = 48 00
Byte:0478: Bit:2, DMA_AUTOACTIVATE_SUPPORTED = 0
Byte:0478: Bit:3, DEVICE_INITIATED_POWER_MANAGEMENT_SUPPORTED = 1
Byte:0478: Bit:6, PRESERVE_SETTINGS_ON_COMRESET_SUPPORTED = 1
Byte:047A: SATAFeaturesEnabled = 40 00
Byte:047A: Bit:2, DMA_AUTOACTIVATE_ENABLED = 0
Byte:047A: Bit:3, DEVICE_INITIATED_POWER_MANAGEMENT_ENABLED = 0
Byte:047A: Bit:6, PRESERVE_SETTINGS_ON_COMRESET_ENABLED = 1
Byte:047C: MajorVersionNumber = F0 01
Byte:047C: Bit:1, ATAPI_1_SUPPORTED = 0
Byte:047C: Bit:2, ATAPI_2_SUPPORTED = 0
Byte:047C: Bit:3, ATAPI_3_SUPPORTED = 0
Byte:047C: Bit:4, ATAPI_4_SUPPORTED = 1
Byte:047C: Bit:5, ATAPI_5_SUPPORTED = 1
Byte:047C: Bit:6, ATAPI_6_SUPPORTED = 1
Byte:047C: Bit:7, ATAPI_7_SUPPORTED = 1
Byte:047D: Bit:0, ATAPI_8_ACS_SUPPORTED = 1
Byte:047E: MinorVersionNumber = 29 00
Byte:0480: CommandSetSupported = 6B 34
Byte:0480: Bit:0, SMART_SUPPORTED = 1
Byte:0480: Bit:1, SECURITY_MODE_FEATURE_SET_SUPPORTED = 1
Byte:0480: Bit:5, WRITE_CACHE_SUPPORTED = 1
Byte:0480: Bit:6, READ_LOOKAHEAD_SUPPORTED = 1
Byte:0481: Bit:2, HOST_PROTECTED_AREA_SUPPORTED = 1
Byte:0481: Bit:4, WRITE_BUFFER_CMD_SUPPORTED = 1
Byte:0481: Bit:5, READ_BUFFER_CMD_SUPPORTED = 1
Byte:0481: Bit:6, NOP_CMD_SUPPORTED = 0
Byte:0482: CommandSetsSupported = 01 7D
Byte:0482: Bit:1, READ_WRITE_DMA_QUEUED_SUPPORTED = 0
Byte:0482: Bit:3, ADVANCED_POWER_MANAGEMENT_SUPPORTED = 0
Byte:0482: Bit:5, POWER_UP_IN_STANDBY_SUPPORTED = 0
Byte:0482: Bit:6, SET_FEATURES_SPINUP_REQUIRED_SUPPORTED = 0
Byte:0483: Bit:0, SET_MAX_SECURITY_EXTENSION_SUPPORTED = 1
Byte:0483: Bit:1, AUTO_ACOUSTIC_MANAGEMENT_SUPPORTED = 0
Byte:0483: Bit:2, FOURTYEIGHT_BIT_SUPPORTED = 1
Byte:0483: Bit:3, DCO_COMMAND_SETS_SUPPORTED = 1
Byte:0483: Bit:4, FLUSH_CACHE_SUPPORTED = 1
Byte:0483: Bit:5, FLUSH_CACHE_EXT_SUPPORTED = 1
Byte:0484: CommandSetSupportedExtension = 23 41
Byte:0484: Bit:0, SMART_ERROR_LOGGING_SUPPORTED = 1
Byte:0484: Bit:1, SMART_SELF_TEST_SUPPORTED = 1
Byte:0484: Bit:2, MEDIA_SERIALNUMBER_SUPPORTED = 0
Byte:0484: Bit:4, STREAMING_FEATURE_SET_SUPPORTED = 0
Byte:0484: Bit:6, FUA_WRITE_EXT_COMMANDS_SUPPORTED = 0
Byte:0484: Bit:7, FUA_WRITE_QUEUED_EXT_COMMANDS_SUPPORTED = 0
Byte:0485: Bit:0, SIXTYFOUR_BIT_WWN_SUPPORTED = 1
Byte:0485: Bit:3, AV_LITE_SUPPORTED = 0
Byte:0485: Bit:4, AV_LITE_RC_WC_SUPPORTED = 0
Byte:0485: Bit:5, IDLE_IMMEDIATE_UNLOAD_SUPPORTED = 0
Byte:0486: CommandSetEnabled = 69 34
Byte:0486: Bit:0, SMART_ENABLED = 1
Byte:0486: Bit:1, SECURITY_MODE_FEATURE_SET_ENABLED = 0
Byte:0486: Bit:5, WRITE_CACHE_ENABLED = 1
Byte:0486: Bit:6, READ_LOOKAHEAD_ENABLED = 1
Byte:0487: Bit:2, HOST_PROTECTED_AREA_ENABLED = 1
Byte:0488: CommandSetsEnabled = 01 BC
Byte:0488: Bit:3, ADVANCED_POWER_MANAGEMENT_ENABLED = 0
Byte:0488: Bit:5, POWER_UP_IN_STANDBY_ENABLED = 0
Byte:0488: Bit:6, SET_FEATURES_SPINUP_REQUIRED_ENABLED = 0
Byte:0488: Bit:7, ADDRESS_OFFSET_RESERVED_AREA_BOOT = 0
Byte:0489: Bit:0, SET_MAX_SECURITY_EXTENSION_ENABLED = 0
Byte:0489: Bit:1, AUTO_ACOUSTIC_MANAGEMENT_ENABLED = 0
Byte:048A: CommandSetEnabledExtension = 23 41
Byte:048A: Bit:2, MEDIA_SERIALNUMBER_IS_VALID = 0
Byte:048B: Bit:3, AV_LITE_ENABLED = 0
Byte:048B: Bit:4, AV_LITE_RC_WC_ENABLED = 0
Byte:048C: FreeFallSensitivity = 44 00
Byte:048E: CurrentAPMValue = FE FE
Byte:0490: MasterPasswordRevisionCode = FE FF
Byte:0492: AcousticLevel = 00 FE
Byte:0494: StreamMinRequestSize = 00 00
Byte:0496: StreamXferTimeDMA = 00 00
Byte:0498: StreamAccessLatency = 00 00
Byte:049A: StreamPerformanceGranularity = 00 00 00 00
Byte:049E: StreamXferTimePIO = 00 00
Byte:04A0: Max512ByteUnitsPerDownloadMicrocode = 00 00
Byte:04A2: PhysicalLogicalSectorSize = 00 00
Byte:04A2: Bit:0, TWO_X_LOG_SECTORS_PER_PHY_SECTOR_B0 = 0
Byte:04A2: Bit:1, TWO_X_LOG_SECTORS_PER_PHY_SECTOR_B1 = 0
Byte:04A2: Bit:2, TWO_X_LOG_SECTORS_PER_PHY_SECTOR_B2 = 0
Byte:04A2: Bit:3, TWO_X_LOG_SECTORS_PER_PHY_SECTOR_B3 = 0
Byte:04A3: Bit:4, DEV_LOG_SEC_LEN_GREATER_THAN_256W = 0
Byte:04A3: Bit:5, DEV_HAS_MUL_LOG_SECTORS_PER_PHY_SECTOR = 0
Byte:04A4: AVLiteWorstCaseTimer = 00 00
Byte:04A6: WordsPerLogicalSector = 00 00 00 00
Byte:04AA: ATACommandSetSupportedExt2 = 0E 40
Byte:04AA: Bit:1, WRITE_READ_VERIFY_SUPPORTED = 1
Byte:04AA: Bit:2, WRITE_UNCORRECTABLE_SUPPORTED = 1
Byte:04AA: Bit:3, READ_AND_WRITE_DMA_EXP_GPL_COMMANDS_SUPPORTED = 1
Byte:04AA: Bit:5, FREEFALL_SENSOR_SUPPORTED = 0
Byte:04AC: ATACommandSetEnabledExt2 = 08 40
Byte:04AC: Bit:1, WRITE_READ_VERIFY_ENABLED = 0
Byte:04AC: Bit:3, READ_AND_WRITE_DMA_EXP_GPL_COMMANDS_ENABLED = 1
Byte:04AC: Bit:5, FREEFALL_SENSOR_ENABLED_BY_DEFAULT = 0
Byte:04AE: ATATransportMajorRevisionNumber = 08 10
Byte:04B0: ATATransportMinorRevisionNumber = 00 00
Byte:04B2: ATSMARTDefaultFlags = 01 00
Byte:04B2: Bit:0, SMARTDEFAULTON = 1
Byte:04B4: ATSMARTConfig =
0F 00 06 00 03 00 00 00 32 00 14 00 33 00 24 00
0F 00 1E 00 32 00 00 00 13 00 61 00 32 00 14 00
32 00 00 00 3A 00 00 00 22 00 2D 00 32 00 00 00
32 00 00 00 32 00 00 00 22 00 00 00 1A 00 00 00
12 00 00 00 10 00 00 00 3E 00 00 00 32 00 63 00
32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 32 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
Byte:04B4: SMART1Status = 0F 00
Byte:04B6: SMART1Threshold = 06
Byte:04B8: SMART2Status = 03 00
Byte:04BA: SMART2Threshold = 00
Byte:04BC: SMART3Status = 32 00
Byte:04BE: SMART3Threshold = 14
Byte:04C0: SMART4Status = 33 00
Byte:04C2: SMART4Threshold = 24
Byte:04C4: SMART5Status = 0F 00
Byte:04C6: SMART5Threshold = 1E
Byte:04C8: SMART6Status = 32 00
Byte:04CA: SMART6Threshold = 00
Byte:04CC: SMART7Status = 13 00
Byte:04CE: SMART7Threshold = 61
Byte:04D0: SMART8Status = 32 00
Byte:04D2: SMART8Threshold = 14
Byte:04D4: SMART9Status = 32 00
Byte:04D6: SMART9Threshold = 00
Byte:04D8: SMART10Status = 3A 00
Byte:04DA: SMART10Threshold = 00
Byte:04DC: SMART11Status = 22 00
Byte:04DE: SMART11Threshold = 2D
Byte:04E0: SMART12Status = 32 00
Byte:04E2: SMART12Threshold = 00
Byte:04E4: SMART13Status = 32 00
Byte:04E6: SMART13Threshold = 00
Byte:04E8: SMART14Status = 32 00
Byte:04EA: SMART14Threshold = 00
Byte:04EC: SMART15Status = 22 00
Byte:04EE: SMART15Threshold = 00
Byte:04F0: SMART16Status = 1A 00
Byte:04F2: SMART16Threshold = 00
Byte:04F4: SMART17Status = 12 00
Byte:04F6: SMART17Threshold = 00
Byte:04F8: SMART18Status = 10 00
Byte:04FA: SMART18Threshold = 00
Byte:04FC: SMART19Status = 3E 00
Byte:04FE: SMART19Threshold = 00
Byte:0500: SMART20Status = 32 00
Byte:0502: SMART20Threshold = 63
Byte:0504: SMART21Status = 32 00
Byte:0506: SMART21Threshold = 00
Byte:0508: SMART22Status = 00 00
Byte:050A: SMART22Threshold = 00
Byte:050C: SMART23Status = 00 00
Byte:050E: SMART23Threshold = 00
Byte:0510: SMART24Status = 00 00
Byte:0512: SMART24Threshold = 00
Byte:0514: SMART25Status = 00 00
Byte:0516: SMART25Threshold = 00
Byte:0518: SMART26Status = 32 00
Byte:051A: SMART26Threshold = 00
Byte:051C: SMART27Status = 00 00
Byte:051E: SMART27Threshold = 00
Byte:0520: SMART28Status = 00 00
Byte:0522: SMART28Threshold = 00
Byte:0524: SMART29Status = 00 00
Byte:0526: SMART29Threshold = 00
Byte:0528: SMART30Status = 00 00
Byte:052A: SMART30Threshold = 00
Byte:052E: SCTCommandSetSupported = 3B 10
Byte:052E: Bit:0, SCT_SUPPORTED_COMMAND_SET = 1
Byte:052E: Bit:1, SCT_SUPPORTED_LONG_SECTOR_ACCESS = 1
Byte:052E: Bit:2, SCT_SUPPORTED_LBA_SEGMENT_ACCESS = 0
Byte:052E: Bit:3, SCT_SUPPORTED_ERROR_RECOVERY_CONTROL = 1
Byte:052E: Bit:4, SCT_SUPPORTED_FEATURES_CONTROL = 1
Byte:052E: Bit:5, SCT_SUPPORTED_DATA_TABLE = 1
Byte:0530: SCTFanControlMaxOperatingTemp = 00
Byte:0531: SCTFanControlOverRangeTemp = 00
Byte:0532: SCTFanControlUnderRangeTemp = 00
Byte:0533: SCTFanControlMinOperatingTemp = 00
Byte:0534: SCTVendorFlags = 04 00
Byte:0534: Bit:0, SCT_VENDORFLAGS_SEATOOLS = 0
Byte:0534: Bit:1, SCT_VENDORFLAGS_WRITE_SAME = 0
Byte:0534: Bit:2, SCT_VENDORFLAGS_CORRECTABLE_BIT = 1
Byte:0535: Bit:7, SCT_VENDORFLAGS_DEBUG_MODE = 0
Byte:0536: SCTTimerReadDefault = 00 00
Byte:0538: SCTTimerWriteDefault = 00 00
Byte:053A: SCTTenMsecCount = 00
Byte:053B: SCTPerformanceFlags = 00
Byte:053C: SCTTempDataTableSize = 80 00
Byte:053E: SCTSamplingPeriod = 01 00
Byte:0540: SCTInterval = 01 00
Byte:0542: ATAPadSlewRate = 00
Byte:0543: ATAIORDYPadControl = 00
Byte:0544: PreampHotTweak = 00
Byte:0545: PreampColdTweak = 00
Byte:0546: LubeMitigationRetries = 00 00
Byte:0548: LengthOfWriteSpaceToFlush = 00 00
Byte:054A: LengthOfWriteCommandToTriggerFlush = 00 00
Byte:054C: NDSLBAThresholdA = 00 00
Byte:054E: NDSLBAThresholdB = 00 00
Byte:0550: NDSPartitionDependencies = 00 00
Byte:0552: NDSODOffsetConfig = 00
Byte:0553: NDSIDOffsetConfig = 00
Byte:0554: APMTimer1mSec = 40 04
Byte:0556: APMTimer2mSec = 00 15
Byte:0558: APMStandByTimer = 20 00
Byte:055A: APMTimerForDither = 2C 01
Byte:055C: ReadDelayMinimum = 00
Byte:055D: WriteDelayMinimum = 00
Byte:055E: WriteDelayIncremental = 00
Byte:055F: ReadDelayIncremental = 00
Byte:0560: FeatureFlags = 80 A0 00 18
Byte:0560: Bit:0, WRITE_CONFIG_DATA_TO_FLASH = 0
Byte:0560: Bit:1, SPINUP_WRITE_FAULT_THRESHOLDS_ENABLED = 0
Byte:0560: Bit:2, IOEDC_CHECK_ENABLED = 0
Byte:0560: Bit:3, IOEDC_ERROR_ENABLED = 0
Byte:0560: Bit:4, DOWNLOAD_MICROCODE_FUTURE_USE_ONLY = 0
Byte:0560: Bit:5, SUPPRESS_SERIAL_PORT_PRINTS = 0
Byte:0560: Bit:6, DRQ_CLEAR_ON_PIO_READ_ERR_SUPPORTED = 0
Byte:0560: Bit:7, OFFLINE_SEEK_AWAY = 1
Byte:0561: Bit:0, DELAY_SLEEP_STANDBY_CMDCOMPLETE = 0
Byte:0561: Bit:1, IDLE_IMMEDIATE_UNLOAD_EMERGENCY = 0
Byte:0561: Bit:2, ENABLE_ALLOW_RAW_ERROR_RATE_UPDATE = 0
Byte:0561: Bit:3, OP_SHOCK_DETECTION_ENABLED = 0
Byte:0561: Bit:4, LOG99_CONTROL = 0
Byte:0561: Bit:5, READ_WRITE_LONG_EXTENDED_ENABLED = 1
Byte:0561: Bit:6, WRITE_REORDERING_DISABLED = 0
Byte:0561: Bit:7, ALLOW_AAM_FEATURE_SET = 1
Byte:0562: Bit:0, DATA_LOG_ENABLED = 0
Byte:0562: Bit:1, HOST_STREAM_RECORD_FIRST_ERROR_BLOCK = 0
Byte:0562: Bit:2, SAVE_ATA_COMMAND_HISTORY_TO_DISC = 0
Byte:0562: Bit:3, EIB_ON_POWERUP = 0
Byte:0562: Bit:4, LEFT_JUSTIFY_SERIAL_NUMBER = 0
Byte:0562: Bit:5, SUN_MICRO_MODEL_NUMBER_UPDATE = 0
Byte:0562: Bit:6, REVERTING_TO_POWER_ON_DEFAULTS_SUPPORTED = 0
Byte:0562: Bit:7, RIGHT_JUSTIFY_FIRMWARE_REVISION = 0
Byte:0563: Bit:0, SEGMENT_INITIALIZED = 0
Byte:0563: Bit:1, DISPLAY_SMART_COMMANDS_ON_SERIAL_PORT_ENABLED = 0

Byte:0563: Bit:2, DISABLE_SMART_AUTO_UPDATES = 0
Byte:0563: Bit:3, DISABLE_LEGACY_READ_WRITE_LONG = 1
Byte:0563: Bit:4, VERSION_ENFORCEMENT_SUPPORTED = 1
Byte:0564: PerformanceFlags = 00 3F
Byte:0564: Bit:0, REDUCED_RAW_TRANSITION_FLUSH = 0
Byte:0564: Bit:1, REDUCED_AV_RETRIES = 0
Byte:0564: Bit:5, ZERO_LATENCY_RD_ENABLED = 0
Byte:0565: Bit:0, DAR_ENABLED = 1
Byte:0565: Bit:1, OFFLINE_SPARING_ENABLED = 1
Byte:0565: Bit:2, JIT3 = 1
Byte:0565: Bit:3, JIT2 = 1
Byte:0565: Bit:4, JIT1 = 1
Byte:0565: Bit:5, JIT0 = 1
Byte:0565: Bit:6, DISABLE_IDLE_ACTIVITY = 0
Byte:0566: AggressivelyScanThisManyTimes = 00 00
Byte:0568: LongSeekEventTime = FF FF
Byte:056A: SleepStandbyDelay = 00 00
Byte:056C: CustomerUniques = 00 00 00 00
Byte:0570: CustomerType = 00 00 00 00
Byte:0574: AdditionalSATAFeatureConfig = 0F 06 00 00
Byte:0574: Bit:0, SATA_FORCE_EARLY_STATUS = 1
Byte:0574: Bit:1, SATA_EARLY_STATUS_FORCE_COMRESET = 1
Byte:0574: Bit:2, SATA_INTRACOMMAND_PHY_MANAGEMENT_ENABLED = 1
Byte:0574: Bit:3, SATA_ENABLE_PHY_PM_CALIBRATION = 1
Byte:0574: Bit:4, SATA_ENABLE_SPI_VIS_MODE = 0
Byte:0574: Bit:5, SATA_ENABLE_RERR_TESTING = 0
Byte:0574: Bit:6, SATA_ENABLE_SSC = 0
Byte:0574: Bit:7, SATA_EYEQ_TEST = 0
Byte:0575: Bit:0, SATA_DISABLE_PRIMITIVE_SCRAMBLING = 0
Byte:0575: Bit:1, SATA_ULTRA_AGGRESSIVE_INTER_COMMAND_PHY_SUPPORTED =
1
Byte:0575: Bit:2, SATA_ULTRA_AGGRESSIVE_INTRA_COMMAND_PHY_SUPPORTED =
1
Byte:0578: FactoryODScanMBytes = 00 00
Byte:057A: FactoryIDScanMBytes = 00 00
Byte:057C: MaxDSTSelfTestTime = CE 18
Byte:057E: DSTShortTestTimeLimit = 3C 00
Byte:0580: BootFlagsForROM = 02 00
Byte:0580: Bit:0, BOOT_FLAG_POWER_ON_IN_STANDBY = 0
Byte:0580: Bit:1, BOOT_FLAG_PARTIAL_OOB = 1
Byte:0580: Bit:2, USE_SMALL_ID_FORMAT = 0
Byte:0580: Bit:3, LOW_CURRENT_SPINUP = 0
Byte:0582: LastCongenWriteCaller = 00 00
Byte:0584: HostStreamJumpSizeInSectors = 00 00
Byte:0586: HostStreamTotalJumpSteps = 00
Byte:0587: SerialDebugLevel = 00
Byte:0588: DefaultStandbyTimer = 00
Byte:0589: ATAInterSectorTime = 08
Byte:058A: StandbyDelayBeforePostingStatus = 05 00
Byte:058C: StandbyPostingStatusFlags = 00 00
Byte:058C: Bit:0, ENABLE_WAIT_FOR_DRIVE_SPINDOWN_BEFORE_POSTING_STATUS
_AFTER_STANDBY = 0
Byte:058C: Bit:1, ENABLE_HEADS_ON_RAMP_BEFORE_POSTING_STATUS_AFTER_STA
NDBY = 0
Byte:058C: Bit:2, ENABLE_DELAY_BEFORE_POSTING_STATUS_AFTER_STANDBY = 0

Byte:058F: LTTCPowerOnHours = 0A
Byte:0590: DebugAddress0 = 00 00 00 00
Byte:0594: DebugValue0 = 00 00 00 00
Byte:0598: DebugAddress1 = 00 00 00 00
Byte:059C: DebugValue1 = 00 00 00 00
Byte:05A0: Bit:0, EIB_WRT_MSG_ENABLE = 0
Byte:05A0: Bit:1, EIB_SWD_MSG_ENABLE = 0
Byte:05A0: Bit:2, EIB_SIM_MSG_ENABLE = 0
Byte:05A0: Bit:3, EIB_DEBUG_MSG_ENABLE = 0
Byte:05A1: Expansion =
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
''
=============================================================================

if my drive is 'visible' for BIOS but with SIZE 0MB, then only the command 'm0,2,2,0,0,0,0,22' (Enter) is needed, right? no other command before this would be needed.

i type this in T level (= F3 T>)?


thx

regards

cmburns

#481
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag

it seems that you testing on ES.2 (probably SN05) drive not on 7200.11, try just F without any numbers


i am on a ST3500320AS with firmware SD1A (it is already updated, since it is my experimenting-drive, on which i try all out to see if it works BEFORE i use it on my RAID drive.....

i typed only F

.......... (removed)

Close log which you pasted in [codebox] log put here [/codebox]


if my drive is 'visible' for BIOS but with SIZE 0MB, then only the command 'm0,2,2,0,0,0,0,22' (Enter) is needed, right? no other command before this would be needed.

i type this in T level (= F3 T>)?


it should be enough.

@edit

I never tested that fixed firmware, it seems code is slight different. Only time can show us is these patches really works.

Edited by aviko, 02 February 2009 - 03:52 PM.

Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#482
Fuzzy_3D

Fuzzy_3D

    Newbie

  • Member
  • 43 posts
Just Fixed My Drive :thumbup

Got my RS232-TTL adapter this morning, backing up my data right now.

But only after figuring out that the connections are TX to TXD, and RX to RXD. Should've been the first thing I checked :blushing:

Thanks to everyone who helped and contributed to this solution, and Gradius for putting up this guide, and putting up with the naysayers.
Posted Image

#483
pichi

pichi

    Member

  • Member
  • PipPip
  • 170 posts

it seems that you testing on ES.2 (probably SN05) drive not on 7200.11, try just F without any numbers


i am on a ST3500320AS with firmware SD1A (it is already updated, since it is my experimenting-drive, on which i try all out to see if it works BEFORE i use it on my RAID drive.....

...

if my drive is 'visible' for BIOS but with SIZE 0MB, then only the command 'm0,2,2,0,0,0,0,22' (Enter) is needed, right? no other command before this would be needed.

i type this in T level (= F3 T>)?


thx

regards

cmburns

SD1A has differents commands.

You can see all commands of your 7200.11 disc with this:
Ctrl+z
F3 T>/C
F3 C>Q
(List all commands of your hdd)

SD15:
Level T 'm': Rev 0001.0000, Flash, FormatPartition,
m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertif
yTrkRewrites],[ValidKey]

SD1A:
Level T 'm': Rev 0012.0000, Flash, FormatPartition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertif
yTrkRewrites],[ValidKey],[DataPattern]

I don't know if 'm0,2,2,0,0,0,0,22,' (Enter) (note: with last comma) works or not. But there is one person has repaired his hdd doing:
1.- Change firmware from SD1A to AD14.
2.- Repair 0GB problem with the G-List Erase and Translator regeneration commands.
3.- Change firmware from AD14 to SD1A.

In spanish: http://www.msfn.org/...mp;#entry830608

#484
cmburns

cmburns

    Newbie

  • Member
  • 12 posts

it should be enough.



well guys, i think it worked on one of my RAID drives !!!!!!!!

it is late now,
....i dont want to make any careless mistake today, so ill continue tomorrow BUT thank you all (aviko, Gradius2, pichi and all the others) so far, it is amazing, how much better you are than the company seagate, who is to blame for all this in the first place!!

ill report more tomorrow!!!

thanx again!

good nite

kind regards,

cmburns

#485
RedIon1992

RedIon1992
  • Member
  • 9 posts

When you say you see the arrow, do you mean the '>' character as shown after the "F3 F" text? If so, then
it may be doing what you want, but you just can't see all the text being echoed to the display but only the
last character which you are interpreting as an arrow head (not the mouse symbol).

I'm not sure if windows terminal allows one to change the terminal emulation from lets say whatever you have to VT100
with 80 columns. For those who have windows setup for other character sets or right to left prompting, could this be
the cause? I'm not sure how windows terminal would handle this too.

Can you post screen prints of your hyperterminal settings under File->properties and show us the settings for each screen tab under this
area? This will help with determining if they are set properly.....

Just some thoughts on the arrow problem. :whistle:


I'll post these when I get home.

OK, I've currently shorted my TX and RX lines, but no matter which way around I connect them to the drive, I get nothing in the terminal.

They're only connected to the converter, so either it's not doing its job, and simply passing the signals through, or the hard drive isn't sending any signals.

Any hints?


If you shorted them, then you might fried the terminals.


I should have been more specific - I shorted the TX and RX lines on the adapter I built - not on the drive.

#486
my77stang

my77stang

    Newbie

  • Member
  • 19 posts
i still dont think i got a reply on this and i even posted boobies, so i'll ask again =)

just to clarify when using the cell phone cable method, all i need is the tx and rx cables from it right? then plug the HD into any sata power cable (i have a 2nd PSU i can use for this)

i just want to make sure im 100% clear on this. there's not going to be too many volts going thru the tx/rx lines (like 5v from the usb port or anything), and i dont need to worry about any kind of ground wire in the cell phone cable right?


^ is that correct?

#487
pichi

pichi

    Member

  • Member
  • PipPip
  • 170 posts

i still dont think i got a reply on this and i even posted boobies, so i'll ask again =)

just to clarify when using the cell phone cable method, all i need is the tx and rx cables from it right? then plug the HD into any sata power cable (i have a 2nd PSU i can use for this)

i just want to make sure im 100% clear on this. there's not going to be too many volts going thru the tx/rx lines (like 5v from the usb port or anything), and i dont need to worry about any kind of ground wire in the cell phone cable right?


^ is that correct?

You need join GNDs, is the second PSU GND connected to GND of cable (= GND of PC)?
You can protect RX and TX lines with 1K resistances.

Edited by pichi, 02 February 2009 - 05:14 PM.


#488
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag

just to clarify when using the cell phone cable method, all i need is the tx and rx cables from it right? then plug the HD into any sata power cable (i have a 2nd PSU i can use for this)

i just want to make sure im 100% clear on this. there's not going to be too many volts going thru the tx/rx lines (like 5v from the usb port or anything), and i dont need to worry about any kind of ground wire in the cell phone cable right?


it would be good if u will connect ground of adapter too, pin next to rx and tx.

just for safety you should connect ground of both power suppiles together (black wire)
Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#489
my77stang

my77stang

    Newbie

  • Member
  • 19 posts
so, like a jumper wire from the ground on a molex plug from one PSU to the other? ir would i be better to take the ground wire from the cell phone cable and ground it out to the body of the HD?

#490
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag

so, like a jumper wire from the ground on a molex plug from one PSU to the other? ir would i be better to take the ground wire from the cell phone cable and ground it out to the body of the HD?


both. there is ground on pin 3 in terminal connector:

Posted Image

You can solder a ground wire into back of jumper and put it as limit to 1,5gbits
Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#491
pichi

pichi

    Member

  • Member
  • PipPip
  • 170 posts

so, like a jumper wire from the ground on a molex plug from one PSU to the other? ir would i be better to take the ground wire from the cell phone cable and ground it out to the body of the HD?

The GND is a complicated thing.
Normally GND=Molex black wire=Chassis=Ground of 220/110V plug.
The better is join only one GND, example: from the cell phone cable to the body of the HD/third pin.
I suppose that the second PSU is a floating power supply.
Precautions: All others grounds are separated (check plug, wires, chassis, etc)

Edited by pichi, 05 February 2009 - 01:51 AM.


#492
tifa

tifa
  • Member
  • 2 posts
Aviko, maybe you can help me?
My ST3500320NS drive doesn't answer on the terminal when PCB is disconnected from the rest of disk.
But when both parts are connected i can unlock terminal for about 1-2 seconds and again got LED:000000CC...

Im very sad because i had huge collection of great photos of my 1-year old son only on that hd...

#493
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Aviko, maybe you can help me?
My ST3500320NS drive doesn't answer on the terminal when PCB is disconnected from the rest of disk.
But when both parts are connected i can unlock terminal for about 1-2 seconds and again got LED:000000CC...

Im very sad because i had huge collection of great photos of my 1-year old son only on that hd...


read PM
Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#494
my77stang

my77stang

    Newbie

  • Member
  • 19 posts
i was thinking it only needed one ground. ike taking the usb ground wire, stripping some and wrapping around a screw then screwing it into the mounting holes on the side of the drive.

yeah, the 2nd PSU will be a floater, but honestly i could use the system's PSU to power the drive if it helps.

#495
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag

i was thinking it only needed one ground. ike taking the usb ground wire, stripping some and wrapping around a screw then screwing it into the mounting holes on the side of the drive.

yeah, the 2nd PSU will be a floater, but honestly i could use the system's PSU to power the drive if it helps.


unless you connect sata connectors to mainboard/sata controller the only way where ground both psu meets is in your adapter connected to terminal. i think its not worth a risk. sure you can power it from pc psu. byt there is danger when you do power cycle power surge can turn off other disks in your pc for just a sec. it happens to me when i have much drives connected on same cable when I power on one of them, rest make a power reset too.
Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#496
Nirvanowiec

Nirvanowiec
  • Member
  • 1 posts
Maybe it will be usefull to somebody ->
http://yura.projekta...agate/s3ku.html

#497
Gradius2

Gradius2

    IT Consultant

  • Member
  • PipPip
  • 240 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Just wanna to confirm this once for all (specially for those who just found this topic).

Thanks to this guide, over 1000 HDDs were 100% repaired without any issue, or data loss until date.

There are innumerables "Thanks" here as evidence, so this just reaffirm the guide is flawlessly (as far the user understand every step of guide and is able to following them).

I'll just say that: In which you'll trust?, in someone who came here for flamewar, caos, and Confucius's thing (using untested cmds and doubtful methods), or those who really wants to help? ;)

Well, I don't even need to answer that, right? :whistle:

Gradius

PS: 6 years is nothing, specially when you pass over 20 years into this stuff. ;)

Edited by Gradius2, 02 February 2009 - 07:35 PM.

"Two things are infinite: The Universe and Human stupidity; and I'm not sure about the Universe." Albert Einstein

#498
aviko

aviko

    user inactive

  • Member
  • Pip
  • 86 posts
  • OS:Windows 7 x64
  • Country: Country Flag
To dear mr Gradius2:

I really dont want start an flamewar. When someone comming here and reads your first post, everything looks as you are autor of this solution. To be honest did you underestand what are you doing? No, you just grabbed all infos from Yura site and called him a thief. I cant forgive you that. How dare you?

You make terrible mistakes when translating that site by google and you dont want to listen when we tryed to tell you what is wrong in "your tutorial". There are rare cases when problems can occur, but it happens. I sent PM to you, you ignored that. Its your choice. But people have right to know that you dont have any idea how this really works.

Anyway there are many drives where terminal locks up. It will happen after do a power cycle, which was totally unnecessary at that moment and dangerous for drive. All these steps can be done without any power cycle between steps, but its necessary to do additional checks. Without, it can be a lottery and noone wants to gamble with own (or worse customers) data.

What can i say? If anyone feels that I helped and want to make a donation? Sure, but not for me, send money to unicef, caritas or any other organization who really needs it. I dont want anyones money for helping here. I like my job and it makes me fun when I can help someone without any interest in it.

As your tutorial is on first page, I really suggest you mr Gradius2 to review all steps and correct what is wrong with it.

First, there is no any reason to clear G-list if it not contain errors, moreover it will destroy all content in sectors which was remapped. It will not visible just by checking content of directories and check few files for consistence.

Second: power cycles are no need and are potentialy dangerous.

Third: Touching any single screw on drive is not necessary too. Yes you dont need to take off pcb to do all steps. So ppl dont need torx screwdriver that you wanted to sell in kit.

Fourth: making unnecessary double signal conversion is a potentialy source of problems: from USB (which is +5V) to RS232 levels (which are -12V to +12V) and back to TTL levels (+5V) which btw is a little too much but noone fried his drive due that.

When you read posts from yesterday you (maybe) will find out what else are wrong.
Choice is yours. Fortunately it's your data not mine. Here all of this was started. even single spark can burn forest. Nobody's perfect. I'm nobody.

#499
my77stang

my77stang

    Newbie

  • Member
  • 19 posts
i believe you both know alot more than most of us - if you can put your heads together maybe there can be a solution that is agreed upon by both of you.... and be the best route for us all to take.

#500
Jason Husky

Jason Husky
  • Member
  • 6 posts
Hey,

Hi.
Now I need help.
My ST3500320AS doesn't spin on anymore. This evening I wanted to try this workaround (busy mode) again. But after connecting the hd to the powersupply nothing happened.
In bios: 0MB, under OS X in the disk utility: 2 TB. ?!


It seems that you burned motor ic, Im almost sure that you connect motor when pcb was not stopped and gives voltage to motor. Thats why I told its was really stupid to disconnect it, you will not know when motor is powered and when not.

Does drive making any sounds? (it can be really silent, just put ear on it and power on). Does drive says anything on terminal? Maybe something like this: Buzz Buzz Buzz if yes, it means that microprogram is trying to start motor but could not. Let me know.


hm...... that's bad. :(
But how did I do that?! It is really dissapointing cause I checked every connection twice but didn't get the right output in the terminal.
Know I've damaged something. Data gone forever?!
Greetz
Jan




5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users



How to remove advertisement from MSFN