RT-AC68U and external HDD

[gjf]

Hi All!

As I reported earlier I am extremely unhappy with the way latest Merlin firmware works with external HDD.

I am using latest firmware (not beta) and 1 Tb HDD connected via USB 3.0 to RT AC-68U.

It looks like te device has not enough memory to check HDD. Also the HDD is marked red because of "errors", when I try to open scanner it shows a message "Fail to get the log of fsck!"

Anyway scanning does not show results except the information about "errors", the log contains the following:

Jun 29 13:13:45 rc_service: disk_monitor 1001:notify_rc start_samba
Jun 29 13:13:45 rc_service: disk_monitor 1001:notify_rc start_dms
Jun 29 13:13:45 rc_service: waitting "start_samba" via disk_monitor ...
Jun 29 13:13:46 kernel: gro enabled with interval 2
Jun 29 13:13:48 Samba Server: daemon is started
Jun 29 13:13:48 rc_service: disk_monitor 1001:notify_rc start_mt_daapd
Jun 29 13:13:48 rc_service: waitting "start_dms" via disk_monitor ...
Jun 29 13:13:49 disk monitor: done


Today I observed also a total mess in syslog (attached).

When I connect HDD to PC and check it - there is no any error.

Please note the old driver (I cannot remember the version of Merlin firmware, but it was a really long ago) did not give me any trouble.

My questions are:

1. How to make it work normally with my HDD? There is no documented restrictions with 1 Tb size, so what is wrong?

2. If the problem cannot be solved - how to totally disable fsck to overcome stupid logging and even more stupid marking of "problem with HDD".

 

[pete y testing]

1. How to make it work normally with my HDD?

simple answer buy a NAS

minidlna is always going to be problematic

usb is a waste of time as a data sharing feature

 

[gjf]

Thank you, man.
Please write it to Asus to remove the feature at all.
Also, please buy a dedicated DNS server, a dedicated OpenVPN server, a dedicated QoS etc. Certainly it will work much better.

Any more smart answers, please?

 

[RMerlin]

That error message seems to come from the USB printer daemon "u2ec" and not from the disk sharing code.

The issue is not the size, as I was doing my original tests with a 3 TB HDD.

 

[gjf]

But what is the issue in my case?
Maybe number of files? I ahve a lot of them, including multimedia - some conflict with UPnP?
I would be happy to provide any additional info to solve this issue finally!

 

[Yiannis]

I have connected a 1TB external hard disk for the past weeks. I am pretty happy with the stability.

I had no problems using it. I basically store kids movies and stream them at the Apple TV 4 without any issues.

I am pretty disappointed with the USB3 speeds. Maximum read speed was about 15-20MB/s . (Although this seems to be common problem , others have reported much higher speeds )

On my setup I only have active the "network place (samba) share"
All others USB related features are deactivated. I try to follow a minimal approach in terms of features.

I do remember that when I first bought the router, I had huge problems with the same disk on the Asus stock firmware.

I tried Merlin and never went back.

 

[gjf]

That error message seems to come from the USB printer daemon "u2ec" and not from the disk sharing code.

The issue is not the size, as I was doing my original tests with a 3 TB HDD.

May I ask what is the model of 3 Tb HDD you have used for tests?

 

[latenitetech]

Somewhat old thread, but for those having problems, have you installed a swap file? I'm running 2x 256G flash drives on my RT-AC68U, both primarily contain media files served up by minidlna and pyTivo. I was having numerous problems both with minidlna completing its database creation, and running fsck on those drives before I installed a 512M swap file. That cured all my problems (well, at least related to this).

Just as an observation, I see 450G+ of swap being used during the minidlna database creation, so that tells me it really needed it.

 

[gjf]

Me not. And it would be nice to know details how did you do it.

Actually I would like to add swap as well as entware/optware, but I understand that I need to re-format my HDD into ext3. With about 900 Gb data stored at 1 Tb HDD it is impossible, and unfortunately I cannot find a spare 1 Tb HDD to backup data, format initial one and copy data back.
That's why I am looking for a new HDD with bigger capacity.
I understand possible power problems - that's why I think external HDD with additional power supply is needed.
Also I understand some HDD does not allow to create ext3 partitions because of controller limitations (but allow a lot of unnecessary stuff like crypting and backing up).
That's why I would like to have some recommendations about possible reliable models. I have seen Verbatim Store n Save SuperSpeed USB 3.0 4 Tb with Seagate HDD on board - any ideas about that?

 

[gjf]

By the way I found a possible problem with my HDD.
It was really caused by minidlna: it creates a art_cache and some files obtain >256 symbols path.
Just found them and manually deleted.
It's too bad and annoying. Also I have found the following trick for minidlna - any comments on it?

 

[RMerlin]

May I ask what is the model of 3 Tb HDD you have used for tests?

