Posts by Borygo77

Borygo77 · 2020-01-23T00:21:59+00:00

I'm running one of 905W 1/8 in our bedroom and is no different than s905x 2/16 in living room. There is no need for bigger storage or ram to be honest. Just got no idea why your source would miss SD card slot? 🤔

905x is running from SD card and it was on internal before it got corrupted. 905w runs from internal 2 years already....and it will run until corrupt then I'll switch to SD card 😉

Borygo77 · Jan 6th 2020

Quote from Jerry

does not install, it does not work, generic hdd installation

LibreELEC:~ # opkg install coreutils-expr

-sh: opkg: not found

LibreELEC:~ #

Did you went through link I've posted? It's not that simple to install entware but it's possible. I had it working in official libre 8....

Borygo77 · Jan 6th 2020

LibreELEC entware installation (opkg / optware) – Artem Butusov Blog

Borygo77 · Dec 29th 2019

Quote from phob08

cognitive dissonance detected: relief AND embarassment

thank you borygo77!

Lemme know if it's working for you If not we will solve it hard linking your external storage The thing Da Flex is talking about

Borygo77 · Dec 28th 2019

Try to use this command without ~ before var 😉

docker run -d --restart=always -v /var/media/[EXTERNAL DRIVE NAME]:/root/Downloads -v ~/jdownloader/cfg:/opt/JDownloader/cfg --name jdownloader -u $(id -u) jaymoulin/jdownloader

Borygo77 · Dec 23rd 2019

Nice! Thanks Thoradia. Looks like I've been waiting with update too long 😉

Marry Christmas! 🌲

edit: all grand after update to 9.2, thanks again!

Borygo77 · Dec 11th 2019

Just delete password file and you got your settings without password. Can't remember path but I can find it in a min 😉

edit:

There are 2 folders in .kodi/userdata/service.tvheadend42 folder.

accesscontrol where you find users and folder passwd where passwords are stored for them.

Remember I messed something once and after deleting password for my account I could get in without login.

Borygo77 · Nov 29th 2019

No worries! Thanks Chewitt

Borygo77 · Nov 29th 2019

Thanks Chewitt! Got my own samba.conf for ages but never been checking journalctl for warnings/errors. So it was bugging me as hell.

Had this sorted same day after finding some sources in google and added line for master browser

This machine is serving files mostly so it's always on...

There is one thing I need help with. How do I stop recreating folders from /storage/ ?

If I delete videos,music,tvshows etc those always coming back after reboot. Don't like this mess really.

If there is any way to stop it can you help please ? If not I can live with it

Here is my samba journalctl

Code

