• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Suse 15.4 --> langsamer Start (51.824s userspace!)

thio

Hacker
Hallo,

an meine Laptop (Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz)

Startet Suse 15.4 recht langsam...

Habt Ihr eine Ekrlärung, für das langsame booten:

Code:
@localhost:~> systemd-analyze
Startup finished in 2.938s (firmware) + 10.084s (loader) + 1.640s (kernel) + 5.725s (initrd) + 51.824s (userspace) = 1min 12.213s
graphical.target reached after 51.810s in userspace


Code:
@localhost:~> systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @51.810s
└─display-manager.service @47.979s +3.829s
  └─systemd-user-sessions.service @47.922s +54ms
    └─remote-fs.target @47.916s
      └─iscsi.service @45.668s +2.245s
        └─network-online.target @45.666s
          └─NetworkManager-wait-online.service @37.816s +7.849s
            └─NetworkManager.service @36.340s +1.291s
              └─network-pre.target @36.338s
                └─wpa_supplicant.service @39.765s +391ms
                  └─dbus.service @24.480s
                    └─basic.target @24.438s
                      └─sockets.target @24.438s
                        └─snapd.socket @24.436s +2ms
                          └─sysinit.target @24.335s
                            └─systemd-update-utmp.service @24.272s +61ms
                              └─auditd.service @23.983s +285ms
                                └─systemd-tmpfiles-setup.service @23.577s +403ms
                                  └─local-fs.target @23.511s
                                    └─home.mount @23.010s +499ms
                                      └─systemd-fsck@dev-disk-by\x2duuid-94bec177\x2de92c\x2d4ccb\x2d825b\x2d182e34e74df9.service @22.499s +507ms
                                        └─dev-disk-by\x2duuid-94bec177\x2de92c\x2d4ccb\x2d825b\x2d182e34e74df9.device @584542y 2w 2d 20h 1min 46.129s +25.917s

Code:
@localhost:~> systemd-analyze blame
25.918s dev-disk-by\x2did-scsi\x2dSATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart10.device
25.918s dev-disk-by\x2did-scsi\x2d350000395f5701a72\x2dpart10.device
25.918s dev-disk-by\x2dpartuuid-06b6a037\x2d0e5b\x2d4b1a\x2db4a5\x2d2b8568c1022f.device
25.918s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart10.device
25.918s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart10.device
25.918s dev-disk-by\x2did-scsi\x2d1ATA_TOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart10.device
25.918s dev-sda10.device
25.917s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda10.device
25.917s dev-disk-by\x2did-scsi\x2d0ATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart10.device
25.917s dev-disk-by\x2duuid-94bec177\x2de92c\x2d4ccb\x2d825b\x2d182e34e74df9.device
25.917s dev-disk-by\x2did-wwn\x2d0x50000395f5701a72\x2dpart10.device
25.917s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart10.device
25.308s dev-disk-by\x2did-scsi\x2d0ATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart11.device
25.308s dev-disk-by\x2did-scsi\x2d350000395f5701a72\x2dpart11.device
25.308s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda11.device
25.308s dev-sda11.device
25.308s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart11.device
25.308s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart11.device
25.308s dev-disk-by\x2dpartuuid-4934587a\x2dabbe\x2d4410\x2dbfc2\x2db8faea4223c4.device
25.308s dev-disk-by\x2duuid-58B23AB3B23A958A.device
25.308s dev-disk-by\x2dlabel-RECOVERY.device
25.308s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart11.device
25.308s dev-disk-by\x2did-scsi\x2dSATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart11.device
25.308s dev-disk-by\x2did-scsi\x2d1ATA_TOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart11.device
25.308s dev-disk-by\x2did-wwn\x2d0x50000395f5701a72\x2dpart11.device
25.156s dev-disk-by\x2did-scsi\x2d1ATA_TOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart1.device
25.156s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
25.156s dev-disk-by\x2duuid-E4C64C63C64C37D6.device
25.156s dev-sda1.device
25.155s dev-disk-by\x2dpartuuid-06c72598\x2d7c98\x2d4189\x2d93a9\x2df111eeed6358.device
25.155s dev-disk-by\x2dlabel-WINRE.device
25.155s dev-disk-by\x2did-scsi\x2dSATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart1.device
25.155s dev-disk-by\x2did-scsi\x2d0ATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart1.device
25.155s dev-disk-by\x2did-wwn\x2d0x50000395f5701a72\x2dpart1.device
25.155s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart1.device
25.155s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.device
25.155s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart1.device
25.155s dev-disk-by\x2did-scsi\x2d350000395f5701a72\x2dpart1.device
24.630s dev-disk-by\x2did-scsi\x2d0ATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart3.device
24.630s dev-disk-by\x2did-scsi\x2d350000395f5701a72\x2dpart3.device
24.630s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart3.device
24.630s dev-disk-by\x2did-wwn\x2d0x50000395f5701a72\x2dpart3.device
24.630s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda3.device
24.630s dev-sda3.device
24.630s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart3.device
24.630s dev-disk-by\x2dpartuuid-5cecdbf3\x2d607f\x2d417c\x2db573\x2d010ea2e8cd5a.device
24.630s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
24.630s dev-disk-by\x2did-scsi\x2d1ATA_TOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart3.device
24.630s dev-disk-by\x2did-scsi\x2dSATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart3.device
24.630s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart3.device
24.447s dev-disk-by\x2did-scsi\x2d350000395f5701a72\x2dpart6.device
24.447s dev-disk-by\x2did-ata\x2dTOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart6.device
24.447s dev-disk-by\x2did-wwn\x2d0x50000395f5701a72\x2dpart6.device
24.447s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart6.device
24.447s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart6.device
24.447s dev-disk-by\x2did-scsi\x2dSATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart6.device
24.447s dev-disk-by\x2did-scsi\x2d1ATA_TOSHIBA_MQ01ABF050_Z443SGVSS\x2dpart6.device
24.447s dev-disk-by\x2dpartuuid-f82cb1f3\x2d9b54\x2d4257\x2dbb33\x2ddac86879a238.device
24.447s dev-disk-by\x2did-scsi\x2d0ATA_TOSHIBA_MQ01ABF0_Z443SGVSS\x2dpart6.device
lines 1-59
 