WD Caviar green 3 TB, inside a Vantec enclosure (can't remember the exact model, I'm not at home to check right now, was probably a CX).

 

[latenitetech]

By the way I found a possible problem with my HDD.
It was really caused by minidlna: it creates a art_cache and some files obtain >256 symbols path.
Just found them and manually deleted.
It's too bad and annoying. Also I have found the following trick for minidlna - any comments on it?

I have several suggestions I can offer in this space. I spent quite a bit of time really understanding what was happening with minidlna, and then created a Wiki article describing my findings and recommendations. Take a look at it here: https://github.com/RMerl/asuswrt-merlin/wiki/Minidlna:--Common-Issues-&-Solutions

I suspect you're hitting up against two of the three issues I explain in that article.

I also have some recommendations on getting a required Linux file system so you can install entware and a swapfile, but I'll include that in a separate post.

 

[latenitetech]

Me not. And it would be nice to know details how did you do it.

Actually I would like to add swap as well as entware/optware, but I understand that I need to re-format my HDD into ext3. With about 900 Gb data stored at 1 Tb HDD it is impossible, and unfortunately I cannot find a spare 1 Tb HDD to backup data, format initial one and copy data back.

I don't recommend reformatting an entire external HDD to EXT3. All you really need is a ~4G Linux filesystem for entware, swap, your minidlna database, and perhaps other application files. The easiest way to get that is format a small flashdrive EXT2 and you're done.

Now a downside to that approach is that you probably want both that flashdrive, and your external HDD on USB3 for maximum speed. Unfortunately, the router doesn't support USB3 hubs (they only work at USB2 speeds, even on the USB3 port). So you could move the HDD to the USB2 port, and then plug a USB3 flashdrive in the USB3 port and that might work OK for your needs.

The other trick I've seen done (and this is what I did on one my 256G USB3 flash drives), shrink the existing Windows partition already on the drive by ~4G, then create a small Linux partition in the freed-up space. Note, it's important to put the Linux partition at the tail of the drive for the drive to still be recognized on a Windows box. The free 'MiniTool Partition Wizard' does a great job with this, and only takes a few minutes. It will not affect the current content on the HDD.

Once you have that Linux partition available, this Wiki article covers installing both entware and a swapfile at the same time: https://www.hqt.ro/how-to-install-new-generation-entware/

One final caveat - I don't think the "shrink existing partition" trick will work on certain external USB3 HDDs, especially ones over 2T in size. They typically employ a hardware trick to allow the drive to run on old OSs (e.g WinXP), making the drive appear like an 'old-style' MBR disk. I don't think you'll run into that problem with your 1T drive though.

Good luck! Let us know how it works out for you.

 

[gjf]

I cannot use USB flash drive because the second USB port is used for printer.
So I am going to add ext3 partition at the end of my current HDD.
Do I understand correctly both partitions - first NTFS and last ext3 - should be primary or I should make ext3 as a logical partition?

 

[latenitetech]

They should both be primary.

 

[gjf]

And one more question.
My HDD effectively uses spinning down feature (when Download Master is disabled of course).
Will enabling swap affect on this? I like spinning down as I believe it prolongs lifetime of my drive, but as far as I see from the manuals spinning down is not compatible with swap.

 

[latenitetech]

Hmm, hadn't thought about that. Yes, I could imagine having swap on an HDD that spins down could be problematic. By design, swap needs to be fast, and always available. Perhaps others could chime in on this issue, as I don't have any experience with other than flashdrives on my router.

If it turns out spin-down and swap are incompatible, then I think your options are either disable spin-down, or use a flashdrive for your Linux partition. The router does a good job supporting USB2 hubs, and I'd be very surprised if you had any issue with putting a USB hub on the USB2 port with your printer and a storage device. And I would tend to opt for moving your 1T HDD to the USB2 hub, leaving the USB3 port available for a fast USB3 flashdrive (to give maximum speed to the swap file).

If you don't get any more recommendations on this thread, you might just have to do some trial and error and see what works best.

 

[gjf]

Sorry, but it looks like using USB stick via USB hub together with printer is a really bad idea. And I suspect USB hub is a bad idea at all.
I don't want to connect HDD via USB2.0 because I need a fast storage in my home network.
But USB2.0 seems working bad with hub: the stick works about 10-15 minutes with errors after that:

Spoiler: Logs