Nov 29 04:09:42 HTPC nmbd[1027]: [2019/11/29 04:09:42.076960, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Nov 29 04:09:42 HTPC nmbd[1027]: *****
Nov 29 04:09:42 HTPC nmbd[1027]:
Nov 29 04:09:42 HTPC nmbd[1027]: Samba name server HTPC is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Nov 29 04:09:42 HTPC nmbd[1027]:
Nov 29 04:09:42 HTPC nmbd[1027]: *****
Nov 29 04:09:42 HTPC nmbd[1027]: [2019/11/29 04:09:42.077527, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Nov 29 04:09:42 HTPC nmbd[1027]: *****
Nov 29 04:09:42 HTPC nmbd[1027]:
Nov 29 04:09:42 HTPC nmbd[1027]: Samba name server HTPC is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1
Nov 29 04:09:42 HTPC nmbd[1027]:
Nov 29 04:09:42 HTPC nmbd[1027]: *****
Nov 29 04:09:42 HTPC nmbd[1027]: [2019/11/29 04:09:42.077948, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Nov 29 04:09:42 HTPC nmbd[1027]: *****
Nov 29 04:09:42 HTPC nmbd[1027]:
Nov 29 04:09:42 HTPC nmbd[1027]: Samba name server HTPC is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.111
Nov 29 04:09:42 HTPC nmbd[1027]:
Nov 29 04:09:42 HTPC nmbd[1027]: *****

Display More

Borygo77 · Nov 26th 2019

It's not stopping at all Can I add something to smb.conf to change behaviour of less important two ?

Thanks for looking after

Borygo77 · Nov 26th 2019

Hi guys! Not sure if I should care much about it but my journalctl is flooded with this warning everytime I'm going in to it....

Have three libreelec devices at home with 192.168.1.111, 112, 113.

Any chance to fix it somehow ?

Code

Nov 26 00:00:59 HTPC nmbd[939]: [2019/11/26 00:00:59.543359, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:00:59 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:00:59 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:05:59 HTPC nmbd[939]: [2019/11/26 00:05:59.786246, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:05:59 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:05:59 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:10:59 HTPC nmbd[939]: [2019/11/26 00:10:59.609231, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:10:59 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:10:59 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:16:02 HTPC nmbd[939]: [2019/11/26 00:16:02.725912, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:16:02 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:16:02 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:16:33 HTPC connmand[399]: ntp: adjust (slew): +0.000165 sec
Nov 26 00:21:09 HTPC nmbd[939]: [2019/11/26 00:21:09.523679, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:21:09 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:21:09 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:26:19 HTPC nmbd[939]: [2019/11/26 00:26:19.811415, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:26:19 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:26:19 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:31:12 HTPC nmbd[939]: [2019/11/26 00:31:12.158004, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:31:12 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:31:12 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:33:37 HTPC connmand[399]: ntp: adjust (slew): +0.000423 sec
Nov 26 00:36:19 HTPC nmbd[939]: [2019/11/26 00:36:19.670959, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:36:19 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:36:19 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:41:19 HTPC nmbd[939]: [2019/11/26 00:41:19.912215, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:41:19 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:41:19 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:46:19 HTPC nmbd[939]: [2019/11/26 00:46:19.539168, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:46:19 HTPC nmbd[939]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:46:19 HTPC nmbd[939]: This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.

Display More

Borygo77 · Nov 25th 2019

Hi guys! Does anyone know why special characters are displayed wrong in ruTorrent rss webgui ?

Any setting I need to change to get it working ok ?

Got ¶ instead of ś or Ї instead of ż

It seems to be set to Windows 1251 instead of 1250

Here is issue I've raised with rutorrent author Polish special signs · Issue #1970 · Novik/ruTorrent · GitHub

As he tried to help the issue is probably with mbstring module missing from php....

Is there any chance you can have a look on it Thoradia please?

Borygo77 · Sep 2nd 2019

Quote from CvH

try my update script

ssh into LE

wget -O /storage/.kodi/addons/service.emby/bin/emby-update http://ix.io/1i4E

reboot

then emby-update is available

Display More

And you can always use CvH update script it worked great when I used libre before 👍😊

Borygo77 · Jun 4th 2019

Works for me as well Thanks a mill! Need to reboot to check if it will come back but wife watching TV now so not a chance

Code

[2019-06-04 16:56:26] Failed password for invalid user roo from 192.168.1.43 port 50718 ssh2
[2019-06-04 16:56:26] Failed password for invalid user roo from 192.168.1.43 port 50718 ssh2
[2019-06-04 16:56:29] Failed password for invalid user roo from 192.168.1.43 port 50718 ssh2
[2019-06-04 16:56:29] Received disconnect from 192.168.1.43 port 50718:11: Normal Shutdown [preauth]
[2019-06-04 16:56:29] Disconnected from invalid user roo 192.168.1.43 port 50718 [preauth]
[2019-06-04 16:56:42] Accepted password for root from 192.168.1.43 port 50719 ssh2
[2019-06-04 19:08:11] Accepted password for root from 192.168.1.43 port 52539 ssh2

Borygo77 · Jun 4th 2019

Told you before! You're legend to me! 😊 Will try it once back home.

Thanks again!

Borygo77 · Jun 4th 2019

Thank you vpeter! 😊

Is there any manual you're following for ssh_args or got everything in your head ? 😳

Borygo77 · Jun 4th 2019

Got another question How can I preserve those changes between and after reboots ?

My log looks like this one below and I would like to have timestamps as well ? Any chances vpeter ?

Code

Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
Accepted password for root from 192.168.1.19 port 58507 ssh2
Accepted password for root from 192.168.1.19 port 58508 ssh2
Accepted password for root from 192.168.1.19 port 60206 ssh2
Received disconnect from 192.168.1.19 port 58507:11: Normal Shutdown
Disconnected from user root 192.168.1.19 port 58507
Received disconnect from 192.168.1.19 port 60206:11: cleanup
Disconnected from user root 192.168.1.19 port 60206
Accepted password for root from 192.168.1.19 port 60269 ssh2
Accepted password for root from 192.168.1.19 port 60271 ssh2
Exiting on signal 15
Exiting on signal 15
Received signal 15; terminating.
Exiting on signal 15
Exiting on signal 15
Exiting on signal 15
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
Accepted password for root from 185.178.71.131 port 52097 ssh2
Accepted password for root from 145.239.254.70 port 50212 ssh2
Accepted password for root from 145.239.254.70 port 50213 ssh2
Received disconnect from 145.239.254.70 port 50213:11:
Disconnected from user root 145.239.254.70 port 50213
Accepted password for root from 145.239.254.70 port 50234 ssh2
Accepted password for root from 145.239.254.70 port 50235 ssh2
Received disconnect from 145.239.254.70 port 50235:11:
Disconnected from user root 145.239.254.70 port 50235
Accepted password for root from 145.239.254.70 port 50238 ssh2
Accepted password for root from 145.239.254.70 port 50239 ssh2
Received disconnect from 145.239.254.70 port 50239:11:
Disconnected from user root 145.239.254.70 port 50239
Accepted password for root from 145.239.254.70 port 50240 ssh2
Received signal 15; terminating.
Exiting on signal 15
Exiting on signal 15
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
Accepted password for root from 192.168.1.19 port 61033 ssh2
Accepted password for root from 192.168.1.19 port 61034 ssh2
Accepted password for root from 192.168.1.19 port 61035 ssh2
Exiting on signal 15
Received signal 15; terminating.
Exiting on signal 15
Exiting on signal 15
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
Accepted password for root from 192.168.1.19 port 61060 ssh2
Received signal 15; terminating.
Exiting on signal 15
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
Accepted password for root from 192.168.1.43 port 50337 ssh2
Accepted password for root from 192.168.1.43 port 50339 ssh2
Received disconnect from 192.168.1.43 port 50337:11: Normal Shutdown
Disconnected from user root 192.168.1.43 port 50337
Invalid user roo from 192.168.1.43 port 50344
Could not get shadow information for NOUSER
Failed password for invalid user roo from 192.168.1.43 port 50344 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50344 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50344 ssh2
Received disconnect from 192.168.1.43 port 50344:11: Normal Shutdown [preauth]
Disconnected from invalid user roo 192.168.1.43 port 50344 [preauth]
Invalid user roo from 192.168.1.43 port 50345
Could not get shadow information for NOUSER
Failed password for invalid user roo from 192.168.1.43 port 50345 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50345 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50345 ssh2
Received disconnect from 192.168.1.43 port 50345:11: Normal Shutdown [preauth]
Disconnected from invalid user roo 192.168.1.43 port 50345 [preauth]
Invalid user roo from 192.168.1.43 port 50347
Could not get shadow information for NOUSER
Failed password for invalid user roo from 192.168.1.43 port 50347 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50347 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50347 ssh2
Received disconnect from 192.168.1.43 port 50347:11: Normal Shutdown [preauth]
Disconnected from invalid user roo 192.168.1.43 port 50347 [preauth]
Invalid user roo from 192.168.1.43 port 50348
Could not get shadow information for NOUSER
Failed password for invalid user roo from 192.168.1.43 port 50348 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50348 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50348 ssh2
Received disconnect from 192.168.1.43 port 50348:11: Normal Shutdown [preauth]
Disconnected from invalid user roo 192.168.1.43 port 50348 [preauth]
Invalid user roo from 192.168.1.43 port 50350
Could not get shadow information for NOUSER
Failed password for invalid user roo from 192.168.1.43 port 50350 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50350 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50350 ssh2
Received disconnect from 192.168.1.43 port 50350:11: Normal Shutdown [preauth]
Disconnected from invalid user roo 192.168.1.43 port 50350 [preauth]
Invalid user roo from 192.168.1.43 port 50351
Could not get shadow information for NOUSER
Failed password for invalid user roo from 192.168.1.43 port 50351 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50351 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50351 ssh2
Received disconnect from 192.168.1.43 port 50351:11: Normal Shutdown [preauth]
Disconnected from invalid user roo 192.168.1.43 port 50351 [preauth]
Invalid user roo from 192.168.1.43 port 50353
Could not get shadow information for NOUSER
Failed password for invalid user roo from 192.168.1.43 port 50353 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50353 ssh2
Failed password for invalid user roo from 192.168.1.43 port 50353 ssh2
Received disconnect from 192.168.1.43 port 50353:11: Normal Shutdown [preauth]
Disconnected from invalid user roo 192.168.1.43 port 50353 [preauth]
Accepted password for root from 192.168.1.43 port 50358 ssh2

Display More

Borygo77 · Jun 2nd 2019

You're legend vpeter! Thanks a mill!

Posts by Borygo77

Mecool M8S Plus W ($15, S905W)

entware

entware

Issue with Write-Acces,External HDD

Issue with Write-Acces,External HDD

Thoradia Add-ons

NFR - TVHeadend reset admin inside addon settings

nmbd service problem

nmbd service problem

nmbd service problem

nmbd service problem

Thoradia Add-ons

.Net Core runtime and Emby

SSH logs

SSH logs

SSH logs

SSH logs

SSH logs