Thanks for that snap.

I read his guide from January of this year but I kept getting an error when installing openrc (which probably means i did something wrong).

Solved!

Im not sure wtf was going on I just figured out how to get around it.

It appears to have been a systemd issue so rather than fight it anymore I just did away with systemd and went back to sysvinit. Please someone tell me why I will regret this. I dont see any downside but I could be wrong.

Heres what I did and it seems to have fixed all my issues

sudo apt-get install sysvinit-core sysvinit sysvinit-utils

Reboot

Then remove systemd
apt-get remove --purge --auto-remove systemd


And stop systemd from being installed later on
sudo su
echo -e 'Package: systemd\nPin: origin ""\nPin-Priority: -1' > /etc/apt/preferences.d/systemd

So nobody else has had this issue at all? This has been going on for me on two different machines and starts on a fresh install

I have now installed yet again and when updating held back initramfs-tools and linux-image-4.6.0-1-amd64

Finally after all the updates were installed I was able to install linux-image-4.7.0-1-amd64 (I thought it might be kernel related)

removing swap fixes one error but /home still errors and systemd seems to be unable to mount it properly

Im not sure what else to try at this point.

^ Very cool! I havent fished Frenchman in a long time. Do you still live in that area?

PackRat Im headed up to Mammoth, CA for some trout fishing next Friday night until Wednesday

I fish quite a bit. Here are some recent pics

And this is after running dist-upgrade and holding back linux-image-4.6.0-1-amd64


luke@montech1:~$ sudo journalctl -b -p 3
[sudo] password for luke:
Sep 04 17:18:38 montech1 pidof[1089]: can't get program name from /proc/1056/stat
Sep 04 17:20:08 montech1 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-18731e08\x2d3798\x2d4358\x2da82e\x2d09eda6a703f5.device.
Sep 04 17:20:08 montech1 root[1346]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Sep 04 17:20:13 montech1 systemd[1141]: emergency.service: Failed at step EXEC spawning /bin/plymouth: No such file or directory
Sep 04 17:20:16 montech1 lvmetad[1076]: Failed to accept connection.
Sep 04 17:20:17 montech1 ntpd[1486]: error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
Sep 04 17:20:17 montech1 root[1834]: /etc/dhcp/dhclient-enter-hooks.d/avahi-autoipd returned non-zero exit status 1
Sep 04 17:20:17 montech1 ntpdate[1890]: no servers can be used, exiting






luke@montech1:~$ systemd-analyze blame
    1min 30.628s dev-sda1.device
    1min 30.265s quota.service
           539ms keyboard-setup.service
           413ms networking.service
           346ms wicd.service
           313ms exim4.service
           214ms hddtemp.service
           202ms ntp.service
           137ms irqbalance.service
           131ms systemd-logind.service
           126ms lm-sensors.service
           113ms nfs-common.service
            89ms lvm2-monitor.service
            83ms lightdm.service
            77ms systemd-user-sessions.service
            77ms rpcbind.service
            75ms rsyslog.service
            60ms rc-local.service
            58ms avahi-daemon.service
            53ms systemd-udev-trigger.service
            53ms alsa-restore.service
            51ms systemd-tmpfiles-setup-dev.service
            43ms systemd-udevd.service



Heres my boot log


luke@montech1:~$ sudo journalctl -b -p 3
-- Logs begin at Sun 2016-09-04 16:44:26 PDT, end at Sun 2016-09-04 16:53:01 PDT
Sep 04 16:45:56 montech1 systemd[1]: Timed out waiting for device dev-disk-by\x2
Sep 04 16:45:56 montech1 root[1849]: /etc/dhcp/dhclient-enter-hooks.d/avahi-auto
Sep 04 16:45:57 montech1 systemd[1122]: emergency.service: Failed at step EXEC s
Sep 04 16:46:03 montech1 root[2431]: /etc/dhcp/dhclient-enter-hooks.d/avahi-auto
Sep 04 16:46:03 montech1 ntpdate[2490]: no servers can be used, exiting




This is a fresh install with no swap




luke@montech1:~$ sudo blkid
/dev/sda1: UUID="693aeeee-795f-4a4d-99c2-d82eb1e91e99" TYPE="ext4" PARTUUID="ce66e1ad-01"
/dev/sda3: UUID="18731e08-3798-4358-a82e-09eda6a703f5" TYPE="ext4" PARTUUID="ce66e1ad-03"



