I found that every time I reboot my MBL, Twonky Server rescans my media files even if nothing has been changed. Rescaning is unnecessary, time-consuming and it will definitely shorten MBL’s life span, since I have tens of thousand media files. Is there any way to disable this function?
wmy5555 wrote:
Twonky Server rescans my media files even if nothing has been changed.
That’s a logical misstep. How should Twonky know nothing has changed without scanning?
and it will definitely shorten MBL’s life span
Horsecrap.
TonyPh12345 wrote:
That’s a logical misstep. How should Twonky know nothing has changed without scanning?
Why not just check the log file? When adding new files the MBL doesn’t rescan all the files, it just does delta scanning.
TonyPh12345 wrote:
Horsecrap.
I have filled my MBL with less than 1,000 media files. However, it has never finished scanning, though the control panal said it is done. I’m sure it was scanning because I had disabled remote access function and turned off all my computers. Once the harddisk kept on reading/writing for more than 3 days quite intensely, and continuously until I shut it down, Shouldn’t I worry about that?
wmy5555 wrote:
Why not just check the log file? When adding new files the MBL doesn’t rescan all the files, it just does delta scanning.
What log file?
wmy5555 wrote:
I’m sure it was scanning because I had disabled remote access function and turned off all my computers. Once the harddisk kept on reading/writing for more than 3 days quite intensely, and continuously until I shut it down, Shouldn’t I worry about that?
Twonky certainly doesn’t take 3 DAYS to scan that little media. I have over 4,000 items on my disk. I just forced a rescan, and it took about 40 seconds.
You have something else going on.
TonyPh12345 wrote:
You have something else going on.
Maybe you are right. Rescan seems to take only several minutes. Is it normal that Twonky Server keep MBL awake and reading/writing disk? When I turn on Twonky, the MBL doesn’t sleep, and it is always doing something with the light flickering, even though the UI tells me rescanning is finished. Certainly there is noting device trying to get access to the MBL. I’m confused now.
I can’t tell when mine is sleeping or awake. My MBL’s LED has been dead for weeks. :dizzy_face:
There is some info in THIS thread:
http://community.wdc.com/t5/My-Book-Live/My-book-live-never-sleeps/td-p/199912
I have gone throngh that thread, but don’t get any solution. Thank you all the same.
MyBookLive:~# ps -aux
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.6 4352 1664 ? Ss Aug18 0:01 init [2]
root 2 0.0 0.0 0 0 ? S Aug18 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? S Aug18 0:00 [ksoftirqd/0]
root 4 0.0 0.0 0 0 ? S Aug18 0:00 [watchdog/0]
root 5 0.0 0.0 0 0 ? S Aug18 0:00 [events/0]
root 6 0.0 0.0 0 0 ? S Aug18 0:00 [khelper]
root 9 0.0 0.0 0 0 ? S Aug18 0:00 [async/mgr]
root 159 0.0 0.0 0 0 ? S Aug18 0:00 [sync_supers]
root 161 0.0 0.0 0 0 ? S Aug18 0:00 [bdi-default]
root 162 0.0 0.0 0 0 ? S Aug18 0:46 [kblockd/0]
root 167 0.0 0.0 0 0 ? S Aug18 0:00 [ata/0]
root 168 0.0 0.0 0 0 ? S Aug18 0:00 [ata_aux]
root 169 0.0 0.0 0 0 ? S Aug18 0:00 [ksuspend_usbd]
root 174 0.0 0.0 0 0 ? S Aug18 0:00 [khubd]
root 177 0.0 0.0 0 0 ? S Aug18 0:00 [kseriod]
root 197 0.0 0.0 0 0 ? S Aug18 0:00 [rpciod/0]
root 224 0.0 0.0 0 0 ? S Aug18 0:00 [khungtaskd]
root 225 0.0 0.0 0 0 ? S Aug18 0:19 [kswapd0]
root 226 0.0 0.0 0 0 ? S Aug18 0:00 [aio/0]
root 227 0.0 0.0 0 0 ? S Aug18 0:00 [nfsiod]
root 228 0.0 0.0 0 0 ? S< Aug18 0:00 [kslowd000]
root 229 0.0 0.0 0 0 ? S< Aug18 0:00 [kslowd001]
root 230 0.0 0.0 0 0 ? S Aug18 0:00 [xfs_mru_cache]
root 231 0.0 0.0 0 0 ? S Aug18 0:00 [xfslogd/0]
root 232 0.0 0.0 0 0 ? S Aug18 0:00 [xfsdatad/0]
root 233 0.0 0.0 0 0 ? S Aug18 0:00 [xfsconvertd/0]
root 234 0.0 0.0 0 0 ? S Aug18 0:00 [crypto/0]
root 333 0.0 0.0 0 0 ? S Aug18 0:00 [scsi_tgtd/0]
root 345 0.0 0.0 0 0 ? S Aug18 0:00 [scsi_eh_0]
root 375 0.0 0.0 0 0 ? D Aug18 0:00 [btn_t]
root 383 0.0 0.0 0 0 ? S Aug18 0:00 [a3gblink_t]
root 442 0.0 0.0 0 0 ? S Aug18 0:00 [md0_raid1]
root 444 0.0 0.0 0 0 ? S Aug18 0:00 [kjournald]
root 509 0.0 0.5 4608 1472 ? S<s Aug18 0:00 udevd --daemon
root 903 0.0 0.8 9920 2112 ? S<s Aug18 0:00 /usr/sbin/sshd
root 905 0.0 0.3 3584 896 ? Ss Aug18 0:03 logsave -s /var/log/fsck/checkfs fsck -C -R -A -
root 1130 0.0 0.8 4160 2240 ? Ss Aug18 0:00 dhclient3 -pf /var/run/dhclient.eth0.pid -lf /va
root 1266 0.0 1.1 71872 2880 ? Sl Aug18 0:50 /usr/local/bin/upnp_nas_device -webdir /var/loca
daemon 1278 0.0 0.4 3968 1088 ? Ss Aug18 0:00 /sbin/portmap
root 1435 0.0 1.7 31616 4416 ? Sl Aug18 0:27 /usr/sbin/rsyslogd -c3
root 1456 0.0 9.4 66560 24064 ? S<s Aug18 0:18 /usr/sbin/apache2 -k start
root 1467 0.0 0.0 0 0 ? S Aug18 0:11 [jbd2/sda4-8]
root 1468 0.0 0.0 0 0 ? S Aug18 0:00 [ext4-dio-unwrit]
root 1685 0.0 1.0 5632 2752 ? SN Aug18 1:10 /bin/sh /usr/local/sbin/monitorio.sh
root 1705 0.0 0.5 3712 1472 ? Ss Aug18 0:02 /usr/sbin/ifplugd -i eth0 -q -f -u0 -d5 -w -I
root 1727 0.0 0.5 4032 1408 ? Ss Aug18 0:00 /sbin/rpc.statd
root 1736 0.0 0.4 7808 1024 ? Ss Aug18 0:00 /usr/sbin/rpc.idmapd
root 1755 0.0 0.0 0 0 ? S Aug18 0:00 [lockd]
root 1756 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1757 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1758 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1759 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1760 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1761 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1762 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1763 0.0 0.0 0 0 ? S Aug18 0:00 [nfsd]
root 1767 0.0 0.2 4480 576 ? Ss Aug18 0:00 /usr/sbin/rpc.mountd --manage-gids
root 1778 0.0 1.4 12032 3776 ? Ss Aug18 0:01 /usr/sbin/nmbd -D
root 1781 0.0 1.1 20096 3008 ? S<s Aug18 0:00 /usr/sbin/smbd -D
root 1798 0.0 0.2 20096 704 ? S< Aug18 0:00 /usr/sbin/smbd -D
root 1811 0.0 0.6 4288 1600 ? S Aug18 0:00 /usr/sbin/cnid_metad -l log_note
root 1849 0.0 0.6 7168 1600 ? S< Aug18 0:14 /usr/sbin/afpd -U uams_dhx2.so,uams_clrtxt.so -g
root 1874 0.0 0.7 3776 1920 ? Ss Aug18 0:00 /usr/local/bin/mDNSResponderPosix -b -f //etc/mD
103 1889 0.0 0.5 5312 1408 ? Ss Aug18 0:00 /usr/bin/dbus-daemon --system
root 1942 0.0 2.1 45696 5504 ? Ssl Aug18 0:49 /usr/local/bin/forked-daapd
root 2085 0.0 0.3 3584 960 ? S Aug18 0:00 /usr/local/bin/resetbtnd /dev/input/event0 4 /us
root 2153 0.0 0.5 3840 1472 ? S Aug18 0:00 /usr/local/bin/lld2d eth0
root 2593 0.0 0.5 3776 1344 ttyS0 Ss+ Aug18 0:00 /sbin/getty -L ttyS0 115200 vt100
root 17557 0.0 0.0 0 0 ? S Aug18 0:00 [flush-9:0]
root 17961 0.0 1.0 5120 2688 ? SNs Aug18 0:00 /usr/sbin/cron
root 18769 0.0 2.1 13696 5504 ? S<s 00:10 0:00 sshd: root@pts/0
root 18772 0.0 1.4 9472 3584 pts/0 S<s 00:10 0:00 -bash
root 18865 0.0 0.7 3840 1792 ? SN 00:10 0:00 /usr/local/twonkymedia-5/twonkymedia -D -appdata
root 18867 15.4 4.1 24640 10624 ? SNl 00:10 4:21 /usr/local/twonkymedia-5/twonkymediaserver -D -a
www-data 25134 0.0 4.4 66560 11200 ? S< 00:37 0:00 /usr/sbin/apache2 -k start
www-data 25135 0.0 4.4 66560 11200 ? S< 00:37 0:00 /usr/sbin/apache2 -k start
www-data 25136 0.0 4.4 66560 11200 ? S< 00:37 0:00 /usr/sbin/apache2 -k start
root 25245 0.0 0.7 3904 1856 ? SN 00:38 0:00 sleep 60
root 25249 0.0 1.1 4928 3008 pts/0 R<+ 00:39 0:00 ps -aux
That’s all my processes. Anything strange?
I was running Twonky on a Linksys NSLU and never was satisfied. I switched to Mediatomb and now I’m running an Apple TV with the remote app for iPad and iPod. With Twonky the NLSU attached HD never goes to sleep.
I am guessing this is WD’s fix to Twonky corrupting it’s database at random times. Something I researched and found a workaround which was to erase the internal media database so Twonly rebuilds it. I’m guessing if I examine the scripts then WD’s fix is to erase the internal media database assuming that it is corrupted so Twonky has to rebuild it’s media database.
I could be wrong. It’s a guess.