Jan 13 02:18:19 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:19 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:19 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:19 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:19 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:20 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:20 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 00 80 00 00 08 00
Jan 13 02:18:20 kernel: end_request: I/O error, dev sda, sector 128
Jan 13 02:18:20 kernel: Buffer I/O error on device sda1, logical block 0
Jan 13 02:18:20 kernel: lost page write due to I/O error on sda1
Jan 13 02:18:20 kernel: EXT2-fs (sda1): error: ext2_readdir: bad page in #2
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:20 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:20 kernel: EXT2-fs (sda1): previous I/O error to superblock detected
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:20 kernel: sd 1:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 00 80 00 00 08 00
Jan 13 02:18:20 kernel: end_request: I/O error, dev sda, sector 128
Jan 13 02:18:20 kernel: Buffer I/O error on device sda1, logical block 0
Jan 13 02:18:20 kernel: lost page write due to I/O error on sda1
Jan 13 02:18:20 kernel: EXT2-fs (sda1): error: ext2_readdir: bad page in #2
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:29 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:29 kernel: EXT2-fs (sda1): previous I/O error to superblock detected
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:29 kernel: sd 1:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 00 80 00 00 08 00
Jan 13 02:18:29 kernel: end_request: I/O error, dev sda, sector 128
Jan 13 02:18:29 kernel: Buffer I/O error on device sda1, logical block 0
Jan 13 02:18:29 kernel: lost page write due to I/O error on sda1
Jan 13 02:18:29 kernel: EXT2-fs (sda1): error: ext2_readdir: bad page in #2
Jan 13 02:18:29 sd-idle-2.6[367]: spinning up /dev/sda after 30 secs
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:30 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:30 kernel: EXT2-fs (sda1): previous I/O error to superblock detected
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:30 kernel: sd 1:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 00 80 00 00 08 00
Jan 13 02:18:30 kernel: end_request: I/O error, dev sda, sector 128
Jan 13 02:18:30 kernel: Buffer I/O error on device sda1, logical block 0
Jan 13 02:18:30 kernel: lost page write due to I/O error on sda1
Jan 13 02:18:30 kernel: EXT2-fs (sda1): error: ext2_readdir: bad page in #2
Jan 13 02:18:38 rc_service: httpd 454:notify_rc restart_media
Jan 13 02:18:40 iTunes: daemon is stopped
Jan 13 02:18:40 custom script: Running /jffs/scripts/minidlna.postconf (args: /etc/minidlna.conf)
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:43 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:43 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:43 kernel: EXT2-fs (sda1): previous I/O error to superblock detected
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:43 kernel: sd 1:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 00 80 00 00 08 00
Jan 13 02:18:43 kernel: end_request: I/O error, dev sda, sector 128
Jan 13 02:18:43 kernel: Buffer I/O error on device sda1, logical block 0
Jan 13 02:18:43 kernel: lost page write due to I/O error on sda1
Jan 13 02:18:43 kernel: EXT2-fs (sda1): error: ext2_readdir: bad page in #2
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] CDB: Read(10): 28 00 00 00 17 f8 00 00 08 00
Jan 13 02:18:44 kernel: end_request: I/O error, dev sda, sector 6136
Jan 13 02:18:44 kernel: EXT2-fs (sda1): previous I/O error to superblock detected
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] Device not ready
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 13 02:18:44 kernel: sd 1:0:0:0: [sda] Sense Key : Not Ready [current]
Jan 13 02:18:45 kernel: sd 1:0:0:0: [sda] Add. Sense: Medium not present
Jan 13 02:18:45 kernel: sd 1:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 00 80 00 00 08 00
Jan 13 02:18:45 kernel: end_request: I/O error, dev sda, sector 128
Jan 13 02:18:45 kernel: Buffer I/O error on device sda1, logical block 0
Jan 13 02:18:45 kernel: lost page write due to I/O error on sda1
Jan 13 02:18:45 kernel: EXT2-fs (sda1): error: ext2_readdir: bad page in #2

So it's not possible to use it for even for Entware, forget about swap at all!

 

[gjf]

