Boot Problems "[FAILED] Failed to mount data.mount - /data"

Support and Troubleshooting
1

Hello friends,

I’m having a problem and I can’t solve it. I bought a HDD model: “Western Digital WD Purple HDD, 4TB, 3.5, 5400RPM, Sata III 6GB/s, Cache 256MB, WD43PURZ”, to use on Umbrel 0.56. I managed to install and use it correctly using Ubuntu 22.00. When I updated Umbrel to the latest version “Umbrel 1.1.2”, I can install it but when I tried to restart it, it won’t boot anymore. I’ve researched all possible problems but still haven’t had a concise answer. The errors are as follows:

[FAILED] Failed to mount data.mount - /data.
See ‘systemct] status data.mount’ for details.
[DEPEND] Dependency failed for systend-growfsedata.service - Grow File System on /data.
[DEPEND] Dependency failed for var-log-mount - /var/log -
[DEPEND] Dependency failed for systemd-update-utmp-runlevel.service - Record Runeuel Change in UTMP.

Attached are images.

IMG_0867.HEIC
IMG_0867.HEIC3024×4032 3.02 MB

IMG_0866.HEIC
IMG_0866.HEIC3024×4032 2.73 MB

IMG_0869.HEIC
IMG_0869.HEIC4032×3024 2.88 MB

IMG_0868.HEIC
IMG_0868.HEIC3024×4032 2.57 MB

IMG_0870.HEIC
IMG_0870.HEIC4032×3024 3.34 MB

2

Did you installed Umbrel in the disk or did you added this disk in a machine with Umbrel?

3

Hello, did you manage to solve this issue?

4

“I noticed that data.mount has a limited time to execute. Basically, what I did was to make this time unlimited with the help of ChatGPT.”

copy

To disable the mount timeout for the device /dev/disk/by-partuuid/d1d36e34-2753-4dc7-96eb-3c9b5584e867, you can add the option noauto,x-systemd.mount-timeout=infinity to the corresponding line in the fstab file. Here’s how you can do that:

  1. Open a terminal.

  2. Edit the fstab file with a text editor, such as nano or vim. For example:

    sudo nano /etc/fstab

  3. Find the line that corresponds to the device you want to modify:

    /dev/disk/by-partuuid/d1d36e34-2753-4dc7-96eb-3c9b5584e867   /data          auto       defaults,x-systemd.growfs      0  0

  4. Modify this line to include the option noauto,x-systemd.mount-timeout=infinity:

    /dev/disk/by-partuuid/d1d36e34-2753-4dc7-96eb-3c9b5584e867   /data          auto       defaults,noauto,x-systemd.mount-timeout=infinity      0  0

  5. Save the changes and close the text editor.

  6. Restart the system for the changes to take effect, or you can manually remount the file system to apply the changes, but that can be more complicated.

Now, the device /dev/disk/by-partuuid/d1d36e34-2753-4dc7-96eb-3c9b5584e867 will no longer have a defined mount timeout.

“It would be important for the developers to allow more time for this function because I noticed that it took just 3 extra seconds for the disk to be mounted.”

1 Like
5

I am sure I am missing something obvious. I have exactly the situation displayed in your img_0870 where “Failed…to mount data” and those same failed “Dependencies”. I used the UmbrelOS usb install stick to install onto the harddrive of a x86 beelink mini-pc. Here is my probably dumb question regarding step 1 of your solution “open a terminal”. How? When one presses “enter to continue”, one cannot get to a login prompt and I have searched for the ip of the umbrel node with angry ip scanner and cannot find it so I also cannot ssh in. I am wondering how you opened a terminal to edit the /etc/fstab .

6

I have the same issue and no idea how to open the console to attempt the suggested solution.

Update: I managed to mount the umbrel partition with a live distro and edit the etc/fstab and add the infinite timeout.