APM musst du nicht deaktivieren. Das ALPM macht ggf die Probleme.
Mhh anderer kernel? Debian upgrade, BIOS?
der gleiche Kernel seit Monaten, selbes BIOS, Debian updates, kein upGRADE.
aber bis jetzt sind keine Fehler aufgetaucht. Vielleicht liegt es wirklich an ALPM
So ich habe jetzt...
- alle Sata Kabel ausgetauscht
- alle powertop tuning optionen deaktiviert
- die APM einstellung aller Festplatten Deaktiviert
Mal sehen ob jetzt noch was kommt. Wenn ja werde ich mal anstatt die onboard Sata ports eine Sata Karte benutzen um zu sehen ob das Problem immer noch auftaucht.
Mir ist gerade eingefallen das ich diese Error Mails erst seit ca einer Woche bekomme...Ich weiss nicht was sich seit dem verändert hat.
Jetzt gerade habe ich wieder eine Mail bekommen:
Jan 28 19:37:35 server postfix/smtp[16675]: 7ED743000AE4: replace: header Subject: SMART error (ErrorCount) detected on host: server: Subject: SMART error (ErrorCount) detected on host: server [server.WORKGROUP]
Jan 28 19:37:35 server postfix/smtp[16678]: 8F44930004BF: replace: header Subject: SMART error (ErrorCount) detected on host: server: Subject: SMART error (ErrorCount) detected on host: server [server.WORKGROUP]
Jan 28 19:37:36 server postfix/smtp[16702]: 7F8083000B4A: replace: header Subject: SMART error (ErrorCount) detected on host: server: Subject: SMART error (ErrorCount) detected on host: server [server.WORKGROUP]
Jan 28 19:37:36 server postfix/smtp[16699]: 752153000B4F: replace: header Subject: SMART error (ErrorCount) detected on host: server: Subject: SMART error (ErrorCount) detected on host: server [server.WORKGROUP]Ich werde gleich ein paar Sachen überprüfen und berichten
Soooo....
1. Im Syslog finde ich keinen Eintrag, gibt es ein Syslog archiv?
2. Ja
3. Enable SATA link power management for wird per powertop auf "good" gestellt. Keine Anpassungen in rc.local.
Wenn es das Sata Kabel sein sollte, dann müssten es ja alle 3 Kabel sein O_o.
Diese Fehler treten ja bei allen 3 Festplatten auf, alle 3 Platten defekt???
Ich finde es nur komisch das diese Fehlermeldungen keinerlei auswirkung auf das System haben, alles läuft wie geschmiert.
Heute stand im SMART log das hier:
Jan 28 16:07:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee25fd40306 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 130 to 123
Jan 28 16:07:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee25fd40306 [SAT], ATA error count increased from 28 to 29
Jan 28 16:07:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 129 to 123
Jan 28 16:07:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], ATA error count increased from 24 to 25
Jan 28 16:07:34 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4EN39HYFH [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 130 to 123
Jan 28 16:07:34 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4EN39HYFH [SAT], ATA error count increased from 28 to 29
Jan 28 16:07:34 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 129 to 123
Jan 28 16:07:34 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], ATA error count increased from 24 to 25
Jan 28 16:37:32 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee25fd40306 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 123 to 122
Jan 28 16:37:32 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 123 to 122
Jan 28 16:37:33 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4EN39HYFH [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 123 to 122
Jan 28 16:37:33 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 123 to 122
Jan 28 17:37:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee25fd40306 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 122 to 126
Jan 28 17:37:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 122 to 126
Jan 28 17:37:33 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4EN39HYFH [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 122 to 126
Jan 28 17:37:33 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 122 to 126
Jan 28 18:07:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee25fd40306 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 126 to 129
Jan 28 18:07:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 126 to 128
Jan 28 18:07:34 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4EN39HYFH [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 126 to 129
Jan 28 18:07:34 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 126 to 128
Jan 28 18:37:33 server smartd[3254]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 128 to 129
Jan 28 18:37:33 server smartd[3254]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 128 to 129gestern kam das ein paar mal vor:
Jan 26 18:38:41 server smartd[11780]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4EN39HYFH [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 180 to 181
Jan 26 18:38:41 server smartd[11780]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4EN39HYFH [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 115 to 114
Jan 26 18:38:41 server smartd[11780]: Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 179 to 181
Jan 26 19:08:40 server smartd[11780]: Device: /dev/disk/by-id/wwn-0x50014ee25fd40306 [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 181 to 182
Jan 26 19:08:40 server smartd[11780]: Device: /dev/disk/by-id/wwn-0x50014ee25fd40306 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 114 to 116
Jan 26 19:08:40 server smartd[11780]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 181 to 182
Jan 26 19:08:40 server smartd[11780]: Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 115 to 116Ich kann jetzt wirklich nicht sagen wie lange das schon ist, ich habe nie darauf geachtet da mir der S.M.A.R.T. selftest immer ein PASSED gab.
Es ist ein Dell T20 allerdings mit einem E3-1245 V3.
Festplatten sind:
1x Samsung HD103SJ
2x WD40EFRX-68W
Ist jetzt seit ca. 6 Monaten im Betrieb.
Ich habe bis jetzt keinerlei Problem mit Datenverlust gehabt, alles läuft bestens! Aber die Fehlermeldungen verwundern mich etwas...
Ich nutze den 3.16er Backports Kernel.
Hier gibts ein paar infos zu dem Dell: http://www.hardwareluxx.de/com…oweredge-t20-1031138.html
Wie gesagt, G3220 wurde durch einen E3-1245 V3 ersetzt.
Mhh alles abort errors. Unspezifisch.
Erstmal kabel tauschen und abwarten.
Wenn es nochmal auftritt den Eintrag im syslog suchen, mal gucken was Linux Kernel dazu sagt.
Komischerweise habe ich diese ABRT Errors bei allen von meinen 3 Festplatten...
Da habe ich bei mir stehen.
Error 25 [0] occurred at disk power-on lifetime: 4776 hours (199 days + 0 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:04:20.762 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 00:04:20.762 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 00:04:20.761 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 00:04:20.760 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 00:04:20.760 SMART READ LOG
Error 24 [23] occurred at disk power-on lifetime: 4776 hours (199 days + 0 hours)
When the command that caused the error occurred, the device was in standby mode.
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 01:16:47.404 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 01:16:47.404 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 01:16:47.403 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 01:16:47.403 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 01:16:47.402 SMART READ LOG
Error 23 [22] occurred at disk power-on lifetime: 4776 hours (199 days + 0 hours)
When the command that caused the error occurred, the device was in standby mode.
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 01:16:47.344 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 01:16:47.344 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 01:16:47.344 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 01:16:47.344 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 01:16:47.344 SMART READ LOG
Error 22 [21] occurred at disk power-on lifetime: 4775 hours (198 days + 23 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:05:17.394 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 00:05:17.394 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 00:05:17.392 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 00:05:17.391 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 00:05:17.391 SMART READ LOG
Error 21 [20] occurred at disk power-on lifetime: 4775 hours (198 days + 23 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
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 4d+08:59:52.769 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 4d+08:59:52.769 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+08:59:52.768 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+08:59:52.767 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 4d+08:59:52.767 SMART READ LOG
Error 20 [19] occurred at disk power-on lifetime: 4773 hours (198 days + 21 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
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 4d+07:44:28.944 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 4d+07:44:28.944 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+07:44:28.943 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+07:44:28.942 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 4d+07:44:28.942 SMART READ LOG
Error 19 [18] occurred at disk power-on lifetime: 4773 hours (198 days + 21 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
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 4d+07:42:05.934 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 4d+07:42:05.934 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+07:42:05.933 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+07:42:05.932 SMART WRITE LOG
2f 00 00 00 01 00 00 00 00 00 11 40 08 4d+07:42:05.931 READ LOG EXT
Error 18 [17] occurred at disk power-on lifetime: 4773 hours (198 days + 21 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
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 4d+07:41:44.799 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 4d+07:41:44.799 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+07:41:44.798 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 4d+07:41:44.797 SMART WRITE LOG
2f 00 00 00 01 00 00 00 00 00 11 40 08 4d+07:41:44.797 READ LOG EXTAlso ganz unten im SMART Bericht der entsprechenden HDD sollten ein paar details zu dem Error stehen (da werden immer die letzten 5 gespeichert).
Des Weiteren kannst Du im Syslog mal suchen. Das kann ein CRC, UNC .. usw Error sein.
Gruß
Sagt euch das was?
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 278 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 3 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 4607 Vendor specificHallo,
Ich bekomme seit 2 Tagen diesen SmartD error bei 2 von meinen Festplatten:
The following warning/error was logged by the smartd daemon:
Device: /dev/disk/by-id/wwn-0x50014ee2091f2d63 [SAT], ATA error count increased from 10 to 12
Device: /dev/disk/by-id/scsi-SATA_WDC_WD40EFRX-68_WD-WCC4E0291590 [SAT], ATA error count increased from 10 to 12wwn-0x50014ee2091f2d63
Finde ich aber nirgends bei meinen Festplatten.
Und auch ein Smart Selftest bei der Platte mit der Seriennummer WCC4E0291590 ergibt keine Fehler...
Weiß jemand was hier vor sich geht?
Danke!
Scared of downloading from One Click Hosters?
Greetings
David
Well...I don't know. Safer than not using anything at all?
I have a feature request but I don't know if this is possible...
Could someone add an option that JDownloader is bound to a specific network adapter? For example tun0. So when tun0 goes down, JDownloader will not be able to download anything?
Maybe this could get added to OMV in general for all processes?
Or are there any work arounds to get this working right now?
I just followed these steps and it is also working fine for me!
One question though. I want to tunnel JDownloader through the VPN adapter. Is it possible that the user jdownloader can only use tun0? And if tun0 doesn't exist, it just shouldn't connect at all.
Thanks!
Hello everyone!
I have a question regarding CIFS shares.
As of now I have 2x 3TB Red drives. On each drive I have a single Folder for example: Storage_New.
This Folder contains other folders such as: Downloads, Pictures, Music, etc....
I now created one CIFS share for each drive which shares that one main Folder.
So in this case I have two CIFS shares: Storage_New, Storage_Old.
These two shares shares the entire contents of my two drives. Is this a bad thing? Is there a recommended way?
Thanks!
Is anyone working on a VPN Client yet? I would really love something like this for the GUI. One that supports multiple protocols. PPTP, OpenVPN, etc...
Thanks!
Do me the favor and check the load on a live system with data disks detached just to be sure that it is infact the CPU which doesn't cut power down properly.
Greetings
David
Will do this shortly.
EDIT: The CPU Driver intel_pstate is the cause of this! I disabled it and used acpi-cpufreq and toggled all tuneables under Powertop to good. The package fell right into C7 state and the Power consumption dropped immediatley.
This is with the conservative govenor, trying powersave now!
EDIT EDIT: With the Data Drives spun down, CPU Driver set to acpi-cpufreq and governor set to powersave. The System now IDLEs at 25 Watt!
It isn't. It will never spindown...
Greetings
David
Right...so something else is keeping the system from going into IDLE. I find it just weird that others are getting much better results with the same setup...
My data HDDs are spinning down correctly, I'm not sure about the system drive. I will check this in a moment.
Ok the System drive does not spindown...Is it even supposed to?
Hello Guys,
For some time now it seemed that my server has been using too much power...
Here is my setup:
Dell Poweredge T20
8GB Ram
Xeon 1245v3
1x 1TB HDD
2x 4TB HDD
I am getting around 42 Watt in IDLE State.
Others who have the exact same setup are reporting 15 - 20 Watt in IDLE.
I have noticed that in Powertop, the Package doesn't go into C6 state... Could this be the cause?
Cool, Updating works!
The Web GUI now told me that there is an update available. Should I press the update button in the GUI?
