Beiträge von Pike of the Lake

Pike of the Lake · 18. Oktober 2014

I don't know much about this stuff, but these errors don't look good.... What do you think? Also, I had to delete some info as it wouldn't allow me to post more than 10,000 characters. I deleted what I thought was irrelevant.
Thanks so much for the help David.

Code

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.


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   117   083   006    Pre-fail  Always       -       132114559
  3 Spin_Up_Time            0x0003   100   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       314
  5 Reallocated_Sector_Ct   0x0033   001   001   036    Pre-fail  Always   FAILING_NOW 4095
  7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       83792772
  9 Power_On_Hours          0x0032   059   059   000    Old_age   Always       -       36360
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       221
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   095   095   000    Old_age   Always       -       5
188 Command_Timeout         0x0032   100   083   000    Old_age   Always       -       390848053341
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       150
190 Airflow_Temperature_Cel 0x0022   053   036   045    Old_age   Always   In_the_past 47 (101 21 47 47)
194 Temperature_Celsius     0x0022   047   064   000    Old_age   Always       -       47 (0 12 0 0)
195 Hardware_ECC_Recovered  0x001a   051   021   000    Old_age   Always       -       132114559
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       249614909345285
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       1105008341
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1405262392


SMART Error Log Version: 1
ATA Error Count: 28784 (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 28784 occurred at disk power-on lifetime: 35107 hours (1462 days + 19 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 00      09:28:29.808  SET FEATURES [Set transfer mode]
  ff 00 00 00 00 00 00 00      09:28:29.747  [VENDOR SPECIFIC]
  00 00 00 00 00 00 00 04      09:28:29.747  NOP [Abort queued commands]
  25 00 08 ff ff ff ef 00      09:28:29.747  READ DMA EXT
  ef 03 46 00 00 00 a0 00      09:28:29.525  SET FEATURES [Set transfer mode]


Error 28783 occurred at disk power-on lifetime: 35107 hours (1462 days + 19 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 00      09:28:29.525  SET FEATURES [Set transfer mode]
  ff 00 00 00 00 00 00 00      09:28:29.464  [VENDOR SPECIFIC]
  00 00 00 00 00 00 00 04      09:28:29.464  NOP [Abort queued commands]
  25 00 08 ff ff ff ef 00      09:28:29.464  READ DMA EXT
  ef 03 46 00 00 00 a0 00      09:28:29.241  SET FEATURES [Set transfer mode]


Error 28782 occurred at disk power-on lifetime: 35107 hours (1462 days + 19 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 00      09:28:29.525  SET FEATURES [Set transfer mode]
  ff 00 00 00 00 00 00 00      09:28:29.464  [VENDOR SPECIFIC]
  00 00 00 00 00 00 00 04      09:28:29.464  NOP [Abort queued commands]
  25 00 08 ff ff ff ef 00      09:28:29.464  READ DMA EXT
  ef 03 46 00 00 00 a0 00      09:28:29.241  SET FEATURES [Set transfer mode]


Error 28781 occurred at disk power-on lifetime: 35107 hours (1462 days + 19 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 00      09:28:29.241  SET FEATURES [Set transfer mode]
  ff 00 00 00 00 00 00 00      09:28:29.181  [VENDOR SPECIFIC]
  00 00 00 00 00 00 00 04      09:28:29.181  NOP [Abort queued commands]
  25 00 08 ff ff ff ef 00      09:28:29.181  READ DMA EXT
  ef 03 46 00 00 00 a0 00      09:28:28.958  SET FEATURES [Set transfer mode]


Error 28780 occurred at disk power-on lifetime: 35107 hours (1462 days + 19 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 46 00 00 00 a0 00      09:28:29.241  SET FEATURES [Set transfer mode]
  ff 00 00 00 00 00 00 00      09:28:29.181  [VENDOR SPECIFIC]
  00 00 00 00 00 00 00 04      09:28:29.181  NOP [Abort queued commands]
  25 00 08 ff ff ff ef 00      09:28:29.181  READ DMA EXT
  ef 03 46 00 00 00 a0 00      09:28:28.958  SET FEATURES [Set transfer mode]


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.

Alles anzeigen

Pike of the Lake · 16. Oktober 2014

Hi Everyone,

I am very new to OMV. I was running an smb server off my dd-wrt router and wasn't satisfied with the speeds so I bought a banana pi and am now running OMV with a usb attached 1.5tb hdd.

The problem I'm encountering is that when I start up OMV, it hangs and I see the red light on the hdd go on non-stop. SMART analysis is showing a failure on the hdd, could that be hanging the system?

If I disconnect the hdd, OMV starts up no problem. I can then reconnect the hdd and it seems to work ok (although my network speeds are worse than they were with the dd-wrt setup...)

If you would like me to print output from the OMV, could you please direct me on how I do that? I'm assuming I just copy from the OMV gui and then place it in the source option in this forum....

Many thanks!

Beiträge von Pike of the Lake

Hanging on boot with hdd going crazy

Hanging on boot with hdd going crazy