LINUX.ORG.RU

Что-то арчик долго грузится

 ,


0

1
[int13h@homepc ~]$ systemd-analyze
Startup finished in 3.637s (kernel) + 1min 34.249s (userspace) = 1min 37.887s
[int13h@homepc ~]$ systemd-analyze blame
          5.152s dev-sda2.device
          4.523s man-db.service
          1.835s libvirtd.service
          1.657s lm_sensors.service
          1.514s systemd-logind.service
          1.334s systemd-journal-flush.service
          1.281s systemd-udevd.service
          1.205s systemd-journald.service
          1.123s systemd-tmpfiles-setup-dev.service
           969ms upower.service
           860ms systemd-modules-load.service
           724ms udisks2.service
           576ms systemd-udev-trigger.service
           533ms systemd-backlight@backlight:acpi_video0.service
           485ms polkit.service
           475ms sys-kernel-debug.mount
           474ms dev-mqueue.mount
           470ms dev-hugepages.mount
           437ms transmission.service
           417ms systemd-remount-fs.service
           393ms user@1000.service
           390ms systemd-vconsole-setup.service
           280ms ntpd.service
           277ms mnt-DATA1.mount
           268ms tmp.mount
           243ms systemd-random-seed.service
           230ms mnt-DATA2.mount
           226ms updatedb.service
           219ms dhcpcd.service
           206ms systemd-tmpfiles-setup.service
           178ms systemd-update-utmp.service
           167ms systemd-tmpfiles-clean.service
           130ms systemd-sysctl.service
           109ms kmod-static-nodes.service
            62ms logrotate.service
            53ms systemd-user-sessions.service
            32ms home-int13h-.cache-chromium.mount
            20ms sys-kernel-config.mount
            17ms rtkit-daemon.service
             3ms shadow.service
             2ms alsa-restore.service
             1ms sys-fs-fuse-connections.mount
           942us home-int13h-.cache-google\x2dchrome.mount
[int13h@homepc ~]$ 

Или дело в старом убиттом ноутбучном винчестере?

★★★★★

Ответ на: комментарий от CHIPOK
[int13h@homepc ~]$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 34.236s
└─multi-user.target @1min 34.236s
  └─libvirtd.service @1min 32.380s +1.855s
    └─network.target @1min 32.324s
      └─dhcpcd.service @9.919s +1.915s
        └─basic.target @9.864s
          └─sockets.target @9.864s
            └─dbus.socket @9.864s
              └─sysinit.target @9.863s
                └─sys-fs-fuse-connections.mount @24.317s +2ms
                  └─systemd-modules-load.service @2.317s +438ms
                    └─system.slice @2.280s
                      └─-.slice @1.749s

int13h ★★★★★ ()
Ответ на: комментарий от CHIPOK

Ппц как медленно грузится, у меня на wd green за 10-20c c автостартом.

anonymous ()
Ответ на: комментарий от CHIPOK

Ну, визуально, медленно. Да и по цифрам.

Больше грешу на свой дохлый винт. Все никак времени нет заменить в десктопе =)

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio Blue Serial ATA
Device Model:     WDC WD2500BEVT-22ZCT0
Serial Number:    WD-WXH409969432
LU WWN Device Id: 5 0014ee 2580f4220
Firmware Version: 11.01A11
User Capacity:    250 059 350 016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.5, 3.0 Gb/s
Local Time is:    Mon Dec  7 12:08:45 2015 MSK
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

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: 		( 7200) 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: 	 (  86) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x303f)	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     0x002f   199   198   051    Pre-fail  Always       -       12962
  3 Spin_Up_Time            0x0027   190   185   021    Pre-fail  Always       -       1491
  4 Start_Stop_Count        0x0032   095   095   000    Old_age   Always       -       5649
  5 Reallocated_Sector_Ct   0x0033   029   029   140    Pre-fail  Always   FAILING_NOW 1365
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   077   077   000    Old_age   Always       -       17122
 10 Spin_Retry_Count        0x0033   100   099   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   096   096   000    Old_age   Always       -       4989
192 Power-Off_Retract_Count 0x0032   199   199   000    Old_age   Always       -       865
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       681347
194 Temperature_Celsius     0x0022   113   094   000    Old_age   Always       -       34
196 Reallocated_Event_Count 0x0032   001   001   000    Old_age   Always       -       249
197 Current_Pending_Sector  0x0032   200   199   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0009   100   253   051    Pre-fail  Offline      -       0

SMART Error Log Version: 1
Warning: ATA error count 9819 inconsistent with error log pointer 1

