[SF8008] Small issue with fstrim on my internal SSD - It doesn't work

[Joe_90]

Most cron programs will not run scripts with extensions.

I've been running my own fstrim script with a .sh extension in /usr/script for about 10 days now with no issue. On the name collision issue, I suspect that, without the suffix, fstrim will try to execute the command and will fail as the fstrim command requires a target mountpoint.

EDIT - I mean that, unless you specify the full path to the script, the command executable will run and will fail as it requires a target parameter.

 

[Joe_90]

@Orlandox - I ran the new fstrim script from the command line, specifying the location (in my case /usr/script) and got the following log messages in /home/root/logs/messages

Mar 20 15:00:45 vuuno4kse user.notice fstrim: /boot: 1701666816 bytes trimmed
Mar 20 15:00:45 vuuno4kse user.notice fstrim: /: 0 bytes trimmed
Mar 20 15:00:49 vuuno4kse user.notice fstrim: /media/hdd: 781516283904 bytes trimmed

A timestamp is also written to a file /var/lib/fstrim.last

This script checks the timestamp on the next run to ensure at least a week has elapsed.

 

[Orlandox]

@Orlandox - I ran the new fstrim script from the command line, specifying the location (in my case /usr/script) and got the following log messages in /home/root/logs/messages

Mar 20 15:00:45 vuuno4kse user.notice fstrim: /boot: 1701666816 bytes trimmed
Mar 20 15:00:45 vuuno4kse user.notice fstrim: /: 0 bytes trimmed
Mar 20 15:00:49 vuuno4kse user.notice fstrim: /media/hdd: 781516283904 bytes trimmed

A timestamp is also written to a file /var/lib/fstrim.last

This script checks the timestamp on the next run to ensure at least a week has elapsed.

Thank you for the info Joe_90. There the evidence was. So it was run at 15:25. So it works okay.
Thanks to all developers !

 

[Orlandox]

Hello,

what does this mean ?

Mar 21 11:00:01 vuuno4kse authpriv.info crond[3468]: pam_unix(crond:session): session opened for user root(uid=0) by (uid=0)
Mar 21 11:00:01 vuuno4kse cron.info CROND[3469]: (root) CMD (/usr/bin/fstrim)
Mar 21 11:00:11 vuuno4kse user.notice fstrim: /usr/sbin/fstrim-all: fork: Cannot allocate memory
Mar 21 11:00:43 vuuno4kse cron.info CROND[3468]: (root) CMDEND (/usr/bin/fstrim)

 

[Joe_90]

At a guess, I would say that you have insufficient RAM left to run fstrim. Do you have a lot of plugins loaded?
Maybe check your available memory on the Information/Memory menu screen.

 

[Orlandox]

Solved. Box had enough memory. When I added .sh to name (fstrim.sh) it worked. My Ultimo4K had it, but forgot to change the name at Uno4K SE.

Mar 21 16:10:00 vuuno4kse authpriv.info crond[10374]: pam_unix(crond:session): session opened for user root(uid=0) by (uid=0)
Mar 21 16:10:00 vuuno4kse cron.info CROND[10375]: (root) CMD (/usr/bin/fstrim.sh)
Mar 21 16:10:01 vuuno4kse user.notice fstrim: /boot: 1686327296 bytes trimmed
Mar 21 16:10:01 vuuno4kse user.notice fstrim: /: 0 bytes trimmed
Mar 21 16:10:03 vuuno4kse user.notice fstrim: /media/hdd: 396968603648 bytes trimmed
Mar 21 16:10:03 vuuno4kse cron.info CROND[10374]: (root) CMDEND (/usr/bin/fstrim.sh)
Mar 21 16:10:03 vuuno4kse authpriv.info CROND[10374]: pam_unix(crond:session): session closed for user root

 

[Joe_90]

Ok, thanks @Orlandox. I personally did not like the fact that the OpenATV script had the same name fstrim as the executable it was ultimately invoking. But, @Huevos seemed to think that cron would not invoke scripts with an extension (suffix like .sh). However, it works with .sh for both you and me and I think it makes a clearer distinction between the script and the executable. Glad it's now working for you.

 

[smipx]

Let's see if it can be repaired or made to work on something besides a SF8008
Try the attached Joe. Some adjustments to drive recognition have been made.

Hi el bandido and Twol,

I have just upgraded to 6.8.006 on my SF8008 and on this release the package fstrim-cron-vix is now installed at the flash time. When I try to install the IPK for the trim that is useful for the SF8008 there is a clash. It tells me it cannot install fstrim-cron_1.0-r13_all.ipk because of this. I thought, as the (now) built-in fstrim is not useful for the SF8008 I would try to remove it using opkg remove fstrim-cron-vix but this also failed with the error below.

Solver encountered 1 problem(s):
Problem 1/1:
- package openvix-base-6.8-r7.sf8008 requires fstrim-cron-vix, but none of the providers can be installed
- conflicting requests
- problem with installed package openvix-base-6.8-r7.sf8008

Solution 1:
- allow deinstallation of openvix-base-6.8-r7.sf8008


Solution 2:
- do not ask to deinstall fstrim-cron-vix

