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.

writing into /mnt/user/ gives an i/o error!

Featured Replies

Hi guys, i was replacing one of my drives and power went away. i do have ups, and i believe unraid shutdown properly.

after booting it up, i started data rebuilding again, from the beginning.

then i start to notice my docker containers are failing, especially my download manager.

later i discovered if i mount the path to /mnt/cache/ instead of /mnt/user, everything works fine.

i tried with both my pools and the array, writing into it through /mnt/disk*/ or /mnt/cache/ is totally fine. whereas writing into /mnt/user/anyfolder/ gives an i/o error!

can anyone help please?

Solved by kjames2001

  • Author

sorry, my first time posting here.

kindly note disks 3 and 4 are rebuilding.

  • Community Expert

There appears to be a container constantly restarting; see if you can find out which one by looking at their uptimes, fix that, then reboot and post new diags after array start.

  • Author
34 minutes ago, JorgeB said:

There appears to be a container constantly restarting; see if you can find out which one by looking at their uptimes, fix that, then reboot and post new diags after array start.

Thanks for your help.

there are a few containers constantly restarting, all because they couldnt make writes to /mnt/user/appdata.

Im still rebuilding data on disks 3 and 4. will restart after that is done.

  • Author
  • Solution

figured it out.

turns out my new disk 4 needs to be repaired and expanded to 16tb and re-added to the array.

after that everything is now ok.

here are the commands i used in case anyone encounter the same problem:

mkdir /mnt/disks/1

mount /dev/sdh1 /mnt/disks/1

umount /mnt/disks/1

xfs_repair /dev/sdh1

mount /dev/sdh1 /mnt/disks/1

xfs_growfs /mnt/disks/1

umount /mnt/disks/1

rm -rf /mnt/disks/1

  • Author

now that i think of it, my parity disks could have contained corrupted data, which caused the new disk to remain at 8tb and corrupted the FUSE_based file system.

im re-syncing my parity disks now.

  • Community Expert

You will need to, since with the way you did the filesystem check parity was not updated; next time you can use the GUI.

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.