Christina

Moderator
Teammitglied
an meine Laptop (Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz)
Startet Suse 15.4 recht langsam...
Habt Ihr eine Ekrlärung, für das langsame booten:
Code:
@localhost:~> systemd-analyze
Startup finished in 2.938s (firmware) + 10.084s (loader) + 1.640s (kernel) + 5.725s (initrd) + 51.824s (userspace) = 1min 12.213s
graphical.target reached after 51.810s in userspace
Hi thio,
wenn du als Desktop KDE Plasma 5 verwendest und in deinem Notebook nur eine TOSHIBA MQ01ABF050 HDD steckt, halte ich die Startzeiten für reell.
Die HDD bremst bei dir die CPU aus. Vor 10 Jahren war eine SSD noch Luxus, heute ist sie fast gar Pflicht.
Mit einer SSD dürfte sich die Startzeit für "userspace" & "graphical.target" bei deinem Notebook zumindest halbieren.

Ich habe dir mal ein paar einfache Benchmarks angefertigt:
Eine Crucial MX500 250GB SSD (links) und eine Hitachi HGST-Z5K500 500GB 2,5" HDD (rechts). Die Hitachi ist vergleichbar mit der Toshiba HDD.

MegaByte pro Sekunde:
Crucial-MX500-250GB-MBPS.pngHGST-Z5K500-500GB-MBPS.PNG

Input/Output-Operations pro Sekunde:
Crucial-MX500-250GB-IOPS.pngHGST-Z5K500-500GB-IOPS.PNG

Anm.: Die SSD steckt in einem externen Gehäuse mit ASM235CM-Chip angeschlossen an USB3.2 10Gbit/s. Die HDD steckt in einem Notebook.
Leider war es mir organisatorisch nicht möglich solche Benchmarks komplett unter Linux zu generieren.
LG Christina
 
OP
T

thio

Hacker
Code:
linux:~ # fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA MQ01ABF0
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: FF66B02A-0B29-419A-99AD-6D57F715DD42

Device         Start       End   Sectors   Size Type
/dev/sda1       2048   1333247   1331200   650M Windows recovery environment
/dev/sda2    1333248   1865727    532480   260M Microsoft basic data
/dev/sda3    1865728   2127871    262144   128M Microsoft reserved
/dev/sda4    2127872 308975068 306847197 146.3G Microsoft basic data
/dev/sda5  308975616 312569855   3594240   1.7G Windows recovery environment
/dev/sda6  312569856 312592383     22528    11M EFI System
/dev/sda7  312592384 316801023   4208640     2G Microsoft basic data
/dev/sda8  316801024 317122559    321536   157M EFI System
/dev/sda9  317122560 390154239  73031680  34.8G Microsoft basic data
/dev/sda10 390154240 926969855 536815616   256G Microsoft basic data
/dev/sda11 926969856 976762879  49793024  23.7G Microsoft basic data


