jaclaz

JFYI : http://www.marriedtothesea.com/041808/this-is-what-i-get.gif jaclaz

Waiter, come taste this soup.... http://www.imdb.com/title/tt0094898/crazycredits Ahaaa... jaclaz

Normally a "wiped" hard disk is ALL 00's, as well a "pristine one" contains in non-used sectors 00's (and NOT FF's). When there is "localized" problems (like a bunch of bad sectors, like the ones you seem to have around sectors 1600400) usually other parts of the hard disk remain readable/are untouched. But it could well be a defective head. Unfortunately it is not easy to even diagnose it "remotely". You can try opening the \\.\physicaldrive in a disk editor (tiny hexer suggested): http://www.boot-land.net/forums/index.php?showtopic=8734 and search for the first occurrence of 0000. File->disk->Open drive->(choose correct \\.\PhysicalDriven Then Edit->Find/Replace->0000->Find Press "yes to all" to continue scanning past the first sector. jaclaz

From "common sense" (not having the faintest idea what diskminder is or how it works ) it could be that the partition (which should be formatted with the FAT32 filesystem, from it's size) has the backup bootsector (sector 6) out of sync from the main one (sector 0). http://thestarman.pcministry.com/asm/mbr/MSWIN41.htm Just check them with any disk editor. If you did NOT reformat the partition under WIN9x, and simply exchanged the previous bootsector invoking NTLDR with one invoking the IO.SYS (by using bootpart, or a similar utility, possibly even SYS.COM behaves like that ), the backup will still contain the "old" bootsector. jaclaz

Check GROUNDING. "random" characters may come from that. CHECK the read-me-first, point #7: EVERYTHING should be GROUNDed. CHECK the RS-232->TTL converter: is it at 3.3V levels? (or post a link to where you got it from) jaclaz

I have serious doubts about your command line. -eltorito-boot and -no-emul-boot look a lot like fighting each other.... The: -hide-joliet-trans-tbl is essentially pointless: http://en.wikipedia.org/wiki/TRANS.TBL The: -duplicates-once should be of scarce utility in a build such as these PE3 thingy The: -force-uppercase is a choice , but shouldn't actually be used normally, as it can create other kind of problems on certain builds. This is known to be working for grub4dos: http://www.boot-land.net/forums/index.php?showtopic=9696&st=26'>http://www.boot-land.net/forums/index.php?showtopic=9696&st=26 Read the whole thread, you may need to check the case of grldr: http://www.boot-land.net/forums/index.php?showtopic=9696 jaclaz

cuudulieu already tried his luck with the friendly guys over at hddguru : http://forum.hddguru.com/seagate-barracuda-7200-cc44-t15592.html http://forum.hddguru.com/7200-erorr-firmware-cc38-t16552.html http://forum.hddguru.com/seagate-7200-st31000333as-cc1f-clicks-during-post-t14997.html from the general tone of his posts: he has NOT a good familiarity with English (apparently he is from Vietnam) he is not an "innocent" home user with a problem caused by the morons at Seagate: he looks a lot like a wanna-be-pro attempting to run a business out of HD recovery he even appears to own a PC-3000 (real or fake) <- this is specialized hardware costing a few thousands bucks (real) or several hundreds (clone) Maybe he needs a more explicit text: @cuudulieu WE ARE NOT HD HARDWARE SPECIALISTS WE DO NOT KNOW ANY ANSWER TO YOUR QUESTIONS STOP POSTING YOUR PROBLEMS EVERYWHERE IT WILL ONLY MAKE BOARD MEMBERS ANGRY AT YOU Please, DO NOT DOUBLE POST (see Rule #2.a): http://www.msfn.org/board/topic/18408-forum-rules-updated-must-read/ jaclaz

Hmmm, I presume the drive has already died. The file contains ONLY FF's. No way out "from a distance", unless a pro has a look at it and diagnoses what the problem is. Several things may have happened, some easily fixable, some fixable but out of your reach (even if guided) and some stil fixable but only by a pro with the adequate hardware and software, plus a limited number of things that could have made the disk completely unrecoverable. Any "strange" noise coming from the disk when it spins up? Like a vibration or repeating attempts to read (click/click/click)? jaclaz

Yep, it's just a "half a**ed" htm page with a bunch of javascript in it, really not my field, it was intended as a quick and dirty tool for internal use, but since it ended up as being only dirty (and not quick at all ) I put it online so that othere people may use it. It is intended ONLY for links to posts (and forums) and is VERY far from being complete, or "fully functional", but it (sometimes) works, even when it doesn't, it mostly works, i.e. with a minimal manual correction to the result it can be made working. If anyone with a better knowledge of javascript is willng to give suggestions, provide better code, etc. I'am all for it. @Fredledingue Link in my signature. The matter was discussed here: Oops, I mean here : http://www.msfn.org/board/index.php?showtopic=137119 jaclaz

*usually* yes. Mainly, TESTDISK, but in some occasions manual intervention is faster/better (and even easier ). Two threads about similar issues solved: http://www.msfn.org/board/index.php?showtopic=145574 http://www.msfn.org/board/index.php?showtopic=141687 Generally speaking the RAW filesystem (provided that the partition is still actually seen) is due to a missing or plainly wrong bootsector or to a pointer in the partition table misplaced/pointing to the wrong address, the two given threads show the two mentioned different problems leading to the same effect. Particularly I would appreciate this occsion to contradict you : Actually the probabilities of recovering a NTFS partition that became "RAW" is very, very HIGH (nearly 100% if the problem is one of the mentioned ones or a similar one). The problem of the OP may however come from other reasons: It could well be a dying hard disk.... Call me any name you want , but in my book anyone who somehow escaped from the 7200.11 BSY or LBA problem and does still rely on the fixed drive (and has not a proper, Full backup) *deserves* NOT any help with data recovery... jaclaz

"shooting one's foot, but programmatically": http://www.kirchwitz.de/~amk/shoot_foot.shtml jaclaz

Problem is that we DO NOT know what the problem is, nor if a solution exists at all. Similar messages on the 7200.11 mean that the drive is in BSY or LBA0 state. So you can try the "7200.11" fix, but there is NO guarantee whatsoever that it will help you recover the drive (or the DATA in it). For all we know those sets of commands applied on a 7200.12 could also put the drive on fire or make it blow up. JFYI: http://webcache.googleusercontent.com/search?q=cache:VhOffLbD30QJ:www.salvationdata.com/forum/download/file.php%3Fid%3D494 What this means, if it applies to your particular drive or case, etc. etc., we cannot say. The command: [quote]F3 T>m0,2,2,0,0,0,0,22 (enter)[/quote] appears like being a "general reset" of some kind, but there is NO way to know if it is applicable to your situation, compare with point #1 of the read-me-first for the 7200.11: jaclaz

I don't want to seem more grumpy that I really am, but evidently you completely failed: to read the stickies and, expecially, the read-me-first: to take some time browsing and searching on the "main" thread: NO. (please note how the last character in the above line is a "dot" or "full stop" or "period") JFYI : http://www.msfn.org/board/index.php?showtopic=128807&st=3063 jaclaz

Unfortunately I doubt this will happen. This: appears like a question aimed to telepaths or clairvoyants, that usually do not post on the board.... With reference to this: http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.html We are right now at the "I'm ill, doctor. Help!" stage. Please provide some meaningful details, as-is the question is not understandable, let alone answerable. jaclaz

The read-me-first covers this topic nicely IMNSHO: Point #5. Please read it attentively. Updating the firmware is the LEAST and LAST of the problems. Forcing an update is NOT adviced. Also review the conversation with Falcon7, some 25 posts starting from here: Take your time reading the thread, most of the answers are ALREADY in it. jaclaz

What the heck are you running? That screenshot tells you that you have I/O errors around sector 1600400 hex, which means around sector 23,069,696 which means around bytes: 23,069,696x512=11,811,684,352 i.e aroud 12 Gb! You need first 51,200 bytes or 51,200/512=100 sectors. You told the program to image first 51,200 Mbytes! http://www.datarescue.com/photorescue/v3/drdd.htm In the LOWER set of boxes SECTORS, you want to have 0-100-100 (in the UPPER set of boxes, Mbytes, you will see 0-1-1 which is a rough approximation of the very small amount of needed sectors) jaclaz

Happy to know there is another happy bunny in the basket. http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

Can I burn it with ANY .iso burning app, including as an example the Freeware IMGBURN: http://www.imgburn.com/ or should I use "Nero" ? jaclaz

Let's put it this way : We have a read-me-first: (BTW linked to on the "tutorial at the beginning off this thread") that lists (point #3) TWO tutorials: Now, which one would you choose? One posted in a semi-hurry by Gradius 1 1/2 year ago and not updated/bettered/refined or one that has been edited/changed in response to the various questions/problems/whatever and is actually RECOMMENDED? A third one.... (which is allright , but then why asking for help here?) OF COURSE the PCB has to be powered, the original tutorial gave this as implied. (as it is, since we are talking about communicating with a device - have you ever tried communicating to your modem, or handy, or whatever when the device is powered off or has batteries removed or has the mains plug disconnected?) On the other hand, if you actually read the Gradius' tutorial you will see that the really difficult part is to screw back the detached PCB while power is on.....which has been removed by the clever trick of the paper strip. Next post should be about the image not showing a GROUND connected..... jaclaz

You are very welcome to disagree with me, expecially in the (rare ) occasions when you are actually right. Yep , from experience, if you tell people to ALWAYS, and when I mean ALWAYS, I do mean ALWAYS, use CaSe SeNsItIvE commands, most of them will do, say 90%. (the remaining 10% will anyway ignore this recommendation and fail, before or later) If you start telling them that some commands are NOT case sensitive, whilst some other ones are CaSe SeNsItIvE, say 65% will understand when to use case sensitive ones and when not, and 35% will fail. Of the ones that fail: 5% will remain silent 10% are smart enough to re-do the steps using the "other" case and succeed 30% will adopt the infinite monkey approach and type randomly until they get the result 55% will start whining that the command did not work.... Since the general idea is to reduce to a minimum the global amount of whining (which like entropia seems deemed to always increase ), the used approach, (just like the "§@ç#ing GROUND everything" and the "DO NOT use CA-42" ) i.e. the grumpy "DO EXACTLY WHAT YOU ARE TOLD!" approach allows for a unfortunately minimal step in the right direction of increasing the amount of successes and conversely decrease the amount of failures and whining... Believe me, one of the things that is very difficult to convey to people is that BEFORE making assumptions and introducing variations of ANY kind, they should try to follow the actual instructions exactly, completely and precisely. jaclaz

If I may, you are using a "proprietary" undocumented method to create your own recovery partition. It would seem to me far easier to use properly documented available tools instead. Besides the Terabyte MBR, there is mbldr, which you may want to try, some initial reference is here: http://www.msfn.org/board/index.php?showtopic=131620&st=105 jaclaz

Happy everything went well. jaclaz

Can you see the difference between a "simple" path with NO spaces and a path like C:\Program Files (x86)\ .... You know, one of those paths that should never be used on command line or if really needed should be put inside double quotes? Try EXACTLY the command suggested including it's simple path, if it doesn't work, it may be a 7 (x64? ) kind of problem. Use this other app, which is GUI: http://www.boot-land.net/forums/index.php?showtopic=7783 http://www.datarescue.com/photorescue/v3/drdd.htm you stil want roughly first 100 sectors. jaclaz

It would be nice if you could start a new thread reporting your experience, so that other people may find it more easily than navigating the present thread. @tlh1005 The CA-42 is deprecated not because it won't work, only because it won't work easily (provided you have a "good" CA-42 and not a "bad" one ). Basically you shouldn't type anything to the terminal once the disk is connected, only Ctrl+Z (mind you Ctrl+Z is NOT Ctrl+z) and get: F3 T> The BSY should not prevent booting, AFAIK, but it may depend on the OS you are running, it seems like 7 has this problem : http://www.msfn.org/board/index.php?showtopic=145325 (but that is NOT a BSY) jaclaz

My guess is that the problem lies here: as you can see on the given thread, this on USB becomes media=usb Now, it is possible that there is another cheat code for .iso images. You chould try understanding which "base" distro is used for this CD, maybe there is one, some have a "fromiso" kind of parameter.... As well it is possible that changing the init is necessary. There is even a third possibility, which is using something similar to the hmload approach (check the README_GRUB4DOS.txt) i.e. copying the whole image to rd(0) or use the memdisk approach, but really cannot say. You are most probably in case #3 or #4 . What you report about boot-land is strange, a number of members have joined in the last hour or so. If you detail what is happening when you trying to register, I may be able to post a "bug thread" there. jaclaz