I used the S00.sh script to change some nfs setting but the S00.sh script doesn't seem to run anymore.

 

Is this true or is there a workaround. I have S00.sh placed in a folder in the powerdown folder on my USB key. Must it be placed somewhere else now.

You need the powerdown plugin installed for that to work.

 

http://lime-technology.com/forum/index.php?topic=31735.0

You need the powerdown plugin installed for that to work.

 

http://lime-technology.com/forum/index.php?topic=31735.0

 

I have.

 

 

upto the update to 6.1.7

 

i saw these lines in the syslog:

 

Nov 29 12:44:42 Tower1 rc.unRAID[28463][28468]: Processing /etc/rc.d/rc.unRAID.d/ start scripts.

Nov 29 12:44:42 Tower1 rc.unRAID[28463][28472]: Running: "/etc/rc.d/rc.unRAID.d/S00.sh"

 

but no longer after updating to 6.1.7 and rebooting.

 

S00.sh is in config/plugins/powerdown/rc.unRAID.d and contains:

 

if [ -f /proc/fs/nfsd/max_block_size ]

then

/etc/rc.d/rc.nfsd stop

echo 4096 > /proc/fs/nfsd/max_block_size

/etc/rc.d/rc.nfsd start

fi

 

 

 

 

 

 

Post your diagnostics.

Post your diagnostics.

 

 

Here it is.

 

tower1-diagnostics-20160214-1235.zip

I have found the problem and will issue an update to the powerdown plugin.

I have found the problem and will issue an update to the powerdown plugin.

 

So nothing wrong on my server?

 

Like to know what the issue is and when we can expect the update.

 

 

It was a problem in the powerdown plugin.  Fix has been released.

It was a problem in the powerdown plugin.  Fix has been released.

 

Was this introduced in 2.18 or is it handled differently in unraid 6.1.7?

Seem to be working again:

 

Feb 14 14:23:24 Tower1 rc.unRAID[17534][17540]: Processing /etc/rc.d/rc.unRAID.d/ start scripts.

Feb 14 14:23:24 Tower1 rc.unRAID[17534][17548]: Running: "/etc/rc.d/rc.unRAID.d/S00.sh"

Feb 14 14:23:24 Tower1 rpc.mountd[15802]: Caught signal 15, un-registering and exiting.

 

Thanks a lot!

 

There have been some changes in the way the plugin is installed (unraid installplg) and the order of when the package was installed caused the /usr/local/emhttp/plugins/powerdown/event to be created by the package and then removed when the plugin was installed.  I updated the version to 2.19 so the package would update and fix the missing directory and a reboot would not be required.

 

EDIT: I stand corrected.  It looks like this was a problem I created somewhere along the way.