[SOLVED] Boot up takes 1 minute and 9 seconds on a fast SSD

[LenAsh]

Hi - hopefully someone can decipher the bootchart log and tgz attached. I'm at a loss. I get 3 "COMRESET" errors about 10 seconds apart during boot. Shutdown takes about 1 second.

This is a "fast" system...

Windows boots in 8 seconds on another SSD.

Thanks!

https://drive.google.com/file/d/0B_ESvfV...sp=sharing
https://drive.google.com/file/d/0B_ESvfV...sp=sharing


EDIT: Fixed on any Linux distro. The problem was an "old" Intel 32GB SSD. This worked absolutely fine on W7, but any Linux didn't like it at all at boot. It had the latest firmware too, wgich was dated 2010. I've now removed it and binned it as I have no real need for this tiny drive.

Thanks for all help offered in any case.

[LenAsh]

Sharing links updated...!

[tompa]

Hi,
I'm a bit surprised to see my LL2 start in 28sec on new SSD, it was about the same boot time with old HD (on the same PC) .
My windows 7 boots in 30 sec on this PC/SSD.... 

/tompa

[Valtam]

If you don't have bluetooth you can disable it during boot, same with printing services. Menu, Settings, Session and Startup, Autostart tab. Those are the only 2 that are safe to untick, the rest must not be unticked. For a more advanced tool, try Boot Up Manager (B.U.M.):

Code:

sudo apt-get install bum

Only untick items if you know what you are doing. Disabling items without researching their function may render your machine unbootable.

[tompa]

If you don't have bluetooth you can disable it during boot, same with printing services. Menu, Settings, Session and Startup, Autostart tab. Those are the only 2 that are safe to untick, the rest must not be unticked. For a more advanced tool, try Boot Up Manager (B.U.M.):

Code:

sudo apt-get install bum

Only untick items if you know what you are doing. Disabling items without researching their function may render your machine unbootable.

Thanks for the tip!
Didn't make any difference here though

/tompa

[LenAsh]

Doesn't make any real difference. The problem seems to be something disk wise/ATA problems....

[anon222]

You are using kernel 3.16.0-031600rc4-generic
See if this resolves your problem https://www.freecinema2022.gq/forums/index...en#msg3725

[LenAsh]

Done that, the same.

I originally "updated" the kernel to the one linked due to sound problems with the Z97 chipset.

The problem is the same on 3.13, 3.15, 3.16rc4

[Valtam]

Checklist:
See if there is a firmware update for your SSD.
Also make sure your BIOS is set to AHCI and not IDE.
Have you enabled Trim on the SSD? - Help Manual, Install Guide,  Enabling TRIM on your SSD.

Here are a couple of links that have provided solutions for people - http://askubuntu.com/questions/315921/co...boot-times & http://askubuntu.com/questions/62295/how...iled-error

[LenAsh]

Firmware is the latest.
BIOS is AHCI - defaults to it.
TRIM is enabled and I have also forced a TRIM activity (sudo fstrim -v /)

By the way - and this is something I should have mentioned. ALL Linux distros have this problem on my machine. I've installed 2 others... they also have the audio problem. This CAN be overcome by switching the machine OFF after Windows and cold starting in to Linux. A restart from Windows produces no audio. This was the reason for updating kernels.

For further background: CPU is Intel i5 - 4690, Mobo is Gigabyte Z97-D3H, 16GB DDR3-1600 RAM.

2 SSDs, the Linux one is an Intel X25, 80GB

Thanks for your perseverance.