shutdown/reboot hangs for 2-3 minutes on 17.3 KDE

JackDinn · 02-24-2016, 04:12 AM

Iv trolled the net for suggestions but have not found anything that works.

Code:

System:    Host: greg-W76OC Kernel: 3.19.0-32-generic x86_64 (64 bit gcc: 4.8.2)
           Desktop: KDE Plasma 4.14.2 (Qt 4.8.6) Distro: Linux Mint 17.3 Rosa
Machine:   System: CLEVO product: W76OC
           Mobo: CLEVO model: W760C Bios: Phoenix v: CALPELLACRB.86C.0000.X.0000000000 date: 03/02/2010
CPU:       Dual core Intel Pentium P6000 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 ssse3) bmips: 7447
           clock speeds: max: 1866 MHz 1: 1866 MHz 2: 1599 MHz
Graphics:  Card: Intel Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: X.Org 1.17.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.0hz
           GLX Renderer: Mesa DRI Intel Ironlake Mobile GLX Version: 2.1 Mesa 10.5.9 Direct Rendering: Yes
Audio:     Card Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k3.19.0-32-generic
Network:   Card-1: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi v: in-tree: bus-ID: 05:00.0
           IF: wlan0 state: up mac: <filter>
           Card-2: JMicron JMC250 PCI Express Gigabit Ethernet Controller
           driver: jme v: 1.0.8 ports: 3400 3000 bus-ID: 06:00.5
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 160.0GB (15.3% used) ID-1: /dev/sda model: Hitachi_HTS54501 size: 160.0GB
Partition: ID-1: / size: 66G used: 20G (31%) fs: ext4 dev: /dev/sda3
           ID-2: swap-1 size: 4.08GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 62.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 179 Uptime: 11 min Memory: 891.0/3751.6MB Init: Upstart runlevel: 2 Gcc sys: 4.8.4
           Client: Shell (bash 4.3.111) inxi: 2.2.28

Code:

GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'
GRUB_CMDLINE_LINUX=""

Any suggestions pls.

hydrurga · 02-25-2016, 01:12 PM

At what point does it "hang"?

I have the same problem, intermittently, with the long pause being at BIOS level, probably during hardware analysis. Setting the BIOS to fast boot may cure the problem.

JackDinn · 02-25-2016, 01:17 PM

but sounds like you are talking about bootup im talking shutdown however it hangs at the KDE logo that shows just before its supposed to shutdown/reboot.

hydrurga · 02-25-2016, 01:40 PM

Quote:

Originally Posted by JackDinn

but sounds like you are talking about bootup im talking shutdown however it hangs at the KDE logo that shows just before its supposed to shutdown/reboot.

Ah, I see. :-)

It sounds suspiciously as if the shutdown process is waiting for an incalcitrant service to terminate.

Have you tried stopping various services before shutdown to see if you can narrow it down to which service is causing the problem?

JackDinn · 02-25-2016, 02:25 PM

no not really but if i knew where a shutdown log was kept it would be easier ?

hydrurga · 02-25-2016, 05:33 PM

Quote:

Originally Posted by JackDinn

no not really but if i knew where a shutdown log was kept it would be easier ?

It certainly would, but I'm not knowledgeable enough on these things.

I do see, however, with a quick trawl of the web:

Quote:

Log files can be found in /var/log/upstart/<service>.log. You can increase log priority from the default message to debug to get more details.

JackDinn · 02-26-2016, 04:54 AM

I have got 85 /var/log/upstart/<service>.log.[1,2,3,4,5].gz files in that folder not sure which one to look at or what to open it with as none of the archive apps (rar, ark, 7-zip) seem to be able to open them.

hydrurga · 02-26-2016, 07:18 AM

Quote:

Originally Posted by JackDinn

I have got 85 /var/log/upstart/<service>.log.[1,2,3,4,5].gz files in that folder not sure which one to look at or what to open it with as none of the archive apps (rar, ark, 7-zip) seem to be able to open them.

Why don't you cat them all and pipe through a grep for "error"?

Or shutdown, encounter the problem, note the time, and only have a look at those files which were changed about that time.

You can ignore the .gz files as they are old logs, just look at the .log files.

You will probably need to have sudo privileges to read them.

JackDinn · 02-26-2016, 07:28 AM

I think i found what the problem is but i dont know what to do about it. I removed the quite splash from grub and found it was hanging at this output:-

nm-dispatcher.action caught signal 15

so searching that i found im not the only one.

https://bugs.launchpad.net/ubuntu/+s...er/+bug/869635

Iv tried the suggestions (except un-installing the network manager as im sure im using it).

I suppose this is another bug to stick on my list of the myriad of others , like iv still got screen tearing (spent 3 months trying to fix that) , The network often wont show my workgroups (spent ages on that, still not fixed). Could not mount my NAS (took months but in the end i did find a fix for that one).

Im desperate to get all my comps off windows but after a year on linux all iv got if a bundle of problems on each and every computer

hydrurga · 02-26-2016, 07:45 AM

Have you seen the answer here?

http://askubuntu.com/questions/55897...hutdown-reboot

JackDinn · 02-26-2016, 08:59 AM

well now im buggered , i tried this suggestion from your link

Quote:

I changed this line in file /etc/default/grub to look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash init=/lib/systemd/systemd"

After that, I ran sudo update-grub in a Terminal

now it wont boot at all and i cant figure how to put it back how it was again (god dam in hell,,,grr) , iv booted into the recovery root console but even though im root it wont let me write to /etc/default/grub.

I did manage to edit /etc/default/grub through a live disk but i cant figure how to update its grub , i tried in the recovery console but it wont work.

suppose iv got to spend the day searching how to fix the grub now, always stepping backwards.

hydrurga · 02-26-2016, 09:36 AM

I've found Boot Repair Disk to be useful in the past for recovering borked GRUBs. Burn it onto CD/DVD/USB stick and boot off it.

https://sourceforge.net/projects/boot-repair-cd/

Mint 17.3 uses upstart as its init program, so getting it to use systemd wasn't the right choice.

JackDinn · 02-26-2016, 09:48 AM

Ok im back , i went into the /boot/grub/grub.cfg file from a live disk and edited it manually. I was lucky this time cos i have no clue what im doing ^^

I have also found if i dismount all my NAS devices before shutdown it shuts down fine but i cant be doing that every time i want to shutdown (there are a few).

there was that suggestion to reduce the 300 sec timer but i think i shall leave it for now that was too close, i nearly lost the last week of work installing and setting up this desktop.

A lot of things im just going to have to put up with i suppose (windows is looking more and more appealing with every "thing i have to put up with")

hydrurga · 02-26-2016, 10:43 AM

Ok, no problem. You *have* to be taking daily backups if the system is in flux like it is with yours at the moment.

I backup my root partition to an external HDD using Macrium Reflect on a live boot USB stick created using Yumi (on which I've also put other ISOs such as Boot Repair Disk). You can also backup your home partition in the same way. It takes me 5 minutes to back up my root partition, and 5 minutes to restore the partition if things go awry.

Do it.

It means that you won't need to pussyfoot around.

JackDinn · 02-26-2016, 10:47 AM

yea i do use clonezilla but in this case i have not got to a point of being happy enough to even take an image. When its all working to my liking i prob will but really is no point before that time.