And what have I done: I have combined your trick and the one I have mentioned above (and which is completely stupid because it doesn't change strings in /etc/minidlna.conf but doubling them).

So I put the following minidlna.conf.base file at my HDD:

Spoiler: minidlna.conf.base

# base custom minidlna config file (minidlna.conf.base)
#
# friendly_name, media_dir and other system fields are extracted by postconf
# script from system-generated minidlna.conf and appended to this file, then
# postconf script replaces the system-generated file with the newly created one
#
#db_dir=/opt/minidlna
# Move the database to the tmp directory (ramdisk, will be recreated on reboot !!)
db_dir=/tmp/.minidlna
enable_tivo=no
strict_dlna=no
inotify=yes
notify_interval=600
#album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
# disable album art indexing
album_art_names=NO_ALBUM_ARTS.x
#root_container=B
#create a custom minidlna logfile
log_dir=/var/log

And then I put the following minidlna.postconf at /jffs/scripts with corresponding permissions:

Spoiler: minidlna.postconf

#!/bin/sh

# minidlna.postconf script (to be placed in /jffs/scripts)
# Checks for existence of required files/directories before allowing minidlna to start normally.
# If anything is missing (e.g. a required volume hasn't mounted yet), this script ensures there won't
# be a .conf file (under /etc) available when the system auto-starts minidlna, so it will just abort
# rather than try to start without all required resources available.
#
# Once all files/directories are available, a custom conf file is created by combining the base custom conf file
# with key fields extracted from the system-generated conf file. The custom conf file is then installed
# allowing minidlna to start. The key fields extracted are those which are set by the router's Web GUI,
# thereby retaining full Web GUI functionality transparent to the end-user.

# user directory for minidlna related files (must reside on a Linux storage volume)

MDLNA_DIR=/tmp/.minidlna
SETDIR=/mnt/VERBATIM_HD/.minidlna

CONF=minidlna.conf
BASECONF=$SETDIR/$CONF.base
SYSCONF=/etc/$CONF.system
MRGCONF=$SETDIR/.$CONF.merged

# rename the system-generated conf file; this is what causes minidlna startup to abort if all required
# resources aren't available and we haven't supplied a custom .conf file in its place
mv /etc/$CONF $SYSCONF

# Look for availability of required files/directories: BASECONF check ensures entware volume is mounted,
# as well as the base conf file is available, as it's critical in this scheme.
# The nvram part verifies all media_dirs are available (it returns all the media directories entered thru
# the web GUI), and it's ultimately what gets loaded in the 'final' system-generated .conf file we use
# to build the final custom .conf file.
for n in $BASECONF `nvram get dms_dir_x | tr \< " "`
do
if [ ! -e "$n" ] ; then
logger "$0:" "WARNING: $n not found, forcing abort of minidlna startup."
exit 1
fi
done

# should be good to go - create custom minidlna.conf file
echo "# Custom generated $CONF file by $0. DO NOT EDIT THIS FILE." > $MRGCONF
grep -v \# $BASECONF >> $MRGCONF
grep "network_interface=" $SYSCONF >> $MRGCONF
grep "port=" $SYSCONF >> $MRGCONF
grep "presentation_url=" $SYSCONF >> $MRGCONF
grep "friendly_name=" $SYSCONF >> $MRGCONF
grep "media_dir=" $SYSCONF >> $MRGCONF
grep "serial=" $SYSCONF >> $MRGCONF
grep "model_number=" $SYSCONF >> $MRGCONF

logger "$0:" "Installing custom $CONF in /etc"
cp $MRGCONF /etc/$CONF

exit $?

As for now postconf script changes minidlna.conf in such way so the db is creating at /tmp and no caching images occures.

Will see on results.

 

[gjf]

Ah, crap - same errors while scanning HDD:

Spoiler: Errors log

ntfsck 3014.5.21
Checking NTFS Superblock ...
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 512 bytes
Current volume size: 1000202043392 bytes (1000203 MB)
Current device size: 1000202043392 bytes (1000203 MB)
Checking for bad sectors ...
Scanning $MFT ...
Checking directory structure ...
Checking for orphaned files ...
0.00 percent completed
0.23 percent completed
0.46 percent completed
0.69 percent completed
0.91 percent completed
1.14 percent completed
1.37 percent completed
1.60 percent completed
1.83 percent completed
2.06 percent completed
2.28 percent completed
2.51 percent completed
2.74 percent completed
2.97 percent completed
3.20 percent completed
3.43 percent completed
3.66 percent completed
3.88 percent completed
4.11 percent completed
4.34 percent completed
4.57 percent completed
4.80 percent completed
............................................
95.03 percent completed
95.26 percent completed
95.49 percent completed
95.72 percent completed
95.95 percent completed
96.17 percent completed
96.40 percent completed
96.63 percent completed
96.86 percent completed
97.09 percent completed
97.32 percent completed
97.54 percent completed
97.77 percent completed
98.00 percent completed
98.23 percent completed
98.46 percent completed
98.69 percent completed
98.91 percent completed
99.14 percent completed
99.37 percent completed
99.60 percent completed
99.83 percent completed
100.00 percent completed
Scanning orphaned files completed.
Checking attributes ...
0.00 percent completed
0.23 percent completed
0.46 percent completed
0.69 percent completed
0.91 percent completed
1.14 percent completed
1.37 percent completed
.....................................
96.86 percent completed
97.09 percent completed
97.32 percent completed
97.54 percent completed
97.77 percent completed
98.00 percent completed
98.23 percent completed
98.46 percent completed
98.69 percent completed
98.91 percent completed
99.14 percent completed
99.37 percent completed
99.60 percent completed
99.83 percent completed
100.00 percent completed
Failed to calloc 244189952 bytes: Cannot allocate memory
Checking cluster allocation ...
ERROR(12): Failed to setup allocation bitmap: Cannot allocate memory
Syncing device ...

At least I will not obtain errors due to minidlna DB.