Jump to content

spadge

Member
  • Posts

    12
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by spadge

  1. Ok, this doesn't seem to work either... Will get the same read errors... I don't think this is the result of a headcrash. Another strange thing: if I try to get an image via DatarescueDD but from the other direction it won't work either - read errors are all I get, but no strange sounds or anything which sounds like a headcrash. Maybe there was just something configured wrong like for example some drive parameters and therefor the drive's firmware won't read further.
  2. So far so good... After changing the partition id to 12 I was able to boot up windows and now DatarescueDD is running - we will see if it works better then the dos imaging tool.
  3. NO, the "old" one is "lost forever", but running the manufacturer tool should make a new one. You are talking of Seagate's Seatools? Or what do you suggest? But regenerating them is somekind similar to a lowlevel format (losing all data) or am I wrong? Or are there some AT commands to regenerate the G-list without destroying any data? DST short or long test ( AT Command NB or NC in Level 1) won't help here, right? It is NOT a good idea to "insist" on a failed/failing HD area. Which tool are you using? You may want to try making partial chunks of image, skipping the problematic part(s). (I don't think that any of the programs on UBCD have this possibility) - maybe Diskman I'm using "partition saving" tool of UBCD. Currently >176.000 unreadable sectors in a row, starting at sector 58133624 - maybe this is the spare sector area? I don't prefer DOS to linux, was just the first thing I've tried due to the fact that dos does no try to mount/interpret the filesystem structure as this will result in a system slowdown. Ok I will give ddrescue a try... Thank you very much jaclaz, spadge
  4. Hm, I think I've wiped the G-List. Is there a way to restore/regenerate it? The instructions I followed advice to do this Currently I'm trying to get a dump of the whole drive using the Universal Boot Disk running the DOS rescue system. It just works but after severeal gigabyte I got a lot of read errors, >400 sectors - probably all in a row - could not be read properly. After that I will try the LBA fix and then I'll run the seatools. Thanks jaclaz for your support. Will take some time now (getting a dump of the drive) as soon as I get further I will post...
  5. It crossed my mind that maybe something is wrong with the defective sector list - could this be possible?
  6. Ok, I will try this - but note that I've also the same problems using various linux live/rescue cds. I will repeat the LBA fix as you suggested. Shoudl I use AD14 or should I try using SD1A?
  7. I've tried updating again to SD1A - using the latest firmware found on seagate's homepage. Doesn't help either... If I hotplug the drive to the mainboards SATA interface in windows, it's nearly the same than using USB: windows slows down, but I'm unable to see anything in drivemanager or in windows explorer (but I see all 3 partition letters in the "remove hardware dialog"). Note: after downgrading to AD14 the drive is not recognized in BIOS but accessible for a firmware update (SD1A) using the standard seagate update ISO. Another curious thing running SD1A: MHDD does not recognize the harddisk, but the BIOS does. If the drive is powered up running SD1A you can hear every 1 or 2 seconds the ususal clicking (short) as if the drive is accessing something (even connected only to power). Going back to SD15 (the original version) is not possible because I haven't got the proper version - I think I will need SD15 for 2 discs - not for 3 or 4 discs as found on hddguru. Do you probably know a source for this? Would it make sense to ask seagte for it? Next thing I would try is to access it using testdisk. Do you have some more ideas?
  8. Hi BlouBul, Hi jaclaz, merry christmas to both of you... I've had the latest firmware update ISO from seagate - I've heard of the problems of the first updates also, but I think the version I get should be fine @jaclaz: I don't know if the drive would work using SATA but I haven' had enough patience wait until windows starts - broke the startup after about 15 min. Using USB is some kind of similar to this but I managed to see my 3 partitions in windows explorer, but the drive stays busy and windows gets slowed down. After a while a message appears like "Drive E: is not formatted, would you like to do this now? Is there a way to do a bitwise copy of the whole drive bypassing the OS, BIOS and maybe CRC or similar of the drive? I will give it another try to update firmware to SD1A and will read through your links, thanks a lot to both of you, I will let you know as soon as I have done this - christmas is horrible time consuming
  9. This thread should be used to separate my issue as suggested by BlouBul and is targeted especially @jaclaz So here is a summary of what happened and what I did (wrong ): I own a ST3500320AS (original SD15 Firmware, made in China) which had the BSY issue. After the BSY occured I found out that there is a way unlocking the disk by using a terminal RS232 connection - so I followed the instructions unlocking the device from BSY and fixing LBA0 (isolating the pcb<->motor connection aso.). Everything worked out fine - until now... Stupidly I updated to firmware SD1A after rebooting from unlocking the BSY and LBA0 issues. Currently I'm having a drive which is accessible by the BIOS but not by the OS itself because in my opinion the OS sees/gets only corrupted data and therefore windows nor linux will start (at least not after a reasonable time). Next thing I've tried is to access the drive using USB - this doesn't work either - system gets slowed down but I see at least the 3 partitions (ntfs) I've on this disk in windows explorer - but I'm unable to access anything further than that. Ok my last try was to downgrade the firmware to AD14 and back again to SD1A - as I haven't found a SD15 update suitable for my drive (I've found a SD1A-34D.bin on hddguru but I was not able to flash it, the flash just didn't work/did any progress). So now I'm stuck here and beg for some help. Maybe if someone has the right SD15 firmware I would try that or a good suggestion. I lay everything now into all your mighty hands
  10. Yes your are right - be asured I've already regret the update God to hear that at least you see some hope... So I will try as you suggested, hope to see you soon in a new thread *g*
  11. Hi BlouBul, thank you for the welcome Ok I see that I was a little bit short on explaining what I did. After BSY I found out that there is a way unlocking the disk by using a terminal RS232 connection - so I followed the instructions unlocking the device from BSY and fixing LBA0 (isolating the pcb<->motor connection aso.). Everything worked out fine. But after that - and this was the big fault of me - I thought it would be best to perform the SD1A update before doing anything else. So here I am now, having a drive which is accessible by the BIOS but not by the OS itself because in my opinion the OS sees/gets only corrupted data. As I stated before, I've tried to get to an older Firmware (ADd14, because I haven't found a working SD15 for my drive). AD14 did not work so I tried - as some others did - to update again to SD1A (from AD14). But nothing helped out to access my data - which is surely available on the platters itself. Thanks for reading
  12. First of all I would like to say "thank you" for collecting and sharing this information, it helped me alot. I own a ST3500320AS (original SD15 Firmware, made in China) which had the BSY issue. Sadly I first tried the solution of another source and therfore I missed your FGA - needless to say, I wrecked something up. So probably everything here should have worked for me but I made the big mistake to update my ST3500320AS to SD1A. Now I'm not able to read data from the device, partitions are recognized but nothing more. Linux or Windows hangs after connecting the device via USB or just won't start if connected via SATA. Does anybody have a link to firmware SD15 for this drive? I already tried the to downgrade to AD14 - but as some others mentioned this firmware version won't work, so after that I went back to SD1A but that won't help either. Any suggestions?
×
×
  • Create New...