Beiträge von jigg3

jigg3 · 19. Mai 2015

Hi Guys,

my NAS is not able to hybernate any more.

Code

PM: Starting manual resume from disk
May 19 10:13:01 NAS kernel: [    1.534091] PM: Hibernation image partition 8:5 present
May 19 10:13:01 NAS kernel: [    1.534093] PM: Looking for hibernation image.
May 19 10:13:01 NAS kernel: [    1.534253] PM: Image not found (code -22)
May 19 10:13:01 NAS kernel: [    1.534256] PM: Hibernation image not present or could not be loaded.

Code

root@NAS:~# pm-is-supported --hibernate
root@NAS:~# echo $?
0

As soon as I start my NAS by send magic packets, it is booting as if it was shut down.

Thank you guys

jigg3 · 19. Mai 2015

Code

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     10096         -
# 2  Short offline       Completed without error       00%     10072         -
# 3  Short offline       Completed without error       00%     10049         -
# 4  Short offline       Completed without error       00%     10025         -
# 5  Short offline       Completed without error       00%     10003         -
# 6  Short offline       Completed without error       00%      9978         -
# 7  Short offline       Completed without error       00%      9954         -
# 8  Short offline       Completed without error       00%      9930         -
# 9  Short offline       Completed without error       00%      9906         -
#10  Short offline       Completed without error       00%      9882         -
#11  Short offline       Completed without error       00%      9858         -
#12  Short offline       Completed without error       00%      9834         -
#13  Short offline       Completed without error       00%      9810         -
#14  Short offline       Completed without error       00%      9786         -
#15  Short offline       Completed without error       00%      9762         -
#16  Short offline       Completed without error       00%      9738         -
#17  Short offline       Completed without error       00%      9714         -
#18  Short offline       Completed without error       00%      9690         -


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.


SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    34 Celsius
Power Cycle Min/Max Temperature:     22/37 Celsius
Lifetime    Min/Max Temperature:     18/42 Celsius
Under/Over Temperature Limit Count:   0/0
SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (236)


Index    Estimated Time   Temperature Celsius
 237    2015-05-19 05:24    34  ***************
 ...    ..(120 skipped).    ..  ***************
 358    2015-05-19 07:25    34  ***************
 359    2015-05-19 07:26    37  ******************
 ...    ..(108 skipped).    ..  ******************
 468    2015-05-19 09:15    37  ******************
 469    2015-05-19 09:16    36  *****************
 ...    ..(  9 skipped).    ..  *****************
   1    2015-05-19 09:26    36  *****************
   2    2015-05-19 09:27    35  ****************
 ...    ..( 30 skipped).    ..  ****************
  33    2015-05-19 09:58    35  ****************
  34    2015-05-19 09:59    34  ***************
 ...    ..(133 skipped).    ..  ***************
 168    2015-05-19 12:13    34  ***************
 169    2015-05-19 12:14     ?  -
 170    2015-05-19 12:15    34  ***************
 ...    ..(  3 skipped).    ..  ***************
 174    2015-05-19 12:19    34  ***************
 175    2015-05-19 12:20    33  **************
 176    2015-05-19 12:21    34  ***************
 ...    ..( 59 skipped).    ..  ***************
 236    2015-05-19 13:21    34  ***************


SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)


SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2           22  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2           22  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4        76269  Vendor specific

Alles anzeigen

jigg3 · 19. Mai 2015

