Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (â‹®) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Mounting cloud storage with Rclone - No space left on device

Featured Replies

Hi all,

 

Happy almost-new-year! I'm hoping to find a solution to an issue I'm facing with Unraid, I've condensed the info as best as I could below 🙂.

The Premise:

I've had success in mounting my external, cloud storage drive (MEGA) into "/mnt/disks/mega" using rclone. The process was fairly painless, and I'm using user-scripts to achieve this. I'm on the free tier with MEGA and it allows 20GBs of storage, and I'm using (Dockerised) Krusader for file access, hence the mount point needs to be accessible to Docker.

 

# Mounting script (on array-start):
mkdir -p /mnt/disks/mega
rclone mount --vfs-cache-mode writes --allow-other mega: /mnt/disks/mega

# Unmounting script (on array-stop):
fusermount -u /mnt/disks/mega

 

The Problem:

I cannot copy any files >=6GBs to this mount point, I keep getting a "no space left on device" error. Looking at disk-space usage I see the below:

 

Filesystem      Size  Used Avail Use% Mounted on
rootfs          7.7G  2.1G  5.7G  27% /
tmpfs            32M  2.1M   30M   7% /run
/dev/sda1        29G  1.1G   28G   4% /boot
overlay         7.7G  2.1G  5.7G  27% /lib/firmware
overlay         7.7G  2.1G  5.7G  27% /lib/modules
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs           7.8G     0  7.8G   0% /dev/shm
cgroup_root     8.0M     0  8.0M   0% /sys/fs/cgroup
tmpfs           128M  1.1M  127M   1% /var/log
tmpfs           1.0M     0  1.0M   0% /mnt/disks
tmpfs           1.0M     0  1.0M   0% /mnt/remotes
tmpfs           1.0M     0  1.0M   0% /mnt/rootshare
/dev/md1        5.5T  4.3T  1.3T  78% /mnt/disk1
/dev/md2        5.5T  3.8T  1.7T  70% /mnt/disk2
/dev/nvme0n1p1  350G   16G  216G   7% /mnt/cache
shfs             11T  8.0T  3.0T  74% /mnt/user0
shfs             11T  8.0T  3.0T  74% /mnt/user
/dev/loop2       50G   11G   40G  21% /var/lib/docker
tmpfs           1.6G     0  1.6G   0% /run/user/0

 

So far my thoughts are:

 

  1. Is this because "/mnt/disks/mega" is mounted and stored within rootfs?
  2. Is there a way to perhaps move this mount point (similar to how "/dev/loop2" for Docker is configured with 50GBs)?
    Sorry if this is a silly question...

 

Thank you for reading, any help or advice would be appreciated! :)

Edited by StarrLizzard
Forgot to mention Krusader and the need for Docker access to the mount point

  • Author

Bumping to see if anyone can advise/help 😊

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.