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.

NFS shares disappear

Featured Replies

13 minutes ago, badmark said:

I'm sorry, I'm all over the place, what questions have I not yet answered?

 

  • Replies 67
  • Views 4.9k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • There is a config variable in v7.0.0-rc.2 which can be used to set the max number of open file descriptors for the 'shfs' processes.  At time of this post, there is no webGUI control for setting this.

  • samsausages
    samsausages

    @limetech I do have a syslog server setup, but I don't have a good log aggregator setup, so digging through them is a bit of a pain right now.  I did find the logs from last time I crashed, before I p

  • I am having a similar issue. Googling the dmesg entries brought me here, as my syslog had similar messages. This all started when I upgraded from 6.12.8 to 6.12.14. After upgrading, I could not mount

Posted Images

On 12/26/2024 at 9:29 AM, badmark said:

Nope NFS still dying when rebuilding array on 6.12.9!

Which version does not have NFS issues?

I was running 6.12.10 with NFS mounts working fine in Wondows 10 for me, just upgraded to .14 and all the mounts broke, I'm going back to .10. 

 

Unless anyone has anything I can try to get my mounts back?

 

More info here: 

 

Edited by shdwkeeper

9 hours ago, shdwkeeper said:

I was running 6.12.10 with NFS mounts working fine in Wondows 10 for me, just upgraded to .14 and all the mounts broke, I'm going back to .10. 

 

Unless anyone has anything I can try to get my mounts back?

 

More info here: 

 

Your best bet is to upgrade to 7.0.0-rc2 as the NFS issue with NFS stopping properly has been fixed.

  • 4 weeks later...
  • Author

SO I was finally able to finish, then the 7.0.0 update flashed, so I figured it was a safe bet, updated rebooted and the drive now has to be rebuilt again, like it never acknowledge when I first removed the bad drive, as it showed up again! Now on 7.0.0 can't get past 15% rebuilding before NFS dies on me, trying to restart the service via CLI just hangs, can't even kill the process. 

Not sure what to do now...

4 hours ago, badmark said:

SO I was finally able to finish, then the 7.0.0 update flashed, so I figured it was a safe bet, updated rebooted and the drive now has to be rebuilt again, like it never acknowledge when I first removed the bad drive, as it showed up again! Now on 7.0.0 can't get past 15% rebuilding before NFS dies on me, trying to restart the service via CLI just hangs, can't even kill the process. 

Not sure what to do now...

There are two new settings in 7.0.0 that should fix this for you:

  • Go to Settings->Global Settings and set the "Number of fuse File Descriptors:" to 100,000.
  • Go to Settings->NFS and set the "Number of Threads:" to 32.

Feel free to tweak these even more if ncessary.

  • 3 weeks later...
  • Author

I finally am starting to make progress, I added the following script to cron.daily and just restart the nfs server every 24 hours which has thus far been before it dies, because once it does that nothing will allow me to stop and restart it. I'm currently 21% in with 11 days left.
 

#!/bin/sh
/usr/local/etc/rc.d/rc.rpc stop
/usr/local/etc/rc.d/rc.nfsd stop
killall nfsd
sleep 30s
/usr/local/etc/rc.d/rc.rpc start
/usr/local/etc/rc.d/rc.nfsd start
exportfs


 

  • Author

I finally am starting to make progress, I added the following script to cron.daily and just restart the nfs server every 24 hours which has thus far been before it dies, because once it does that nothing will allow me to stop and restart it. I'm currently 21% in with 11 days left.
 

#!/bin/sh
/usr/local/etc/rc.d/rc.rpc stop
/usr/local/etc/rc.d/rc.nfsd stop
killall nfsd
sleep 30s
/usr/local/etc/rc.d/rc.rpc start
/usr/local/etc/rc.d/rc.nfsd start
exportfs


Regardless of what I do, the rebuild never finishes before NFS just completely dies, I don't know what else to do!

I guess I'll lose all of my data thanks to Unraid...

Why has NFS always worked for me except for here?

  • Community Expert
20 minutes ago, badmark said:

I'm currently 21% in with 11 days left.

Is this still the disk rebuild? If yes, why not finish rebuilding the disk before starting to transfer the data?

  • Author

I need the data live while I'm doing this.

Is there anyway for me to restart the rebuild process after a reboot, a pause?

  • Community Expert
8 hours ago, badmark said:

I need the data live while I'm doing this.

I don't follow, first let the rebuild finish, don't transfer any data at the same time, since it will slow it down by a lot, you can still use the server for reads or small writes, but any other heavy i/o should also be avoided.

  • Author

I've disconnected the shares, this is what time I looking to rebuild? Now there is no I/O but the rebuild, and it's going to take two months?!?!

How is this in anyway acceptable?

image.png.78b3554dd6ae3026ec677f15dab31d9f.png

  • Community Expert
1 minute ago, badmark said:

I've disconnected the shares, this is what time I looking to rebuild? Now there is no I/O but the rebuild, and it's going to take two months?!?!

How is this in anyway acceptable?

image.png.78b3554dd6ae3026ec677f15dab31d9f.png

There is obviously something going on to slow down the rebuild.    You should post diagnostics created while you are experiencing this slow rebuild.

  • Community Expert

It looks like disk6 has significant issues:

5 Reallocated_Sector_Ct   PO--CK   095   095   010    -    21416

and there are continual read errors on that drive so I would not expect the rebuild to be successful.

  • Author

I know, it did not three months ago when I began this process, but having only one parity drive I have no options here!

So what, I'm screwed and my data is lost? I was convinced by others that Unraid was reliable and I could depend on it, but apparently this is not the case.

  • Community Expert

Single parity can protect again one bad disk, not two, for that, you would need to have dual parity, run an extended SMART test on disk6.

 

Do you still have old disk7, or is it completely dead?

  • Author

Old Disk 7 is dead. I planned on adding parity, but did not expect rebuild to take months...

 

  • Community Expert
10 hours ago, badmark said:

but did not expect rebuild to take months...

The time it takes to add parity will depend mostly on the disks size and other hardware, but if all is working well and there aren't any controllers bottleneck, it should take around 2 to 3 hours per TB, if it's taking more than a couple of days even for large disks, there's a typically an issue.

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.