[SOLVED] XFS partition or Harddrive failing

mclang · 2009-03-08 12:47:24

Hello

My /home XFS-formatted partition is in different disk (seagate 750G). Lately it has begun failing constantly when doing lots of copying/moving work with following type of errors:
- cannot read first 512 bytes
- mount: special device "dev/mount-by-label/home" does not exist

The last one happened during normal boot. After powering off, waiting a while and booting again all was good - until I tried to backup my data, when midway while copying I got:

FXS metadata write error block 0x403e880 in sdb1
I/O error in filesystem meta-data ("xlog_iodone") error 5 buf count 2560
Filesystem: Log I/O Error Detected

I tried to find solution from several forums, but all I got was to try "xfs_repair". It doesn't find any errors when the partition/drive is working properly, but after I tried backup my data and got those errors above, "xfs_repair" gives following:

[root@golved ~]# xfs_repair /dev/sda1
Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval -1
fatal error -- Input/Output error

I am currently trying "smartmontools", but at leas now it doesn't work. Maybe after reboot it gives me some sensible output. Meanwhile, can any of you give me any pointers how to find out is the problem in XFS filesystem or in my year old Seagate Barracuda 7200.11/12(?) 750G harddrive? How about getting my data out, is there way to bypass the logging that xfs does? I am thinking about that because of those "Log I/O errors"... Currently, whenever the drive mounts properly, I can do some copying but it halts eventually. Maybe disabling logging and all other non-needed things from xfs would let me backup more data before I/O errors arise?

Last edited by mclang (2009-03-11 06:43:21)

jwcxz · 2009-03-08 14:28:27

The more reviews I read on NewEgg, the more scared I am to buy a high-capacity drive. The failure rates are definitely not low.

You can try using dd_rescue to pull all the data (rather, as much as you can) off of the drive. This, of course, assumes that you have some >750 gig drive lying around.

mclang · 2009-03-08 17:23:09

Okay, after couple of boots smartctl gave following:

smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST3750330AS
Serial Number:    9QK06CMQ
Firmware Version: SD15
User Capacity:    750 156 374 016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Mar  8 18:42:27 2009 EET
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:      ( 121)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline 
data collection:          ( 634) 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:      ( 172) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x103b)    SCT Status 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   101   097   006    Pre-fail  Always       -       52655725
  3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       26
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       2043
  7 Seek_Error_Rate         0x000f   070   060   030    Pre-fail  Always       -       8613925167
  9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       8431
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       26
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   031   031   000    Old_age   Always       -       69
188 Unknown_Attribute       0x0032   100   099   000    Old_age   Always       -       8590065666
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   070   055   045    Old_age   Always       -       30 (Lifetime Min/Max 28/32)
194 Temperature_Celsius     0x0022   030   045   000    Old_age   Always       -       30 (0 21 0 0)
195 Hardware_ECC_Recovered  0x001a   047   022   000    Old_age   Always       -       52655725
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       4
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       4
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 100 (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 100 occurred at disk power-on lifetime: 8426 hours (351 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 02      00:27:26.893  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      00:27:26.887  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:27:26.733  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      00:27:21.427  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      00:27:21.420  IDENTIFY DEVICE

Error 99 occurred at disk power-on lifetime: 8426 hours (351 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 02      00:27:26.887  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:27:26.733  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      00:27:21.427  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      00:27:21.420  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:27:21.267  NOP [Abort queued commands]

Error 98 occurred at disk power-on lifetime: 8426 hours (351 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 02      00:27:21.427  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      00:27:21.420  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:27:21.267  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      00:27:20.931  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      00:27:20.887  IDENTIFY DEVICE

Error 97 occurred at disk power-on lifetime: 8426 hours (351 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 02      00:27:21.420  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      00:27:21.267  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      00:27:20.931  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      00:27:20.887  IDENTIFY DEVICE
  c8 00 30 af 05 ae e3 00      00:27:17.797  READ DMA

Error 96 occurred at disk power-on lifetime: 8426 hours (351 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
  -- -- -- -- -- -- --
  04 71 04 9d 00 32 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 02      00:27:20.931  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      00:27:20.887  IDENTIFY DEVICE
  c8 00 30 af 05 ae e3 00      00:27:17.797  READ DMA
  c8 00 40 e7 ce 4a e4 00      00:27:17.774  READ DMA
  c8 00 10 a7 44 b9 e3 00      00:27:17.747  READ DMA

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%      8428         6574443
# 2  Short offline       Completed: read failure       90%      8428         184053
# 3  Extended offline    Completed: read failure       90%      8428         6574443
# 4  Short offline       Completed: read failure       90%      8427         184053

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.

All errors seem to be same type, some kind of abort signals... Too bad I don't understand anything of this, so I my bag is out of solutions

That "dd_rescue" could work if I had 750G drive, which I dont. I think now my only option is mount the home partition as read only to prevent more damage, and try to copy remaining data in smaller pieces - maybe then the drive won't bork.

mclang · 2009-03-08 17:39:24

Others seems to have also problems with Seagate 7200.11

New firmware update could solve the matter:
http://seagate.custkb.com/seagate/crm/s … cId=207951

My drive is ST3750330AS & SD15 so it IS affected... But do I have the guts to try firmware update without knowing if it destroys my data? And why this is having after one year? Or is this the root of the problem at all?

OK, has to get back to booting my pc again and salvaging some more files...

Edit:
Now the drive disappeared also from BIOS
I hope cutting power completely fixes this... Cables etc should be good, I checked them of course.

Last edited by mclang (2009-03-08 17:48:07)

mclang · 2009-03-11 06:53:00

Solved,

meaning that the drive will be replaced as soon as possible. I managed to save most of the data but not all. Some files just wouldn't copy... I didn't have time to try the firmware update, so I don't know if that would have fixed the problem.

One note:
copying home to ntfs drive may NOT be the best idea. It of course messed all permissions
I hope following fixes this

$ find . -type f -exec chmod 644 {} \;
$ find . -type d -exec chmod 755 {} \;

Arch Linux

#1 2009-03-08 12:47:24

[SOLVED] XFS partition or Harddrive failing

#2 2009-03-08 14:28:27

Re: [SOLVED] XFS partition or Harddrive failing

#3 2009-03-08 17:23:09

Re: [SOLVED] XFS partition or Harddrive failing

#4 2009-03-08 17:39:24

Re: [SOLVED] XFS partition or Harddrive failing

#5 2009-03-11 06:53:00

Re: [SOLVED] XFS partition or Harddrive failing

Board footer