LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This 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


Reply
  Search this Thread
Old 05-01-2021, 01:21 PM   #16
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Done


Quote:
Originally Posted by colorpurple21859 View Post
Boot into mint, run gparted, highlight sda1, manage flags, uncheck hidden, keep esp boot flag
Done.
Not Hidden. No changes.

$ sudo parted -l
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat32 EFI system partition boot, esp
2 274MB 408MB 134MB Microsoft reserved partition msftres
3 408MB 1938GB 1938GB ntfs Basic data partition msftdata
4 1938GB 1938GB 1049kB
5 1938GB 1939GB 538MB fat32 msftdata
6 1939GB 1939GB 538MB fat32 msftdata
7 1939GB 2000GB 61.0GB ext4


Model: ATA WDC WD10EADS-65M (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32.3kB 1000GB 1000GB primary ntfs
 
Old 05-01-2021, 03:22 PM   #17
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,451

Rep: Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056
According to boot repair
Quote:
BootCurrent: 000E
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
Code:
sudo efibootmgr -o 000E,001C,0000,001D,001E,0011,0003,0017,0019,0004,0008,000C,000D,0009
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.

Last edited by colorpurple21859; 05-01-2021 at 03:24 PM.
 
Old 05-01-2021, 05:30 PM   #18
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
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
Code:
sudo efibootmgr -o 000E,001C,0000,001D,001E,0011,0003,0017,0019,0004,0008,000C,000D,0009
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
 
Old 05-01-2021, 06:37 PM   #19
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,451

Rep: Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056
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.
 
Old 05-01-2021, 10:02 PM   #20
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Better.

Quote:
Originally Posted by colorpurple21859 View Post
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
Code:
sudo efibootmgr -o 000E,001C,0000,001D,001E,0011,0003,0017,0019,0004,0008,000C,000D,0009
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.
$ efibootmgr
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 Controller
 
Old 05-01-2021, 10:10 PM   #21
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
systemd-analyze

I can't get cat to work. Here's the time recorded by the system.

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

Last edited by zzpatrick; 05-01-2021 at 10:11 PM.
 
Old 05-02-2021, 12:41 AM   #22
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 17,237
Blog Entries: 10

Rep: Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160Reputation: 5160
Quote:
Originally Posted by zzpatrick View Post
BootCurrent: 0000
Apparently what colourpurple requested hasn't worked.

Quote:
Originally Posted by zzpatrick View Post
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
Code:
systemd-analyze blame
 
Old 05-02-2021, 07:09 AM   #23
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ondoho View 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).

$ systemd-analyze blame
53.123s upower.service
43.171s fwupd.service
25.095s fwupd-refresh.service
12.652s man-db.service
10.140s networkd-dispatcher.service
7.364s udisks2.service
6.531s accounts-daemon.service
5.516s ubuntu-system-adjustments.service
5.324s NetworkManager.service
5.284s dev-sda7.device
5.106s systemd-journal-flush.service
5.097s logrotate.service
4.034s polkit.service
4.010s avahi-daemon.service
4.009s bluetooth.service
3.850s wpa_supplicant.service
3.849s thermald.service
3.846s systemd-logind.service
3.006s ModemManager.service
2.846s grub-common.service
2.400s hddtemp.service
2.265s secureboot-db.service
2.215s gpu-manager.service
1.897s systemd-resolved.service
1.653s rsyslog.service
1.498s lightdm.service
1.492s plymouth-quit-wait.service
883ms systemd-udevd.service
764ms apparmor.service
744ms e2scrub_reap.service
711ms networking.service
685ms systemd-tmpfiles-setup.service
600ms systemd-modules-load.service
492ms alsa-restore.service
401ms keyboard-setup.service
398ms grub-initrd-fallback.service
359ms systemd-sysusers.service
359ms lm-sensors.service
347ms systemd-rfkill.service
337ms systemd-random-seed.service
326ms systemd-fsck@dev-disk-by\x2duuid-E20A\x2d328C.service
310ms dns-clean.service
292ms pppd-dns.service
283ms systemd-udev-trigger.service
214ms colord.service
204ms lvm2-monitor.service
169ms swapfile.swap
165ms systemd-sysctl.service
164ms user@1000.service
160ms setvtrgb.service
155ms systemd-journald.service
145ms systemd-user-sessions.service
136ms systemd-tmpfiles-setup-dev.service
123ms ifupdown-pre.service
119ms systemd-timesyncd.service
106ms kerneloops.service
106ms systemd-remount-fs.service
104ms ufw.service
98ms dev-hugepages.mount
97ms dev-mqueue.mount
96ms sys-kernel-debug.mount
95ms sys-kernel-tracing.mount
92ms blk-availability.service
89ms kmod-static-nodes.service
83ms console-setup.service
62ms boot-efi.mount
43ms rtkit-daemon.service
41ms systemd-update-utmp.service
30ms plymouth-read-write.service
16ms plymouth-start.service
12ms systemd-update-utmp-runlevel.service
12ms user-runtime-dir@1000.service
7ms finalrd.service
7ms e2scrub_all.service
5ms sys-fs-fuse-connections.mount
4ms openvpn.service
4ms sys-kernel-config.mount
3ms motd-news.service
 
