Chirurgia cranio-cerebrală minim invazivă
Tehnicile minim invazive impun utilizarea unei tehnologii ultramoderne. Endoscoapele operatorii de diverse tipuri, microscopul operator dedicat, neuronavigația, neuroelectrofiziologia, tehnicile avansate de anestezie, chirurgia cu pacientul treaz reprezintă armamentarium fără de care neurochirurgia prin "gaura cheii" nu ar fi posibilă. Folosind tehnicile de mai sus, tratăm un spectru larg de patologii cranio-cerebrale. www.neurohope.ro |
Linux Mint 20.04 Ulyana - Slow Startup Q 6600
Last Updated: Sep 10 2020 11:08, Started by
mfmig200
, Sep 08 2020 15:29
·
0
#1
Posted 08 September 2020 - 15:29
Linux Mint 20.04 - Start-up-ul este foarte lent aproximativ 90 secunde cu SSD - nu stiu de unde provine problema ca sa incerc o solutie de reparare, am incercat din advanced settings boot-area cu alt kernel dar este exact acelasi comportament, mai jos sunt informatiile legate de acest sistem.
System: Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal Machine: Type: Desktop Mobo: Gigabyte model: P35-DS3 v: x.x serial: <filter> BIOS: Award v: F14 date: 06/18/2009 CPU: Topology: Quad Core model: Intel Core2 Quad Q6600 bits: 64 type: MCP arch: Core Merom rev: B L2 cache: 4096 KiB flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 19200 Speed: 1596 MHz min/max: 1600/2400 MHz Core speeds (MHz): 1: 1602 2: 1600 3: 1600 4: 1600 Graphics: Device-1: NVIDIA GF104 [GeForce GTX 460] vendor: Point of View BV driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0e22 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1280x1024~60Hz OpenGL: renderer: NVC4 v: 4.3 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel 82801I HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e Device-2: NVIDIA GF104 High Definition Audio vendor: Point of View BV driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0beb Sound Server: ALSA v: k5.4.0-26-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel port: d000 bus ID: 04:00.0 chip ID: 10ec:8168 IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 1.13 TiB used: 9.18 GiB (0.8%) ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB speed: 3.0 Gb/s serial: <filter> ID-2: /dev/sdb vendor: Kingston model: SMS200S3120G size: 111.79 GiB speed: 3.0 Gb/s serial: <filter> ID-3: /dev/sdc vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB speed: 3.0 Gb/s serial: <filter> Partition: ID-1: / size: 36.28 GiB used: 9.18 GiB (25.3%) fs: ext4 dev: /dev/sdb2 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 chip ID: 1d6b:0002 Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 chip ID: 1d6b:0002 Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 chip ID: 1d6b:0001 Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 chip ID: 1d6b:0001 Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 chip ID: 1d6b:0001 Device-1: 5-1:2 info: HP Elite Keyboard type: Keyboard,HID driver: hid-generic,usbhid rev: 1.1 chip ID: 03f0:034a Device-2: 5-2:3 info: Logic3 / SpectraVideo plc LG Optical Mouse 3D-310 type: Mouse driver: hid-generic,usbhid rev: 1.1 chip ID: 1267:0210 Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 chip ID: 1d6b:0001 Hub: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 chip ID: 1d6b:0001 Hub: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 chip ID: 1d6b:0001 Sensors: System Temperatures: cpu: 46.0 C mobo: N/A gpu: nouveau temp: 34 C Fan Speeds (RPM): N/A gpu: nouveau fan: 1530 Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com ulyana main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse 6: deb http: //archive.canonical.com/ubuntu/ focal partner Info: Processes: 197 Uptime: 10m Memory: 7.77 GiB used: 868.4 MiB (10.9%) Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client inxi: 3.0.38 La analiza pare ca iese si mai prost: Startup finished in 5.759s (kernel) + 4min 54.190s (userspace) = 4min 59.949s graphical.target reached after 1min 31.771s in userspace La comanda: sudo systemd-analyze blame 3min 23.578s fstrim.service 3.083s man-db.service 1.314s dev-sdb2.device 1.263s networkd-dispatcher.service 985ms udisks2.service 649ms systemd-logind.service 517ms upower.service 510ms lightdm.service 485ms plymouth-quit-wait.service 467ms accounts-daemon.service 407ms ModemManager.service 389ms ubuntu-system-adjustments.service 372ms e2scrub_reap.service 357ms logrotate.service 341ms [email protected] 261ms NetworkManager.service 260ms avahi-daemon.service 237ms polkit.service 225ms systemd-journald.service 217ms systemd-resolved.service 204ms keyboard-setup.service 204ms systemd-timesyncd.service 190ms gpu-manager.service lines 1-23 De aici tezulta ca am 3min 23.578s fstrim.service ce sa ii fac ca sa nu se agate aici? Edited by mfmig200, 08 September 2020 - 15:25. |
#2
Posted 08 September 2020 - 15:50
fstrim e o functie pentru optimizare SSD, daca tin bine minte. Ar trebui sa ruleze o data pe saptamana, nu la fiecare boot.
|
#3
Posted 08 September 2020 - 15:59
bun si atunci cum o setez asa sa mearga 1 data pe saptamana sau care ar fi workaround-ul?
|
#4
Posted 08 September 2020 - 16:07
journalctl -u fstrimSi de aici pleci cu troubleshooting-ul. Adica vezi in log-uri ce se zice de respectivul proces. |
#5
Posted 08 September 2020 - 17:38
journalctl -u fstrim
-- Logs begin at Fri 2020-07-17 23:55:10 EEST, end at Tue 2020-09-08 21:32:50 E> Jul 22 09:15:27 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on files> Jul 22 09:18:22 mf4-P35-DS3 fstrim[929]: /: 27,9 GiB (29889269760 bytes) trimme> Jul 22 09:18:22 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Jul 22 09:18:22 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on files> -- Reboot -- Aug 14 00:20:26 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on files> Aug 13 21:23:36 mf4-P35-DS3 fstrim[946]: /: 27,6 GiB (29635629056 bytes) trimme> Aug 13 21:23:36 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Aug 13 21:23:36 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on files> -- Reboot -- Sep 02 23:05:00 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on files> Sep 02 23:08:19 mf4-P35-DS3 fstrim[951]: /: 27,2 GiB (29163909120 bytes) trimme> Sep 02 23:08:19 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Sep 02 23:08:19 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on files> -- Reboot -- Sep 08 19:03:41 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on files> Sep 08 16:07:03 mf4-P35-DS3 fstrim[933]: /: 27,2 GiB (29196736512 bytes) trimme> Sep 08 16:07:03 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Sep 08 16:07:03 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on files> lines 1-20/20 (END)...skipping... -- Logs begin at Fri 2020-07-17 23:55:10 EEST, end at Tue 2020-09-08 21:32:50 EEST. -- Jul 22 09:15:27 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Jul 22 09:18:22 mf4-P35-DS3 fstrim[929]: /: 27,9 GiB (29889269760 bytes) trimmed on /dev/sdb2 Jul 22 09:18:22 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Jul 22 09:18:22 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab. -- Reboot -- Aug 14 00:20:26 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Aug 13 21:23:36 mf4-P35-DS3 fstrim[946]: /: 27,6 GiB (29635629056 bytes) trimmed on /dev/sdb2 Aug 13 21:23:36 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Aug 13 21:23:36 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab. -- Reboot -- Sep 02 23:05:00 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Sep 02 23:08:19 mf4-P35-DS3 fstrim[951]: /: 27,2 GiB (29163909120 bytes) trimmed on /dev/sdb2 Sep 02 23:08:19 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Sep 02 23:08:19 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab. -- Reboot -- Sep 08 19:03:41 mf4-P35-DS3 systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Sep 08 16:07:03 mf4-P35-DS3 fstrim[933]: /: 27,2 GiB (29196736512 bytes) trimmed on /dev/sdb2 Sep 08 16:07:03 mf4-P35-DS3 systemd[1]: fstrim.service: Succeeded. Sep 08 16:07:03 mf4-P35-DS3 systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-20/20 (END) intre timp am gasit pe net cum se da disable la Trim si o sa o fac manual din cand in cand, https://askubuntu.co...-high-boot-time dar tot am slow bot: systemd-analyze blame 1.484s dev-sdb2.device 660ms udisks2.service 610ms systemd-logind.service 505ms networkd-dispatcher.service 472ms lightdm.service 463ms plymouth-quit-wait.service 372ms accounts-daemon.service 360ms ubuntu-system-adjustments.service 350ms upower.service 307ms e2scrub_reap.service 256ms [email protected] 244ms NetworkManager.service 226ms avahi-daemon.service 220ms systemd-journald.service 192ms systemd-resolved.service 186ms keyboard-setup.service 184ms gpu-manager.service 184ms polkit.service 178ms networking.service 169ms ModemManager.service 169ms systemd-udev-trigger.service 165ms systemd-modules-load.service 153ms systemd-timesyncd.service lines 1-23 Edited by mfmig200, 08 September 2020 - 17:46. |
#6
Posted 08 September 2020 - 17:56
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 @1min 31.342s └─multi-user.target @1min 31.341s └─getty.target @1min 31.341s └─[email protected] @1min 31.341s └─system-getty.slice @1min 31.339s └─setvtrgb.service @1min 31.306s +31ms └─systemd-user-sessions.service @1min 30.825s +9ms └─network.target @1min 30.820s └─NetworkManager.service @1min 30.575s +244ms └─dbus.service @1min 30.570s └─basic.target @1min 30.547s └─sockets.target @1min 30.547s └─uuidd.socket @1min 30.546s └─sysinit.target @1min 30.536s └─systemd-timesyncd.service @724ms +153ms └─systemd-tmpfiles-setup.service @682ms +35ms └─systemd-journal-flush.service @544ms +135ms └─systemd-journald.service @322ms +220ms └─systemd-journald.socket @312ms └─-.mount @303ms lines 1-23 |
#7
Posted 08 September 2020 - 18:19
mfmig200, on 08 septembrie 2020 - 17:56, said:
└─sysinit.target @1min 30.536s └─systemd-timesyncd.service @724ms +153ms Quote
linux /vmlinuz-linux root=/dev/mapper/linux-root rw cryptdevice=UUID=dece9428-0f25-47c6-8100-39d587ecddb8:archlinux cryptkey=rootfs:****** quiet intel_pstate=powersave net.ifnames=0 acpi_osi= nmi_watchdog=0 rcutree.rcu_idle_gp_delay=1 |
#8
Posted 08 September 2020 - 20:22
Ai dreptate aici e buba a mers accesat cu Esc -ul apasat:
Attached FilesEdited by mfmig200, 08 September 2020 - 20:23. |
#9
Posted 08 September 2020 - 21:42
Hmmm.... fie e tot fstrim pornit de un alt serviciu, posibil sa fie chiar plymouth de vina. Mai poti incerca sa rulezi:
sudo journalctl -b 0Si cauti sa vezi ce a mai rulat la boot dupa ce a pornit plymouth. Acolo ramane un proces agatat si parca din /etc/systemd/system.conf setezi timeot-ul la ceva mai mic de 90 de secunde. Sunt 3 linii comentate, 2 au valoarea 90, una nu are nici o valoare setata, toate incep cu Default si contin Timeout. Poti sa scazi timpul la o valoare acceptabila si sa verifici din nou. Verifica si man-db sa nu porneasca la boot ca e posibil ca el sa fie de vina, eu a trebuit sa il omor ca la fiecare boot avea chef sa refaca cache-ul man si se lungeau urechile ca asteptam dupa el sa termine. ┌(ghost)─(Timberwolf)─(5.8.7-arch1-1) └─(Campaign 2 - The Mighty Nein)─(74 files, 92GB)─ $ sudo systemctl list-unit-files | i man-db man-db.service static - man-db.timer disabled disabled |
#10
Posted 09 September 2020 - 08:45
Merci! Cred/ sper ca s-a rezolvat am mai gasit problema pe forum la askubuntu: https://askubuntu.co...for-dev-disk-by
dev/sda5 la mine este SWAP-ul care nu stiu din ce motiv a creat problema asta l-am sters de tot si am refacut partitia de SWAP acum am la boot dupa selectarea Mint vreo maxim 20 de secunde ceea ce pentru SATA 2 cum e placa de baza de la Q6600 e chiar ok! Edited by mfmig200, 09 September 2020 - 08:55. |
|
#11
Posted 09 September 2020 - 12:26
Muta swap-ul de pe SSD. Sau in loc de partitie swap setezi un fisier care sa functioneze ca si swap. Cat RAM ai pe jucaria aia? SWAP-ul e folosit? Ca daca nu e renunti cu totul la el.
|
#12
Posted 09 September 2020 - 13:28
Salut- am 8 GB DDR2 pe jucarie nu cred ca ajunge des in SWAP sa poata afecta SSD-ul.
|
#13
Posted 09 September 2020 - 14:11
La 8 GiB RAM renunta la swap. In cel mai rau caz muta swap-ul pe HDD. Eu tot 8GiB RAM am si nu am swap.
|
#14
Posted 10 September 2020 - 11:08
Bine, incerc sa vad cum merge fara SWAP daca spui tu ca nu o sa afecteze functionalitatea sistemului.
|
Anunturi
▶ 0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users