SSD Profile Tool app removal

Introduce yourself to us and other members here, or share your own product reviews, suggestions, and tips and tricks of using QNAP products.
Post Reply
gnestor
New here
Posts: 3
Joined: Sun Nov 25, 2018 7:05 am

SSD Profile Tool app removal

Post by gnestor » Sun Nov 25, 2018 7:20 am

I have a TS-431 (4 bay) NAS running firmware 4.3.5.0728 build 20181013. (I don't think the other items are relevant to this question, such as my computers OS)

I made the mistake of installing the "SSD Profiling Tool" (version 1.0.0696), which told me when I installed it that I was giving my permission to pass data from my NAS back to QNap, but it also told me that I could remove my permission for this by removing the tool. This made me assume that it was like many other apps and that I could just remove it whenever I wanted. That isn't the case, and when I reached out to the helpdesk they told me "it's a system function, it shouldn't be removed". (The other frustrating thing is that I've stopped the app numerous times, but find when I check a few weeks later that it has magically re-enabled itself). Needless to say I'm a bit annoyed.

I've shelled into the NAS and found the directory that the tool is installed in, but I don't think it's wise to just delete the directory. (It's in /mnt/ext/opt/SSDLabaratory I think).

Bottom line, does anyone know how to safely remove/uninstall this app? (I'm fine with using unix/linux commands if you tell me what I should type in).

Please help!

dolbyman
Guru
Posts: 10859
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: SSD Profile Tool app removal

Post by dolbyman » Sun Nov 25, 2018 7:25 am

I think you can just stop//deactivate the tool .. then it should he as good as gone..minus the bit of space used for the program on disk

User avatar
xftroxgpx
New here
Posts: 4
Joined: Mon Nov 26, 2018 9:43 pm

Re: SSD Profile Tool app removal

Post by xftroxgpx » Mon Nov 26, 2018 11:58 pm

I've tried setting the schedule for it(from within Qboost) and set all cubes(representing hours for the days of the week) to disabled, selected "Enable Schedule" then Apply and even Auto Apply. It seems to work FOR THE CURRENT SESSION, as SSD Profile Tool is stopped and appears as Always Disabled! But on next NAS boot, the schedule is disabled ("Enable Schedule" is unchecked), and the SSD Profiling Tool is happily running again :)) I don't think this should be happening! I think the schedule should be remembered and not magically disable itself for this app (I haven't tried setting a schedule for other apps though)

I can also just stop it (from within Qboost) without setting a schedule, but it's back on again after reboot.


Looks like /mnt/ext/opt/SSDLabaratory is the result of a qpkg installation?(just guessing, also don't know how qpkg stuff works yet)
But running the qpkg command (without any args) yields "Segmentation fault" =)
[14981.209554] Segmentation fault (pid 25916) qpkg:
[14981.209554] 1. /lib/libc.so.6(strcmp+0x18) [0x7fa9e76858]
[14981.209554] 2. qpkg() [0x40dfc0]

Ok, qpkg_cli seems to work.

Code: Select all


# qpkg_cli --status SSDLaboratory
[CLI] QPKG SSDLaboratory is installed
[~] # qpkg_cli --stop SSDLaboratory
[CLI] QPKG SSDLaboratory is queuing
# qpkg_cli --disable SSDLaboratory
[CLI] QPKG SSDLaboratory is queuing
You get a notice that says App Center SSD Profiling Tool disabled. (oddly enough that message appears only in Latest Notifications, but not in System Event Logs, even with All Severity Levels filter - but does show the Stopped message; QTS 4.3.5.0760 Build 20181114)
I'm currently dd-ing /dev/zero on one of my drives, since hdparm is dumbed down and unable to issue a security erase, so I will test later if after rebooting the NAS the SSD Profiling Tool still starts again. I'm guessing it won't. But if it does, there's always:
qpkg_cli --remove SSDLaboratory left to try (see qpkg_cli --help)
EDIT: disable didn't work, SSD Profiling Tool was still running on next boot.
--remove doesn't work for this, you get a Warning [App Center] Failed to uninstall SSD Profiling Tool. You are not allowed to do this action.

ok trying:

Code: Select all


[~] # /mnt/ext/opt/SSDLaboratory/.uninstall.sh
Remove SSDLaboratory
Remove /etc/config/SSDLaboratory
/mnt/ext/opt/SSDLaboratory/.uninstall.sh: line 11: unexpected EOF while looking for matching `"'
/mnt/ext/opt/SSDLaboratory/.uninstall.sh: line 16: syntax error: unexpected end of file
ok, who programmed this? lacking a "

Code: Select all


#!/bin/sh
QPKG_NAME="SSDLaboratory"
SYS_QPKG_CONFIG_FILE="/etc/config/qpkg.conf"
QPKG_DIR=`/sbin/getcfg SSDLaboratory Install_Path -f ${SYS_QPKG_CONFIG_FILE}`
echo "Remove ${QPKG_NAME}"
#/etc/init.d/ssd_lab.sh stop 1>/dev/null 2>&1

echo "Remove /etc/config/${QPKG_NAME}"
/bin/rm -rf /etc/config/${QPKG_NAME}"

echo "Remove ${QPKG_DIR}_database"

/bin/rm -r ${QPKG_DIR}_database

/bin/rm /tmp/spt_run_once_on_boot -f
/mnt/ext/opt/SSDLaboratory/ still stands... and upon rebooting the NAS(good lord, it takes at least 535 seconds to finish booting up since the Restart finished, and Qboost didn't even started yet!ytf is NAS so slow, geebus), SSD Profiling Tool is still started!
and this is back:

Code: Select all

[~] # ls -la /etc/init.d/*ssd*
lrwxrwxrwx 1 admin administrators 37 2018-11-27 08:11 /etc/init.d/ssd_lab.sh -> /mnt/ext/opt/SSDLaboratory/ssd_lab.sh*
ok removing whole dir /mnt/ext/opt/SSDLaboratory/ (forgot to run .uninstall first, oh well)
rebooting NAS
TS-228A 2 bay, 2 HDDs, firmware 4.3.5.0760 Build 20181114
8:21:10am a short beep happens after choosing Restart
8:21:37am blue "Rebooting, please wait..." screen
8:22:45am another short beep happens
8:22:58am another short beep happens
8:25:22am the NAS IP that I've set(not 169.254.100.100 which is always pingable during all this time) becomes pingable
8:30:00am (could be a few seconds earlier) login screen becomes accessible and can log in, but greeted by message: "Qboost is currently starting up. Please try again later."
8:30:29am a long beep happens
8:31:28am i refresh the page, shows "Loading..."
8:32:47am page still shows "Loading..."
8:33:02am I refresht he page again, shows "Loading..."
8:33:12am page loaded (so it stopped showing "Loading...") and Qboost is there also.
So what like at least 10 minutes until NAS is usable? how is this in any way acceptable, QNAP?! (or is it just a side-effect of not having a DHCP server on the LAN and/or not giving NAS internet access?)

Surprise surprise SSD Profiling Tool is still there, running!
Well, this is annoying. Considering throwing NAS across room, for a few seconds...

/mnt/ext/opt/SSDLaboratory/ is still there despite "rw" mount... hmm md=memory device? so temporary... thus this should've been done in the firmware img?

Code: Select all

[~] # ls -la /mnt/ext/opt/SSDLaboratory/
total 152
drwxr-xr-x 6 admin administrators 4096 2018-11-27 08:28 ./
drwxr-xr-x 32 admin administrators 4096 2018-11-27 08:30 ../
drwxr-xr-x 2 admin administrators 4096 2018-11-13 21:26 cgi/
drwxr-xr-x 2 admin administrators 4096 2018-11-13 21:26 lib/
-rwxr-xr-x 1 admin administrators 27719 2018-11-13 17:00 .qpkg_icon_68.gif*
-rw-r--r-- 1 admin administrators 28941 2018-11-13 17:00 .qpkg_icon_80.gif
-rw-r--r-- 1 admin administrators 28941 2018-11-13 17:00 .qpkg_icon.gif
-rw-r--r-- 1 admin administrators 22590 2018-11-13 17:00 .qpkg_icon_gray.gif
lrwxrwxrwx 1 admin administrators 38 2018-11-27 08:28 ssd_lab.conf -> /etc/config/SSDLaboratory/ssd_lab.conf
-rw-r--r-- 1 admin administrators 565 2018-11-27 08:31 ssd_lab.log
-rwxr-xr-x 1 admin administrators 4081 2018-11-13 17:00 ssd_lab.sh*
lrwxrwxrwx 1 admin administrators 35 2018-11-27 08:28 ssd_op.db -> /etc/config/SSDLaboratory/ssd_op.db
drwxr-xr-x 3 admin administrators 4096 2018-11-13 21:26 ui/
-rwxr-xr-x 1 admin administrators 418 2018-11-13 17:00 .uninstall.sh*
drwxr-xr-x 2 admin administrators 4096 2018-11-13 21:26 util/
[~] # df /mnt/ext/opt/SSDLaboratory/
Filesystem Size Used Available Use% Mounted on
/dev/md13 417.0M 340.3M 76.7M 82% /mnt/ext
[~] # mount|grep md13
/dev/md13 on /mnt/ext type ext4 (rw,data=ordered,barrier=1,nodelalloc)

Code: Select all

[~] # find / -name SSDLaboratory
/mnt/HDA_ROOT/.config/SSDLaboratory
/mnt/HDA_ROOT/home/httpd/cgi-bin/qpkg/SSDLaboratory
/mnt/ext/opt/SSDLaboratory
/mnt/ext/opt/SSDLaboratory/ui/SSDLaboratory
/mnt/ext/opt/SSDLaboratory/ui/SSDLaboratory/SSDLaboratory
Well then...

gnestor
New here
Posts: 3
Joined: Sun Nov 25, 2018 7:05 am

Re: SSD Profile Tool app removal

Post by gnestor » Wed Nov 28, 2018 1:27 pm

dolbyman wrote:
Sun Nov 25, 2018 7:25 am
I think you can just stop//deactivate the tool .. then it should he as good as gone..minus the bit of space used for the program on disk
Thanks, but tried this and it doesn't work. It auto-magically re-enables itself. See behavior below in xftroxgpx's post...I think he's starting to feel my frustration! As he steps through various attempts to keep it stopped/remove it, it just keep showing back up and re-enabling itself on boot up. (I think this is a borderline malicious app if there isn't a way for the user to disable/remove it after installing it from the QNAP app store.)

User avatar
xftroxgpx
New here
Posts: 4
Joined: Mon Nov 26, 2018 9:43 pm

Re: SSD Profile Tool app removal

Post by xftroxgpx » Wed Nov 28, 2018 2:39 pm

Yeah, I'm (looking into) replacing QTS with something else like Xigmanas, openmediavault or even ArchLinuxARM. Sorry QNAP but all this isn't worth it: 10min to start up + there's no firewall on it and netstat -pantu shows lots of open ports even when all services are disabled(according to System Status - System Services) and after a shutdown

Code: Select all

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN      12434/cupsd
tcp        0      0 127.0.0.1:58080         0.0.0.0:*               LISTEN      12619/_thttpd_
tcp        0      0 127.0.0.1:3310          0.0.0.0:*               LISTEN      8629/mysqld
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      8468/dnsmasq
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      13782/sshd
tcp        0      0 127.0.0.1:58080         127.0.0.1:36350         TIME_WAIT   -
tcp        0      0 127.0.0.1:36338         127.0.0.1:58080         CLOSE_WAIT  20712/apache_proxys
tcp        0      0 127.0.0.1:58080         127.0.0.1:36364         FIN_WAIT2   -
tcp        0      0 127.0.0.1:58080         127.0.0.1:36347         TIME_WAIT   -
tcp        0      0 127.0.0.1:34624         127.0.0.1:58080         CLOSE_WAIT  20712/apache_proxys
tcp        0      0 127.0.0.1:35126         127.0.0.1:58080         CLOSE_WAIT  20712/apache_proxys
tcp        0      0 127.0.0.1:58080         127.0.0.1:36342         TIME_WAIT   -
tcp        0      0 127.0.0.1:58080         127.0.0.1:36354         TIME_WAIT   -
tcp        0      0 127.0.0.1:58080         127.0.0.1:36356         FIN_WAIT2   -
tcp        0      0 127.0.0.1:58080         127.0.0.1:36358         TIME_WAIT   -
tcp        0      0 127.0.0.1:36356         127.0.0.1:58080         CLOSE_WAIT  20712/apache_proxys
tcp        0      0 127.0.0.1:59962         127.0.0.1:8080          TIME_WAIT   -
tcp        0      0 127.0.0.1:36302         127.0.0.1:58080         CLOSE_WAIT  20712/apache_proxys
tcp        0      0 127.0.0.1:58080         127.0.0.1:36344         TIME_WAIT   -
tcp        0      0 127.0.0.1:59972         127.0.0.1:8080          TIME_WAIT   -
tcp        0      0 127.0.0.1:36364         127.0.0.1:58080         CLOSE_WAIT  20712/apache_proxys
tcp        0      0 127.0.0.1:58080         127.0.0.1:36336         TIME_WAIT   -
tcp        0      0 127.0.0.1:58080         127.0.0.1:36346         TIME_WAIT   -
tcp        0    464 169.254.100.100:22        169.254.100.11:36532     ESTABLISHED 16288/0
tcp        0      0 :::631                  :::*                    LISTEN      12434/cupsd
tcp        0      0 :::443                 :::*                    LISTEN      13616/apache_proxys
tcp        0      0 :::8080                 :::*                    LISTEN      12801/apache_proxy
tcp        0      0 :::80                   :::*                    LISTEN      12381/Qthttpd
tcp        0      0 :::22                   :::*                    LISTEN      13782/sshd
tcp        0      0 ::ffff:169.254.100.100:443 ::ffff:169.254.100.11:43450 TIME_WAIT   -
tcp        0      0 ::ffff:169.254.100.100:443 ::ffff:169.254.100.11:43454 ESTABLISHED 20712/apache_proxys
udp        0      0 127.0.0.1:55283         127.0.0.1:514           ESTABLISHED 12381/Qthttpd
udp        0      0 0.0.0.0:57901           0.0.0.0:*                           8468/dnsmasq
udp        0      0 127.0.1.1:53            0.0.0.0:*                           8468/dnsmasq
udp        0      0 127.0.0.1:53593         127.0.0.1:514           ESTABLISHED 12619/_thttpd_
udp     2304      0 255.255.255.255:8097    0.0.0.0:*                           16580/bcclient
udp        0      0 255.255.255.255:8097    0.0.0.0:*                           16580/bcclient

[~] # iptables -t nat -vnL
Chain PREROUTING (policy ACCEPT 264 packets, 11724 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain INPUT (policy ACCEPT 42 packets, 2184 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 1496 packets, 95893 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain POSTROUTING (policy ACCEPT 1496 packets, 95893 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MASQUERADE  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match ! 0x0/0xffff
 1498 97164 VPNNAT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           
 1498 97164 SYSNAT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain SYSNAT (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain VPNNAT (1 references)
 pkts bytes target     prot opt in     out     source               destination         
[~] # iptables -t filter -vnL
Chain INPUT (policy ACCEPT 51862 packets, 18M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 49535 packets, 31M bytes)
 pkts bytes target     prot opt in     out     source               destination         
[~] # iptables -t mangle -vnL    
Chain PREROUTING (policy ACCEPT 52149 packets, 18M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain INPUT (policy ACCEPT 51925 packets, 18M bytes)
 pkts bytes target     prot opt in     out     source               destination         
36341   16M CHECKHOST  all  --  *      *       0.0.0.0/0           !169.254.0.0/16      
51925   18M CONNMARK   all  --  *      *       0.0.0.0/0            0.0.0.0/0            CONNMARK save

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 49575 packets, 32M bytes)
 pkts bytes target     prot opt in     out     source               destination         
49575   32M CONNMARK   all  --  *      *       0.0.0.0/0            0.0.0.0/0            CONNMARK restore
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            match-set HOSTSET dst MARK xset 0x10000/0xf0000

Chain POSTROUTING (policy ACCEPT 49579 packets, 32M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain CHECKHOST (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            match-set NATSET src MARK xset 0x10000/0xf0000

Chain VPNCHECKHOST (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            match-set VPNSET src MARK xset 0x10000/0xf0000

Chain VPNCUSSETMARK (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain VPNDEFSETMARK (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain VPNSETMARKENTRANCE (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 VPNCUSSETMARK  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 VPNDEFSETMARK  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xffff


gnestor
New here
Posts: 3
Joined: Sun Nov 25, 2018 7:05 am

Re: SSD Profile Tool app removal

Post by gnestor » Thu Dec 06, 2018 10:58 am

The help desk gave me a couple things to try. Here's what they told me to do:

"To remove it, you will have to open an ssh session.
Then enter cd /mnt/HDA_ROOT/.config/
From there enter vi qpkg.conf and remove everything from [SSDLaboratory] and below it by pressing dd on each line.
After that enter cd /mnt/ext/opt/ and enter rm -r SSDLaboratory/"

BUT...it magically re-appears after reboot (the directory is back and the qpkg.conf file has the SSDLaboratory entry back in it at the bottom). I went back a few times and he talked to his tech lead, and the word is that this is part of the firmware in 4.3.5+, and the only way to remove it is to revert to firmware 4.3.4 (which I am considering doing).

If anyone figures out how to permanently get rid of this, I'd much appreciate the post!

Post Reply

Return to “Users' Corner”