F5F Stay Refreshed Software Operating Systems Unable to establish a network drive for persistence.

Unable to establish a network drive for persistence.

Unable to establish a network drive for persistence.

Pages (2): Previous 1 2
1
11_JOEL_11
Member
247
11-10-2025, 09:15 PM
#11
It seems the network method isn't remembering well. Checking kernel settings or boot options might help. It works in fstab, so it should auto-activate. At least NFS has that behavior.
1
11_JOEL_11
11-10-2025, 09:15 PM #11

It seems the network method isn't remembering well. Checking kernel settings or boot options might help. It works in fstab, so it should auto-activate. At least NFS has that behavior.

B
Back2Blaze
Member
204
11-19-2025, 10:04 PM
#12
Since it's user-managed, it won't mount automatically until you handle it locally. It should no longer appear in your mount list once you interact with it. It must be present at the path you defined in fstab. The folder needs to exist before mounting can occur. https://wiki.archlinux.org/title/samba#As_mount_entry Using the "_netdev" setting will prevent mounting until the network is up.
B
Back2Blaze
11-19-2025, 10:04 PM #12

Since it's user-managed, it won't mount automatically until you handle it locally. It should no longer appear in your mount list once you interact with it. It must be present at the path you defined in fstab. The folder needs to exist before mounting can occur. https://wiki.archlinux.org/title/samba#As_mount_entry Using the "_netdev" setting will prevent mounting until the network is up.

C
CaptainMeeha
Member
213
11-20-2025, 03:19 AM
#13
Hello! Glad to help. I appreciate your support.
C
CaptainMeeha
11-20-2025, 03:19 AM #13

Hello! Glad to help. I appreciate your support.

I
ItsFubsii
Member
50
11-26-2025, 09:57 AM
#14
It wasn’t found in the designated folder. The device just vanishes. Can you locate a recent guide that explains how to install it correctly?
I
ItsFubsii
11-26-2025, 09:57 AM #14

It wasn’t found in the designated folder. The device just vanishes. Can you locate a recent guide that explains how to install it correctly?

E
Endiath
Junior Member
8
11-26-2025, 11:39 AM
#15
I initially missed this detail, but I did locate the drive in fstab. It was created by the system automatically. To ensure automatic wake-up, you’ll need to adjust the settings so it activates when powered on, even with the Standby option disabled. When the computer starts, the drive should initialize and become active.
E
Endiath
11-26-2025, 11:39 AM #15

I initially missed this detail, but I did locate the drive in fstab. It was created by the system automatically. To ensure automatic wake-up, you’ll need to adjust the settings so it activates when powered on, even with the Standby option disabled. When the computer starts, the drive should initialize and become active.

F
FistMeAway
Member
225
11-26-2025, 01:06 PM
#16
The issue appeared to resolve on its own. I adjusted the last digit of the fstab entry and set it to 2, unaware the path had changed. Both qbittorrent and plex were missing files again. I reset the last digit to 0 and restarted the server. Then the path shifted, I reconfigured the programs, and now the drive initializes correctly from the beginning. I’m unsure what caused this, but the folder wasn’t mounted before today. A system update a few days prior and a power outage recently might have triggered changes in the files. It’s unclear how these events affected the system, but it seems resolved for now.
F
FistMeAway
11-26-2025, 01:06 PM #16

The issue appeared to resolve on its own. I adjusted the last digit of the fstab entry and set it to 2, unaware the path had changed. Both qbittorrent and plex were missing files again. I reset the last digit to 0 and restarted the server. Then the path shifted, I reconfigured the programs, and now the drive initializes correctly from the beginning. I’m unsure what caused this, but the folder wasn’t mounted before today. A system update a few days prior and a power outage recently might have triggered changes in the files. It’s unclear how these events affected the system, but it seems resolved for now.

M
Mrgreenbean921
Junior Member
29
11-26-2025, 01:58 PM
#17
The sixth entry in the fstab file specifies a command to scan filesystems for data. Setting it to 0 tells the system to act as if it were a root filesystem, which likely triggered an issue with NTFS and led the drive to be unmounted to prevent possible harm. Ideally, the root filesystem should point to /, the boot files should be on 1, and all other entries should be at least 2. This behavior is clearly outlined in the fstab manual page.
M
Mrgreenbean921
11-26-2025, 01:58 PM #17

The sixth entry in the fstab file specifies a command to scan filesystems for data. Setting it to 0 tells the system to act as if it were a root filesystem, which likely triggered an issue with NTFS and led the drive to be unmounted to prevent possible harm. Ideally, the root filesystem should point to /, the boot files should be on 1, and all other entries should be at least 2. This behavior is clearly outlined in the fstab manual page.

Pages (2): Previous 1 2