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.

[SOLVED] Cannot unmount /mnt/cache to Stop array

Featured Replies

same issue every time I try to stop my array (or shutdown) on one of my servers.

 

I have notice every couple of days, something on that server causes docker issues on a perfectly working server. to solve my problem, I have to restart and so use the kill command on the faulty server to be able to reboot and have everything ok again.

 

prety anoying

  • 8 months later...

This is still an issue.
For me, some of my docker containers stop working.
When I go to the dashboard, dockers are blank. Go to the docker tab, and it says the docker service isn't running, even though it is enabled and several containers are still running.
Disable and re-enable the service changes nothing and if I try to reboot, it gets stuck "retrying unmount" on an endless cycle, forcing a dirty shut down and 4 day parity check.

This is an old issue that really needs to be addressed.

Mind you, this issue only STARTED for me since updating 7.x. Leads me to believe an old bug got let back into the code.


 

Edited by dojesus

  • 5 months later...

running into same problem. its been more than hr or so now.

version: 6.12.6, can attach diagnostics if needed.

i keep getting:

Logs

Nov 8 09:16:49 Beta root: umount: /mnt/cache: target is busy.

Nov 8 09:16:49 Beta emhttpd: shcmd (30293350): exit status: 32

Nov 8 09:16:49 Beta emhttpd: Retry unmounting disk share(s)...

i checked lsof and losetup and nothing shows up. so i just went ahead and tried to un-mount it directly using umount -l /dev/loop2 and now i see this in my logs.

Logs again

Nov 8 10:19:56 Beta kernel: sd 5:0:0:0: [sdf] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s

Nov 8 10:19:56 Beta kernel: sd 5:0:0:0: [sdf] tag#10 CDB: opcode=0x28 28 00 00 72 fd a0 00 00 20 00

Nov 8 10:19:56 Beta kernel: I/O error, dev sdf, sector 7536032 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2

Nov 8 10:19:56 Beta kernel: BTRFS error (device sdf1: state EA): bdev /dev/sdf1 errs: wr 99, rd 160091136, flush 0, corrupt 0, gen 0

any suggestions ?

  • Community Expert
15 hours ago, maddog said:

any suggestions ?

See my reply to your other post about the same thing. Also, you have issues with the sdf device, which I assume is from a pool, if you need help with that, please start a new thread and post the diagnostics.

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.