Hey there! I have recently installed solus budgie everything works fine except very slow booting. I have a 32gb samsung ssd (22gb free) and it use boot windows 10 under 25 seconds. Now after installing solus budgie it takes nearly 3mins to boot the system i can only see black screen with a blinking hyphen for 2 mins.If anybody knows solution please provide it
[New user] Slow booting
- Edited
pLaYeR45 Normal load times for Solus are less than load times for Windows 10 on the same computer. Something is hanging (the 2 minutes of blinking cursor). We won't be able to help resolve the issue until we know what is hanging.
The only way I know to find out what is hanging is to run sudo journalctl -b in the terminal and then hunt through the resulting output, which is likely to be somewhere between 1500 and 2000 lines long. You can use the arrow key on your keyboard to scroll down through the entries.
Here is what you should be looking for:
(1) Any lines that are in red. Red indicates processes that did not complete. Make note of any red entries (you can copy and paste into the notepad for convenience).
(2) Timestamp lags on the left side of each entry. Timestamp lags will show where the system is hanging, and probably identify the issue.
These are a few lines from my journalctl -b results (the timestamps are in bold so you will know where to look to find timestamps):
Apr 23 12:51:39 dell-ts-7070-solus systemd[705]: Created slice User Core Session Slice.
Apr 23 12:51:39 dell-ts-7070-solus systemd[705]: Starting Virtual filesystem service...
Apr 23 12:51:40 dell-ts-7070-solus systemd[705]: Started Virtual filesystem service.
Apr 23 12:51:40 dell-ts-7070-solus systemd[705]: Started Accessibility services bus.
Make note of the lines (you can copy and paste into the notepad for convenience) immediately before and immediately after any process that takes more than a second or two to complete. In all likelihood, those lines will identify what is hanging.
Then report back and we'll see if we can help.
This is a completely blind guess, but what you are describing suggests a hardware/driver problem.
pLaYeR45
Yeah that's waaaaaaaayyyy too long. Mine boots in 4.88 seconds, and my hardware isn't even all that great.
Check the output of the following command to see if it can identify the part of the boot that is slow, and possibly the cause of the slowdown:
systemd-analyze (to see how long each part of the boot takes)
systemd-analyze blame (to maybe find the culprit)
This is neat!
~ $ systemd-analyze
Startup finished in 5.373s (firmware) + 477ms (loader) + 1.402s (kernel) + 2.272s (initrd) + 15.371s (userspace) = 24.897s
multi-user.target reached after 15.354s in userspace
0[14:17:45](sasha@bunux): ~ $ systemd-analyze blame
12.152s NetworkManager-wait-online.service
3.334s vboxdrv.service
1.955s apparmor.service
860ms org.cups.cupsd.service
732ms initrd-switch-root.service
590ms systemd-journal-flush.service
550ms upower.service
496ms bluetooth.service
491ms systemd-logind.service
481ms NetworkManager.service
436ms ModemManager.service
373ms ufw.service
354ms polkit.service
328ms systemd-udev-trigger.service
280ms systemd-udevd.service
244ms aa-lsm-hook.service
204ms user@1000.service
195ms auditd.service
191ms initrd-parse-etc.service
130ms colord.service
121ms clr-boot-manager-booted.service
90ms systemd-tmpfiles-setup.service
86ms systemd-tmpfiles-setup-dev.service
66ms systemd-rfkill.service
63ms systemd-user-sessions.service
62ms power-profiles-daemon.service
59ms systemd-journald.service
54ms systemd-modules-load.service
53ms systemd-remount-fs.service
44ms systemd-tmpfiles-clean.service
42ms systemd-sysctl.service
41ms dev-hugepages.mount
40ms dev-sda2.swap
40ms dev-mqueue.mount
39ms sys-kernel-debug.mount
38ms systemd-random-seed.service
38ms sys-kernel-tracing.mount
37ms alsa-restore.service
37ms sys-fs-fuse-connections.mount
35ms sys-kernel-config.mount
33ms modprobe@configfs.service
33ms modprobe@drm.service
33ms kmod-static-nodes.service
32ms modprobe@fuse.service
28ms rtkit-daemon.service
28ms user-runtime-dir@1000.service
27ms tmp.mount
25ms initrd-cleanup.service
23ms systemd-fsck-root.service
16ms systemd-boot-system-token.service
16ms avahi-daemon.service
16ms snapd.socket
14ms systemd-update-utmp.service
14ms systemd-backlight@backlight:acpi_video0.service
11ms systemd-update-utmp-runlevel.service
6ms initrd-udevadm-cleanup-db.service
elfprince Interesting. I don't get anything close to that level of detail on Solus Budgie:
$ systemd-analyze
Startup finished in 7.988s (firmware) + 2.605s (loader) + 2.751s (kernel) + 7.772s (userspace) = 21.117s
graphical.target reached after 7.767s in userspace
And that's it. None of the detail you report.
Checked on Ubuntu Budgie, and no more detail reported on that build either.
The interesting news is that I got remarkably similar results -- 21 +/- seconds for both Solus Budgie and Ubuntu Budgie. I was surprised by how close the results were, because Solus "felt" a little faster. Windows 11 (timed by my watch) takes about 31 seconds by way of comparison.
tomscharbach Did you try the second command? systemd-analyze blame
- Edited
elfprince Did you try the second command? systemd-analyze blame
Yeah, I get a lot more information (104 lines) out of systemd-analyze blame, but since my system is booting fine, I don't get results that would show me what happens in a situation like @pLaYeR45's boot lags. I'm glad to learn about the two commands, though, because I wasn't aware of them . I'm old enough to be old school -- read a ton of lines in a log and see what I make of it.
tomscharbach I'm glad to learn about the two commands, though.
That's what this forum is for, right?
- Edited
tomscharbach
ran sudo journalctl -b no red colour lines found
Staudey
ran
systemd-analyze
Startup finished in 1.803s (kernel) + 1min 9.186s (initrd) + 1.186s (userspace) = 1min 12.176ssystemd-analyze blame
17.196s lvm2-pvscan@8:18.service >
552ms initrd-switch-root.service >
528ms upower.service >
476ms systemd-udev-trigger.service >
415ms systemd-fsck-root.service >
248ms udisks2.service >
184ms systemd-journal-flush.service >
167ms systemd-udevd.service >
141ms initrd-parse-etc.service >
140ms aa-lsm-hook.service >
134ms ModemManager.service >
134ms user@1000.service >
92ms NetworkManager.service >
73ms lightdm.service >
63ms auditd.service >
55ms avahi-daemon.service >
50ms systemd-logind.service >
47ms accounts-daemon.service >
47ms org.cups.cupsd.service >
46ms systemd-tmpfiles-clean.service >
45ms polkit.service >
41ms systemd-tmpfiles-setup.service >
38ms systemd-tmpfiles-setup-dev.service >
37ms systemd-rfkill.service >
35ms systemd-fsck@dev-disk-by\x2duuid-7d48592b\x2d97b0\x2d40e8\x2d9532\x2d25>
35ms dev-hugepages.mount >
34ms dev-mqueue.mount >
33ms colord.service >
32ms dev-disk-by\x2duuid-9582c8f5\x2dd188\x2d4236\x2db7ff\x2d6f58dc19be11.sw>
32ms sys-kernel-debug.mount >
30ms systemd-sysctl.service >
30ms sys-kernel-tracing.mount >
30ms bluetooth.service >
26ms kmod-static-nodes.service >
23ms clr-boot-manager-booted.service >
22ms systemd-random-seed.service >
22ms initrd-cleanup.service >
20ms systemd-journald.service >
19ms systemd-remount-fs.service >
18ms systemd-update-utmp-runlevel.service >
16ms wpa_supplicant.service >
12ms systemd-user-sessions.service >
12ms user-runtime-dir@1000.service >
11ms tmp.mount >
8ms systemd-update-utmp.service >
8ms systemd-backlight@leds:toshiba::kbd_backlight.service >
8ms systemd-backlight@backlight:intel_backlight.service >
5ms sys-fs-fuse-connections.mount >
5ms initrd-udevadm-cleanup-db.service >
1ms snapd.socket
>
i think the slow boot is because of my hitachi hard drive (320gb).This drive has lot of bad sectors and it is not working
Every time i boot into the system ......notification pops up "disk is likely to fail soon"
You can try systemd-analyze critical-chain too
- Edited
pLaYeR45 systemd-analyze
Startup finished in 1.803s (kernel) + 1min 9.186s (initrd) + 1.186s (userspace) = 1min 12.176s
Note that the time delay (1min 9.186s) occurs at the second stage (initrd) of the process. Although the lag doesn't show up in the detail you reported, the lag exists.
What I would suggest at this point is that you run sudo journalctl -b again (no need to reboot; it will report your most recent boot) and scroll down the long list of log entries.
Using my example timestamp from above, you should see one or more points with a large time difference between one process and the next. That is where the lag is happening. If you can find it, copy the 4-5 lines above the time lag and the 4-5 lines below the time lag, and we might be able to see what is happening.
pLaYeR45 i think the slow boot is because of my hitachi hard drive (320gb).This drive has lot of bad sectors and it is not working.
I'm missing something, I think.
Your initial report ("I have a 32gb samsung ssd (22gb free) and it use boot windows 10 under 25 seconds. Now after installing solus budgie it takes nearly 3mins to boot the system ...") suggested that you are booting off the 32GB Samsung drive. The screen you displayed shows that the 320GB Hitachi hard drive is what is failing. What does a report on the 32GB Samsung drive show? If the 32GB Samsung is okay, and you are booting off the Samsung, then probably it isn't a bad sector issue unless the 320GB Hitachi drive is somehow accessed during boot. What do you have on the 320GB hard drive that might be involved with booting Solus?
- Edited
tomscharbach
Just got off from zoom class ....saw ur notification.....Turned on the laptop(it was still booting) went to hang out with friends came back. Its been like 50 mins its still booting(blinking hyphen with black screen) I guess its 4th boot since installation. Did i just break the system?Do i need to install it again?
Laptop specifications:
Processor: i5 3317u
Graphics: intel hd 4000
- Edited
pLaYeR45 Did i just break the system?
Who knows, but your system isn't working right. None of the terminal commands we've been discussing in this thread could break anything. I doubt you broke anything. Something is wrong with your installation.
pLaYeR45 Do i need to install it again?
If I were you, I would at this point. Your current installation isn't working and a reinstall might be the simplest solution.
If you decide to install again, don't do anything fancy. When you get to "How should I install?" point in the installation process, select the "wipe the entire drive and install a fresh version" option rather than the "install along side existing operating system" option. I don't remember the exact words, the but the choice should be obvious. The idea is to completely wipe your drive and start fresh.
- Edited
tomscharbach
Yeah i will try to reinstall. I'll let u guyz know if the boot problem still exist after reinstallation btw thanks for helping me
- Edited
tomscharbach
UPDATE: just reinstalled solus
ran sudo journalctl -b
found many red lines after reinstallation
Apr 24 20:28:01 solus kernel: blk_update_request: I/O error, dev sda, sector 2 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
Apr 24 20:28:01 solus kernel: Buffer I/O error on dev sda, logical block 2, async page read
Apr 24 20:28:01 solus kernel: ata1: EH complete
Apr 24 20:28:04 solus kernel: ata1.00: exception Emask 0x0 SAct 0x10c000 SErr 0x0 action 0x0
Apr 24 20:28:04 solus kernel: ata1.00: irq_stat 0x40000008
Apr 24 20:28:04 solus kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 24 20:28:04 solus kernel: ata1.00: cmd 60/01:a0:00:00:00/00:00:00:00:00/40 tag 20 ncq dma 512 in
res 51/40:01:00:00:00/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Apr 24 20:28:04 solus kernel: ata1.00: status: { DRDY ERR }
Apr 24 20:28:04 solus kernel: ata1.00: error: { UNC }
the following same red line alternating continued for like 2 min with different logical block.
is my ssd full of bad sectors?
tomscharbach
i just figured out the error shows Buffer I/O error on dev sda, logical block 2
the error is in dev sda which is my hitachi(320gb)
is there any way i can stop system to access this hard drive ?
is solus on the 320 gb hard drive or the 32 gb solid state drive. looks like the 320 gb hard drive is failing . have you used Disks to check the drive? Disks comes preinstalled on Solus. look for it in the menu and open it. next click on the 320 gb drive and then click on the hamburger ( 3 dots) menu and chose drive test from sub menu. it should tell you if your drive is okay . but from the readout you posted above i would say the drive is failing . can you remove the 320 gb hard drive from the system and leave only the 32 gb solid state drive ? once you do that reinstall solus on the 32 gb ssd and see if your problems are still present. good luck
- Edited
Solus budgie is installed on 32gb ssd (Samsung) and yes the drive with 320gb(Hitachi) has lot of bad sector and it starts to click when it is mounted. If i mount it and try to repair or run test i belive the os(solus) might crash. I tried to remove bad sectors in windows and the drive started to make clicking sound. I have no problem in deleting 320 gb hard drive and it doesnt have any of my data. I dont want to remove 320gb hdd manually i just want solus to not access it and try reading it.The problem with manually removing is that i am not good at disassembling laptop if it was in pc i could have easily removed it.
- Edited
pLaYeR45 is there any way i can stop system to access this hard drive ?
I don't know. Solus is set up on the 32 GB Samsung, exactly as you said, and the boot partition (sdb1) is on that drive. I don't know why Solus is trying to access the 320 GB HJitachi (sda), unless there is something in the BIOS boot process that looks for a boot partition on sda first, and then, not finding a boot partition on sda, looks to sdb, where it finds the boot partition. But that is just a guess, and not an informed guess.
pLaYeR45 I have no problem in deleting 320 gb hard drive and it doesnt have any of my data. I dont want to remove 320gb hdd manually i just want solus to not access it and try reading it.The problem with manually removing is that i am not good at disassembling laptop if it was in pc i could have easily removed it.
I spent the morning coaching one of my grandsons through the process of disassembling his laptop so that he could install more RAM. He was all thumbs at first, of course, but as we went through the process, he got more confident and more skilled. But his laptop is an older Dell Latitude I gave him, and it has a metal case designed for easy disassembly. I'm all thumbs myself when it comes to the plastic cases, even though I've done it many times and have the plastic tools needed for the job. So I understand what you are saying.
I have two thoughts that might help.
(1) Go into BIOS (this document is a resource to find the right key combination to get into BIOS if you don't know it for your laptop) and see if you can disable the 320GB hard drive in BIOS. I can do it on my Dell computers, but BIOS capabilities vary, so you might not be able to do so. If you can disable the drive in BIOS, Solus might not look to it at all during the boot process.
(2) If that doesn't work, and nobody else comes along with a better idea, you are probably going to have to get the drive out of the machine (better yet, replace it with a cheap SATA 2.5" SSD). That means you will will have to disassemble the laptop. Because I am not good at cracking the case on plastic laptops, one of the things I do is look for a YouTube video showing how to open the case for the make/model I'm working with, or a make/model that is close. There is usually a trick to it (start at a specific point, and so on), and once I know the trick, I can usually do it. Another possibility is to see if you can find a friend who is good at this stuff and get your friend to do it for you.
- Edited
Try wiping the disk do not reformat it or anything just wipe it and try that system I think would not
see it then. (may not wipe if its to far gone)
I havent wiped any disks with linux not sure of program in linux maybe somebody knows
If the hitachi has any boot info on it the uefi probably grabbing it and causing the hang.
But I would do Like tom said disable it in bios,and I dont know your boot sequence either if that disk is first in list might be hanging it. Best thing do is remove it from laptop.