{
  "id": 10162039,
  "title": "Using fstab instead of autofs for a samba share",
  "url": "https://urgent.news/2026/09/27/using-fstab-instead-of-autofs-for-a-samba-share",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-27T07:11:12.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jantolentino/using-fstab-instead-of-autofs-for-a-samba-share-18a0"
  },
  "original_language": "en",
  "account": "A few weeks ago, the author set up a Raspberry Pi 4B to serve as a network storage solution for their home. The device was running Fedora Server 38 and was configured to use Samba for file sharing. The primary challenge was mounting a BTRFS, encrypted drive via Samba. The drive was often unmounting automatically due to inactivity and required a passphrase to unlock. To resolve these issues, the author initially tried using autofs and crypttab, which worked well for a few weeks. However, a race condition emerged when the Samba service attempted to access the share before autofs had finished mounting the encrypted drive. The resolution was to use the built-in Fedora feature called fstab, which permanently mounts the drive at boot time, ensuring it is available before Samba starts. The author removed the autofs configuration, created a mount point using mkdirmounted the drive with fstab, updated the Samba configuration to use the new mount point, and rebooted the Raspberry Pi. The result was a stable network storage solution that ensured file security and consistency.",
  "summary": "A few weeks ago, I borrowed a Raspberry Pi 4B from a friend. Since it wasn't going to be used for a while, I decided to set up a network storage for our home network. It seemed like the most practical use for the Pi. The Problemo Everything was working great until today. After a quick look at the service status, here's what I was dealing with: Sep 14 03:06:13 homeserver systemd[1]: Starting…",
  "key_points": [
    "Author used Samba for network storage on Fedora Server 38",
    "Initial autofs and crypttab configuration failed due to race condition",
    "Fstab permanently mounted drive, solved Samba access issue"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}