bug of network share

If something seems really buggy, report it here!

Ads helps Volumio remain Free and Open Source. Please consider donating to help us continue to serve you.

bug of network share

Postby Stanley » Thu Nov 23 2017 10:55

I found a issue in the latest verion (volumio-2.323-2017-11-17).

I can't add a new network drive to windows share folder.

The root cause is Microsoft Windows rejected the connection via samba protocol version 1.0 due to Security Issue (WannaCry ransomware use a SMB v1.0 vulnerability).

The volume system use the following CLI to mount network driver, it will fail.

mount -t cifs -o username=abc -r //windows-host/share-folder /mnt/NAS/music

The correct CLI to mount drive network driver is:

mount -t cifs -o username=abc,vers=2.1 -r //windows-host/share-folder /mnt/NAS/music
Random avatar
Stanley
Fresh off the boat
Fresh off the boat
 
Posts: 1
Joined: Thu Nov 23 2017 10:22

Ads helps Volumio remain Free and Open Source. Please consider donating to help us continue to serve you.


bug of network share

Postby Leo79 » Sun Dec 17 2017 05:54

This bug may exist in the most recent version (2.344), too. My NAS (Samba) specifies:
server min protocol = SMB2

I have no trouble connecting to the network share from iOS, Linux and Windows applications.

The only error information I can find is the short-lived toast indicator which states:
"Error in adding network drive
(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)"

I thought that entering vers=2.1 in the Advanced Options "Options" field might solve the problem, but it did not. I also tried putting a comma in front of vers to no avail.

Also, ssh appears to be disabled for user volumio, so I cannot troubleshoot from a terminal.
Random avatar
Leo79
Fresh off the boat
Fresh off the boat
 
Posts: 1
Joined: Sun Dec 17 2017 05:34


bug of network share

Postby chsims1 » Sun Dec 17 2017 08:00

Also, ssh appears to be disabled for user volumio, so I cannot troubleshoot from a terminal.


How to enable ssh
New to Volumio? Please read the Quick Start Guide to get your system up and running :). FAQs? Docs?
User avatar
chsims1
Moderator
 
Posts: 1806
Joined: Sat Aug 02 2014 10:44
Location: East Yorkshire, UK


bug of network share

Postby taravasya » Mon Dec 18 2017 00:33

I have this problem too... While I create new mount from UI, its always return to me: mount error(112): Host is down.
In my case, then I add vers=2.0 in field "options", I was have successful mounted share.
Снимок.PNG
Снимок.PNG (2.36 MiB) Viewed 1800 times
User avatar
taravasya
Sunday DIYer
Sunday DIYer
 
Posts: 19
Joined: Tue Aug 01 2017 20:09


bug of network share

Postby michelangelo » Mon Dec 18 2017 12:59

Thanks for sharing this.

I think the only way to handle this without breaking compatibility is to make volumio try to mount with 2.0 option in case its rejected.
I will see and report back
User avatar
michelangelo
Founder
 
Posts: 4179
Joined: Sun Dec 15 2013 23:18


bug of network share

Postby 8point6 » Sat Dec 23 2017 10:08

Can confirm this addressed my mounting issues after spending some quality time troubleshooting.

Thanks for reporting this here and providing the bandaid, only found it because this has been added as a bug in github, so thanks all!

Hope this gets addressed for all others who might otherwise be stumbling around in silence.
Random avatar
8point6
Fresh off the boat
Fresh off the boat
 
Posts: 2
Joined: Sat Dec 23 2017 10:03


Return to Bug reports

Who is online

Users browsing this forum: No registered users and 0 guests