3.0.3.6-061 wierd problem

[arul]

Hey guys, i am having this wierd thing going on with this fw. every once in a while, the cpu will be at 95-100%. i telnet to the router and checked whats using the cpu that much. it says minidlna is running at 70-95% cpu. my settings is on "update for new files only". the web status is already shows a static number and no longer running up. what is it really doing? it will do it a few times a day and stop after a while(took nearly an hour each time). it bothers me because everytime it happens, i cant watch anything on my tv, it will stop the video after a few minutes. what should i do? my hdd is formatted to ex3 and hfs+. i only set it to scan the ext3 only at (/media/AiDisk_a2).

 

[Guz]

I've run into this before.

1. Set the UPnP Media Server to "Update for newer files only".
2. Stop the UPnP Media Server.
3. Reboot the router
4. Telnet in to the router.
5. Look for the ".dms" directory on your drives (it will be a hidden directory at the root of a drive).
6. Delete the contents of the ".dms" directory

cd into the .dms directory, then run "rm -rf *" (without the quotes, and make darn sure you are in the .dms directory before you run the rm command)
​

7. Start the UPnP Media Server
8. Wait... let it re-catalog your content.

If it doesn't re-catalog your content, set the UPnP Media Server to "force update whole catalog". Then wait till it finishes, then set UPnP Media Server back to "Update for newer files only".

 

[arul]

what if i unplug the hdd and delete the .dms file alltogether?
i did that and let it force update the whole database. then change update new files after its done. but it still does it. utilizing the cpu 100% even when i change it to never update.

 

[Guz]

That's one way to do it. Although I've had issues trying to delete the directory on my PC, which is why I suggested the above method.

So, that didn't work. Now you're going to need to telnet into the router anyway, while the CPU is spiking to determine what's taxing the CPU.

You're going to run the 'top' command and look for which process is using the most CPU time. Then post back. Hopefully it will be an easy fix.

 

[arul]

The top command was the one that shows me that minidlna was using it.

 

[Guz]

