You are not logged in.
I apologize in advance, because I'm not getting an error, and I don't really know what information I can share here that will help the problem. I've been using arch over a year and have always been able to solve all my own problems, but I just don't have any idea where to even begin with this issue.
Sometimes, when I start my laptop, it just runs at around 1/4 of it's normal speed. When this happens, I just shut it down, and turn it back on again, and the laptop works normally. I don't understand why this is happening, I do not get errors, and nothing seems out of place, it's just everything runs slow until I reboot.
Thank you in advance for any help you are able to provide.
Offline
Do you have Windows as second OS installed? What is your hard disk drive(s)? Can you provide logs from your last boot or list of failed systemd services?
Offline
No windows, it's just arch. When i enter systemctl list-units --state=failed i get 0 loaded units listed.
here are my drives
Disk model: WDC WD10SPZX-24Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: DFFC4C0F-7D1D-4F14-B10E-9A1BCC8974B9
Device Start End Sectors Size Type
/dev/sda1 2048 2099199 2097152 1G EFI System
/dev/sda2 2099200 1953525134 1951425935 930.5G Linux filesystem
Offline
Please provide output of smartctl -x /dev/sda
Offline
=== START OF INFORMATION SECTION ===
Device Model: WDC WD10SPZX-24Z10
Serial Number: WD-WXS1A686A6RU
LU WWN Device Id: 5 0014ee 608d311fb
Firmware Version: 04.01A04
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Nov 4 17:50:18 2019 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 96 (intermediate level with standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: ENABLED, PW level HIGH, not locked, frozen [SEC6]
Wt Cache Reorder: 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: ( 1140) seconds.
Offline data collection
capabilities: (0x71) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No 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: ( 24) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x303d) 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 194 193 021 - 1266
4 Start_Stop_Count -O--CK 098 098 000 - 2443
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 100 100 000 - 436
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 - 230
187 Reported_Uncorrect -O--CK 100 100 000 - 0
192 Power-Off_Retract_Count -O--CK 200 200 000 - 8
193 Load_Cycle_Count -O--CK 192 192 000 - 24992
194 Temperature_Celsius -O---K 113 093 000 - 30 (Min/Max 12/50)
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 0
198 Offline_Uncorrectable ----CK 100 253 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0
206 Flying_Height -O---K 100 000 000 - 36
240 Head_Flying_Hours -O--CK 100 100 000 - 373
||||||_ 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]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 6 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x24 GPL R/O 288 Current Device Internal Status Data log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
0xa8-0xb6 GPL,SL VS 1 Device vendor specific log
0xb7 GPL,SL VS 74 Device vendor specific log
0xb9 GPL,SL VS 4 Device vendor specific log
0xbd GPL,SL VS 1 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL VS 93 Device vendor specific log
0xdf GPL,SL VS 1 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (1 sectors)
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.
SCT Status Version: 3
SCT Version (vendor specific): 258 (0x0102)
Device State: Active (0)
Current Temperature: 30 Celsius
Power Cycle Min/Max Temperature: 23/31 Celsius
Lifetime Min/Max Temperature: 12/50 Celsius
Specified Max Operating Temperature: 25 Celsius
Under/Over Temperature Limit Count: 0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
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): 128 (10)
Index Estimated Time Temperature Celsius
11 2019-11-04 15:43 33 **************
... ..( 7 skipped). .. **************
19 2019-11-04 15:51 33 **************
20 2019-11-04 15:52 32 *************
21 2019-11-04 15:53 32 *************
22 2019-11-04 15:54 32 *************
23 2019-11-04 15:55 34 ***************
24 2019-11-04 15:56 33 **************
25 2019-11-04 15:57 33 **************
26 2019-11-04 15:58 34 ***************
... ..( 2 skipped). .. ***************
29 2019-11-04 16:01 34 ***************
30 2019-11-04 16:02 33 **************
... ..( 3 skipped). .. **************
34 2019-11-04 16:06 33 **************
35 2019-11-04 16:07 32 *************
... ..( 5 skipped). .. *************
41 2019-11-04 16:13 32 *************
42 2019-11-04 16:14 31 ************
... ..( 28 skipped). .. ************
71 2019-11-04 16:43 31 ************
72 2019-11-04 16:44 30 ***********
... ..( 13 skipped). .. ***********
86 2019-11-04 16:58 30 ***********
87 2019-11-04 16:59 ? -
88 2019-11-04 17:00 18 -
89 2019-11-04 17:01 18 -
90 2019-11-04 17:02 19 -
91 2019-11-04 17:03 19 -
92 2019-11-04 17:04 ? -
93 2019-11-04 17:05 19 -
94 2019-11-04 17:06 19 -
95 2019-11-04 17:07 20 *
96 2019-11-04 17:08 21 **
97 2019-11-04 17:09 ? -
98 2019-11-04 17:10 23 ****
99 2019-11-04 17:11 23 ****
100 2019-11-04 17:12 24 *****
101 2019-11-04 17:13 25 ******
102 2019-11-04 17:14 26 *******
103 2019-11-04 17:15 26 *******
104 2019-11-04 17:16 27 ********
... ..( 5 skipped). .. ********
110 2019-11-04 17:22 27 ********
111 2019-11-04 17:23 28 *********
... ..( 2 skipped). .. *********
114 2019-11-04 17:26 28 *********
115 2019-11-04 17:27 29 **********
116 2019-11-04 17:28 28 *********
117 2019-11-04 17:29 29 **********
118 2019-11-04 17:30 28 *********
119 2019-11-04 17:31 29 **********
120 2019-11-04 17:32 30 ***********
121 2019-11-04 17:33 31 ************
122 2019-11-04 17:34 31 ************
123 2019-11-04 17:35 30 ***********
124 2019-11-04 17:36 31 ************
125 2019-11-04 17:37 30 ***********
... ..( 12 skipped). .. ***********
10 2019-11-04 17:50 30 ***********
SCT Error Recovery Control:
Read: 150 (15.0 seconds)
Write: 150 (15.0 seconds)
Device Statistics (GP/SMART Log 0x04) not supported
Pending Defects log (GP Log 0x0c) not supported
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 3 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 5 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-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 2482 Vendor specific
Last edited by ErtyJr (2019-11-04 22:59:33)
Offline
HDD SMART info looks good. Could you please show output of systemd-analyze blame ?
Offline
29.663s systemd-journal-flush.service
15.579s NetworkManager-wait-online.service
10.950s lvm2-monitor.service
10.562s dev-sda2.device
4.666s systemd-udevd.service
2.636s NetworkManager.service
2.337s systemd-logind.service
2.119s systemd-fsck@dev-disk-by\x2duuid-B4AB\x2d4239.service
1.868s systemd-tmpfiles-setup.service
1.732s systemd-tmpfiles-clean.service
1.518s systemd-tmpfiles-setup-dev.service
915ms swapfile.swap
824ms user@1000.service
773ms boot.mount
629ms systemd-random-seed.service
478ms systemd-journald.service
466ms systemd-udev-trigger.service
466ms polkit.service
298ms systemd-sysctl.service
216ms systemd-backlight@backlight:amdgpu_bl0.service
207ms sys-kernel-debug.mount
207ms kmod-static-nodes.service
180ms systemd-update-utmp.service
172ms systemd-rfkill.service
152ms wpa_supplicant.service
102ms dev-hugepages.mount
100ms dev-mqueue.mount
47ms systemd-remount-fs.service
44ms sys-kernel-config.mount
Offline
Is this list corresponds to the "slow" bootup? If yes, could you provide the same for "quick" boot? 30 seconds for journal flushing service seems too long...
Offline
it's running normally at the moment, and i just put in the command. Actually I do believe I saw it hang on journal flushing service in the past. Is this something I could fix?
Offline
journalctl --vacuum-time=2d
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@58285850efb1426abcc6a935eeb217c8-0000000000000001-00057d23dc992e51.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/user-1000@f4ba38e1843642fd89075bd08c6a8381-00000000000004d6-00057d23de6e6320.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@000581ce361b6441-da514c5e53abef78.journal~: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/user-1000@e27d47c187f24c579ee5332bf5fa8c09-0000000000016e9a-00057f88a5794b89.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@4df47d1ea58c45a695123afcf1185b44-0000000000000001-000581ce36118895.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/user-1000@e27d47c187f24c579ee5332bf5fa8c09-0000000000021ceb-000581f58e2b31b8.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@4df47d1ea58c45a695123afcf1185b44-0000000000021cec-000581f58e3f180d.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@4df47d1ea58c45a695123afcf1185b44-0000000000023765-000588b4ed7eb28e.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/user-1000@346ef7764b89493b83f963726085d96a-0000000000023964-000588b4f10a8f9b.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@4df47d1ea58c45a695123afcf1185b44-0000000000023d71-00058e4befaeb825.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/user-1000@28a4672e91854ceb93ba793602ebaa2d-0000000000023f6f-00058e4bf3a2da68.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@000592601922c61d-534edee9fce3974f.journal~: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/user-1000@e9a2826fc3de42e08a240ce70139008b-000000000002b97d-000592384f69787a.journal: Permission denied
Failed to delete archived journal /var/log/journal/87054fed928a488fb02984fdf0ff436b/system@1be0c743e4044049ba8c504dd7dbf4c8-0000000000000001-00059260191691c1.journal: Permission denied
Offline
Delete journals by root/sudo. You can even try to specify vacuum size of 0 bytes.
Offline
Did you run that journalctl vacuum as root, or as your regular user?
(edit) too slow
Offline
yea I realized that after I posted it lol. I'm going to try rebooting and see how my blame looks
Offline
This is after my 2d vacuum. It's still very slow, I will also try 0 bytes but it seems like there is some problem with it
systemd-analyze blame
18.757s systemd-journal-flush.service
14.309s NetworkManager-wait-online.service
8.611s lvm2-monitor.service
7.587s dev-sda2.device
3.719s ldconfig.service
2.927s NetworkManager.service
2.634s systemd-logind.service
2.343s systemd-udevd.service
1.908s systemd-sysusers.service
1.322s systemd-fsck@dev-disk-by\x2duuid-B4AB\x2d4239.service
1.214s systemd-rfkill.service
1.125s systemd-random-seed.service
1.063s user@1000.service
946ms systemd-tmpfiles-setup.service
805ms systemd-tmpfiles-setup-dev.service
726ms swapfile.swap
583ms systemd-journald.service
525ms boot.mount
515ms systemd-journal-catalog-update.service
491ms systemd-sysctl.service
339ms systemd-udev-trigger.service
261ms systemd-backlight@backlight:amdgpu_bl0.service
137ms dev-hugepages.mount
136ms dev-mqueue.mount
129ms systemd-remount-fs.service
122ms kmod-static-nodes.service
113ms systemd-update-done.service
113ms systemd-update-utmp.service
103ms systemd-user-sessions.service
Offline
What file system do you use?
Offline
ext4
Offline
You could try to use e2defrag tool to check fragmentation of your hard drive and defragment it if necessary
Offline
after running
journalctl --rotate
journalctl --vacuum-time=1s
It is now starting up significantly faster. I am still unsure if the initial problem I had of the computer sometimes just running at 1/4 speed is solved, but at least now I know a few things to look at the next time it is running slowly. Thank you for all the help, will update if it runs slow again in the future.
will also look into defragging
13.035s NetworkManager-wait-online.service
6.278s lvm2-monitor.service
5.989s dev-sda2.device
3.042s systemd-journal-flush.service
2.272s NetworkManager.service
2.213s systemd-logind.service
1.832s systemd-tmpfiles-setup-dev.service
1.686s systemd-udevd.service
863ms swapfile.swap
829ms systemd-fsck@dev-disk-by\x2duuid-B4AB\x2d4239.service
541ms systemd-random-seed.service
492ms systemd-tmpfiles-setup.service
474ms user@1000.service
472ms systemd-rfkill.service
363ms systemd-journald.service
349ms systemd-udev-trigger.service
331ms systemd-sysctl.service
296ms systemd-hostnamed.service
159ms systemd-backlight@backlight:amdgpu_bl0.service
129ms boot.mount
114ms dev-hugepages.mount
114ms systemd-remount-fs.service
114ms dev-mqueue.mount
99ms kmod-static-nodes.service
97ms wpa_supplicant.service
84ms systemd-update-utmp.service
76ms sys-kernel-debug.mount
30ms systemd-user-sessions.service
26ms user-runtime-dir@1000.service
Last edited by ErtyJr (2019-11-04 23:54:34)
Offline
What exactly does "runs at around 1/4 of it's normal speed" mean? Did it only relate to the boot process or your desktop session?
In case of the latter, does it mean your GUI behaves like a diashow or would eg.
time echo "scale=5000; a(1)*4" | bc -l
take 4 times as long? (nb. that depending on your CPU this command can take 30 seconds to finish anyway)?
Offline
Also I've noticed that you use NetworkManager-wait-online. Are there any reasons to use this service? You could try to disable it and stay with simple NetworkManager.service unit. Perhaps waiting for ready-for-online state may cause such long bootups
Offline
If everything runs at a quarter of the normal speed, that should mean the CPU is clocked slower than normal.
As a first step in troubleshooting, if your system happens to start running at a lower speed again post the output of
dmesg -x
and read the files in /sys/devices/system/cpu/cpu0/cpufreq (this should be data for the first CPU core).
Other than that you could try cleaning the insides of your laptop from dust that possibly acts as a thermal/airflow insulator.
Last edited by Neven (2019-11-10 00:09:28)
Offline
Hello again all. I have not been checking the forums since the computer seemed to be working fine for the time being. However, I just booted up extremly slow again. In the past I have always immediately rebooted the laptop because I3 takes forever to start up and then I can't do any thing at all for quite a while. Well this time I waited it out and I ran
systemd-analyze blame
The results surprised me. my computer had already been running for some time, and the firs time I entered the command I got an error
systemd-analyze blame
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
I waited around for a while, and then I tried again and here are the results. after running the results, my computer seems to now be running at a normal speed, so it appears the problem is only in boot up.
systemd-analyze blame
4min 3.590s fstrim.service
1min 9.596s man-db.service
19.707s NetworkManager-wait-online.service
6.359s lvm2-monitor.service
5.905s NetworkManager.service
5.631s dev-sda2.device
5.531s systemd-logind.service
4.245s logrotate.service
3.822s user@1000.service
3.380s systemd-journal-flush.service
2.291s systemd-sysusers.service
1.716s ldconfig.service
1.502s systemd-udevd.service
1.273s systemd-random-seed.service
1.087s swapfile.swap
991ms wpa_supplicant.service
684ms systemd-fsck@dev-disk-by\x2duuid-B4AB\x2d4239.service
482ms systemd-tmpfiles-setup.service
385ms systemd-tmpfiles-setup-dev.service
374ms systemd-journald.service
311ms systemd-journal-catalog-update.service
311ms systemd-rfkill.service
309ms user-runtime-dir@1000.service
220ms boot.mount
208ms systemd-udev-trigger.service
170ms sys-kernel-debug.mount
164ms systemd-user-sessions.service
157ms dev-hugepages.mount
154ms dev-mqueue.mount
So it appears that fstrim and man-db are the culprits.
Also I've noticed that you use NetworkManager-wait-online. Are there any reasons to use this service? You could try to disable it and stay with simple NetworkManager.service unit. Perhaps waiting for ready-for-online state may cause such long bootups
thanks, I have taken your advice and disabled it, which should help.
Last edited by ErtyJr (2019-11-12 00:36:05)
Offline
trying to delete this repost
Last edited by ErtyJr (2019-11-12 00:38:34)
Offline
Do you have any SSDs installed? fstrim is necessary only for doing TRIM once a week for compatible devices so if you have none you could disable it too
Offline
Do you have any SSDs installed? fstrim is necessary only for doing TRIM once a week for compatible devices so if you have none you could disable it too
I do not have an ssd on this particular device. I will disable it as well, thanks.
You have been a huge help dviktor, Just want to say I appreciate your time.
Last edited by ErtyJr (2019-11-12 22:14:57)
Offline