Jump to content


Photo

HDD filesystem error

ET9000

  • Please log in to reply
18 replies to this topic

#1 Robinson

  • Senior Member
  • 2,523 posts

+30
Good

Posted 10 September 2014 - 19:11

Hi,

 

Almost a year ago I had a problem with my previous internal HDD on my ET9000 and so I bought a new one.

Unfortunately, it is starting to play tricks with me too. :(

I recently got the following error:

/dev/sda1: UNEXPECTED INCONSISTENCY;
RUN fsck MANUALLY.
(i.e., without -a or -p options)

Here is an output from dmesg:

 

root@et9x00:~# dmesg
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 a0 00 00 08 00
end_request: I/O error, dev sda, sector 1956
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:8c:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 8c
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 88 00 00 08 00
end_request: I/O error, dev sda, sector 1932
ata1: EH complete
EXT4-fs error (device sda1): __ext4_get_inode_loc:3762: inode #3115: block 243:
comm enigma2: unable to read itable block
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:30:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:31:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 31
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 30 00 00 08 00
end_request: I/O error, dev sda, sector 1841
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:a0:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:a4:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 a4
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 a0 00 00 08 00
end_request: I/O error, dev sda, sector 1956
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:10:80:07:00/00:00:00:00:00/e0 tag 0 dma 8192 in
         res 51/40:00:84:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 84
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 80 00 00 10 00
end_request: I/O error, dev sda, sector 1924
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:8c:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 8c
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 88 00 00 08 00
end_request: I/O error, dev sda, sector 1932
ata1: EH complete
EXT4-fs error (device sda1): __ext4_get_inode_loc:3762: inode #3107: block 243:
comm enigma2: unable to read itable block
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:08:02:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:08:02:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 02 08
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 02 08 00 00 08 00
end_request: I/O error, dev sda, sector 520
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:f0:01:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:f2:01:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 01 f2
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 01 f0 00 00 08 00
end_request: I/O error, dev sda, sector 498
ata1: EH complete
EXT4-fs error (device sda1): __ext4_get_inode_loc:3762: inode #205: block 61: co
mm enigma2: unable to read itable block
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:30:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:31:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 31
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 30 00 00 08 00
end_request: I/O error, dev sda, sector 1841
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:80:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:84:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 84
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 80 00 00 08 00
end_request: I/O error, dev sda, sector 1924
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:88:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:8c:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 8c
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 88 00 00 08 00
end_request: I/O error, dev sda, sector 1932
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x60000000 action 0x0
ata1.00: BMDMA stat 0x4
ata1: SError: { }
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:a0:07:00/00:00:00:00:00/e0 tag 0 dma 4096 in
         res 51/40:00:a4:07:00/00:00:00:00:00/00 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        00 00 07 a4
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 00 00 07 a0 00 00 08 00
end_request: I/O error, dev sda, sector 1956
ata1: EH complete
EXT4-fs error (device sda1): __ext4_get_inode_loc:3762: inode #3114: block 243:
comm enigma2: unable to read itable block
root@et9x00:~#

 

And here is output from smartctl:

 

root@et9x00:~# smartctl -a /dev/sda
smartctl 5.42 2011-10-20 r3458 [mips-linux-3.8.7] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.12
Device Model:     ST3500418AS
Serial Number:    6VM10A3C
LU WWN Device Id: 5 000c50 013e54b49
Firmware Version: CC34
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
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:    Wed Sep 10 20:02:48 2014 CEST
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:                (  600) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off supp
ort.
                                        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:        (  95) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103f) 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   088   088   006    Pre-fail  Always       -
       103319861
  3 Spin_Up_Time            0x0003   099   097   000    Pre-fail  Always       -
       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -
       3707
  5 Reallocated_Sector_Ct   0x0033   090   090   036    Pre-fail  Always       -
       433
  7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -
       8709548976
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -
       12669
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -
       0
 12 Power_Cycle_Count       0x0032   097   097   020    Old_age   Always       -
       3707
183 Runtime_Bad_Block       0x0000   100   100   000    Old_age   Offline      -
       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -
       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -
       312
188 Command_Timeout         0x0032   098   098   000    Old_age   Always       -
       4295294982
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -
       0
190 Airflow_Temperature_Cel 0x0022   063   048   045    Old_age   Always       -
       37 (Min/Max 31/48)
194 Temperature_Celsius     0x0022   037   052   000    Old_age   Always       -
       37 (0 15 0 0 0)
195 Hardware_ECC_Recovered  0x001a   033   026   000    Old_age   Always       -
       103319861
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -
       13
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -
       13
199 UDMA_CRC_Error_Count    0x003e   200   195   000    Old_age   Always       -
       144
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -
       102714142902692
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -
       1221977546
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -
       3430642531

