# Add an option in dietpi-drive\_manager to customize mount options like relatime or strictatime to enable accurate atime tracking

**URL:** https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315
**Category:** Requests
**Created:** [23 April 2025 13:05 UTC](https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315 "2025-04-23T13:05:10Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![rid3r45](https://dietpi.com/forum/user_avatar/dietpi.com/rid3r45/32/7156_2.png) [@rid3r45](https://dietpi.com/forum/u/rid3r45)
#### Post date: [23 April 2025 13:05 UTC](https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315/1 "2025-04-23T13:05:10Z")

</div>

Hello DietPi Team,

First, thank you for your continued efforts in developing and maintaining DietPi. It’s an excellent lightweight distribution that I’ve found incredibly useful.

I would like to request a feature enhancement for the `dietpi-drive_manager` utility. Currently, it appears that custom mount options, such as `relatime` or `strictatime`, cannot be set through the Drive Manager interface. Moreover, manual edits to `/etc/fstab` are often overwritten when using `dietpi-drive_manager`, which makes it challenging to maintain custom configurations.

This limitation affects use cases where accurate file access time (`atime`) tracking is essential. For instance, I have automation scripts that rely on `atime` to identify and manage files that haven’t been accessed in a specified number of days. Without the ability to set `relatime`, these scripts cannot function as intended.

Therefore, I propose the following enhancement:

**Allow Custom Mount Options:** Introduce an option within `dietpi-drive_manager` to set custom mount options, enabling users to specify parameters like `relatime`, `strictatime`, or others as needed.

Implementing this feature would greatly enhance the flexibility and usability of DietPi for users with specialized requirements.

Thank you for considering this request. I appreciate your time and look forward to any updates on this matter.

Best regards

---

<div class="post-metadata">

### Author: ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)
#### Post date: [23 April 2025 19:40 UTC](https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315/2 "2025-04-23T19:40:55Z")

</div>

Since we use `systemd` we can work around this problem. You could create a systemd mount unit, which is not affected by fstab changes.

In this example we mount `/dev/sdb1` to `/mnt/example`.

First create the mount point `mkdir /mnt/example`.  
The mount point for this path needs to be named `mnt-example.mount`, so we create this file:

```auto
sudo nano /etc/systemd/system/mnt-example.mount

```

Add this content (adjust to your needs):

```auto
[Unit]
Description=Mount /mnt/example with options
DefaultDependencies=no
After=local-fs.target

[Mount]
What=/dev/sdb1
Where=/mnt/example
Type=ext4
Options=strictatime

[Install]
WantedBy=multi-user.target

```

Save and close the file and run:

```auto
sudo systemctl daemon-reload
sudo systemctl enable --now mnt-example.mount

```

You can also mount and unmount like you would (re)start and stop a sytemd service:

```auto
sudo systemctl stop mnt-example.mount
sudo systemctl start mnt-example.mount

```

---

<div class="post-metadata">

### Author: ![rid3r45](https://dietpi.com/forum/user_avatar/dietpi.com/rid3r45/32/7156_2.png) [@rid3r45](https://dietpi.com/forum/u/rid3r45)
#### Post date: [24 April 2025 08:09 UTC](https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315/3 "2025-04-24T08:09:38Z")

</div>

This solved my issue indeed, many thanks for the help !

---

<div class="post-metadata">

### Author: ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)
#### Post date: [24 April 2025 17:31 UTC](https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315/4 "2025-04-24T17:31:58Z")

</div>

@MichaIng @StephanStS  
Maybe we (or myself 🙂 ) should write a blog entry or a note in the docs about this possibility?

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [27 April 2025 17:17 UTC](https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315/5 "2025-04-27T17:17:58Z")

</div>

As always for such cases, the question is whether it is more work to write a blog post about how to manually overcome limitations of a DietPi script, or whether it makes more sense/less work to just implement this feature 😅.

---

<div class="post-metadata">

### Author: ![system](https://dietpi.com/forum/uploads/default/original/1X/7e1021de2213860bce185915ce2c1786e56490ec.png) [@system](https://dietpi.com/forum/u/system)
#### Post date: [26 July 2025 17:18 UTC](https://dietpi.com/forum/t/add-an-option-in-dietpi-drive-manager-to-customize-mount-options-like-relatime-or-strictatime-to-enable-accurate-atime-tracking/23315/6 "2025-07-26T17:18:02Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