ATA Error Count: 9819 (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.


int13h ★★★★★ ()
Ответ на: комментарий от int13h
Error 9819 occurred at disk power-on lifetime: 16941 hours (705 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 71 8a 5c 40  Error: UNC at LBA = 0x005c8a71 = 6064753

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 d0 a0 91 7b 17 08      03:52:04.541  READ FPDMA QUEUED
  60 08 58 58 f1 bf 12 08      03:52:04.531  READ FPDMA QUEUED
  60 08 a0 d8 fc 1e 11 08      03:52:04.524  READ FPDMA QUEUED
  60 08 18 a0 4a c5 19 08      03:52:04.517  READ FPDMA QUEUED
  60 08 38 28 1f 21 0d 08      03:52:04.513  READ FPDMA QUEUED

Error 9818 occurred at disk power-on lifetime: 15967 hours (665 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 SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 d9 bb 62 40  Error: UNC at LBA = 0x0062bbd9 = 6470617

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 f0 08 8d f4 06 08      03:13:58.479  READ FPDMA QUEUED
  60 08 e8 90 be 1c 07 08      03:13:58.477  READ FPDMA QUEUED
  60 20 e0 38 3a 4c 07 08      03:13:58.465  READ FPDMA QUEUED
  60 20 d8 d8 bb 62 1c 08      03:13:58.441  READ FPDMA QUEUED
  60 18 d0 c0 bb 62 1c 08      03:13:58.435  READ FPDMA QUEUED

Error 9817 occurred at disk power-on lifetime: 15915 hours (663 days + 3 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 61 02 00 00 00 a0  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 10 02 00 00 00 00 00   1d+09:41:59.630  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 00 00   1d+09:41:59.629  IDENTIFY DEVICE
  ef 03 46 00 00 00 00 00   1d+09:41:59.629  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 00 00   1d+09:41:59.628  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 00 00   1d+09:41:59.627  IDENTIFY DEVICE

Error 9816 occurred at disk power-on lifetime: 15915 hours (663 days + 3 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 61 46 00 00 00 a0  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 00 00   1d+09:41:59.629  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 00 00   1d+09:41:59.628  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 00 00   1d+09:41:59.627  IDENTIFY DEVICE
  c8 00 08 36 6d e8 00 00   1d+09:41:59.618  READ DMA
  ef 10 02 00 00 00 00 00   1d+09:41:59.618  SET FEATURES [Enable SATA feature]

Error 9815 occurred at disk power-on lifetime: 15915 hours (663 days + 3 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 61 02 00 00 00 a0  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 10 02 00 00 00 00 00   1d+09:41:59.628  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 00 00   1d+09:41:59.627  IDENTIFY DEVICE
  c8 00 08 36 6d e8 00 00   1d+09:41:59.618  READ DMA
  ef 10 02 00 00 00 00 00   1d+09:41:59.618  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 00 00   1d+09:41:59.615  IDENTIFY DEVICE

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%      6596         -
# 2  Short offline       Completed without error       00%      4910         -
# 3  Short offline       Completed without error       00%      4669         -
# 4  Short offline       Aborted by host               10%      3214         -
# 5  Short offline       Interrupted (host reset)      90%      1115         -
# 6  Short offline       Interrupted (host reset)      90%       645         -

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.
int13h ★★★★★ ()
Ответ на: комментарий от int13h

Вот думаю когда он быстрее сломается или лень переборю и схожу в магазин =)

int13h ★★★★★ ()
Ответ на: комментарий от int13h

там в основном dhclient относительно долго получает настройки, если сделать статику то будет на порядок быстрее

CHIPOK ★★★ ()

Фигасе, у меня гента без этого поцтерошлака на старом компьютере грузится не больше сорока секунд…

Eddy_Em ☆☆☆☆☆ ()
Ответ на: комментарий от Eddy_Em

ну да, анализатора времени загрузки то нету, вот и не тормозит

irton ★★★★★ ()

Или дело в старом убиттом ноутбучном винчестере?

this

Psych218 ★★★★★ ()

90 секунд — это таймаут запуска юнита. ( Eddy_Em, как всегда, бомбит, ну да и хрен с ним.) Дай либо лог, либо systemd-analyze plot, раз уж с critical-chain ничего не видно.

intelfx ★★★★★ ()
Последнее исправление: intelfx (всего исправлений: 2)

Не спец, но выскажусь(это лор, детка!) - если это загрузка от нажатия кнопки питалова до старта всяких там {NAME}DM, то вполне сносно для старого ж\д. А вот если это до старта консольного входа... То это !ъ.

А так если верить секундомеру, то арч(да и гнета) грузится за 7-10сек(сам не знаю почему такой разброс получается).

exepush ()
Ответ на: комментарий от Jefail

Да я год-два назад про него писал. Еще живой, немного =)

int13h ★★★★★ ()
Ответ на: комментарий от Deleted

Что сократить? Таймаут? Конечно, man TimeoutStart/TimeoutStop/JobTimeout.

intelfx ★★★★★ ()
Ответ на: комментарий от int13h

Мда, опять ничего. Давай лог, что ли. И systemctl list-dependencies default.target до кучи.

intelfx ★★★★★ ()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.