Code

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 9
    CR     = Command Register
    FEATR  = Features Register
    COUNT  = Count (was: Sector Count) Register
    LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
    LH     = LBA High (was: Cylinder High) Register    ]   LBA
    LM     = LBA Mid (was: Cylinder Low) Register      ] Register
    LL     = LBA Low (was: Sector Number) Register     ]
    DV     = Device (was: Device/Head) Register
    DC     = Device Control Register
    ER     = Error register
    ST     = Status register
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 9 [8] occurred at disk power-on lifetime: 13914 hours (579 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 COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     21:11:08.647  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 08     21:11:08.647  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     21:11:08.647  SMART READ LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08     21:11:08.646  SMART WRITE LOG
  b0 00 d5 00 01 00 00 00 c2 4f 09 00 08     21:11:08.645  SMART READ LOG


Error 8 [7] occurred at disk power-on lifetime: 13893 hours (578 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     00:28:08.165  SMART READ LOG
  60 04 00 00 08 00 00 0c 31 3a 38 40 08     00:28:08.117  READ FPDMA QUEUED
  60 04 00 00 00 00 00 0c 31 36 38 40 08     00:28:08.117  READ FPDMA QUEUED
  60 04 00 00 f0 00 00 0c 31 32 38 40 08     00:28:08.117  READ FPDMA QUEUED
  60 04 00 00 e8 00 00 0c 31 2e 38 40 08     00:28:08.117  READ FPDMA QUEUED


Error 7 [6] occurred at disk power-on lifetime: 13893 hours (578 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     00:28:08.107  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     00:28:08.107  SMART READ LOG
  60 04 00 00 b8 00 00 0c 30 f2 38 40 08     00:28:08.056  READ FPDMA QUEUED
  60 04 00 00 b0 00 00 0c 30 ee 38 40 08     00:28:08.056  READ FPDMA QUEUED
  60 04 00 00 a8 00 00 0c 30 ea 38 40 08     00:28:08.056  READ FPDMA QUEUED


Error 6 [5] occurred at disk power-on lifetime: 13864 hours (577 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     00:48:52.930  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     00:48:52.929  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 08     00:48:52.929  SMART READ LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08     00:48:52.928  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08     00:48:52.927  SMART WRITE LOG


Error 5 [4] occurred at disk power-on lifetime: 13864 hours (577 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     00:48:12.915  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 08     00:48:12.915  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08     00:48:12.915  SMART READ LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08     00:48:12.913  SMART WRITE LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 08     00:48:12.912  SMART READ LOG


Error 4 [3] occurred at disk power-on lifetime: 9797 hours (408 days + 5 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08  3d+20:15:07.069  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08  3d+20:15:07.069  SMART READ LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08  3d+20:15:07.064  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08  3d+20:15:07.061  SMART WRITE LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 08  3d+20:15:07.061  SMART READ LOG


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


  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  04 -- 51 00 01 00 00 00 00 00 00 00 00  Error: ABRT


  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08  2d+22:29:34.591  SMART READ LOG
  b0 00 d5 00 01 00 00 00 c2 4f e1 00 08  2d+22:29:34.591  SMART READ LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08  2d+22:29:34.585  SMART WRITE LOG
  b0 00 d6 00 01 00 00 00 c2 4f e0 00 08  2d+22:29:34.583  SMART WRITE LOG
  b0 00 d5 00 01 00 00 00 c2 4f e0 00 08  2d+22:29:34.582  SMART READ LOG

Alles anzeigen

jigg3 · 19. Mai 2015

I'm quite not sure if my disks are really dying.

It's strange, cause I'm getting the SMART Error mails for all of my five NAS RAID disks. All the mails contain "ATA error count increased from 4 to 5". I think it is not a cable related issue. The temperatures look so far fine.

Maybe my Mainboard seems to generate such errors ?

Smart just says:
[sorry had to post it down into 3 separate posts.]

Code

smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.16.0-0.bpo.4-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net


=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68AX9N0
Serial Number:    WD-WCC1T1064107
LU WWN Device Id: 5 0014ee 208913c54
Firmware Version: 80.00A80
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   9
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Tue May 19 13:21:56 2015 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:         (38640) 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:      (   2) minutes.
Extended self-test routine
recommended polling time:      ( 255) minutes.
Conveyance self-test routine
recommended polling time:      (   5) minutes.
SCT capabilities:            (0x70bd)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.


SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   177   171   021    -    6125
  4 Start_Stop_Count        -O--CK   099   099   000    -    1304
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   100   253   000    -    0
  9 Power_On_Hours          -O--CK   081   081   000    -    13914
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    241
192 Power-Off_Retract_Count -O--CK   200   200   000    -    53
193 Load_Cycle_Count        -O--CK   200   200   000    -    1250
194 Temperature_Celsius     -O---K   116   108   000    -    34
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   200   200   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning


General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
GP/S  Log at address 0x00 has    1 sectors [Log Directory]
SMART Log at address 0x01 has    1 sectors [Summary SMART error log]
SMART Log at address 0x02 has    5 sectors [Comprehensive SMART error log]
GP    Log at address 0x03 has    6 sectors [Ext. Comprehensive SMART error log]
SMART Log at address 0x06 has    1 sectors [SMART self-test log]
GP    Log at address 0x07 has    1 sectors [Extended self-test log]
SMART Log at address 0x09 has    1 sectors [Selective self-test log]
GP    Log at address 0x10 has    1 sectors [NCQ Command Error]
GP    Log at address 0x11 has    1 sectors [SATA Phy Event Counters]
GP    Log at address 0x21 has    1 sectors [Write stream error log]
GP    Log at address 0x22 has    1 sectors [Read stream error log]
GP/S  Log at address 0x80 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x81 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x82 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x83 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x84 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x85 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x86 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x87 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x88 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x89 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x90 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x91 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x92 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x93 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x94 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x95 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x96 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x97 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x98 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x99 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0xa0 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa1 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa2 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa3 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa4 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa5 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa6 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa7 has   16 sectors [Device vendor specific log]
GP/S  Log at address 0xa8 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xa9 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xaa has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xab has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xac has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xad has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xae has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xaf has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb0 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb1 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb2 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb3 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb4 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb5 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb6 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xb7 has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xbd has    1 sectors [Device vendor specific log]
GP/S  Log at address 0xc0 has    1 sectors [Device vendor specific log]
GP    Log at address 0xc1 has   93 sectors [Device vendor specific log]
GP/S  Log at address 0xe0 has    1 sectors [SCT Command/Status]
GP/S  Log at address 0xe1 has    1 sectors [SCT Data Transfer]

Alles anzeigen

jigg3 · 19. Mai 2015

Resync of my raid.

Maybe its as well related to my not working pm-suspend

jigg3 · 18. Mai 2015

Hi guys,

am I able to add your mentioned parameters to prevent creating such files as well to the Apple Filling Service under advanced options ?

jigg3 · 18. Mai 2015

Hi there,

mostly each time, as soon as I reboot / boot my NAS it is resyncing. About two weeks ago I got a SMART Error nearly on all of my disks " ATA error count increased from 4 to 6". The SMART error seems to be disappeard so far.

So, what shall I do now? It's annoying to wait for so long time.

jigg3 · 17. Mai 2015

Hi guys,

since I experience the above mentioned problems, my NAS is resyncing each 5th or 6th reboot / startup.

Still do not know, how to fix my issue with pm-suspend and the missing wake on image.

Perhaps this is the issue :

ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

Google just says, that the system doesn't support sleep states but how to fix this ?

jigg3 · 8. Mai 2015

The output is just "0"

I have 16gig of RAM but I really do not know how to determine my size of swap.

Recently I tried to check the pm-suspend.log file but it hasn't beend touched since my issue is occuring (Monday 4th of May).

From my point of view the issue dependent due to the update of the kernel which has been released this week. Currently I'm on 3.16.0-0.bpo.4-amd64. Have tried it as well with 3-2-0 Kernel but without success.

-----

swap:

root@NAS:~# swapon -s
Filename Type Size Used Priority
/dev/sda5 partition 2421756 0 -1
------------

meanwhile I have checked the systemlog:

PM: Hibernation image partition 8:5 present
PM: looking for hibernation image
PM: Image not found (code -22)
PM: Hibernation image not present or could not be loaded.

jigg3 · 7. Mai 2015

no

pm-suspend and autoshutdown worked till yesterday.

Now, on each pm-suspend command, my system reboots after waking up by magic packets.

jigg3 · 7. Mai 2015

sorry, had been absent for a long while.

I've installed the backports kernel. as soon as I initiate pm-suspend -a or only pm-suspend , my system will be shut down.

jigg3 · 3. Mai 2015

ne tolle Tante hast du da

Dank deiner Hilfe hats geklappt.

jigg3 · 30. April 2015

Hi, hab das Skript bei mir einbinden können - vielen Dank!

Jetzt habe ich leider ein anderes Problem. Nachdem mein NAS aufgeweckt wurde, bekomme ich durchgehend "invalid checksum" im TV-Headend Webinterface und der Stream ist total kaputt.

Das Modul für meine SkyStart USB HD habe ich meiner Meinung nach korrekt eingebunden. Ein dmesg zeigt mir das Gerät auch an:

Code

root@NAS:/etc/pm/sleep.d# dmesg | grep dvb
[    1.922093] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state.
[    1.923320] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    1.924969] dvb-usb: MAC address: 00:08:c9:f0:34:c0
[    2.143036] dvb-usb: schedule remote query interval to 100 msecs.
[    2.143296] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.
[    2.143335] usbcore: registered new interface driver dvb_usb_technisat_usb2
[ 1635.770462] usbcore: deregistering interface driver dvb_usb_technisat_usb2
[ 1635.887316] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully deinitialized and disconnected.
[ 1638.284056] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in cold state, will try to load a firmware
[ 1638.284381] usb 2-1.8: firmware: direct-loading firmware dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw
[ 1638.350905] usbcore: registered new interface driver dvb_usb_technisat_usb2
[ 1638.535099] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
[ 1640.200379] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state.
[ 1640.200662] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 1640.202255] dvb-usb: MAC address: 00:08:c9:f0:34:c0
[ 1640.388654] dvb-usb: schedule remote query interval to 100 msecs.
[ 1640.388886] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.
[ 1646.024733] dvb-usb: error -71 while querying for an remote control event.
[ 1646.127447] dvb-usb: error -71 while querying for an remote control event.
[ 1646.249115] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully deinitialized and disconnected.
[ 1649.568917] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in cold state, will try to load a firmware
[ 1649.568953] usb 2-1.8: firmware: direct-loading firmware dvb-usb-SkyStar_USB_HD_FW_v17_63.HEX.fw
[ 1649.797884] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
[ 1651.485413] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state.
[ 1651.485684] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 1651.487530] dvb-usb: MAC address: 00:08:c9:f0:34:c0
[ 1651.673470] dvb-usb: schedule remote query interval to 100 msecs.
[ 1651.673773] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.
[ 2694.996882] usbcore: deregistering interface driver dvb_usb_technisat_usb2
[ 2695.139218] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully deinitialized and disconnected.
[ 2705.946844] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state.
[ 2705.947130] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 2706.945884] dvb-usb: MAC address reading failed.
[ 2707.947181] dvb-usb: no frontend was attached by 'Technisat SkyStar USB HD (DVB-S/S2)'
[ 2707.947677] dvb-usb: schedule remote query interval to 100 msecs.
[ 2707.947895] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.
[ 2707.947920] usbcore: registered new interface driver dvb_usb_technisat_usb2
[ 9397.049905] usbcore: deregistering interface driver dvb_usb_technisat_usb2
[ 9397.162307] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully deinitialized and disconnected.
[ 9408.119033] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state.
[ 9408.119300] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 9408.120912] dvb-usb: MAC address: 00:08:c9:f0:34:c0
[ 9408.305062] dvb-usb: schedule remote query interval to 100 msecs.
[ 9408.305307] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.
[ 9408.305336] usbcore: registered new interface driver dvb_usb_technisat_usb2
[10450.082005] usbcore: deregistering interface driver dvb_usb_technisat_usb2
[10450.160919] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully deinitialized and disconnected.
[10484.893915] dvb-usb: found a 'Technisat SkyStar USB HD (DVB-S/S2)' in warm state.
[10484.894200] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[10485.893479] dvb-usb: MAC address reading failed.
[10486.894734] dvb-usb: no frontend was attached by 'Technisat SkyStar USB HD (DVB-S/S2)'
[10486.895440] dvb-usb: schedule remote query interval to 100 msecs.
[10486.895716] dvb-usb: Technisat SkyStar USB HD (DVB-S/S2) successfully initialized and connected.
[10486.895766] usbcore: registered new interface driver dvb_usb_technisat_usb2
root@NAS:/etc/pm/sleep.d#

Alles anzeigen

Womöglich muss ich die FW des Gerätes auch neu laden ?

jigg3 · 25. April 2015

Hi, das Problem mit dem Aufwachen hab ich auch. Wäre toll, wenn du das Skript bereitstellen könntest.

jigg3 · 25. April 2015

Hi zusammen,

ich habe ein Problem mit TV Headend und zwar wird mein NAS alle 20 Minuten geweckt, wenn der TV Headend Prozess aktiv ist. Ich nehme an, dass es am EPG liegt ?!

Ich habe jedes Mal, beim Einsatz von Tv Headend den Prozess gestartet und anders herum ebenfalls wieder entsprechend beendet.

Nun meine Frage, gibt es eine Möglichkeit mein Problem zu automatisieren?

Beim Aufwachen soll Tv Headend laufen und vor dem Schlafen gehen soll es wieder beendet werden.

Gruß

jigg3 · 8. Januar 2015

ok, will try that - thank you! Will I be able to wake up my nas later on ?

jigg3 · 8. Januar 2015

Hi,

it's a Realtek® 8111F, 1 x Gigabit LAN Controller(s)
driver: r8169
version: 2.3LK-NAPI
firmware-version: rtl8168f-1_0.0.4 03/27/12

I'm quite not sure, maybe it's tvheadend whichs is causing the issue.

Don't know, how to go ahead about finding the issue.

jigg3 · 8. Januar 2015

Hi Guys,

I was able to configure the autoshutdown plugin for bringing my nas to sleep / hibernate.
Due to my disk is getting full I'm receving mails from monit about disk usage.

And exactly these mails, I'm receving round about each 13 minutes. As soon as I received such mail, I'd login into my omv. The uptime shows , my NAS is running since 2 to 3 minutes.

How to find the source, which is responsible, why my nas will be turned on ?

thanks

jigg3 · 23. Oktober 2014

Nearly same issue here.

I'm able to press on delete but nothing happens.

drives has not been shared. I was wondering, cause I connected a ntfs drive and was able to mount it. After round about 5 minutes, the drive got disconnected by the system and now I'm having such entry:

additionally I'm receiving mails with following content

Does not exist Service fs_media_98B83289B83265C2

Date: Thu, 23 Oct 2014 22:31:47
Action: restart
Host: NAS.local
Description: filesystem doesn't exist

jigg3 · 23. Oktober 2014

hi guys,

after every reboot of my server, I have to start plex mediaserver manually each time.

any ideas? my nas is currently running on 1.0.29

Beiträge von jigg3

PM-Suspend fails - Hibernation image not present or could not be loaded

Each 2nd boot resync

Each 2nd boot resync

Each 2nd boot resync

Each 2nd boot resync

Prevent .Apple*-Folder from creation/appearing on linked smb-share on windows

Each 2nd boot resync

pm-suspend and wake up fails - system reboots

pm-suspend and wake up fails - system reboots

pm-suspend and wake up fails - system reboots

pm-suspend and wake up fails - system reboots

autoshutdown und tvheadend

autoshutdown und tvheadend

autoshutdown und tvheadend

tvheadend weckt mein nas immer wieder

pm-suspend and wake up fails - system reboots

pm-suspend and wake up fails - system reboots

pm-suspend and wake up fails - system reboots

How to delete old filesystems from OMV-Configuration

plex autostart fails after reboot