Old 05-02-2021, 07:36 AM   #24
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
New Boot Repair message

Quote:
Originally Posted by colorpurple21859 View Post
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?"
 
Old 05-02-2021, 09:13 AM   #25
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,451

Rep: Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056
is there a /etc/initramfs-tools/conf.d/resume file?
 
Old 05-02-2021, 11:14 AM   #26
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
is there a /etc/initramfs-tools/conf.d/resume file?
The folder exists, but there's nothing in it.
 
Old 05-02-2021, 02:08 PM   #27
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,451

Rep: Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056
the two that is the slowest is fwupd and upower. A quick search of fwupd came across this
https://unix.stackexchange.com/quest...doing-that-and
I didn't find anything on upower.
 
Old 05-03-2021, 06:50 AM   #28
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
the two that is the slowest is fwupd and upower. A quick search of fwupd came across this
https://unix.stackexchange.com/quest...doing-that-and
I didn't find anything on upower.
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?

Thanks again.
 
Old 05-03-2021, 07:22 AM   #29
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Thumbs up That fixed it.

Quote:
Originally Posted by colorpurple21859 View Post
the two that is the slowest is fwupd and upower. A quick search of fwupd came across this
https://unix.stackexchange.com/quest...doing-that-and
I didn't find anything on upower.
It was the USB port for my backup drive.

$ systemd-analyze
Startup finished in 19.076s (firmware) + 5.910s (loader) + 5.626s (kernel) + 25.759s (userspace) = 56.373s
graphical.target reached after 19.370s in userspace
 
Old 05-04-2021, 06:59 AM   #30
zzpatrick
LQ Newbie
 
Registered: Apr 2021
Posts: 19

Original Poster
Rep: Reputation: Disabled
Solved/Thanks

Quote:
Originally Posted by colorpurple21859 View Post
the two that is the slowest is fwupd and upower. A quick search of fwupd came across this
https://unix.stackexchange.com/quest...doing-that-and
I didn't find anything on upower.
Thanks. It's appreciated. I learned a lot on top of getting it fixed. Add USB devices AFTER the boot. Totally works.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Boot Repair Tool - Repair The Most Boot Related Problems LXer Syndicated Linux News 0 06-21-2017 09:49 PM
[SOLVED] vobcopy is very very very slow fredak Linux - Software 9 05-03-2013 04:45 PM
Squid Server Very Very Very Slow jatender Linux - Server 1 09-28-2007 11:44 PM
A very very very very big problem!! Elbryan Linux - Software 2 09-23-2005 05:56 AM
Lindows very very very slow jfi Linspire/Freespire 15 03-28-2004 09:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 01:43 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration