Thanks Hamish, when I looked at the man pages for Fstab (at least the
one I looked at first), the nofail was not listed, I have now added it
after googling it as an option, hopefully I won't get an issue to test it.
Tim H
On 18/04/2025 20:09, Hamish McIntyre-Bhatty via dorset wrote:
If you use the "nofail" mount option in /etc/fstab, that should stop
it from stopping the boot process.
Best,
Hamish
On 18/04/2025 19:08, Hugh Frater wrote:
I access my on-prem nas (running trunas) using bookmarked ‘servers’ from
the gtk file manager. These then appear in a totally predictable
/var/run/user/1000/.gvfs folder.
I also use a laptop but run it docked at the office where it can
access the
nas, and undocked when not at the office. Zero issues with boot up
hanging.
I’m running Garuda.
Might be something you can look into?
Sent from my iPhone
On Fri, 18 Apr 2025 at 17:34, Tim <t...@windriders.co.uk> wrote:
So this morning, I turned my laptop on and nothing, Keyboard lit up,
screen flashed but nothing appeared on screen and no boot process was
seen on the screen, tried some random key combinations, but nothing
changed, no flashing hard disk light, nothing seen on screen. After a
couple of minutes I pressed the on\off button.
I re-started the laptop and it started to bootup but complained about
the UEFI partition having an error (SDA1). I used Rescatux07 a live
boot USB to resolve that. But when restarting the laptop again I got as
far as looking for the nas. It then failed to boot up as it could not
find the nas (Nas is listed in my FSTAB to mount on bootup).
I have checked Smart control on the disk and did not show any error or
warnings.
Now I have had this issue in the past where the failure to see the Nas
at bootup hangs the bootup process. I had to boot from a live USB and
disable the mount option in the FSTAB to get the Laptop to boot to a
desktop (I am not aware of a way to do it from the emergency
console). I
was to find out later for what ever the reason the laptop could not
connect to the nas (2 Windows PC could). I rebooted the nas and I was
able to see it from my laptop I then re-enabled the FSTAB entry.
To me there were two problems, one being the failure to bootup, then
the
failure to see the Nas which then breaks the bootup
My question is, is there a way to stop the failure to find the nas at
boot up from crashing the bootup process. I have have looked at Fstab
option for mounting NFS, the only thing I can find is the intr option
but reading nfs mount details suggest that INTR is default so should be
working now. The NAS mount under /media and does not carry any files
that are part of the main OS. The nas entry in fstab looks like this
192.168.18.150: volume1/Data /media/nas nfs defaults 0 0
Any thoughts?
Tim H
--
Next meeting: Online, Jitsi, Tuesday, 2025-05-06 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... https://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
--
Next meeting: Online, Jitsi, Tuesday, 2025-05-06 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... https://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
