Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

RAW File System on Seagate Free Agent Go Flex 1.5TB External HDD After Ejecting


  • Please log in to reply
6 replies to this topic

#1 jlarson4

jlarson4

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 27 April 2013 - 02:38 PM

RAW File System on Seagate Free Agent Go Flex 1.5TB External HDD After Ejecting

As the topic title states, my external hdd is now reading the file system as RAW.  I have been searching for a solution for some time now with no avail.  I saw that improperly ejecting the hdd can cause this problem.  I always properly eject my hdd so I do not know how it happened is this case, maybe it has something to do with power surges in the work trailer I am in.  The drive is supposed to be NTFS. 

 

Anyways, I have followed the advice from http://html5.litten.com/how-to-fix-external-disk-drive-suddenly-became-raw/ and am still having issues.  I have a picture of every step that I have done so maybe there is something in one of them that I am missing.

20130325195356.jpg

 

20130325195341.jpg

 

 

From this point I used Parted Magic to try to copy files off of the hdd by mounting it, and here is what happened.

41820788.jpg

20130325200149.jpg

 

20130325194443.jpg

 

 

I then followed the steps to start analyzing the drive. Here are the pictures for each step.

 

When I clicked analyze, I received this message.

34035931.jpg

 

 

Here is the next screen.

35480483.jpg

 

 

Results of the quick search.

60595475.jpg

 

 

Here are the files that showed up.

32852608.jpg

 

 

I went under advanced and looked at the boot sector and here is what it showed.

92317539.jpg

 

 

I ran a deeper search and this was what was found.

20130325193626.jpg

Once the search reached this cylinder, the search drastically slowed down so I left it running overnight. I thought I took a picture of the results of that, but I guess I lost it.

 

 

I tried changing the heads from "255" to "128" under geometry and then clicked on analyze. Here is what it showed.

25864417.jpg

 

 

This is pretty much everything that I have done up to this point and have had no luck.  Any help would be greatly appreciated.  I will try to rerun the deep scan and take a picture of the results and post it.

 

~John

 

 



BC AdBot (Login to Remove)

 


#2 jlarson4

jlarson4
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 27 April 2013 - 04:16 PM

Forgot to say that I was unable to mount the drive so I cannot get anything off of it.

#3 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:56 AM

Posted 27 April 2013 - 06:07 PM

Hi

 

When I've seen situations similar to yours in the past it is almost always a physical problem with the drive. This can make it difficult to recover the data with a software solution. We can check it a little further as long as the drive is not making any strange noises like loud clicks or beeping that it did not make when it was working normally.

 

I'd like to see the report from the DISK HEALTH program that you ran in PartedMagic. The easiest way to do this is

Boot into PartedMagic

Double-Click the DISK HEALTH icon on the desktop

Double click the bad drive

Click the VIEW OUTPUT button and select and copy all the text in it and paste it in your reply here.

 

To reply here from PartedMagic

Connect the computer to the internet (should be if it is hardwired, if not click the wireless networking icon in the lower right to connect to a wireless network)

Open FireFox from the PartedMagic desktop

Login to this forum and post your reply pasting in the data from the DISK HEALTH report so I can look at it.

 

If you have difficulty replying here from PartedMagic, let me know and I'll give you some instructions for saving the file not another drive or USB key so that you can reply via your normal OS.

Even though there is a Windows version of that Disk Health program, I prefer that you get the report from PartedMagic because it will not try to automatically identify and mount partitions on the drive like Windows does.

 

Shutdown the computer and disconnect the bad drive and put it some place safe. I'll reply as soon as I can.

 

James


Edited by James Litten, 27 April 2013 - 06:08 PM.


#4 jlarson4

jlarson4
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 29 April 2013 - 04:12 PM

Here is what you requested.

 

smartctl 6.0 2012-10-10 r3643 [i686-linux-3.7.9-pmagic] (local build)
Copyright © 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST1500LM003-9YH148
Serial Number:    Z110FGQ2
LU WWN Device Id: 5 000c50 02dfcec86
Firmware Version: CC9F
User Capacity:    1,500,301,910,016 bytes [1.50 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Apr 29 16:11:59 2013 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         (  667) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 382) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x103b)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   092   078   006    Pre-fail  Always       -       1797924803
  3 Spin_Up_Time            0x0003   096   090   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       638
  5 Reallocated_Sector_Ct   0x0033   098   098   036    Pre-fail  Always       -       1776
  7 Seek_Error_Rate         0x000f   067   062   030    Pre-fail  Always       -       8602125543
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       170
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       162
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       11395
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       2
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   051   045    Old_age   Always       -       34 (Min/Max 25/34)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       62
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       845
194 Temperature_Celsius     0x0022   034   049   000    Old_age   Always       -       34 (0 5 0 0 0)
195 Hardware_ECC_Recovered  0x001a   039   031   000    Old_age   Always       -       1797924803
197 Current_Pending_Sector  0x0012   001   001   000    Old_age   Always       -       13607
198 Offline_Uncorrectable   0x0010   001   001   000    Old_age   Offline      -       13607
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       219691872157908
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       664496158
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2088773886

