Comment # 9 on bug 1077063 from
(In reply to Paulo Alcantara from comment #8)
> 1. Did you run 'journalctl -u *.mount' right after getting the failure
> during bootup? If not, could you please do that?

the following was gathered after a reboot (before mount -a)

-- Logs begin at Wed 2018-06-06 22:51:51 CEST, end at Wed 2018-06-06 22:52:49
CEST. --
Jun 06 22:51:52 linux-nehs systemd[1]: Mounting /sysroot...
Jun 06 22:51:52 linux-nehs systemd[1]: Mounted /sysroot.
Jun 06 22:51:53 Hygiea systemd[1]: opt.mount: Directory /opt to mount over is
not empty, mounting anyway.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /opt...
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /boot/efi...
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /boot/grub2/i386-pc...
Jun 06 22:51:53 Hygiea systemd[1]: usr-local.mount: Directory /usr/local to
mount over is not empty, mounting anyway.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /usr/local...
Jun 06 22:51:53 Hygiea systemd[1]: srv.mount: Directory /srv to mount over is
not empty, mounting anyway.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /srv...
Jun 06 22:51:53 Hygiea systemd[1]: var.mount: Directory /var to mount over is
not empty, mounting anyway.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /var...
Jun 06 22:51:53 Hygiea systemd[1]: root.mount: Directory /root to mount over is
not empty, mounting anyway.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /root...
Jun 06 22:51:53 Hygiea systemd[1]: boot-grub2-x86_64\x2defi.mount: Directory
/boot/grub2/x86_64-efi to mount over is not empty, mounting anyway.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /boot/grub2/x86_64-efi...
Jun 06 22:51:53 Hygiea systemd[1]: tmp.mount: Directory /tmp to mount over is
not empty, mounting anyway.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /tmp...
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /boot/efi.
Jun 06 22:51:53 Hygiea systemd[1]: Mounting /home...
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /home.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /opt.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /usr/local.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /srv.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /boot/grub2/i386-pc.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /var.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /root.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /tmp.
Jun 06 22:51:53 Hygiea systemd[1]: Mounted /boot/grub2/x86_64-efi.
Jun 06 22:52:00 Hygiea systemd[1]: Mounting /home/local/openhab...
Jun 06 22:52:00 Hygiea systemd[1]: Mounting /home/local/net...
Jun 06 22:52:00 Hygiea systemd[1]: Mounting /home/local/media...
Jun 06 22:52:00 Hygiea systemd[1]: Mounted /home/local/net.
Jun 06 22:52:00 Hygiea systemd[1]: Mounted /home/local/media.
Jun 06 22:52:00 Hygiea systemd[1]: Mounted /home/local/openhab.
Jun 06 22:52:02 Hygiea systemd[1]: Mounting FUSE Control File System...
Jun 06 22:52:02 Hygiea systemd[1]: Mounted FUSE Control File System.


> 2. Is /local a symlink to /home/local?

Yes

> 3. Could you please paste output of 'mount | grep cifs' after you perform
> 'mount -a' manually to get everything mounted correctly?

Hygiea:/local/net # mount | grep cifs
//nas/share on /home/local/net type cifs
(rw,relatime,vers=1.0,cache=strict,username=root,domain=,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.250.11,file_mode=0644,dir_mode=0755,nounix,serverino,mapposix,noperm,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)
//nas/media on /home/local/media type cifs
(rw,relatime,vers=1.0,cache=strict,username=root,domain=,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.250.11,file_mode=0644,dir_mode=0755,nounix,serverino,mapposix,noperm,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)
//smart-controller/openHAB-conf on /home/local/openhab type cifs
(rw,relatime,vers=1.0,cache=strict,username=openhabian,domain=,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.250.12,unix,posixpaths,serverino,mapposix,acl,noperm,rsize=1048576,wsize=65536,echo_interval=60,actimeo=1)

Noteworthy I didn't have to perform mount -a this time.

Whatever happened inbetween it is either fixed by something I do not know or
it's not consistently failing anymore.
I'm sure though that directly after installation of 15.0 this happened again.

I can only tell that I will watch and report back if it happens again at some
point.


You are receiving this mail because: