Need help to upgrade old NAS. Lots of questions.

Zitat von crashtest

Unfortunately, hardware issues are the hardest to find. There's no decent diagnostics software that covers all of the various brands of Motherboards and peripherals, and rarely will OEM software diagnose a specific fault. Assuming the power supply is up to spec (at least the outputs can measured), hardware "guess work" often begins with Motherboard isolation and burn-in software, then adding memory sticks and peripherals one by one. Most of it is off-line and time intensive.

The above is why, when building a new box, it's best to start with good quality Motherboard from an OEM with a good reputation. (Supermicro, Intel, MSi, ASUS, Gigabyte, etc.) Similarly, a good quality power supply is not wasted money.

At least my PSU, although a bit old and not too strong (360W), is from a good brand (Zalman, SPI Electronics made). Being older than PLUS 80 seal, it lacks this certification, but it fits all the requirements to PLUS 80 White.

I have two other PSU in the shelf, a Corsair AX650 and a Seventeam ST-750z-AF, that has better PLUS 80 scores, but they are too strong for a NAS, I think. But using a PLUS 80 Gold or Bronze PSU in a machine intended to remain on 24/7 should save me in energy consumption in the long term, besides allowing a better cable management.

Best regards.

I finally received a new motherboard from the seller to replace the one with the damaged M.2 slot.

The board is identical to the previous one, with the same poorly written manual of just one page.

Before installing the card, I made two small changes in the case (I replaced the standard Cooler Master fan with a pwm Noctua and replaced the blue Power LED housed in the Power Button with a white one). The installation of the board in the case was uneventful. I also tried, with little hope, to use the NVMe driver from the previous install, but it didn't work, so I used a fresh install of the OMV. I haven't configured all the features yet, but so far everything is going well. However, my media player computers still cannot see the Samba share in OMV that contains my audio files. Very odd.

Best regards

Zitat von chente

When you close those two doors that space will become an oven.

That cabinet remains open 24/7. BTW, that is a lot of fuel under it!

Zitat von crashtest

The time frame was well over a month. I hope we're not talking about Express Package Delivery, in your part of the world.

Not at all. The motherboard was out of stock. I had to wait the vendor receive a new batch.

Best regards

Well, before continuing to install furter resources , I must fix the main reason for building this NAS: somehow my media player computers are locked out from the very shares they must tap.

At first, I thinking that some debian updates (both machines were running Strecth) were preventing samba clients to connect via unsecure protocols (both former NAS use NT1 version). But, after struggle to build this OMV box AND install/use openmediavault-resetperms plugin, mpd still can't access my media share!

Yesterday, after install the plugin and first run it, I spent almost 4 hours trying to make one of the media computers to update the mpd database and play music, with no success. The only way I could produce some effect was by using BubbleUPnP as a proxy between the NAS and the media computer. That way, I know the mpd is functioning and that there is something wrong with Samba (server or clients). Today, as a last effort, I upgraded one of the computers to Debian Bullseye. The only thing thar I accomplished was that now, mpd database is totally empty. By sshing as the user I created to play music into the machine, I can use smbclient and connect and browse through the media share, but the mpd still can't do a thing.

Fact is, I think I reached my incompetence point. There is not a thing that I can think of to diagnose and solve the problem. I need help, please.

Here are some pics:

The windows MPD client from one of the media computers showing its former database.

And the permission error.

Some info about the media computer. I was able to navigate though the share until the point a .dsd file must be shown.

The same picture of the MPD client from the Bullseye updated computer. The database is blank.

Despite the void database, the list of recent files is available, but the files unreacheable.

Info from the Bullseye computer. Same behaviour tho.

Best regards.

Today, with all data transferred to OMV, it was time to gut the old NAS for its drives.

The one on the right will go to the OMV server and the other were supposed to replace the external HDD that suffered the needle noise thing.

This choice was made for they are from the same model.

I plugged both, one at a time, in a Debian computer to wipe they partitions clean.

After installing the drive in its place, I added a case lock and powered it up. At this moment, it is being wiped (again) in OMV.

Now, the oddest thing: I was about to throw the old external 4TB drive in the bin, the one with the needle noise… But the Debian computer was laying there, already opened, just waiting for a last effort try. So, I plugged the drive and it worked! I deleted its partition, created a new one and putted it in its case. I don’t know how reliable it is (I think not much), but I may have another drive to escalate the NAS size.

Best regards

Well, since I got no help on post #88, I will probably open a new tread in Samba subforum.

But I have an issue in another matter: yesterday I installed Nextcloud again following macom's tutorial. I edited docker-compose.yml as required, pointing the same paths for the Nextcloud, MariaDB and Swag volumes that I had used in the previous OMV setup (the one that had the motherboard RMAed). Therefore, these paths and the according files already existed in the file system. I paid no second thought on that, assuming the files was about to be overwrited.

