This seems to be a systemd problem acording to the information I have found so far. If I have an entry for my external HDD, and it isn’t connected at boot time, the system will just hang. Theoretically, to fix this problem I’d need to just add nofail, and indeed it works. However, I don’t wanna wait 1m30 everytime I boot (that’s the timeout). So another option gets in the mix, nobootwait. But it seems it’s not doing anything, as still I have to wait for 90 secs.
Even if you think so, it might be. After all you have a problem and you ask for help. Giving the maximum of information might lure people in trying to help you. Having to ask for the most basic information is frustrating for many and they may turn away from your problem, endulging in a more promising one.
And when you did take the trouble to browse a bit through the threads in this forum (I hope you did, it is the best way to get feeling with the way people work here), you will have seen that people post about problems using a wide range of openSUSE versions (supported and unsupported), or SLES/SLED versions (and they are on the wrong forums), or on other Linux distributions (they are a bit lost), or even on Wiindows (and they are terribly lost). And they often do not tell so to start with, thus spoiling everybodies time.
Hi, just chiming in.
Would “defaults, noauto” be acceptable for you? It won’t mount at boot whether the drive is connected or not, but at least it won’t have to make you wait.
And to concur with hcvv, providing some basic information from the start would be very helpful.
On 2015-03-13 17:36, yzT wrote:
>
> This seems to be a systemd problem acording to the information I have
> found so far. If I have an entry for my external HDD, and it isn’t
> connected at boot time, the system will just hang. Theoretically, to fix
> this problem I’d need to just add nofail, and indeed it works.
> However, I don’t wanna wait 1m30 everytime I boot (that’s the timeout).
> So another option gets in the mix, nobootwait. But it seems it’s not
> doing anything, as still I have to wait for 90 secs.
>
> /dev/mapper/luks-4aaf4423-07dc-43ee-853d-f45999015f17 /media/DATA
> ext4 defaults,nofail,nobootwait 0 2
>
>
> Any ideas?
>
>
If x-systemd.device-timeout= is specified, it may be used to
configure how long systemd should wait for a device to show up before
giving up on an entry from /etc/fstab. Specify a time in seconds or
explicitly specify a unit as "s", "min", "h", "ms".
Have simular problems with NFS mounts with my laptop when I’m not on my home lan(192.168.0.x). Its stopping up and writes ~“waiting for NFS service” max …5 min 38 sec…
I first did a uppgrade from 13.1 to 13.2 and all was working ok. Then I did a new/clean 13.2 install.There my problem started. The lines in fstab is from setup in YaST2/NFS client, later I have added/tried with “noauto”
“defaults noauto” should be “defaults,noauto”. There shouldn’t be a space. Since it’s an NFS mount, might I suggest to add _netdev, making it a total of “defaults,noauto,_netdev”.
From man mount
_netdev
The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system).
Good luck!
On 2015-03-15 16:26, jonte1 wrote:
>
> oS13.2 64bit, KDE.
>
> Have simular problems with NFS mounts with my laptop when I’m not on my
> home lan(192.168.0.x). Its stopping up and writes ~“waiting for NFS
> service” max …5 min 38 sec…
>
> I first did a uppgrade from 13.1 to 13.2 and all was working ok. Then I
> did a new/clean 13.2 install.There my problem started. The lines in
> fstab is from setup in YaST2/NFS client, later I have added/tried with
> “noauto”
>
>
> Code:
> --------------------
> 192.168.0.1:/home/vol1 /home/jodot/vol1 nfs defaults noauto 0 0
> 192.168.0.1:/home/jodot /home/jodot/vol2 nfs defaults noauto 0 0
> --------------------
>
>
> My workaround is to never attach a networkcable/start Wi-Fi until I see
> the login screen in KDE when away/not connected to my home Lan.
>
> Yes I know, -I’m lazy:shame:. Its always seems to be more interesting
> things to do then fix this.
>
> regards
>
>