[SOLVED finally] machine with 2 startup issues [second one solved - NOT]

[lightman47]

I have one machine that has a couple of problems during bootup. It is (as are all machines) an up-to-date CentOS 7 box. I'd appreciate your help in figuring out what's wrong.

1. During boot it presents the message that 'a start job is running for /boot (nn/137)' with an incrementing seconds. This remains fir about 20-25 seconds then proceeds onward. I might note that /boot is NOT out of space.

2. During NetworkManager mounts of NFS shares (with wait-onlne) I get these errors, after which the drives mount most of the time anyway but not always(??). A manual 'mount -a. will cause the mounts to succeed on the few times they actually fail.

boot.log

Code: Select all

[  OK  ] Started Notify NFS peers of a restart.
[  OK  ] Reached target Remote File Systems (Pre).
         Mounting /mnt/wlinux.2tb1...
         Mounting /mnt/wlinux.4tb1...
         Mounting /mnt/wlinux.4tb2...
         Starting Availability of block devices...
[FAILED] Failed to mount /mnt/wlinux.2tb1.
See 'systemctl status mnt-wlinux.2tb1.mount' for details.
[DEPEND] Dependency failed for Remote File Systems.
[FAILED] Failed to mount /mnt/wlinux.4tb1.
See 'systemctl status mnt-wlinux.4tb1.mount' for details.
         Starting Permit User Sessions...
         Starting Crash recovery kernel arming...
         Starting Virtualization daemon...
[  OK  ] Started Availability of block devices.
[FAILED] Failed to mount /mnt/wlinux.4tb2.
See 'systemctl status mnt-wlinux.4tb2.mount' for details.

When I perform the suggested systemctl commands it gives me little more info than the error message did. /var/log/messages shows nothing:

Code: Select all

Dec 21 13:53:39 wcand systemd: Started Notify NFS peers of a restart.
Dec 21 13:53:39 wcand systemd: Started OpenSSH server daemon.
Dec 21 13:53:39 wcand systemd: Reached target Remote File Systems (Pre).
Dec 21 13:53:39 wcand systemd: Starting Remote File Systems (Pre).
Dec 21 13:53:39 wcand systemd: Mounting /mnt/wlinux.4tb2...
Dec 21 13:53:39 wcand systemd: Mounting /mnt/wlinux.4tb1...
Dec 21 13:53:39 wcand systemd: Mounting /mnt/wlinux.2tb1...
Dec 21 13:53:39 wcand systemd: Starting Availability of block devices...
Dec 21 13:53:39 wcand systemd: Started Availability of block devices.
Dec 21 13:53:39 wcand kernel: FS-Cache: Loaded
Dec 21 13:53:39 wcand kernel: FS-Cache: Netfs 'nfs' registered for caching
Dec 21 13:53:39 wcand kernel: Key type dns_resolver registered
Dec 21 13:53:39 wcand fail2ban-client: 2017-12-21 13:53:39,407 fail2ban.server         [1422]: INFO    Starting Fail2ban v0.9.7
Dec 21 13:53:39 wcand fail2ban-client: 2017-12-21 13:53:39,407 fail2ban.server         [1422]: INFO    Starting in daemon mode
Dec 21 13:53:39 wcand kernel: NFS: Registering the id_resolver key type
Dec 21 13:53:39 wcand kernel: Key type id_resolver registered
Dec 21 13:53:39 wcand kernel: Key type id_legacy registered
Dec 21 13:53:39 wcand systemd: Started Dynamic System Tuning Daemon.
Dec 21 13:53:39 wcand systemd: Mounted /mnt/wlinux.2tb1.
Dec 21 13:53:39 wcand systemd: Mounted /mnt/wlinux.4tb1.
Dec 21 13:53:39 wcand systemd: Mounted /mnt/wlinux.4tb2.
Dec 21 13:53:39 wcand systemd: Reached target Remote File Systems.
Dec 21 13:53:39 wcand systemd: Starting Remote File Systems.
Dec 21 13:53:39 wcand systemd: Starting Virtualization daemon...
Dec 21 13:53:39 wcand systemd: Starting Permit User Sessions...

/etc/fstab:

Code: Select all