Disk /dev/loop0: 55.56 MiB, 58261504 bytes, 113792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 68 KiB, 69632 bytes, 136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 47.99 MiB, 50323456 bytes, 98288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 47.98 MiB, 50315264 bytes, 98272 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 346.97 MiB, 363827200 bytes, 710600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 81.26 MiB, 85209088 bytes, 166424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 322.95 MiB, 338636800 bytes, 661400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 55.56 MiB, 58261504 bytes, 113792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 322.9 MiB, 338583552 bytes, 661296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop8: 347.09 MiB, 363945984 bytes, 710832 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 164.76 MiB, 172761088 bytes, 337424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
 

Christina

Moderator
Teammitglied
Hi thio,
poste mal bitte lsblk -o +FSTYPE,FSUSE%,LABEL. Die Partitionierung der Toshiba HDD ist etwas durcheinander.
 
OP
T

thio

Hacker
Code:
@linux:~> lsblk -o +FSTYPE,FSUSE%,LABEL
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS                     FSTYPE   FSUSE% LABEL
loop0     7:0    0 322,9M  1 loop /snap/wine-platform-6-stable/19 squashfs   100%
loop1     7:1    0 164,8M  1 loop /snap/gnome-3-28-1804/161       squashfs   100%
loop2     7:2    0  55,6M  1 loop /snap/core18/2566               squashfs   100%
loop3     7:3    0    48M  1 loop /snap/snapd/17029               squashfs   100%
loop4     7:4    0  81,3M  1 loop /snap/gtk-common-themes/1534    squashfs   100%
loop5     7:5    0  91,7M  1 loop /snap/gtk-common-themes/1535    squashfs   100%
loop6     7:6    0    68K  1 loop /snap/acrordrdc/62              squashfs   100%
loop7     7:7    0    48M  1 loop /snap/snapd/16778               squashfs   100%
loop8     7:8    0   347M  1 loop /snap/wine-platform-runtime/316 squashfs   100%
loop9     7:9    0     4K  1 loop /snap/bare/5                    squashfs   100%
loop10    7:10   0  55,6M  1 loop /snap/core18/2560               squashfs   100%
loop11    7:11   0 322,9M  1 loop /snap/wine-platform-6-stable/14 squashfs   100%
loop12    7:12   0 347,1M  1 loop /snap/wine-platform-runtime/315 squashfs   100%
sda       8:0    0 465,8G  0 disk                                                 
├─sda1    8:1    0   650M  0 part                                 ntfs            WINRE
├─sda2    8:2    0   260M  0 part                                 vfat           
├─sda3    8:3    0   128M  0 part                                                 
├─sda4    8:4    0 146,3G  0 part                                 ntfs            Windows
├─sda5    8:5    0   1,7G  0 part                                 ntfs           
├─sda6    8:6    0    11M  0 part                                                 
├─sda7    8:7    0     2G  0 part [SWAP]                          swap           
├─sda8    8:8    0   157M  0 part /boot/efi                       vfat         3%
├─sda9    8:9    0  34,8G  0 part /var/tmp                        btrfs       67%
│                                 /var/spool                                     
│                                 /var/opt                                       
│                                 /var/log                                       
│                                 /var/lib/pgsql                                 
│                                 /var/lib/named                                 
│                                 /var/lib/mailman                               
│                                 /var/crash                                     
│                                 /usr/local                                     
│                                 /tmp                                           
│                                 /srv                                           
│                                 /opt                                           
│                                 /boot/grub2/x86_64-efi                         
│                                 /boot/grub2/i386-pc                             
│                                 /.snapshots                                     
│                                 /                                               
├─sda10   8:10   0   256G  0 part /home                           ext4        56%
└─sda11   8:11   0  23,7G  0 part                                 ntfs            RECOVERY
sr0      11:0    1  1024M  0 rom
 

Christina

Moderator
Teammitglied
Danke, jetzt ist die Sache klarer.
Das Geschwindigkeitsproblem wirst du nur mit einer SSD lösen können.
Hast du zweimal MS-Windows installiert: 7 & 10 oder 10 & 11?
Eine EFI-Partition (FAT) brauchst du nur einmal, so etwa 100 MiB genügen im Prinzip.
lg Christina
 

Christina

Moderator
Teammitglied
Schaue dir mal die Partitionen sda1 bis sda5 an: Die sind irgendwie doppelt vorhanden.
sda6 ist auch doppelt, denn du hast ja sda8, und du brauchst nur eine EFI-Partition für den UEFI-Start.

Dein Notebook ist noch sehr gut brauchbar. Da würde ich eine (aktuelle) SSD investieren und alles neu installieren.
LG Christina
 
Oben