External storages - SMB: green dot but SMB folder won't appear

carlisle · March 16, 2019, 11:33pm

Nextcloud version (eg, 12.0.2): 15.0.5
Operating system and version (eg, Ubuntu 17.04): Ubuntu 18.10.1 / Windows 10 SMB server
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4.34
PHP version (eg, 7.1): php 7.2.15

The issue you are facing:
No SMB folder appears if it is added an external storage SMB / CIFS like “D:/” or “E:/”
I shared my ENTIRE HDD from my win10 PC and if I add it as a SMB external storage, i get the GREEN circle but in the file section no folder appears (only the manual.pdf file).
This problem occurs only with entire shared HDDs/SSDs, like E:/.
An SMB share E:/Data works fine.

Is this the first time you’ve seen this error? (Y/N): N

Steps to replicate it:

Win10: Share an entire storage device (eg D:/)
Nextcloud: add the external SMB share
SMB share folder won’t appear in the home.

The output of your Nextcloud log in Admin > Logging:

empty

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'instanceid' => '*',
  'passwordsalt' => '*',
  'secret' => '*',
  'trusted_domains' => 
  array (
    0 => '192.168.1.194',
  ),
  'datadirectory' => '/var/www/html/nextcloud/data',
  'dbtype' => 'mysql',
  'version' => '15.0.5.3',
  'overwrite.cli.url' => 'http://192.168.1.194/nextcloud',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'admin',
  'dbpassword' => '*******',
  'installed' => true,
);

The output of your Apache/nginx/system log in /var/log/____:

[Sat Mar 16 13:26:33.156885 2019] [mpm_event:notice] [pid 5081:tid 139859269323712] AH00489: Apache/2.4.34 (Ubuntu) configured -- resuming normal operations
[Sat Mar 16 13:26:33.156959 2019] [core:notice] [pid 5081:tid 139859269323712] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 16 16:05:50.611333 2019] [mpm_event:notice] [pid 5081:tid 139859269323712] AH00491: caught SIGTERM, shutting down
[Sat Mar 16 16:05:50.663143 2019] [mpm_prefork:notice] [pid 17282] AH00163: Apache/2.4.34 (Ubuntu) configured -- resuming normal operations
[Sat Mar 16 16:05:50.663229 2019] [core:notice] [pid 17282] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 16 16:05:50.927162 2019] [mpm_prefork:notice] [pid 17282] AH00169: caught SIGTERM, shutting down
[Sat Mar 16 16:05:51.045677 2019] [mpm_prefork:notice] [pid 17370] AH00163: Apache/2.4.34 (Ubuntu) configured -- resuming normal operations
[Sat Mar 16 16:05:51.045712 2019] [core:notice] [pid 17370] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 16 16:05:54.331233 2019] [mpm_prefork:notice] [pid 17370] AH00169: caught SIGTERM, shutting down
[Sat Mar 16 16:05:54.400805 2019] [mpm_prefork:notice] [pid 17466] AH00163: Apache/2.4.34 (Ubuntu) configured -- resuming normal operations
[Sat Mar 16 16:05:54.400847 2019] [core:notice] [pid 17466] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 16 16:08:51.867566 2019] [mpm_prefork:notice] [pid 17466] AH00169: caught SIGTERM, shutting down
[Sat Mar 16 16:09:00.353197 2019] [mpm_prefork:notice] [pid 1006] AH00163: Apache/2.4.34 (Ubuntu) configured -- resuming normal operations
[Sat Mar 16 16:09:00.353423 2019] [core:notice] [pid 1006] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 16 16:28:05.763458 2019] [mpm_prefork:notice] [pid 1006] AH00169: caught SIGTERM, shutting down
[Sat Mar 16 16:28:05.909003 2019] [mpm_prefork:notice] [pid 4644] AH00163: Apache/2.4.34 (Ubuntu) configured -- resuming normal operations
[Sat Mar 16 16:28:05.909054 2019] [core:notice] [pid 4644] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 16 16:29:52.763465 2019] [mpm_prefork:notice] [pid 4644] AH00169: caught SIGTERM, shutting down
[Sat Mar 16 16:30:00.748185 2019] [mpm_prefork:notice] [pid 990] AH00163: Apache/2.4.34 (Ubuntu) configured -- resuming normal operations
[Sat Mar 16 16:30:00.748353 2019] [core:notice] [pid 990] AH00094: Command line: '/usr/sbin/apache2'

carlisle · March 16, 2019, 11:58pm

Can we get a proper fix please?

clkclkclk · November 26, 2019, 6:08pm

Hi
My first post as I am new to NextCloud (and relatively new to Pi as well)

Have looked at all the different existing posts but none of the “solved” ones seem to work for me. This one appears to be most like the issue I have

I have a Pi and a Windows NAS.
From the Pi using the Command Line I can quite happily connect to and use my Windows NAS by mounting it with
sudo mount -t cifs //192.168.1.28/Sharename /home/pi/NAS540

I have now installed Nextcloud on my Pi as well and that seems to work perfectly well as well.

I want to add my NAS to be available in Nextcloud.

SO by using various forums and help docs I enabled the “external storage” app in Nextcloud, added my NAS as local folder and the FLag next to it goes green which I understand means it is connected

If I go into my Files on Nextcloud I can see, under “external storage” a picture of what I added but when I click on it to open it I just get redirected back to to my local files

So first off, even though I can connect to the NAS from the Pi by an explicit command and it works, am I correct that its not doing it by a SAMBA module in the Pi itself and that a pre-requisite to Nextcloud being able to access the NAS is a samba client on the Pi?

i have tried different Samba clients but are they all compatible with Nextcloud?

all the Samba clients I have do the same thing in Pi Filemanager - when I navigate to Go>Network and I click on Workgroup (the network name of the NAS) I just get an error that says “Failed to retrieve share list from server: Success”. So I guess if they are not working at the Pi level, Nextcloud wont work.

Any help gratefully received

Thanks