When I started the containers, I saw several lines in the CLI warning about preexistence of files ("<filename>: Already exists"). After that, I runned "docker logs -f swag" and got the same error I got before, as reported in post #71 when I assumed the error was due an ISP malfunction.

The thing is: I don't know if this error is from the already present old files from the previous install, OR decorrent from a recurrent ISP issue, OR related to something new (or not perceived yet).

Anyone have any clue on this matter? Here is the result from "docker logs -f swag":

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 02-tamper-check: executing...
[cont-init.d] 02-tamper-check: exited 0.
[cont-init.d] 10-adduser: executing...

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
-------------------------------------

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    ####
User gid:    100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
Variables set:
PUID=####
PGID=100
TZ=#######/#########
URL=#######.tplinkdns.com
SUBDOMAINS=www,
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=http
CERTPROVIDER=
DNSPLUGIN=
EMAIL=################@hotmail.com
STAGING=

Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
SUBDOMAINS entered, processing
Sub-domains processed are:  -d www.#######.tplinkdns.com
E-mail address entered: ################@hotmail.com
http validation is selected
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for #######.tplinkdns.com and www.#######.tplinkdns.com

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
  Domain: www.#######.tplinkdns.com
  Type:   dns
  Detail: DNS problem: NXDOMAIN looking up A for www.#######.tplinkdns.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.#######.tplinkdns.com - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

Best Regards.

Zitat von Zoki

The message is, letsencrypt can't find your server to validate the certificate.

What is on http://www.#######.tplinkdns.com

Use ping www.#######.tplinkdns.com

or nslookup www.#######.tplinkdns.com

and compare to the result of http://checkip.dyndns.org this page

Alles anzeigen

That is odd. I have a Home Assistant running (in a diferent port, of course) witch is accessed by the same address, and it is working all rigth! And both the ports 443 and 80 are forwarded to the internal OMV IP.

Best regards.

Zitat von Zoki

Use ping www.#######.tplinkdns.com

or nslookup www.#######.tplinkdns.com

and compare to the result of http://checkip.dyndns.org this page

Ping couldn't find the host. I don't have an available linux machine to test nslookup rigth now, but I bet the result will be similar.

What I have done wrong?

Best regards.

Ok, I was able to remotely access my PC at home. I SSHed the OMV machine and pinged www.#######.tplink.com and the host could not be found. BUT, when I droped the "www", voilà! It pinged. Then, shame on me, I tried to nslookup the same link, but this particular command is not available in this setup. But exiting the SSH connection, my windows machine could acomplish it.

PS C:\Users\#####> ssh root@192.168.###.###
root@192.168.###.###'s password:
Linux ######## 5.10.0-0.bpo.9-amd64 #1 SMP Debian 5.10.70-1~bpo10+1 (2021-10-10) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Feb 25 14:07:55 2022 from 192.168.###.###
root@########:~# ping #######.tplinkdns.com
PING #######.tplinkdns.com (###.###.#.##) 56(84) bytes of data.
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=1 ttl=63 time=1.28 ms
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=2 ttl=63 time=0.949 ms
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=3 ttl=63 time=1.05 ms
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=4 ttl=63 time=1.06 ms
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=5 ttl=63 time=0.911 ms
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=6 ttl=63 time=1.07 ms
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=7 ttl=63 time=1.11 ms
64 bytes from ###.###.#.##.static.host.###.###.## (###.###.#.##): icmp_seq=8 ttl=63 time=1.09 ms
^C
--- #######.tplinkdns.com ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 18ms
rtt min/avg/max/mdev = 0.911/1.064/1.282/0.109 ms
root@########:~# exit
logout
Connection to 192.168.###.### closed.
PS C:\Users\#####> nslookup #######.tplinkdns.com
Servidor:  UnKnown
Address:  192.168.###.###

No  resposta autoritativa:
Nome:    #######.tplinkdns.com
Address:  ###.###.#.##

But when I do the same from my Windows machine at work, I got diferent results:

PS C:\Users\###########> ping #######.tplinkdns.com

Disparando #######.tplinkdns.com [###.###.#.##] com 32 bytes de dados:
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.

Estatísticas do Ping para ###.###.#.##:
    Pacotes: Enviados = 4, Recebidos = 0, Perdidos = 4 (100% de
             perda),
PS C:\Users\###########> nslookup #######.tplinkdns.com
Servidor:  ##-#####.#####.###.##
Address:  ##.##.#.##

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** O tempo limite da solicitação para ##-#####.#####.###.## expirou
PS C:\Users\###########>

What can I do to solve this?

Best regards.

Zitat von Zoki

Does tplink provide that service?

I have no ideia. I will look for this info.

Best regards

It seems #######.tplinkdns.com is already a subdomain.

Zitat

name "#######.tplinkdns.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 63591 (complete: 175327)

Best regards.

I am considering flashing my router with OpenWRT and migrating to DuckDNS. Will this solve the problem?

Best regards.