[SOLVED] Dual Boot is very slow/Boot Repair didn't work.
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
is what was used, however your boot order has 0000 first in the boot order.
let see if changing the boot order to make /efi/ubuntu/shimx64.efi first helps, from a terminal
According to boot repair is what was used, however your boot order has 0000 first in the boot order.
let see if changing the boot order to make /efi/ubuntu/shimx64.efi first helps, from a terminal
reboot.
After rebooting, if it is still slow open a terminal and run
Code:
efibootmgr
to see if the boot order changed. If not you may have to go into the firmware/bios to change the boot order.
Here's what I'm dealing with
60 seconds after I turn on computer before anything happens.
100 seconds after the mint logo
45 seconds to get to the password login
45 second before I can type a password.
15 seconds after the password and Mint is running.
I also tried changing the boot order in bios and nothing changed. Everything works in both OSs but it takes time. Btw, thanks for your patience.
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,001C,000E,001D,001E,0011,0003,0017,0019,0004,0008,000C,000D,0009
Boot0000* Windows Boot Manager
Boot0003* CD/DVD Device
Boot0004* Generic Usb Device
Boot0008* Generic Usb Device
Boot0009* CD/DVD Device
Boot000C* Generic Usb Device
Boot000D* CD/DVD Device
Boot000E* ubuntu
Boot0011* Generic Usb Device
Boot0017* CD/DVD Device
Boot0019* Generic Usb Device
Boot001C* Windows Boot Manager
Boot001D* UEFI: IPV4 Realtek PCIe GBE Family Controller
Boot001E* UEFI: IPV6 Realtek PCIe GBE Family Control
At the grub menu, highlight the linux mint entry, press e for edit, at the line that begins with linux delete the two words "splash quiet" press ctrl-x or f10 to boot. You will be able to see where the boot process hangs.
What are the specs of your system, processor, memory, graphics card.
post the ouput of
Code:
cat /etc/initramfs-tools/conf.d/resume
Last edited by colorpurple21859; 05-01-2021 at 06:41 PM.
According to boot repair is what was used, however your boot order has 0000 first in the boot order.
let see if changing the boot order to make /efi/ubuntu/shimx64.efi first helps, from a terminal
Apparently what colourpurple requested hasn't worked.
Quote:
Originally Posted by zzpatrick
systemd-analyze
Startup finished in 1min 11.516s (firmware) + 12.295s (loader) + 1min 8.910s (kernel) + 24.097s (userspace) = 2min 56.820s
graphical.target reached after 24.081s in userspace
I am surprised by this output. Why would the kernel take one minute (which is way too long even on a slow system) when the problem is supoposed to be on an EFI boot level, which I suppose should be the previous step?
But I admit I know very little about EFI.
Just to clarify, please also post
Apparently what colourpurple requested hasn't worked.
I am surprised by this output. Why would the kernel take one minute (which is way too long even on a slow system) when the problem is supoposed to be on an EFI boot level, which I suppose should be the previous step?
But I admit I know very little about EFI.
Just to clarify, please also post
Code:
systemd-analyze blame
It boots much faster but no where near what it was before installing 20.1. Whatever happened with the install slowed the entire boot system for both OSs. I'm getting boot errors now on Linux. Is there a way to record them so they can be shown here? For example, "Cannot find TOCBLOCK, database may be corrupt." My system is up to date so I'd be nice if it could fix itself (search boot errors and fix).
At the grub menu, highlight the linux mint entry, press e for edit, at the line that begins with linux delete the two words "splash quiet" press ctrl-x or f10 to boot. You will be able to see where the boot process hangs.
What are the specs of your system, processor, memory, graphics card.
post the ouput of
Code:
cat /etc/initramfs-tools/conf.d/resume
Boot Repair.
"SFS detected. You may want to retry after converting Windows dynamic partitioning (SFS partitions) to a basic disk. This can be performed via tools such as TestDisk or EASEUS-Partition-Master / MiniTool-Partition-Wizard.
Are you sure you want to continue anyway?"
He writes, "The GUI login appears seconds after hitting the power button"
I wish. That's only one part of the problem. I have a 60 or 70-second pause before I see the boot menu.
Then, additional pauses after the logo, and on and after the password page. Password is better now. It takes around 9 seconds before I can type anything. It used to be 45 seconds. I'll try removing all USB devices (the X-Box issue in the link) and see if that makes a difference. There are many USB errors after the boot process begins.
Thanks for all the time you put into this. I'm thinking it's as good as it's going to be for now and I'll adapt to it. As long as I can access both OSs I'm okay with the wait.
I'll also see if I can get up an update to my bios and then maybe a new reinstall. I see there are two Windows partitions stuck in the middle of the Linux partitions after I reinstalled Windows twice. The last reinstall of Linux gave me a boot menu, but also downloaded over 100MG during the installation. Previously I didn't give Linux access to the Internet until after it was installed, which may have caused some of the problems. I watched the system monitor during the last install and there was a big spike in Internet access at the very end of the install. I wish I'd have written down how much was downloaded but who'd have thought of it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.