long time boot linux mint at a toshiba laptop. Tested also Debian and Ubuntu latest stable releases geting similar issues.

jorgespain76 · 08-30-2016, 03:44 AM

I'm using a Toshiba Satellite model L755-1J9 Laptop.

The issue I would want to solve is that the system spends more than ten minutes to reach the login prompt to get into the dektop environment. When choosing the boot option of "recovery mode" at grub it gives output messages from the boot process and they stop progressing the load and giving more messages for long gaps at three points that are the same every time i start the laptop with the "recovery mode" choosen. The messages shown as last step or task of boot supposed to be made when it stops adding more lines of messages and keeps apparently without carrying out any boot activity at all are these:

* the first point it stays blocked is when last printed message shows the text:
"clocksource: switched to clocksource TSC"

* after 10 minutes more or less it starts printing messages of the boot progress again. The first line of text printed after that period stoped is:
"Loading Essential Drivers"

*It does two periods of no activity more, the second, much shorter, is at the message:
"Runing /scripts/init-bottom"

*and the last gap of no progress, the shortest, is when gives a message about loading braille related kind of software features.

Could somebody give me possible reasons or causes of the boot stops for that long ga ps to be more aware of what happens.

Or if somebdy could confirm the way to solve it is not possible to achieve with my skills to follow the necessary steps for an hypothetical solution.

Even would appreciate if somebody let me know it's a non-viable or no solution at all in this kind of malfunction.

Thanks to read this, would be good news having some answer to get information at least. If it's necessary to give more logs or any system working path to detect the way it has this behavior don't doubt ask me for it.

Emerson · 08-30-2016, 06:53 AM

You could use a tool as webboard to paste your dmesg into a pastebin for starters.

TxLonghorn · 08-31-2016, 06:57 AM

Which Mint? 17? 18?
Which Desktop? Cinnamon?
Does the live Mint USB perform the same as the installed Mint?

TxLonghorn · 08-31-2016, 07:11 AM

Quote:

Originally Posted by Emerson

You could use a tool as webboard to paste your dmesg into a pastebin for starters.

WebBoard is no longer used in Mint. Now using pastebin. But you don't need it.
You can create a text file:

Code:

dmesg > ~/Desktop/dmesg.txt

and then paste the contents of the file at pastebin.ubuntu.com - and copy the resulting link to the forum.

jorgespain76 · 09-08-2016, 11:47 AM

Quote:

Originally Posted by TxLonghorn

Which Mint? 17? 18?
Which Desktop? Cinnamon?
Does the live Mint USB perform the same as the installed Mint?

Hi. Thanks for your replies to all.

Mine is a linux Mint 18 and booting usb was a kind of the same issue.

The dmesg output file is attached in this post.

Thanks.

ShvonderSiN · 09-09-2016, 01:09 AM

try use latest kernel
For 32-bit (single command):

Code:

cd /tmp; wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux-headers-4.7.0-040700-generic_4.7.0-040700.201608021801_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux-headers-4.7.0-040700_4.7.0-040700.201608021801_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux-image-4.7.0-040700-generic_4.7.0-040700.201608021801_i386.deb; sudo dpkg -i *.deb

For 64-bit (single command):

Code:

cd /tmp; wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux-headers-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux-headers-4.7.0-040700_4.7.0-040700.201608021801_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/linux-image-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64.deb; sudo dpkg -i *.deb

and

Code:

sudo update-grub
sudo reboot

TxLonghorn · 09-09-2016, 05:27 AM

If you look at your dmesg results you will see a huge 390 second delay when loading the RAID information. Also there is a mention of BTRFS. I have heard that Mint 18 has some problems with BTRFS, but I don't know details. I also don't know how to address problems with RAID, sorry.

Quote:

[ 2.849191] clocksource: Switched to clocksource tsc
[ 392.869737] raid6: sse2x1 gen() 8187 MB/s
[ 392.937726] raid6: sse2x1 xor() 6395 MB/s
[ 393.005726] raid6: sse2x2 gen() 10276 MB/s
[ 393.073719] raid6: sse2x2 xor() 7360 MB/s
[ 393.141715] raid6: sse2x4 gen() 11820 MB/s
[ 393.209710] raid6: sse2x4 xor() 8809 MB/s
[ 393.209711] raid6: using algorithm sse2x4 gen() 11820 MB/s
[ 393.209712] raid6: .... xor() 8809 MB/s, rmw enabled
[ 393.209713] raid6: using ssse3x2 recovery algorithm
[ 393.210731] xor: automatically using best checksumming function:
[ 393.249707] avx : 20110.000 MB/sec
[ 393.262481] Btrfs loaded

Emerson · 09-09-2016, 06:14 AM

This RAID is part of btrfs, how to remove btrfs.

jorgespain76 · 09-10-2016, 02:54 PM

I've tested the two suggested changes: remove BTRFS from the system and install the 4.7 kernel as well, but I got no straight boot yet, the same way as before.

I attach the current dmesg text. For me only to say that looking at messages by the screen when it boots in "recovery mode" the first one after the gap of more than 300 seconds is:"device-mapper:ioctl ... initialized: dm-devel@redhat.com". Don't know if it has something to do on the time waiting.

Thanks to all for the given ideas.