I am trying to use openwrt with my DIR-860L as a DLNA Server.
So far the DLNA is working. But the USB Drive with the Media Files on it can't go to standby or it wakes up from standby just seconds after it went into standby.
This depends on which external USB HDD Case I use.
The LED of the HDD case shows if its
active (LED ON)
or
in standby (LED OFF).
In Standby the Power Consumption is very low, therefore thats what I want.
I have 2 different types of these USB 2.5" external HDD cases.
One sends the Drive into standby just after a few minutes without access.
The other one doesn't do that and so the drive remains active all time.
This works wherever I connect the external cases to.
It does not depend on the actual drive that is used.
It also worked with the DIR-860L before changing the Firmware to openwrt. With openwrt the case which puts the HDD to sleep
is somehow triggert to wake it up again only a few seconds after it went into standby. Every time....
The System and Kernel Log do not show any entries at that time.
Also there is no access through lan. I even disconnected all lan cables and still it happens the same way. W-LAN is also off.
I installed openwrt with only few additional packages for USB, NTFS and DLNA to work.
I was wondering if somebody had a clue which option or package could be responsible for this behavior. Or how I could find out what triggers this.
I am new to oprenwrt but so far manged to get it working.
Unfortunately I only achieved the total opposite of what I was looking for. I wanted a better standby not a worse.
It was working very good for many years on my old DIR-645 but that one is too slow now.
The DIR-860L is faster, but for some reason with the original Firmware it wakes up the USB Drive from Standby every hour.
Probably because the TV checks if the DLNA-Server is still there.
I was trying to solve this by using openwrt. But so far its no improvement.
The Problem is solved.
One of the USB Packages was the Problem.
I guess it was this "block-mount" Package.
I tried what wulfy23 suggested, to remove packages one by one. It turned out to be a really bad idea to do this if you have no clue what the packages are needed for.
Therefore I can only recommend to everybody never to do that.
Here is why:
After a few packages were removed, I noticed that something was not working anymore. So I thought, no Problem, just make a Reset and start all over (I did that before).
But:
The Reset (probably also performed by one of the packages) was not working anymore. Most likely because it was a Package I already removed. ... so what now ?
The Router wasn't working anymore.
The Reset wasn't working anymore.
The Router was unable to Start.
Good thing there is an Emergency Option to Flash New Image.
Otherwise the Router would have been dead.
So solved after all and learned a lot of new things
it's the toggling of them one by one that is beneficial
Yes, "block-mount" or /etc/config/fstab may play a role in how your OS interacts with disks. That is what it is there for and i'm glad you were able to zero in on it ( without help! )
Also for clarity, anyone reading this at a later date should note that editing /etc/config/fstab should be sufficient.... There should be no need to remove it.
