Readynas 104 gives errors during playback via VLC.

mdgm wrote:
What kind of network bond were you using?

I used IEEE 802.3ad LACP. I basically followed the instructions in this post:

http://www.primitivebuteffective.com/20 ... -link.html

Allthough it points to a S*nology NAS, the settings are basically the same, and it has worked perfectly.

And as I said, turning of the bond, hasn't removed the error.

I'll keep looking for causes, there must be some way to track down this error.

Teaming is enabled on my pro-6 (also LACP).

Generally I only see "bad file descriptors" from VLC when I sleep my laptop with VLC open. The messages show up when I wake up the machine, and resume playback again. I haven't seen mid-stream issues with the RN102 either, though that is really used for backup.

Anyway, it sounds like the PC is somehow losing the connection to the NAS. If you keep a windows explorer pane open to the media directory, can you still see the files when the problem occurs?

Is the PC a laptop or desktop? If its a laptop, are both ethernet and wifi enabled?

StephenB wrote:

Teaming is enabled on my pro-6 (also LACP). Generally I only see "bad file descriptors" from VLC when I sleep my laptop with VLC open. The messages show up when I wake up the machine, and resume playback again. I haven't seen mid-stream issues with the RN102 either, though that is really used for backup. Anyway, it sounds like the PC is somehow losing the connection to the NAS. If you keep a windows explorer pane open to the media directory, can you still see the files when the problem occurs? Is the PC a laptop or desktop? If its a laptop, are both ethernet and wifi enabled?

The computer is a desktop machine with Gigabit ethernet connectivity. I allways have full access to the net and the NAS. I can see all the files while VLC fails, the connection is allways rock solid stable. I can transfer hundreds of gigabyte to and from the NAS, without errors.
And as mentioned earlier, playback with VLC with files on my NV+, on the same computer, through the same network cable, from the same network switch, is _allways_ without errors.

I think that this makes it unlikely that the problem is with the PC or the network connection.

As it seems no-one else experiences this error, I guess I'll have to live with it. Will probably have to replace this NAS with something else, and throw it out.

Perhaps its time for a FreeNas build (or something like that). I work in IT as a profession, so I think I know what I'm doing. It should be easy for me to build such a setup.

I wasn't meaning to imply your network (or your PC) was at fault.

Perhaps the newer kernel in 6.3.3 will help (I'm not necessarily suggesting that you install it, though I haven't had any issues with it running on my RN202).

StephenB wrote:
I wasn't meaning to imply your network (or your PC) was at fault. Perhaps the newer kernel in 6.3.3 will help (I'm not necessarily suggesting that you install it, though I haven't had any issues with it running on my RN202).

Didn't now the early release was available for the arm based NAS'es.

Will try the 6.3.3 Beta 9 to see if it solves anything.

Well, 6.3.3 didnt help.

It works fine but the error still persists.

Have been able to actually force the error to show itself, I think.

Playing a video with VLC, if I at the same time log into the web interface, the "Bad file descriptor" message will apear, and playback will stop.

It seems to be an internal problem with the nas, not being able to keep up with the requested data, when its doing other tasks.

These are not high bitrate files I'm trying to play, this time it was a 50 minutes episode of a series, of approx 400MB. Not something that should make this NAS have the least problems keeping up the data stream.

I have been searching for more answers.

First, VLC has a build in caching, that can be changed to adress network buffering pausing errors. Elevating this to 1 second or even 10 seconds doesnt help. I can see it buffering at the start of a video (but for less than 2 seconds(depending on the size of the video)), when the buffer is set at 10 seconds, but still I get the errors.

Searching a little more for the "Bad file descriptor" error, some peoble have found that this is an access rights issue. They get the error when they try to access files on a share where they have lost their priviliges to access files.
Allthough I wonder what happens, this could be the case here, if the NAS revokes the access momentarily to the files I'm streaming. I just wonder why I never see the error in daily use then.And I never have a problem restarting playback.
But perhaps some bug in SMB access is present, where the NAS momentarily removes access to files, even when there should be access.

I'm really into deep water here, it seems there is nothing I can do about the error.

Seems scheduled power off / on doesn't work on 6.3.3

Tha NAS hung itself somewhere during shutdown with a message in the display about "Shutting down, goodbye".

So naturally the NAS didn't power on at the set time.

I am installing 6.2.3 Beta 9 ATM. Since 6.3.3. didn't help on my problem, I think this is a little bit safer.

On your main problem, have you tried a different player? It might give more useful error messages???

No. VLC is normally my player of choice.

But I will try e.g. Windows Media Player or some other player.

This could turn out to be a bug with VLC, allthough I doubt it since playback works with VLC and files on my NV+.