/dev/mapper/centos-root /                       xfs     defaults        0 0
UUID=c1e18710-0210-4421-950f-e2b03b427dc2 /boot                   xfs     defaults        0 0
/dev/mapper/centos-home /home                   xfs     defaults        0 0
/dev/mapper/centos-swap swap                    swap    defaults        0 0
wlinux:/mnt/4tb1/ /mnt/wlinux.4tb1 nfs defaults 0 0
wlinux:/mnt/4tb2/ /mnt/wlinux.4tb2 nfs defaults 0 0
wlinux:/mnt/2tb1/ /mnt/wlinux.2tb1 nfs defaults 0 0
/dev/sdb1 /mnt/Win ntfs defaults 0 0

I should note that all my other machines mount the same shares with no issue. Also, I ran memtest86 on this machine for about 1.5 hours just for the heck of it - it had gotten almost half way through the second iteration without error.

I currently don't know what other info to provide. If you need more let me know.

Thank you.

[TrevorH]

Post the output from blkid and df -h /boot

[lightman47]

blkid

Code: Select all

/dev/sdb1: LABEL="Win" UUID="986CB44E6CB42940" TYPE="ntfs" 
/dev/sdb2: UUID="a37d13bc-dfef-47e8-b008-4ffba360f4d2" TYPE="ext4" 
/dev/sdb3: UUID="potTa8-rMPm-TA7V-f72h-rCp0-uSQ9-gjsDNa" TYPE="LVM2_member" 
/dev/sda3: LABEL="1tb1" UUID="c1e18710-0210-4421-950f-e2b03b427dc2" TYPE="xfs" 
/dev/sda5: UUID="gBjNJG-f00X-BBuX-HUsd-a9v6-7D5t-taZM35" TYPE="LVM2_member" 
/dev/mapper/centos-root: UUID="3fec186e-829b-4ae7-90cd-6670ea6cf4a7" TYPE="xfs" 
/dev/mapper/centos-swap: UUID="d51f81fe-8f4d-458b-97a1-1d04150f22d4" TYPE="swap" 
/dev/mapper/fedora_wcand-swap: UUID="cf8899d1-70da-4c34-bd82-65a55580fb4a" TYPE="swap" 
/dev/mapper/fedora_wcand-home: UUID="74ea4706-11a6-4c52-83be-751c00a52f47" TYPE="ext4" 
/dev/mapper/fedora_wcand-root: UUID="e98f45fe-bd75-45eb-8072-b00b6579911e" TYPE="ext4" 
/dev/mapper/centos-home: UUID="527f94f1-2bcf-48fd-9bdd-fde9778685fd" TYPE="xfs" 

df -h /boot

Code: Select all

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3       497M  339M  159M  69% /boot

*** problem 2 solution
Found network running simultaneously and disabled/rebooted. No more mount errors. I don't know how network got enabled, but I remember another instance in which I found it running after installation.

Thank you.

[hunter86_bg]

To find the boot issue run

Code: Select all

systemd-analyze plot >/tmp/plot.scv

After that you can open it with a web browser.

[lightman47]

hunter86_bg

It worked and I got a detailed, colored bar graph output that doesn't mean much to my older (self-taught) self. I attempted to copy/paste the contents here into a 'code' box, but the file length was ~3 times the limit.

Lacking that ability, I wonder if there's a way to get the file to you (or anyone who could enlighten me) as I see no obvious ability to 'attach'. Ideas?

Thanks

.

[hunter86_bg]

You can upload it to any of the free image hosting websites and then use the '[ img] [ /img] (remove the spaces in the tags, or just press the 'Img' button) to provide the link here.
Or just tell us which bar contains the largest time.

[lightman47]

"A start job is running for /boot" ---

SOLVED by reinstalling grub2 via the rescue entry in Grub Menu. (grub2-install /dev/sda)

THANK YOU, Devs for including that in the menu so I didn't have to dig through disks ...

[lightman47]

I lied. Two boots later both problems were back. I believe I have hardware things going on as mentioned at the bottom of:
viewtopic.php?f=49&t=65661

Thank you.

[lightman47]

A yum reinstall \*.\* solved these, and a couple other problems. Wish I'd have done it sooner!