-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not persistent across reboots #2
Comments
My workaround for now.
Verified working; otherwise the NAS won't write to nvme sequential IO (7GB linux dvd iso) |
Are you using DSM 7.2.1 Update 4? |
No. DSM 7.2.1-69057 Update 3 (Release notes) on DS1522+ |
I am seeing the same issue and I am running DSM 7.2.1-69057 Update 3 on DS1823xs+ After running the script and setting to
But if I run:
And then run the script immediately after (no reboot) I see it correctly set to 0:
But then if I reboot it goes back to
I've worked around this by using a scheduled boot task to run:
|
My Internet was down for 4 hours today so I had time to work on this script. The version I'm working on:
I'm currently working on making it possible to schedule the script to run at boot with an option to specify the caches you want set to sequential I/O. |
v2.0.3 - Added --volumes option to make it possible to schedule script to run at boot-up. - You can specify multiple comma separated volumes. - Added --kb option to replace setting kb via first parameter. - Bug fix for "Not persistent across reboots" issue #2 - Bug fix for when no caches are found. - You need to schedule the script to run at boot-up. - Bug fix for when multiple caches are found.
New version of the script here: https://github.com/007revad/Synology_enable_sequential_IO/releases/tag/v2.0.3 It needs to be scheduled to run as root at boot, with the --volumes=volume_n option. See readme: https://github.com/007revad/Synology_enable_sequential_IO |
Thanks for making this script available. I have followed the setup instructions and upon reboot (regardless of sysctl.conf setting for 0 instead of 1024 the DSM seems to be resetting it to defaults).
Here is some basic debugging after a reboot, note I installed using the script run as root (sudo -i) before rebooting.
The text was updated successfully, but these errors were encountered: