Recent content by Klyken

I thought I'd add this for reference as a setup I haven't had any issues with so far (and it's been a few months) WD Red 3TB on NTFS via a Plugable USB 3.0 Lay-Flat Docking Station (ASMedia ASM1053E Chipset).

NTFS is read write, but it's been said to work best with up to 1TB drives and I've not had any real issues with mine over SAMBA on the N66U.

With a mention of USB changes I thought I'd give this a try over the top of Beta 1. No change with SDK6 DLNA stuttering, but transfer speeds over usb/samba are now very usable up to 14MB/s compared to lows of KB/s on SDK5. I have less reasons to unmount and switch the dock over to eSATA now...

I think you have your wires crossed there. You only need to label (unique,no spaces) once. Mounts are then tmp/mnt/Label instead of dynamic tmp/mnt/sd..

As far as MiniDLNA goes it seems the same as previous SDK6 releases for stuttering on the N66U it doesn't seem to matter if the MiniDLNA is the internal version or an external version on debian entware. EDIT: Despite that I think I'm going to stick with this firmware and perhaps buy a...

Is there an equally simple command based alternative for Intranet/LAN only by IP?

Cheers for posting that human read and edit friendly example Martineau.

Seems ok I can't comment on the unslung, but looking at your minidlna config path. It would be better to label the storage as it might not be mounted as sda1 each time. Preferably use a no spaces label like Media unfortunately that change will require a rescan and updated paths in...

There are two minidlna threads on the next page which should cover it. Best to eject the drive really and in summary you need to disable in the web ui and manual start it without the -R switch in the command.

It never ceases to amaze me how quickly you get these releases out even after you've said you're taking a break. I hope you can work some magic on the minidlna performance too this is the only thing keeping me on sdk5 now. The connection to the TV is fully wired. I don't know what else to...

'hide unreadable' just seems to be ignored I tested it in /jffs/configs/smb.conf in various positions. I don't know if has little or anything to do with, but I thought I'd mention this was on 3.0.0.4.374.36_beta1-sdk5 in case someone else wants to try it on their firmware.

The commands are like this /usr/sbin/minidlna -f /path/to/minidlna.conf or if you want to rebuild the database at start. /usr/sbin/minidlna -R -f /path/to/minidlna.conf These are the default paths /tmp/etc/minidlna.conf /var/cache/minidlna/files.db /var/cache/minidlna/minidlna.log...

I tried this I could see the line appended, but it didn't make any difference. I also tried veto files. An edited /jffs/configs/smb.conf did, but I was after something a bit less disk dependent. Reading some info on samba it should rescan smb.conf so I removed the jffs/configs override and...

This definitely seems to be related to nas apps I've rarely seen this issue, but it started straight away once I started experimenting with umount and mount disk not knowing that I was then on my own for starting and stopping nasapps. It seems the only way to get the ducks back in line is...

I only figured out this issue recently basically you need to manual start minidlna without the rescan switch to replicate how it functioned on 270.26b manually or with a script like in this post http://forums.smallnetbuilder.com/showpost.php?p=49586&postcount=5 from this thread...