View Full Version : SLES 12 Sp3, filestęstems dont mount after reboot?

01-Feb-2018, 10:56
Have a SLES 12 SP3 on Power that have problem mounting filesystems after reboot.
Its randomly which disks dont mount.

request_module: runaway loop modprobe fs-xfs
request_module: runaway loop modprobe fs-xfs
[FAILED] Failed to mount /db2acc04_zdb2lu12_1B.
See 'systemctl status db2acc04_zdb2lu12_1B.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
[FAILED] Failed to mount /db2acc04_zdb2lu12_tsmfailover_1.
See 'systemctl status db2acc04_zdb2lu12_tsmfailover_1.mount' for details.

They can be mounted manually from prompt.

Any parameters or timeout you can set as parameters?
Number of mountpoints ?

Regards Gert

Automatic Reply
07-Feb-2018, 06:30

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- Open a service request: https://www.suse.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot..

Good luck!

Your SUSE Forums Team

09-Feb-2018, 14:32
Hi Gert,

are those mounts depending on some network connection (NFS, iSCSI device) or truly local devices? And are you mounting by /etc/fstab (plus systemd generator for the according *.mount units), then please give us a glimpse of the according entry. If those mount units where created explicitly, what's in there? If that mount point is depending on network, please add "_netdev" to the mount options.

Have you followed the logged recommendation to check the journal entries? ("systemctl status db2acc04_zdb2lu12_1B.mount")

A few more details might help...