Werte (von TOP) sehen gut aus.
Was machst du, wenn dein PC einfriert?
Kalt ausschalten oder ist er nach einer bestimmten Zeit wieder nutzbar?
Wenn er nach einer bestimmten Zeit wieder nutzbar ist - wie lange war er ca. eingefroren?
Und wie oft passiert dieses - ungefähr?
Opensuse 15 friert ein
- 18301
- Geschlossen
- Erledigt
Hinweis: In dem Thema Opensuse 15 friert ein gibt es 27 Antworten auf 3 Seiten. Der letzte Beitrag () befindet sich auf der letzten Seite.
-
-
Es kann sein, dass geplante Timer dein System zu sehr beanspruchen.
Evtl. sind genau dies die Zeitpunkte, an denen dein Rechner unter Last stand / steht.
Dieses kannst du einfach mit diesem Konsolenbefehl testen:Hier siehst du, welche Timer Units wann erledigt wurden bzw. noch starten.
Wenn der Rechner wirklich komplett einfriert, kannst du deine HDD / SSD auch mal testen (Konsole öffnen als root mit su):
sda ist bei mir die erste Platte - kann bei dir auch sdb - sdc usw. sein (aber wahrscheinlich auch sda).
Das kannst du kontrollieren mit (Konsole öffnen als root mit su): -
Code
Alles anzeigensmartctl -a /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.16-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 2.5" HDD MQ01ABD... Device Model: TOSHIBA MQ01ABD100 Serial Number: 54BDP2HRT LU WWN Device Id: 5 000039 582783f79 Firmware Version: AX0A4M User Capacity: 1.000.204.886.016 bytes [1,00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5400 rpm Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Sep 3 18:07:40 2018 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 120) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 253) minutes. SCT capabilities: (0x003d) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1194 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1600 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 8487 10 Spin_Retry_Count 0x0033 131 100 030 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1246 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 217 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 111 193 Load_Cycle_Count 0x0032 086 086 000 Old_age Always - 142591 194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 36 (Min/Max 8/57) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1 220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0 222 Loaded_Hours 0x0032 082 082 000 Old_age Always - 7578 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0 224 Load_Friction 0x0022 100 100 000 Old_age Always - 0 226 Load-in_Time 0x0026 100 100 000 Old_age Always - 177 240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0 SMART Error Log Version: 1 ATA Error Count: 1 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 1 occurred at disk power-on lifetime: 802 hours (33 days + 10 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 -- -- -- -- -- -- -- 84 50 30 40 b0 01 e0 48 sectors at LBA = 0x0001b040 = 110656 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 70 ad 01 e0 00 00:01:54.003 READ DMA EXT 25 00 00 70 a5 01 e0 00 00:01:53.993 READ DMA EXT 25 00 00 70 9d 01 e0 00 00:01:53.983 READ DMA EXT 25 00 00 70 95 01 e0 00 00:01:53.973 READ DMA EXT 25 00 00 70 8d 01 e0 00 00:01:53.965 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 8473 - # 2 Short offline Completed without error 00% 8456 - # 3 Short offline Completed without error 00% 8440 - # 4 Short offline Completed without error 00% 8417 - # 5 Short offline Completed without error 00% 8410 - # 6 Short offline Completed without error 00% 8391 - # 7 Short offline Completed without error 00% 8366 - # 8 Short offline Completed without error 00% 8360 - # 9 Short offline Completed without error 00% 8343 - #10 Short offline Completed without error 00% 8326 - #11 Extended offline Aborted by host 90% 8188 - #12 Extended offline Completed without error 00% 7654 - #13 Extended offline Completed without error 00% 7565 - #14 Extended offline Completed without error 00% 7235 - #15 Extended offline Completed without error 00% 6751 - #16 Extended offline Completed without error 00% 6523 - #17 Extended offline Completed without error 00% 6192 - #18 Extended offline Completed without error 00% 5680 - #19 Extended offline Completed without error 00% 5106 - #20 Extended offline Completed without error 00% 4535 - #21 Extended offline Completed: electrical failure 90% 3769 0 1 of 1 failed self-tests are outdated by newer successful extended offline self-test #12 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.
-
-
Code
dmesg | grep -E -i "error|fail|crit" [ 0.296166] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [ 0.392020] pci 0000:00:1c.1: BAR 14: failed to assign [mem size 0x00100000] [ 2470.983193] sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ 2995.306874] Buffer I/O error on dev sdb1, logical block 60850176, lost sync page write [ 2995.306879] JBD2: Error -5 detected when updating journal superblock for sdb1-8. [ 2995.306882] Buffer I/O error on dev sdb1, logical block 60850176, lost sync page write [ 2995.306884] JBD2: Error -5 detected when updating journal superblock for sdb1-8. [ 2995.307963] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
-
Code
Alles anzeigensystemctl list-timers --all NEXT LEFT LAST PASSED UNIT AC> Mon 2018-09-03 21:00:00 CEST 59min left Mon 2018-09-03 20:00:17 CEST 17s ago snapper-timeline.timer sn> Tue 2018-09-04 00:00:00 CEST 3h 59min left Mon 2018-09-03 00:00:22 CEST 20h ago logrotate.timer lo> Tue 2018-09-04 00:57:43 CEST 4h 57min left Mon 2018-09-03 00:48:22 CEST 19h ago backup-rpmdb.timer ba> Tue 2018-09-04 01:33:31 CEST 5h 32min left Mon 2018-09-03 00:17:18 CEST 19h ago backup-sysconfig.timer ba> Tue 2018-09-04 01:40:23 CEST 5h 39min left Mon 2018-09-03 01:34:14 CEST 18h ago check-battery.timer ch> Tue 2018-09-04 18:26:38 CEST 22h left Mon 2018-09-03 18:26:38 CEST 1h 33min ago snapper-cleanup.timer sn> Tue 2018-09-04 18:31:14 CEST 22h left Mon 2018-09-03 18:31:14 CEST 1h 29min ago systemd-tmpfiles-clean.timer sy> Mon 2018-09-10 00:00:00 CEST 6 days left Mon 2018-09-03 00:00:22 CEST 20h ago btrfs-balance.timer bt> Mon 2018-09-10 00:00:00 CEST 6 days left Mon 2018-09-03 00:00:22 CEST 20h ago fstrim.timer fs> Mon 2018-10-01 00:00:00 CEST 3 weeks 6 days left Sat 2018-09-01 07:20:44 CEST 2 days ago btrfs-scrub.timer bt> 10 timers listed. lines 1-13/13 (END)
-
Mon 2018-09-10 00:00:00 CEST 6 days left Mon 2018-09-03 00:00:22 CEST 20h ago btrfs-balance.timer bt>
Mon 2018-09-10 00:00:00 CEST 6 days left Mon 2018-09-03 00:00:22 CEST 20h ago fstrim.timer fs>
Mon 2018-10-01 00:00:00 CEST 3 weeks 6 days left Sat 2018-09-01 07:20:44 CEST 2 days ago btrfs-scrub.timer bt>Diese drei Timer belasten schon für einige Minuten dein System.
Du siehst, wann diese liefen und wann sie wieder laufen werden.
Das kann schon einer der Zeitpunkte sein, an welchen dein System kaum / bzw. schlechter nutzbar war.
Dieses würde aber niemals zu einem Freeze (einfrieren) führen.Aufgefallen sind mir jedoch die Fehler bzgl. sdb1.
Ich würde diese HDD auch mal checken - nicht dass diese einen Defekt hat.Wieder als root (-:
-
Ich habe btrfs-balance gelöscht und seit dem ist ruhe.
Vielen dank an alle!