Can explore shared drive but cant copy or stream files

[linenoise]

Hi everyone I tried to search the forum for a similar issue but haven't been able to find anything.  Hopefully someone here can help.

 

Issue: 

I can access the shares through windows explorer, list directories.  Unraid has worked without issue for years then a few days ago I started to have problems streaming or even copying files through Windows explorrer/ SMB.   I can view .txt files but anything that requires processing a format such as a video, pdf. mp3. wont play.  The files attempt to open then either times out or in the case of videos plays about 1 second of video and audio then gives the 0x8007003b error when using windows media player.  Using VLC just times out.  When trying to mount a drive in windows 10 the shared drives show up when browsing Unraid directories for a few seconds then disappears.  When trying to copy files the file tries to transfer shows the transfer graph then times out.  This behavior is also seen on other windows 10 computers as well as Nvidia shield.  Now for the strange behavior, when accessing files through plex, media files stream fine, it seems to be when accessing the files remotely not when there is a docker aka plex serving the media.  Another strange while running Tools > "Docker Safe new permissions"  file streaming works fine as long as it is running regardless of the file it is currently changing.  I was able to duplicate this while running Tools > New Permissions.  The moment the file permissions script stops running the streaming stops.  It appears that a few bytes of data is transferred but then somthing happens to stop the transfer.  If the data file is small during the time the connection is up such as txt file it copies/opens fine, video will get a few frames across.

 

What I have done:

• Reboot Unraid server several times.
• Reboot windows machine several times
• ran docker safe new permissions
• rand tools > new permissions
• tried playing videos with Windows media player, VLC, media player classic
• Plex, Emby work fine running from unraid docker on Windows machine/ Nvidia shields
• Ran Fix common problems - came back clean
• Check file permissions all have user nobody 0777 

 

I am getting some errors in the syslog, see below with one particular error that jumped out at me.   I saw the write file error for /boot/config/super.dat and backuppc.cfg but wasnt sure I should change file permissions in these directories.  they have the following permission

 

drwx------  2 root root  8192 Nov 22  2019 shares/

 

I have attached my diagnostic dump.

 

tower-diagnostics-20201116-1814.zip

ov 16 14:43:43 Tower kernel: sd 0:0:0:0: [sda] Write Protect is on
Nov 16 14:44:14 Tower emhttpd: error: put_config, 589: Read-only file system (30): fopen: /boot/config/ident.cfg
Nov 16 14:44:22 Tower kernel: write_file: error 30 opening /boot/config/super.dat
Nov 16 14:44:22 Tower emhttpd: error: put_disk_settings, 3546: Read-only file system (30): fopen: /boot/config/disk.cfg
Nov 16 14:44:23 Tower kernel: write_file: error 30 opening /boot/config/super.dat
Nov 16 14:47:22 Tower kernel: write_file: error 30 opening /boot/config/super.dat
Nov 16 14:47:22 Tower emhttpd: error: put_disk_settings, 3546: Read-only file system (30): fopen: /boot/config/disk.cfg
Nov 16 14:47:58 Tower emhttpd: error: put_disk_settings, 3546: Read-only file system (30): fopen: /boot/config/disk.cfg
Nov 16 14:47:59 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:47:59 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:29 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:33 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:33 Tower kernel: write_file: error 30 opening /boot/config/super.dat
Nov 16 14:48:39 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:42 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:46 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:49 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:52 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:56 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:48:59 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:03 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:06 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:10 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:13 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:16 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:20 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:23 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:27 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:30 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:33 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:37 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:40 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:44 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:47 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:50 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:54 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:49:57 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:01 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:04 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:08 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:11 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:14 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:18 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:21 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:25 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:28 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg
Nov 16 14:50:31 Tower emhttpd: error: put_config_idx, 619: Read-only file system (30): fopen: /boot/config/shares/backuppc.cfg

 

 

Thanks

 

Linenoise

Edited November 17, 2020 by linenoise

[trurl]

On mobile now so can't look at Diagnostics yet. 

 

9 minutes ago, linenoise said:

errors in the syslog, see below

You obviously have a flash problem. 

 

Put in your PC and let it check disk. While there make a backup. 

 

Reboot and see what happens 

[linenoise]

Thanks, I'll do that in the morning, I did have several ungraceful shutdowns.

 

Linenoise

[trurl]

12 hours ago, linenoise said:

I did have several ungraceful shutdowns.

Be sure to let parity check complete and if there are parity errors run a correcting parity check. The only acceptable result is exactly zero sync errors and until you get that result you haven't finished fixing things.

[linenoise]

14 hours ago, trurl said:

On mobile now so can't look at Diagnostics yet. 

 

You obviously have a flash problem. 

 

Put in your PC and let it check disk. While there make a backup. 

 

Reboot and see what happens 

I tried to place the unraid boot usb into my windows machine and it did pop up with errors, but when I try to run run "correct errors" it fails and says the drive is read only.  When I bring up properties for the usb drive it is missing the security tab.  Anyway to make the drive read/write?  This is a micro usb and there is no mechanical write protect switch on it.

[trurl]

Were you able to make a backup of it?

[linenoise]

I tried several methods I found on the internet but couldn't remove the write only, even using partitioning tools.  I ended up getting a new USB drive, based on a video from space invader one.  Backedup and restored onto the new USB drive, got a new Unraid licence.  Now everything is working greate.  It all came down to the USB not being write only.  The drive was probably on its way out.  It would be a nice feature for unraid to have a failover usb option similar to freeNAS.

 

Thanks Constructor for the help and pointing me in the right direction about the USB.

 

Linenoise