[SCRIPT] create-autorun.sh

[OneCD]

first of all thank you for writing this script, and helping out who's in need

Cheers mate!

... and when the boot is completed, if I go to the scripts directory and execute them via './thescript.sh' they'll run just fine ...

Please note: autorun.sh executes scripts before QPKGs. If your scripts need to call QPKG applications that have not yet been re-integrated, they will fail.

If you do need to script installed QPKG applications, please use the RunLast QPKG instead of autorun. It's like autorun, but runs your scripts after all other QPKGs have been re-integrated.

[Haskell]

Thank you so much, I believe this is the point I was missing. cheers mate!

[RichJacot]

I'm a bit new to this, though I was a UNIX/Linux admin many years ago, but will https://git.io/create-autorun.sh work on the TVS-672N? I'm seeing reference to TS-xxx models in the script.

Can we not just use @reboot in the crontab? Pros/Cons?

[OneCD]

... but will https://git.io/create-autorun.sh work on the TVS-672N? I'm seeing reference to TS-xxx models in the script.

You'll need to try it and see.

Can we not just use @reboot in the crontab? Pros/Cons?

@reboot is not supported by QTS cron.

[RichJacot]

Well I guess it's not.

[~] # curl -skL https://git.io/create-autorun.sh | bash
create-autorun.sh (191105)

[ info ] NAS model: TS-X72 (TVS-672N)
[ info ] QTS version: 4.4.2 #20200410
[ info ] default volume: /share/CACHEDEV1_DATA

[ done ] DOM partition found (/dev/sde6)
[ done ] mounted (ext2) DOM partition at [/tmp/create-autorun.SPVDNB]
[ fail ] DOM tag-file was not found!
[ done ] unmounted (ext2) DOM partition

[ fail ] [autorun.sh] creation failed!

[~] #


I found one reference to "DOM tag-file was not found!" (in this thread) but it doesn't look like the guy ever replied back to OneCD's request.

Ideas?

Thanks,
Rich

[OneCD]

I found one reference to "DOM tag-file was not found!" (in this thread) but it doesn't look like the guy ever replied back to OneCD's request.

It's possible that not every model NAS has a copy of [uLinux.conf] stored on the DOM. I don't have access to every model.

I've just uploaded an additional script for you to use that doesn't perform a check for this file. So, your download and execute command will be:

Code: Select all

<link removed>

This new script blindly adds a symlink on the mounted DOM partition that points to your new autorun.sh script processor on your default volume. You might try adding a test script into the scripts directory, enabling autorun in your QTS Control Panel, then rebooting your NAS. Does it work?

[RichJacot]

Now I'm getting the following but also, I can't just go to the URL and view this nocheck script... Trying to view before running I get "No url found for create-autorun-nocheck.sh".

Just trying to run it I get:

[~] # curl -skL <link removed> | bash
bash: line 1: No: command not found
[~] #

[OneCD]

[~] # curl -skL <link removed> | bash
bash: line 1: No: command not found

Bah, I forgot to register a new shortlink with git.io.

Oh well, try it with a direct link instead:

Code: Select all

curl -skL https://raw.githubusercontent.com/OneCDOnly/create-autorun/master/create-autorun-nocheck.sh | bash

[RichJacot]

That worked. Thank you!

Now to test. Hopefully I'll have time after work today.

[RichJacot]

Well I guess it's been toooo many years since I've done much of any scripting...

The autorun appears to be working because the touch I put in my script works but the mount isn't working.

Anyone know what I'm doing wrong? It runs by hand just fine.


[/share/CACHEDEV1_DATA/.system/autorun/scripts] # ll
total 12K
drwxr-xr-x 2 admin administrators 4.0K 2020-05-06 17:25 ./
drwxr-xr-x 3 admin administrators 4.0K 2020-05-06 15:24 ../
-rwxr-xr-x 1 admin administrators 134 2020-05-06 17:18 PlexTranscodeRAMDrive.sh*
-rw-r--r-- 1 admin administrators 0 2020-05-06 17:25 plxran


[/share/CACHEDEV1_DATA/.system/autorun/scripts] # cat PlexTranscodeRAMDrive.sh
#!/bin/sh
/bin/mount -t tmpfs -o size=16G tmpfs /plex.transcoding.tmp
/bin/touch /share/CACHEDEV1_DATA/.system/autorun/scripts/plxran
[/share/CACHEDEV1_DATA/.system/autorun/scripts] #


The /plex.transcoding.tmp exists. I created that when I was toying with it manually.

drwxrwxrwx 2 admin administrators 40 2020-05-06 17:27 plex.transcoding.tmp/

[OneCD]

/bin/mount -t tmpfs -o size=16G tmpfs /plex.transcoding.tmp

Hmm, how much RAM is there in your NAS?

[RichJacot]

32GB - 2 x 16

[OneCD]

Are you creating the [/plex.transcoding.tmp] directory first - before mounting tmpfs to it? It won't be there after a reboot, so you'll need to recreate it after every boot.

Have you checked the stdout and stderr from autorun.sh?

Code: Select all

cat /var/log/autorun.log

[RichJacot]

I checked the autorun.log and it appears to be doing what should...

[/share/CACHEDEV1_DATA/.system/autorun/scripts] # cat /var/log/autorun.log
Wed May 6 17:25:26 CDT 2020 ----- running autorun.sh -----
Wed May 6 17:25:26 CDT 2020 - /share/CACHEDEV1_DATA/.system/autorun/scripts/PlexTranscodeRAMDrive.sh
[/share/CACHEDEV1_DATA/.system/autorun/scripts] #


The /plex.transcoding.tmp exists ahead of time. I created the dir as a mount point to test with several days ago. I show it and it's permissions in the prior post.

[OneCD]

I checked the autorun.log and it appears to be doing what should...

Cool, this means you can perform tests within your script and the output will be captured here.

The /plex.transcoding.tmp exists ahead of time. I created the dir as a mount point to test with several days ago. I show it and it's permissions in the prior post.

And this location (off the root filesystem) remains even after you have rebooted the NAS? That would be a first!

The directory entry you posted doesn't show the full path to your transcoding directory.