Oh, right. (Sorry didn't go back and re-read the original issue).

I'm wondering if you might have some tag issues in your media, or corrupted media files then.

If you have music, I recommend Mp3tag to go through and maybe have it re-save the ID3 tag information.

Video: Not sure what to use.

P.S.
I forgot to ask what partition type you are using? i.e. is the .dms directory on a FAT, FAT32, NTFS, ext2/3/4 patition?

 

[arul]

im on ext3 and hfs+. i only put media/aidisk_a2 to be scanned which is the ext3.

 

[arul]

i am still having the same problem and i cant find a solution guys. =(
i even reverted to older fw too. but the same problem persist. i even ran e2fsck on the drive and its clean. help me out please.

 

[Mat77]

i am still having the same problem and i cant find a solution guys. =(
i even reverted to older fw too. but the same problem persist. i even ran e2fsck on the drive and its clean. help me out please.

does the Problem still exists on the newest Firmware?

version 3.4.3.6-064

 

[arul]

yes it is. i am running it right now.
this is whats on the log if that tell u guys something

Jun 23 17:24:12 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88768513: comm transmission-da: reading directory lblock 0
Jun 23 17:24:21 kernel: sda: sda1 sda2
Jun 23 17:24:21 kernel: sd 6:0:0:0: [sda] No Caching mode page present
Jun 23 17:24:21 kernel: sd 6:0:0:0: [sda] Assuming drive cache: write through
Jun 23 17:24:21 kernel: sd 6:0:0:0: [sda] Attached SCSI disk
Jun 23 17:24:22 kernel: EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem
Jun 23 17:24:22 kernel: ufsd: use builtin utf8
Jun 23 17:24:23 kernel: EXT4-fs (sda2): recovery complete
Jun 23 17:24:23 kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Jun 23 17:24:26 kernel: ufsd: Force nocase=1
Jun 23 17:24:26 kernel: ufsd: sda1 without journal
Jun 23 17:25:25 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #86622209: comm minidlna: reading directory lblock 0
Jun 23 17:25:30 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88629249: comm transmission-da: reading directory lblock 0
Jun 23 17:26:53 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88768513: comm transmission-da: reading directory lblock 0
Jun 23 17:27:04 Media Server: daemon is started
Jun 23 17:27:55 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #86622209: comm rm: reading directory lblock 0
Jun 23 17:27:55 Media Server: daemon is started
Jun 23 17:28:27 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88768513: comm transmission-da: reading directory lblock 0
Jun 23 17:28:45 Media Server: daemon is started
Jun 23 17:28:52 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88768513: comm transmission-da: reading directory lblock 0
Jun 23 17:29:30 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88752130: comm transmission-da: reading directory lblock 0
Jun 23 17:29:30 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88768513: comm transmission-da: reading directory lblock 0
Jun 23 17:29:30 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88752130: comm transmission-da: reading directory lblock 0
Jun 23 17:29:30 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88629252: comm transmission-da: reading directory lblock 0
Jun 23 17:29:30 kernel: EXT4-fs error (device sdb2): ext4_find_entry:935: inode #88768513: comm transmission-da: reading directory lblock 0

 

[arul]

this is all over the place too

kernel: EXT4-fs error (device sda2): ext4_find_entry:935: inode #4415489: comm smbd: reading directory lblock 0
kernel: EXT4-fs error (device sda2): ext4_wait_block_bitmap:410: comm minidlna: Cannot read block bitmap - block_group = 7730, block_bitmap = 253296640

 

[Adamm]

this is all over the place too

kernel: EXT4-fs error (device sda2): ext4_find_entry:935: inode #4415489: comm smbd: reading directory lblock 0
kernel: EXT4-fs error (device sda2): ext4_wait_block_bitmap:410: comm minidlna: Cannot read block bitmap - block_group = 7730, block_bitmap = 253296640

Try terminal running;

umount /dev/sda2
/sbin/e2fsck -p /dev/sda2

then reboot

 

[arul]

this is the reply
/dev/sda2: clean, 7344/91570176 files, 333636243/366267136 blocks
rebooting now.

i did ran this before
e2fsck -y -v -f /dev/sda2
but not sure what it does, reboot and it still d same.

 

[arul]

its still doing it.
i realised that it will happen if i play certain videos.
then the cpu will go up to 95-100 solid for almost an hour.

then these came up first
Jun 24 22:41:34 kernel: usb 1-1: USB disconnect, device number 2
Jun 24 22:41:34 kernel: usb 1-1: new high-speed USB device number 3 using rt3xxx-ehci
Jun 24 22:41:34 kernel: Buffer I/O error on device sda1, logical block 0
Jun 24 22:41:34 kernel: lost page write due to I/O error on sda1
Jun 24 22:41:34 kernel: Buffer I/O error on device sda1, logical block 3
Jun 24 22:41:34 kernel: lost page write due to I/O error on sda1
Jun 24 22:41:34 kernel: usb 1-1: New USB device found, idVendor=1058, idProduct=1140
Jun 24 22:41:34 kernel: usb 1-1: Product: My Book 1140
Jun 24 22:41:34 kernel: usb 1-1: Manufacturer: Western Digital
Jun 24 22:41:34 kernel: usb 1-1: SerialNumber: 5743415A4148393737353935
Jun 24 22:41:34 kernel: scsi1 : usb-storage 1-1:1.0

then a whoooole bunch of these;
Jun 24 22:41:35 kernel: EXT4-fs error (device sda2): ext4_find_entry:935: inode #86622209: comm minidlna: reading directory lblock 0
Jun 24 22:41:35 kernel: EXT4-fs error (device sda2): __ext4_get_inode_loc:3567: inode #86622210: block 346488834: comm minidlna: unable to read itable block

 

[arul]

i figured out something wrong with my media files. specifically my music folder. i dont know exactly whats wrong with it, but im sure its the one that cause the constant cpu use. so i recently made a change on the media path. instead of putting my normal path (/media/'mydiskname').
i force it to only scan my video files only at (V,/media/'mydiskname').
now that i set it at that. it no longer doing the wierd minidlna utilizing cpu at full percentage. thank you for the help i got though.