SMART Error Log Version: 1
ATA Error Count: 312 (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 312 occurred at disk power-on lifetime: 12668 hours (527 days + 20 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 a4 07 00 00  Error: UNC at LBA = 0x000007a4 = 1956

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 a0 07 00 e0 00   1d+05:15:37.311  READ DMA
  27 00 00 00 00 00 e0 00   1d+05:15:37.283  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+05:15:37.280  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   1d+05:15:37.243  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   1d+05:15:37.163  READ NATIVE MAX ADDRESS EXT

Error 311 occurred at disk power-on lifetime: 12668 hours (527 days + 20 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 8c 07 00 00  Error: UNC at LBA = 0x0000078c = 1932

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 88 07 00 e0 00   1d+05:15:34.373  READ DMA
  27 00 00 00 00 00 e0 00   1d+05:15:34.346  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+05:15:34.343  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   1d+05:15:34.324  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   1d+05:15:34.271  READ NATIVE MAX ADDRESS EXT

Error 310 occurred at disk power-on lifetime: 12668 hours (527 days + 20 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 84 07 00 00  Error: UNC at LBA = 0x00000784 = 1924

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 80 07 00 e0 00   1d+05:15:31.451  READ DMA
  27 00 00 00 00 00 e0 00   1d+05:15:31.424  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+05:15:31.421  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   1d+05:15:31.402  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   1d+05:15:31.357  READ NATIVE MAX ADDRESS EXT

Error 309 occurred at disk power-on lifetime: 12668 hours (527 days + 20 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 31 07 00 00  Error: UNC at LBA = 0x00000731 = 1841

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 30 07 00 e0 00   1d+05:15:28.577  READ DMA
  c8 00 08 08 66 7a e3 00   1d+05:15:28.518  READ DMA
  c8 00 08 08 4c 87 e9 00   1d+05:15:28.503  READ DMA
  c8 00 08 08 08 00 e5 00   1d+05:15:24.348  READ DMA
  c8 00 08 08 aa 5b eb 00   1d+05:15:24.335  READ DMA

Error 308 occurred at disk power-on lifetime: 12666 hours (527 days + 18 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 f2 01 00 00  Error: UNC at LBA = 0x000001f2 = 498

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 f0 01 00 e0 00   1d+05:15:21.226  READ DMA
  27 00 00 00 00 00 e0 00   1d+05:15:21.199  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   1d+05:15:21.196  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   1d+05:15:21.178  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   1d+05:15:21.125  READ NATIVE MAX ADDRESS EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


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.

root@et9x00:~#

 

Any chance to bring this HDD to normal operation?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HDD filesystem error #2 betacentauri

  • PLi® Core member
  • 6,135 posts

+271
Excellent

Posted 10 September 2014 - 19:24

Hi,

 

doesn't look good. Reallocated_Sector_Ct 433, Current_Pending_Sector 13, error rates > 0. HDD is almost dead from my sight. And I don't think that SATA cable is the problem, because you shouldn't have reallocated sectors in this case.

 

It should look like this:
 

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   067   064   025    Pre-fail  Always       -       10165
  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       3696
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       6418
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       3021
181 Program_Fail_Cnt_Total  0x0022   100   100   000    Old_age   Always       -       150000
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       422
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   048   000    Old_age   Always       -       36 (Min/Max 15/52)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       1
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       3713

This is my ~2 years old hdd in my et9200.
 


Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: HDD filesystem error #3 40H3X

  • PLi® Contributor
  • 3,786 posts

+122
Excellent

Posted 10 September 2014 - 20:05

I would do a long selftest using smartctl -t long /dev/hddname but it doesn't look promising

Hardware: Vu+ Uno 4k SE - Samsung HM500JI 500GB 2.5 inch - aXas 4K Ultra HD - Amiko Viper Combo HDD - Edision OS mio 4K - Spycat Mini Plus - Vu+ Zero - Vu+ Duo - WD 1TB - Fuba 78 cm - Tripleblock LNB Quad 19.2/23.5/28.2 - NAS 4TB RAID 1
Software : OpenPLi - OScam - Settings van Hans  -  Autotimer  -  EPGImport


Re: HDD filesystem error #4 Robinson

  • Senior Member
  • 2,523 posts

+30
Good

Posted 10 September 2014 - 22:30

I have now done the long test but the output of smartctl -a /dev/sda1 is almost identical as the one I showed earlier today.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HDD filesystem error #5 Robinson

  • Senior Member
  • 2,523 posts

+30
Good

Posted 10 September 2014 - 23:24

What 3.5" HDD could you please recommend for my ET9000 box? I need about 500 GB.

As an alternative, it might also be a 2.5" HDD but they are usually more expensive.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HDD filesystem error #6 40H3X

  • PLi® Contributor
  • 3,786 posts

+122
Excellent

Posted 11 September 2014 - 08:58

I have a WDC WD10ERX (1TB) (or the newer model) Westeren Digital is IMHO always a good choice.


Edited by 40H3X, 11 September 2014 - 08:58.

Hardware: Vu+ Uno 4k SE - Samsung HM500JI 500GB 2.5 inch - aXas 4K Ultra HD - Amiko Viper Combo HDD - Edision OS mio 4K - Spycat Mini Plus - Vu+ Zero - Vu+ Duo - WD 1TB - Fuba 78 cm - Tripleblock LNB Quad 19.2/23.5/28.2 - NAS 4TB RAID 1
Software : OpenPLi - OScam - Settings van Hans  -  Autotimer  -  EPGImport


Re: HDD filesystem error #7 betacentauri

  • PLi® Core member
  • 6,135 posts

+271
Excellent

Posted 11 September 2014 - 12:28

If box is running very often and around the box is not much space, I would propose to use a fan. It's possible to place the fan under the hdd.
And don't buy a hdd with 7200 rpms.
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: HDD filesystem error #8 Robinson

  • Senior Member
  • 2,523 posts

+30
Good

Posted 11 September 2014 - 12:30

For the time being I'm using a spare external USB HDD.

betacentauri, I understand you recommend a slower speed HDD because of heat?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HDD filesystem error #9 Erik Slagter

  • PLi® Core member
  • 45,776 posts

+512
Excellent

Posted 11 September 2014 - 12:35

From the dmesg output alone one can already conclude that the harddisk is defective.

I'd recommend a 2.5" harddisk, they get a lot less warm, and it's heat that often destroys harddisks.
* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: HDD filesystem error #10 Dimitrij

  • PLi® Core member
  • 6,829 posts

+228
Excellent

Posted 11 September 2014 - 14:56



I'd recommend a 2.5" harddisk, they get a lot less warm, and it's heat that often destroys harddisks.

Great recommendations.
And they are much quieter.


Lunix3-4K/VU+solo4k(thanks guys to gisclub.tv)


Re: HDD filesystem error #11 WanWizard

  • Forum Moderator
    PLi® Core member
  • 52,666 posts

+1,023
Excellent

Posted 11 September 2014 - 14:59

And don't forget: silent.

 

My main box is in the bedroom, and does a lot of recording, I don't think I would have gotten much sleep with a noisy 3,5" disk in a quiet bedroom... ;)


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), Octagon SF8008 (S2+T2), SAB Alpha Triple HD (S2+T2), Zgemma H9.2H (T2+fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: HDD filesystem error #12 betacentauri

  • PLi® Core member
  • 6,135 posts

+271
Excellent

Posted 11 September 2014 - 15:40

You don't need a hdd with 7200 rpms. A modern hdd with 5400 rpms is fast enough for > 4 hd recordings and it produces less heat (and noise).
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: HDD filesystem error #13 Pr2

  • PLi® Contributor
  • 4,133 posts

+172
Excellent

Posted 11 September 2014 - 16:01

Hi,

 

Open up your ET-9000 and check the condo on the power supply unit.

I need to replace some condo on my two ET9000, one was already faulty when the other one was not yet but condo were already defective.

 

Your HDD crash can come from power supply problem on the HDD coming from the defective condo.

 

Pr2


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: HDD filesystem error #14 MiLo

  • PLi® Core member
  • 13,951 posts

+294
Excellent

Posted 12 September 2014 - 16:18



I'd recommend a 2.5" harddisk, they get a lot less warm, and it's heat that often destroys harddisks.

Great recommendations.
And they are much quieter.

 

And quicker to spin up. Usually starts in about 2 seconds, most 3.5" disks need over 6 seconds to spin up.

 

2.5 is a perfact "in between" solution, not as expensive as SSD, but also not as hot, noisy and slow to spin up as 3.5" disks.


Real musicians never die - they just decompose

Re: HDD filesystem error #15 Robinson

  • Senior Member
  • 2,523 posts

+30
Good

Posted 12 September 2014 - 17:42

Thank you for your recommendations. I will now stay with my external USB HDD.

By the way it is mounted under /media/usb/ and therefore /media/hdd/ dirctory does not exist.

In such a case it seems impossible for OpenWebif to go to recordings. It looks like Openwebif is looking for /media/hdd/movie/ directory to start from. If it does not exist I get a constant spinner on OpenWebif. Of course, I can use other Openwebif features but not streaming recordings.

Does anyone know how to solve it? In other words, how to either make sure Openwebif does not require /media/hdd/movie/ (I guess it requires code change) or make sure /media/hdd/movie stays after restart.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HDD filesystem error #16 Robinson

  • Senior Member
  • 2,523 posts

+30
Good

Posted 13 September 2014 - 09:30

OK, I think I solved by adding /media/usb/movie to recordings location.


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HDD filesystem error #17 MiLo

  • PLi® Core member
  • 13,951 posts

+294
Excellent

Posted 13 September 2014 - 09:38

I've solved the bug in the webinterface.


Real musicians never die - they just decompose

Re: HDD filesystem error #18 Robinson

  • Senior Member
  • 2,523 posts

+30
Good

Posted 13 September 2014 - 22:52

So do I understand you correctly, MiLo, that from now on a missing /media/hdd/ directory will not bother OpenWebif?


ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HDD filesystem error #19 MiLo

  • PLi® Core member
  • 13,951 posts

+294
Excellent

Posted 14 September 2014 - 08:16

Yup. It will do as the normal movie list does, and pick the largest attached storage device as default recording device.


Real musicians never die - they just decompose





Also tagged with one or more of these keywords: ET9000

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users