Gonna try and older version and see how bad it breaks things.

Might just have to net install like PackRat said.

Quote from: hakerdefo on September 04, 2016, 05:52:29 PM
Hi there lwfitz,
Make a backup of /etc/fstab and remove the following line from it,

Code Select Expand


UUID=e19086b3-142a-4206-88c1-638353a36cbf   none   swap   sw   0   0

Save the file. Reboot & hope for the best
Cheers!!!

Quote from: PackRatTwo items-

First, are you running an NFS or samba server, I know that it can take up to two minutes to shut down if NFS is running, never it stall on startup though.

Second, try a reinstall without a swap file. If you need/want one, pre-partition the disk but leave the partition that will be the swap unused. After boot up use swapon to mount it and leave it mounted when you shut down. If it all works, add the swap partition to fsfab.
,
I've had install issues lately, especially on my older desktop. Same issues you're having. It appears to be related to creating the swap during install. Adding the swap manually post install seems to work, but I occasionally get an error about unmounting the swap partition on shutdown. Leads me to believe this is a systemd issue related to swap file.

I thought the same thing(s) so I did away with the swap partition and removed it from /etc/fstab but that still left the same issue /home partition.

Ive reinstalled with  and without swap and it doesnt seem to make any difference.

I am pretty sure this is kernel related starting in 4.6.0-1 but I dont have any clue how to fix it. MAybe just have to deal with it until things get fixed.


BTW, PackRat I hadnt thought of Samba or NFS. Being that this is a stock install I would think that others wouldve seen a similar issue if it was Samba.

Quote from: jedi on September 04, 2016, 07:12:14 AM
only one really, /etc/fstab.  check to see if it created a swap partition somehow and if so comment it out and reboot.

Hi Jedi  How are you buddy?

Quote from: hakerdefoRemove any duplicate entry and/or swap related entry from /etc/fstab and you should be good to go.
Cheers!!!

Yep, Ive checked this numerous times. None of this makes any sense.


/etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc   /proc   proc   defaults   0   0
# /dev/sda1
UUID=27ef8073-2c1b-4726-83ba-bb5ec70236fe   /   ext4   relatime,errors=remount-ro   0   0
# /dev/sda3
UUID=18731e08-3798-4358-a82e-09eda6a703f5   /home   ext4   defaults   0   0
# /dev/sda2
UUID=e19086b3-142a-4206-88c1-638353a36cbf   none   swap   sw   0   0

QuoteAFAIK drivers are somewhat troublesome lately... once again.

I had everything but "splash" so I added that, updated grub and no luck unfortunately.


I guess I couldve given you guys a bit more info. Im on a temporary desktop as I have sold my MSI laptop.

This PC is a Dell Inspiron desktop with an Intel i5, 8gb ddr3, nVidia geforce 610 and 60gb ssd.

So, for maybe the last 4-5 months (I think) I have had an issue where every time I reboot I have to wait 1:30 with a warning that a start job is running for ............ (enter uuid #). The uuid numbers are anything other than my root partition. Including home.

Thinking it might be a hard drive issue I tried a reinstall from the latest ISO and had the same issue. Then I ran a dist-upgrade and all hell broke loose. I got an error regarding initramfs-tools and linux-image-4.6.0-1-amd64.

Finally I got those packages repaired and installed properly. I ran apt-get update & apt-get dist-upgrade and everything came back clean. No errors.

When I rebooted I got to the normal grub screen, hit enter, and was greeted with a lovely flashing cursor. If I boot normally the flashing cursor lasts about 2 minutes, then it goes past and finally hangs without booting up all the way.
If I boot into recovery mode I get the flashing cursor but after two minutes it will go past and get to the emergency mode warning and I can hit ctrl/D and bypass. Once Im booted and logged in Im fine but it takes 2-5 minutes to boot and its annoying.

Any ideas?


SOLUTION

This worked for me

Been a while, Ive just used the default VSIDO desktop for the lat year or so..........

Time for some change and I think Ill start with some thieving from Jedi.

Me too! Im lucky that I have some really good friends that have boats and love to fish as much as I do.

Very nice PackRat!

Heres a few since my last visit

Thanks buddy!

Still working on it