- do not ask to deinstall fstrim-cron-vix

Thanks guys for looking into this.

Paul

 

[el bandido]

This should solve it. You might want to backup the image completely or be prepared to re-flash the image if needed:
In telnet or Terminal,
opkg remove --force-depends fstrim-cron-vix
opkg install fstrim-cron_1.0-r13_all.ipk

 

[el bandido]

Pretty neat to have inside an image:

 

[smipx]

Im a bit confused. It almost seems like they have incorporated your "special" trim routine for the sf8008??
If that is the case I will hold off doing the .......

opkg remove --force-depends fstrim-cron-vix
opkg install fstrim-cron_1.0-r13_all.ipk

....... until I get some clarification from the admin / developers of OpenVIX as I don't want to make a mess of things and undo any hard work on their side (and make my image non-standard).

I'm confused and my head hurts

 

[smipx]

Pretty neat to have inside an image:
View attachment 68647

View attachment 68648

View attachment 68649

Where are these screens in openvix. I can't find them

 

[twol]

i am sure el bandido will correct if wrong, but I am guessing that is the tnap image where code from OpenATV has been added and extended.

I can look at adding trim command to our storage options.

 

[smipx]

OK Twol. Thanks. Wasn't it conflicting with a VIX module though ( openvix-base-6.8-r7.sf8008 ). this is where im confused. Is it also something to do with the fact that the IPK tries to install fstrim when fstrim is now installed as part of the work to incorporate fstrim into the standard VIX build?

I appreciate that the fstrim is for all boxes but this is pretty confusing for sf8008 users where the standard fstrim is about as useful as a chocolate teapot with its USB to NVME bridge. At the very least the fstrim code for sf8008 should not be included in the image for sf8008 (nor the automatic cron job) as it doesn't work.

Unless I'm totally misunderstanding everyting (which is quite possible).

Paul

 

[twol]

OK Twol. Thanks. Wasn't it conflicting with a VIX module though ( openvix-base-6.8-r7.sf8008 ). this is where im confused. Is it also something to do with the fact that the IPK tries to install fstrim when fstrim is now installed as part of the work to incorporate fstrim into the standard VIX build?

I appreciate that the fstrim is for all boxes but this is pretty confusing for sf8008 users where the standard fstrim is about as useful as a chocolate teapot with its USB to NVME bridge. At the very least the fstrim code for sf8008 should not be included in the image for sf8008 (nor the automatic cron job) as it doesn't work.

Unless I'm totally misunderstanding everyting (which is quite possible).

Paul

so the fstrim included in OpenViX, Openbh and OpenATV covers the basic trim for SSD'S.... even for most sf8008 users who do not have the version with the NVME bridge.
So for most users adding it into the Storage menu would probably be a good idea.
Unfortunately, Octagon as they tend to do, add features differently (and then change them), so for users like yourself, you are left with adding El Bandido's fstrim-all separately - which in the long run is probably safer..
Obviously like el bandido and tnap, I could check for USB-bridged NVMe and call fstrim-all but I would need assurance of its safety in including it as standard.

 

[smipx]

so the fstrim included in OpenViX, Openbh and OpenATV covers the basic trim for SSD'S.... even for most sf8008 users who do not have the version with the NVME bridge.
So for most users adding it into the Storage menu would probably be a good idea.
Unfortunately, Octagon as they tend to do, add features differently (and then change them), so for users like yourself, you are left with adding El Bandido's fstrim-all separately - which in the long run is probably safer..
Obviously like el bandido and tnap, I could check for USB-bridged NVMe and call fstrim-all but I would need assurance of its safety in including it as standard.

Happy to test for you if you let me know and Im sure some others will also be happy to do so. If I do then bear in mind that I have El Bandido's script installed on my SF8008 and it is working well.

 

[el bandido]

Twol Is correct! Let's be clear and understand what we have and do not have.
The screenshots I posted are the Device manager features that were forked from Fairbird's Dreambox build, then I added features. I posted them only as ideas because I like the layout. Maybe someone else will find them useful at some point? Maybe not...

You can build a handful of boxes with more edits and optimizations as compared to building 50 or more like VIX and ATV do. So if you add something like the Device manager in VIX or ATV, then it has to work across the entire build field, OR deleted on the boxes that cannot support it. If you delete something due to incompatibility, then you get the "Where's mine" posts. Take a minute and think about that. A 6 box build verses 50.

Now let's understand what the SF8008 M.2 fstrim Is and isn't.
The fstrim for M.2 was created because none existed for a FTA receiver. Simple as that. However, it has NOT been tested in even 50 receivers yet, plus it was almost 100 percent AI generated, which means, yeah it works, but you do not have the skills or knowledge built into it as compared to someone who has worked with fta receivers for years. This is the most important part. Built by Professional, CLI AI aside, it is still an AI.

Now that everything has been explained, and given these circumstances, should I come here and say: "Here dudes...Put this in your image and all is well"? Absolutely not! Be upfront with what you do and do not have. Over a period of time, it will get used and improved if needed. But right now, today, it is not ready to be included in the VIX image without more vetting. Please understand this and respect WHY. Thanks.