Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Guys, I have a Samsung Series 3 Notebook, model NP300E5a-A05US and I recently upgraded from Mint 18.3 (Cinnamon) to Mint 19.3 (Cinnamon). Once booted, my laptop seems to run fine; in fact, I love the enhancements made since my previous installation of Mint 18.3 (Cinnamon).
Get rid of the boot eye-candy (temporarily) and watch the messages. No doubt waiting for device (90 sec timeout), and I'll have a small wager it's a UUID mismatch on swap.
Get rid of the boot eye-candy (temporarily) and watch the messages. No doubt waiting for device (90 sec timeout), and I'll have a small wager it's a UUID mismatch on swap.
Lots of Google hits describe it, but maybe syg00 made what to do a bit sketchy. Goto https://en.opensuse.org/SDB:Nomodese...tion_Obstacles and read the upper blue paragraph about how to edit in the Grub menu. Don't use nomodeset though. Instead, use that method to test with the list of three items near the end of the page, starting with plymouth.
Unneeded services to disable, among several others, probably include:
lvm2-monitor (if you don't use LVM)
ModemManager (if you are a broadband user)
speech-dispatcher (if you're not blind)
Please paste here commands with output from the following:
[sudo] password for ray:
Model: ATA ST500LM012 HN-M5 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 500GB 500GB primary ext4 boot
~$ sudo cat /etc/fstab
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=04dd8594-1c70-4f0f-b767-126f3d8c160b / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0
Mar 18 15:12:44 Samsung kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Mar 18 15:13:08 Samsung udisksd[840]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Mar 18 15:13:08 Samsung udisksd[840]: Failed to load the 'mdraid' libblockdev plugin
Mar 18 15:13:09 Samsung thermald[827]: sysfs write failed /sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/enabled
Mar 18 15:13:19 Samsung colord[923]: failed to get session [pid 844]: No data available
Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: Failed to construct signal
Mar 18 15:13:23 Samsung wpa_supplicant[843]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Mar 18 15:13:23 Samsung /hpfax[1013]: [1013]: error: Failed to create /var/spool/cups/tmp/.hplip
Mar 18 15:14:15 Samsung pulseaudio[2037]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mar 18 15:14:15 Samsung dbus-daemon[796]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Mar 18 15:18:09 Samsung colord[923]: failed to get session [pid 3404]: No data available
Mar 18 15:25:39 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Mar 18 15:27:08 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Mar 18 15:27:20 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Mar 18 15:29:12 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Mar 18 15:29:22 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Mar 18 15:29:55 Samsung gnome-terminal-[4509]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
You have a quite uncommon configuration that may well play a part in the problem. Most machines use multiple partitions, usually at least two, often more, but you only have one. Thus Mint is using a swap file instead of a partition, and all user data is on the same partition as the operating system. I wouldn't expect this to play a part, but that's not to say it couldn't. I don't have much experience with Mint, and none at all with your partitioning.
Among the failed messages there is only one I recognize as having significant likelihood of material or primary contribution to the delay: mdraid. Why there would be any reference to mdraid on a laptop with only one disk and one partition on that disk I cannot imagine. It may well have a connection to the dev-sda1.device time, but I don't know how to find out. It's possible a perusal of the messages before and after that journal message could provide a clue. Here's a quick way to scan just that portion of the journal:
The journal can readily be scanned in its entirety. It automatically employs the less command, so that you can scroll and use pgup/pgdn keys to navigate through it.
Code:
sudo journalctl -b -e
will open it at the end point. Leave off the -e and it will start at the beginning. If you'd like to share the journal for an entire boot, redirect output to a file then upload it. This should do both in one step:
Code:
sudo journalctl -b | pastebinit
It will provide a URL for you to paste here. If a command not found results:
You have a quite uncommon configuration that may well play a part in the problem. Most machines use multiple partitions, usually at least two, often more, but you only have one. Thus Mint is using a swap file instead of a partition, and all user data is on the same partition as the operating system. I wouldn't expect this to play a part, but that's not to say it couldn't. I don't have much experience with Mint, and none at all with your partitioning.
mrmazda, I think that I partitioned the HDD on the laptop before I installed Mint 19.3. If I reinstalled Mint 19.3 from the CD, would there be an option to install Mint with partitions?
OK, you need to get to a boot menu - if it's dual boot, you already see it. If not, on reboot, right after POST (you may see a message from the PC maker), immediately hit the <Esc> key. Should get the boot menu - if not, keep repeating (faster) till it does.
The first entry should be your Mint option - if not use the cursor keys to highlight it. Hit <Enter>, and cursor down to the linux line, and delete the quiet splash options. Then hit <Ctrl>-x to continue the boot (don't hit <Enter>).
I think that I partitioned the HDD on the laptop before I installed Mint 19.3. If I reinstalled Mint 19.3 from the CD, would there be an option to install Mint with partitions?
I'm not sure any Linux installer fails to at least off it as an option, but let's not be quite so hasty to think reinstallation necessary, unless it's just something you feel like doing.
syg00 describes in another manner what I suggested in the first part of comment #4. What he describes enables a way to observe the boot process which could unveil clues to the problem not yet spotted in journal or elsewhere.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.