SMART Error Log Version: 1
ATA Error Count: 11124 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 11124 occurred at disk power-on lifetime: 170 hours (7 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 a8 c8 4b 00  Error: UNC at LBA = 0x004bc8a8 = 4966568

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 07 a7 c8 4b 40 00      00:06:40.133  READ DMA EXT
  25 03 08 9f c8 4b 40 00      00:06:40.088  READ DMA EXT
  25 03 08 37 00 60 40 00      00:06:40.087  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:37.993  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:37.964  READ DMA EXT

Error 11123 occurred at disk power-on lifetime: 170 hours (7 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 a8 c8 4b 00  Error: UNC at LBA = 0x004bc8a8 = 4966568

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 07 a7 c8 4b 40 00      00:06:35.321  READ DMA EXT
  25 03 08 9f c8 4b 40 00      00:06:35.273  READ DMA EXT
  25 03 08 37 00 60 40 00      00:06:35.271  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:33.169  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:33.141  READ DMA EXT

Error 11122 occurred at disk power-on lifetime: 170 hours (7 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 a8 c8 4b 00  Error: UNC at LBA = 0x004bc8a8 = 4966568

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 07 a7 c8 4b 40 00      00:06:30.564  READ DMA EXT
  25 03 08 9f c8 4b 40 00      00:06:30.510  READ DMA EXT
  25 03 08 37 00 60 40 00      00:06:30.509  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:28.401  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:28.373  READ DMA EXT

Error 11121 occurred at disk power-on lifetime: 170 hours (7 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 a8 c8 4b 00  Error: UNC at LBA = 0x004bc8a8 = 4966568

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 07 a7 c8 4b 40 00      00:06:25.695  READ DMA EXT
  25 03 08 9f c8 4b 40 00      00:06:25.671  READ DMA EXT
  25 03 08 37 00 60 40 00      00:06:25.669  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:23.663  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:06:23.658  READ DMA EXT

Error 11120 occurred at disk power-on lifetime: 170 hours (7 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 a8 c8 4b 00  Error: UNC at LBA = 0x004bc8a8 = 4966568

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 07 a7 c8 4b 40 00      00:03:55.562  READ DMA EXT
  25 03 08 9f c8 4b 40 00      00:03:55.517  READ DMA EXT
  25 03 08 37 00 60 40 00      00:03:55.516  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:03:53.422  READ DMA EXT
  25 03 80 ff ff ff 4f 00      00:03:53.393  READ DMA EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%       136         4966568
# 2  Extended offline    Completed: read failure       90%       136         4966568
# 3  Conveyance offline  Completed: read failure       90%       136         4966568
# 4  Short offline       Completed: read failure       90%       136         4966568
# 5  Short offline       Completed: read failure       90%       126         4966568
# 6  Short offline       Completed: read failure       90%       125         4966568

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.



#5 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:56 AM

Posted 29 April 2013 - 04:59 PM

I'm sorry to say it but that has the symptoms of a physical problem. Probably a problem with one or more of the heads. To recover the data from it, it most likely needs to be disassembled in a clean room by a professional. Seagate offers a service like this but it can be expensive because of the equipment and skills required to perform this type of recovery.

 

I wish I had better news for you.

James



#6 jlarson4

jlarson4
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:05:56 AM

Posted 29 April 2013 - 07:45 PM

That's what I was worried about. Do you think it may be worthwhile to try to repair the boot sector or partition anyway?

Also, I have read about some people formatting their drive and then using a program like Recuva (I think that was it) to recover whatever data they could. What's your thought?

Looks like I'll be calling Seagate since it's still under warranty and get a new one.

Thanks for the help.

John

#7 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:56 AM

Posted 29 April 2013 - 08:28 PM

Hi John

 

I don't think the repairs can be made with software because it can't read important sectors.

 

In order for something like Recuva to work it would need to read the data in the sectors on the platters of the disk drive. In your case the problem is preventing you from being able to read the data in many sectors so it won't get everything if anything at all. If you aren't going to have a professional open it up and recover it then your best bet would probably be to run GNU ddrescue to make an image of it (may take days or even weeks in your case) and then try to run something like Recuva against the image. Even then, I'm not very optimistic based on past experience with drives that have similar symptoms to yours.

 

If you want to try to get specific types of files off of it like pictures or documents, you can try PhotoRec which is free and included with TestDisk. There is also the free trial of the relatively inexpensive software called Restorer Ultimate that may be able to find enough to piece together a temporary file system and recover some files.

 

Remember, though, that running any of these tools may make the problem worse depending on what is causing it.

 

James






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users