General NAS-Central Forums

Welcome to the NAS community
It is currently Fri Oct 20, 2017 3:27 am

All times are UTC




Post new topic Reply to topic  [ 17 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: Problem streaming videos
PostPosted: Wed Dec 21, 2016 10:34 am 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
I've been using the NSA325's Twonky for serving media for the last several years but about a year ago it started disconnecting shortly after starting to play any files. The screen would go black and the error would say that the device has disconnected. I'd got a Raspberry Pi shortly after this, originally for another reason, but I decided to put MiniDLNA on this and have it grab the files from the NSA325 via NFS. Works well enough but my LG smart TV seems to keep asking MiniDLNA what media it has available when it should be concentrating on streaming Netflix. This seems to cause a lot of unneccessary buffering which stops if I stop Minidlna. We got a bit annoyed by this and then I looked more into installing other packages on the NSA325, which is when I found Minidlna available. I think we've watched a few things via Minidlna on the NSA325 but now it's saying device disconnected just like it used to with Twonky. I've had an SSH session open at the time which was showing the top command and whilst it paused briefly, it recovered, so not entirely sure if it was a genuine loss of connectivity or not. Oddly, when I'm SSHing to the box it will sometimes appear to hang for 10 seconds or so before it continues, and I've never had that happen when SSHing to the Pi.

I checked minidlna.log and it shows;
minidlna.c:154: warn: received signal 15, good-bye

Is there any way to determine what's happening?


Top
 Profile  
 
 Post subject: Hard reset
PostPosted: Wed Dec 21, 2016 3:48 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
I'm considering a factory reset but would like to make sure I understand the process first. I installed ffp via Mijzelf's MetaRepository instead of the USB stick. Do I just disable ffp in the firmware/packages section in the admin section? Then hold down the power button until it beeps three times and once it's rebooted, enable ffp again? Would I then have to do that web_prefix thing (IIRC) again to activate MetaRepository?

Is that it? I'm not missing any steps?


Top
 Profile  
 
PostPosted: Wed Dec 21, 2016 8:01 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6048
leesspam wrote:
hold down the power button until it beeps three times
You shouldn't use the power button to reset, but the reset button on the back.

About the packages, all packages will be disabled at a factory reset. (A factory reset basically erases some internal flash partition. The 'enabled' flags are also stored there). You can simply re-enable them in the webinterface, including MR and FFP.

There is no need to disable them first, but it doesn't hurt either.


Top
 Profile  
 
PostPosted: Wed Dec 21, 2016 9:13 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
Thank you for the reply.

My other half has put on a movie and so far it's holding out but tomorrow evening if there's time I'll try the factory reset and over the course of the next few days report back in case it fixes the issue and is of help to others.


Top
 Profile  
 
PostPosted: Fri Dec 23, 2016 4:18 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
It appears to have done the trick. We have watched a couple of movies successfully so far with issue. I will post back if the issue rears it's head again. I was pleasantly surprised how little configuring I had to do after the reset!


Top
 Profile  
 
PostPosted: Wed Dec 28, 2016 9:44 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
Sadly, it has disconnected around 10 minutes into a video. I can resume straight away as usual and there's nothing mentioned in /ffp/var/log/minidlna.log. Open to suggestions again, please.


Top
 Profile  
 
PostPosted: Wed Dec 28, 2016 10:19 pm 
Offline

Joined: Sun Apr 29, 2012 5:24 pm
Posts: 2303
Is there a disconnecting problem with other devices too? I mean, if you are watching movies with PC via DLNA for example.
Have you latest minidlna package installed?


Top
 Profile  
 
PostPosted: Tue May 23, 2017 12:47 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
Hello again.

We have not used the NAS for watching things for a while now but we wanted something the other day and the issue occurred. Last night, I reset the NAS again and tried watching something and it only lasted a few minutes before it disconnected. After that, we continued it, resuming from where it left off and it went through to the finish. This was with minidlna still, the version that is mentioned in this forum. If you can tell me how I'd check I can find out for sure.

Ages ago, I was playing a movie via the TV and also streaming the same movie to a tablet. Both dlna, both stopped at the same time. Upon reading my original post I see my ssh connection hung for a moment on one occasion but then recovered. I know if I disconnect my wifi on the laptop and then reconnect it will recover from that easily enough so it is entirely possible it did drop connection somehow and then just reconnected. Maybe this is what is occasionally happening and its only really been noticeable when streaming. I don't know what would cause this though unless it's a failing NIC. And if it is, I'm not sure if I have many options.


Top
 Profile  
 
PostPosted: Tue May 23, 2017 5:57 pm 
Offline

Joined: Sun Apr 29, 2012 5:24 pm
Posts: 2303
Quote:
This was with minidlna still, the version that is mentioned in this forum
There is a lot minidlna versions mentioned in this forum. Which one exactly has you?
Code:
funpkg -q minidlna

Faulty NIC? Might be, but it is in rare cases. If were you, I would check network cables and especially connectors of them first. If your NAS is getting local IP automatically from DHCP server (router most likely), try to set manual IP for NAS. And vice versa, if it is currently set to manual, try to set auto. Retest each variant with minidlna.
If the problem still not solved, then wait until it occurs and right after that connect to NAS via ssh. Run these commands and paste outputs here:
Code:
/bin/dmesg

Code:
ifconfig -a
ethtool egiga0
ethtool -i egiga0
ethtool -S egiga0


Top
 Profile  
 
PostPosted: Wed May 24, 2017 12:54 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
I will find out what version it is a little later tonight when I'm home, and we'll try streaming again with those commands at the ready. I'd already alternated going from static to DHCP and it's not made any difference. Gut instinct is that it's not minidlna specific because I seem to recall the issue happening with Twonky which is why I installed minidlna on the Pi until I realised it was available for the NAS.


Top
 Profile  
 
PostPosted: Fri May 26, 2017 6:44 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
Code:
See below;

#######################################
---> HD1 back to green on, off blink
program smartd is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartd is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartd is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartd is using a deprecated SCSI ioctl, please convert it to SG_IO

***************************************
*            HD0 stand by now!        *
***************************************
---> blink LED0 for disk1 to green.

***************************************
*            HD1 stand by now!        *
***************************************
---> blink LED2 for disk2 to green.

#######################################
#              HD1 awaked by minidlna !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

#######################################
#              HD0 awaked by minidlna  !        #
#######################################
---> HD0 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************
---> blink LED0 for disk1 to green.

***************************************
*            HD1 stand by now!        *
***************************************
---> blink LED2 for disk2 to green.

#######################################
#              HD0 awaked by minidlna  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by minidlna !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink
egiga0    Link encap:Ethernet  HWaddr EC:43:F6:AA:75:D4 
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2513661 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13384134 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:206980849 (197.3 MiB)  TX bytes:2532444977 (2.3 GiB)
          Interrupt:11

ip6tnl0   Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          NOARP  MTU:1460  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:24980 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24980 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9026946 (8.6 MiB)  TX bytes:9026946 (8.6 MiB)

sit0      Link encap:IPv6-in-IPv4 
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Settings for egiga0:
   Supported ports: [ TP MII ]
   Supported link modes:   10baseT/Half 10baseT/Full
                           100baseT/Half 100baseT/Full
                           1000baseT/Half 1000baseT/Full
   Supports auto-negotiation: Yes
   Advertised link modes:  10baseT/Half 10baseT/Full
                           100baseT/Half 100baseT/Full
                           1000baseT/Half 1000baseT/Full
   Advertised auto-negotiation: Yes
   Speed: 100Mb/s
   Duplex: Full
   Port: MII
   PHYAD: 1
   Transceiver: internal
   Auto-negotiation: on
   Link detected: yes
minidlna-1.1.6_git20161102-arm-1


Top
 Profile  
 
PostPosted: Sat May 27, 2017 7:46 pm 
Offline

Joined: Sun Apr 29, 2012 5:24 pm
Posts: 2303
First of all, your pasted dmesg output is useless, because you pasted only last lines instead of full output. This can be very important, so better redirect all dmesg output to file:
Code:
/bin/dmesg >> /i-data/md0/public/dmesg.log

Content of dmesg.log can be long, so please paste it somewhere on net, pastebin.com for example and link here.
Secondly, I don't see outputs of these commands in your post:
Code:
ethtool -i egiga0
ethtool -S egiga0

Thirdly is related with first one. Do it right after the problem occurs.


Top
 Profile  
 
PostPosted: Mon May 29, 2017 9:06 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
The NAS drops out for a few seconds because ssh is unresponsive but I had a script queued and as soon as it came back I pressed return and the results are in https://pastebin.com/YSVZq4c1


Top
 Profile  
 
PostPosted: Tue May 30, 2017 7:40 pm 
Offline

Joined: Sun Apr 29, 2012 5:24 pm
Posts: 2303
I see no boot info in your dmesg output again. Do next time this way-reboot NAS and repeat:
Code:
/bin/dmesg >> /i-data/md0/public/dmesg_new.log

When a problem occurs better run:
Code:
ethtool -S egiga0

BTW. Do you checked cable?


Top
 Profile  
 
PostPosted: Mon Aug 14, 2017 9:23 pm 
Offline

Joined: Wed Sep 24, 2014 3:48 pm
Posts: 14
Hi barmalej2

Have not been watching things via the NAS for a long time so forgot about this post. The results of your request are in https://pastebin.com/5zb3L2At

The results of ethtool -S egiga0 are;

    NIC statistics:
    skb_alloc_fail: 0
    tx_timeout: 0
    tx_netif_stop: 0
    tx_done_netif_wake: 0
    tx_skb_no_headroom: 0

Running fsck -n /dev/md0 gives;

Code:
fsck from util-linux 2.20
e2fsck 1.41.14 (22-Dec-2010)
Warning!  /dev/md0 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/md0 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (63431156, counted=63382924).
Fix? no

Free inodes count wrong (121935559, counted=121935555).
Fix? no


/dev/md0: ********** WARNING: Filesystem still has errors **********

/dev/md0: 133433/122068992 files (12.3% non-contiguous), 424818042/488249198 blocks

Running fdisk -l gives;

Code:
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x525001c1

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63     1028159      514048+   8  AIX
/dev/sda2         1028160  3907024064  1952997952+  20  Unknown

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xdf45b514

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63     1028159      514048+  83  Linux
/dev/sdb2         1028160  3907024064  1952997952+  20  Unknown

Disk /dev/md0: 1999.9 GB, 1999868715008 bytes
2 heads, 4 sectors/track, 488249198 cylinders, total 3905993584 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

[color=#FF0040]Disk /dev/md0 doesn't contain a valid partition table[/color]

Disk /dev/sdc: 500.1 GB, 500107860992 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773166 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe544dff5

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048   976769023   488383488    7  HPFS/NTFS/exFAT


Looks like file system errors (highlighted). How would I go about fixing them? Am I likely to lose files?

EDIT: No, haven't tried a new cable because the current one goes through the wall, it's a tight fit and I don't have another sufficiently long. The output from the ethtool command has always shown 0.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 17 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: Bing [Bot] and 64 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group