Kodi Community Forum
Broken Synology NAS Nexus/Omega Library scan failure on Omega, SOURCE FOUND > RES NEEDED! - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: Broken Synology NAS Nexus/Omega Library scan failure on Omega, SOURCE FOUND > RES NEEDED! (/showthread.php?tid=377576)

Pages: 1 2 3 4 5 6

Synology NAS Nexus/Omega Library scan failure on Omega, SOURCE FOUND > RES NEEDED! - kittmaster - 2024-05-18

Root cause of issue found: Post #50 > https://forum.kodi.tv/showthread.php?tid=377576&pid=3213367#pid3213367

EDIT: SEE POST 22 for definitive answer to problem located  (Still true, but true answer of what is wrong is listed above)

If this needs to be moved, please advise, figured this was the best place to ask the broad base question.

As I have been developing the Madnox skin, there have been multiple twists and turns and one of the final hooks problems I have is on my personal system which is not unique to the Kodi device accessing the NAS (Synology 918+) with 4 10TB drives running their file format BRFS (I think that is that is what it's called).

@Karellen offered some feedback but we have not yet solved the issue. When I run Nexus 20.5 from any of my devices, Windows 10 i7 laptop with 2.4Gbps link to AX router, my office machine (Mesh Asus network), my FireTV cube, and other various Win10 devices, Nexus took about 1.5 hours to complete 1394 movies. I found that I had video thumbnails turned ond during scan, turned that off, down to 38 minutes.

With the latest Omega, the thing is a complete dog, between 10-15 seconds scan of EACH file from the NAS and most times, parses about 15-20 Movies and then crashes. 

We have tried a clean install, no add-ons, still the same result. My data drive is showing 100% utilization and it just never finishes. All of this is seen in my thread here so I don't have to rehash it:

https://forum.kodi.tv/showthread.php?tid=376313&pid=3196703#pid3196703

I am now in my trailer and I have a TP-link router AC1750 and running Omega x32 and x64 as portable and ran tests and they both ran and completed fairly thee quick:

Code:


x32 Omega

2024-05-17 20:03:53.942 T:10224    info <general>: VideoInfoScanner: Starting scan ..
2024-05-17 20:05:22.799 T:10224    info <general>: VideoInfoScanner: Finished scan. Scanning for video info took 88860 ms

x64 Omega
2024-05-17 20:42:48.339 T:12364    info <general>: VideoInfoScanner: Starting scan ..
2024-05-17 20:44:10.640 T:12364    info <general>: VideoInfoScanner: Finished scan. Scanning for video info took 82305 ms


But this is only 40 ish movies, but the point is, it was scanning as fast as Nexus and doesn't crash in that configuration (TP-Link router with USB drive attached).

The Synology NAS only holds the files as a mapped network drive storage and serves no other purpose but to act as a file storage host. No MariaDB, non of that, just files stored there, other devices have Kodi installed and pointed to their location and scanned from there.

I did some basic tests, and Nexus works without issue, every time, as soon as I switch to Omega, it never completes and is dog slow scanning. ALL of my files, artwork is using the local scraper only as I use Media Companion for all of my scraping needs and NFO generation.

So clearly it seems there is a Synology problem, but I when I transfer files via windows explorer to move the files from the local machine to the NAS, I get full BW transfer of like 110-133MB/s which is the full 1Gbps the router is capable of (GT-AXE11000). So it isn't a network clog, see other thread about Nexus BW vs. Omega BW, not even close to equal rates of BW.

So any idea what could be going on with this Synology device that would cause Nexus to work but Omega to fail miserably?

These are all running in portable mode, which shouldn't be an issue, and my normal install has the same issues not in portable mode.

The logs are listed in thread linked above, and to note, sometimes it crashes with no log data at all. The crash logs (using WinDbg) show language invoker to be part of the problem, but with a clean base install, not clear where to even start.

Lots of info, but hopefully this might give enough to figure out, try this, try that.

Been working with MikeSilvo and he has been beating this up with me, not sure what to do or how to fix.... hoping someone has some insight that I'm missing.

Thank you,
Chris

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link - scott967 - 2024-05-18

No ideas, but to better understand your config, are you going through a 4-port or 8-port embedded switch on your router, or also bridging a wifi connection?  And is this ipv4, ipv6 or dual stack and if ipv6 using link-local or provisioned addresses?

scott s.
.

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link - kittmaster - 2024-05-19

(2024-05-18, 23:39)scott967 Wrote: No ideas, but to better understand your config, are you going through a 4-port or 8-port embedded switch on your router, or also bridging a wifi connection?  And is this ipv4, ipv6 or dual stack and if ipv6 using link-local or provisioned addresses?

scott s.
.

The laptop (Lenovo Y700): NIC: AX210NGW connecting at 2.4Gbps to the AXE-11000. The AXE-11000 is dual Cat5e to the Synology 918+ with a binded Ethernet 5e connection for 2Gbps connection link. Network file transfer rates ~ 110MB/s for a 10GB file size.

The office (Custom): Asrock Z77Extreme 4 Motherboard connected to RT-AX88u as a mesh node via Cat5e to the AXE-11000 via 5G backhaul. Network file transfer rates ~ 55-70MB/s for a 10GB file size. Computer connected via Ethernet 5e to mesh node <> wireless 5G backhaul <> Ethernet binded Ethernet 5e as mentioned above.

All of this is IPV4, IPV6 not in use (or at least by my hand).

All IPs in use are on LAN private as 192.168.0.34 for NAS, and the router does the DHCP for the laptop and reserved address for the mesh node.

The "switch" in the router as mentioned has 4 ports, 1/2 are configured to bind the 2Gbps the rest are all 1Gbps and connected to various local devices which don't interfere since the transfer rates are listed above.

Does that answer the question correctly? LMK if I missed anything or you need more info.

TY for taking the time.
Chris

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link - CrystalP - 2024-05-19

Did you try mapping the shared folder as a drive and using that drive as source in Kodi?

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link - kittmaster - 2024-05-19

(2024-05-19, 15:22)CrystalP Wrote: Did you try mapping the shared folder as a drive and using that drive as source in Kodi?
Each folder share in the NAS is provided as a unique drive i.e. movies, tvshows etc. See image below, but yes, in windows machines, they are mapped as network drives.

Note: I know they show disconnected and one has been redacted, my NAS is OFF and I'm home doing an emergency repair to the truck so I'm just showing a screenshot so you can see the paths, normally, they are green and connected.

Image

I will check back later, please ask if anything else needs to be known.

All the best,
Chris

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link - kittmaster - 2024-05-21

(2024-05-19, 15:22)CrystalP Wrote: Did you try mapping the shared folder as a drive and using that drive as source in Kodi?

The other thing to note, simply by switching between Nexus and Omega using the same exact paths are yielding two radically different results. You can see the thrashing of the harddrive, not sure what is causing that.

Of note, my 3rd laptop in the trailer using the TP-Link the same way, the hard drive was at maybe 10-20% utilization during a library scan, it is a strange problem.

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link - kittmaster - 2024-05-22

So I have a new data point to pass along. Using Omega, no Madnox, just Estuary skin, bland install. I am using NFS to NAS  (home now from trip) to add "Movies". I add Movies from the NAS drive and as soon as the "spinner" stops after it hits 0-100%, it is in "list" mode, I click into the "Movies" and sure enough, all 1380 total movies are listed in "text" form as Kodi starts to parse the library scan for each folder/artwork/fanart etc... THAT is what is taking forever, the list of all the movies is completely populated and as I move the mouse it knows 1/1380, 9/1380 as I hover over it. 

So clearly the problem in Omega, for me at least, all of the artwork is local, the NFO is built from Media Companion, and whatever else it is looking for during library import scan time is already in the folders.

As @Karellen mentioned in a different thread trying to assist, every single piece of artwork is already in each movie folder as it is set to scan recursively, that shouldn't take more than 20/30 minutes at most since there is NOTHING to scrape externally? I have video thumbnails turned off, I turned off download local actors... what else could be hanging this thing up using local scraper onlyHuh

Nexus doesn't exhibit this issue, Omega does... yet everyone says.... "no problems"... I find that very hard to believe. 

What else can be done to put this misery in my rear view mirror? I'm burning all this time to fix it and my skin time is just hanging in the wind because of this.

Please, I'm up to try anything... 

Thx.

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link - kittmaster - 2024-05-23

I have some concrete feedback on what is happening. But I think only the devs will have an idea what is causing this. 

I used Wireshark to monitor the traffic between the NAS and the office computer. I set the boundaries and method exactly and then started with a filtered value that only shows the traffic between the office machine and the NAS. The results are pretty clear, Omega is definitely got a wire crossed somewhere.

Both conditions are identical, both use NFS, both follow the exact same path. You will see that Omega continues to use SMB when NFS is specified, not only that, it is sending out double "\\" and the syntax between the two are similar but Omega has way more trash going on.... I can't define it, you have to see for yourself.

I've also included the full exports of Wireshark so you can see the Ethernet command, acks/nacks, and all the rest.... you will also get the pleasure of watching Omega just crash......for no reason..

The video is about 10 minutes long, but you can scrub through it as needed. But be warned, it is a huge widescreen capture, you will most likely need two monitors side by side and then have your browser span the two. If you try to full screen it, you'll see it, but it is a bit squishy, but the idea is carried across.

Any thoughts on this???? 

Code:
http://www.kittmaster.com/imagedump/kodi/skin/OmegaNexusScan.html

Code:
Nexus.csv

Code:
Omega.csv


RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link >> Updated - kittmaster - 2024-05-25

I found some more issues that point directly at how Omega is dealing with video scan.

My current advancesettings.xml

xml:




<advancedsettings>

    <excludetvshowsfromscan action="append">

        <regexp>[\\/](auxdata|backup|clipinf|playlist|stream|certificate)[\\/]</regexp>

        <regexp>movieobject\.bdmv</regexp>

        <regexp>/extras/</regexp>

        <regexp>[\\/]extras[\\/]</regexp>

    </excludetvshowsfromscan>

<imageres>9999</imageres>

<fanartres>9999</fanartres>

    <videolibrary>

        <importwatchedstate>true</importwatchedstate>

        <importresumepoint>true</importresumepoint>

        <cleanonupdate>true</cleanonupdate>

    </videolibrary>

    <samba>

        

        <clienttimeout>1</clienttimeout>

        <statfiles>false</statfiles>

    </samba>

</advancedsettings>


I found issues with my network drivers and router regarding jumbo packets, I resolved those using ethernet and then resolved my Wi-Fi with Nexus. Scanning 1384 Movies from scratch, Ethernet 1Gbps took 38min, XX secs and WiFi was 35min, XX sec (Packet boosting) and my router didn't have jumbo packets turned on. So with Nexus, I have night and day speed scanning. Each file was about 1 second or so as Karallen mentioned to me.

I go and try Omega, it is of course better but no where near Nexus, it is still slugging at between 5-9 seconds per file and it is hanging up during the image scanning section not the initial list.

Here are some wireshark images, please tell me this helps???

You can clearly see that it is sitting around "waiting" for something that is either not there or is timing out and that LOOKS LIKE something to do with BLURAY which is a nice to have scan, but slowing everything else down. 

If Nexus wasn't like lightning now, I'd have no leg to stand on here, but something is clearly wrong with Omega, how is no one else seeing this? It is maddening to say the least.

 Image

 Image

 Image

 Image

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link >> Updated - CrystalP - 2024-05-25

it's interesting how those capture don't really line up with a debug log posted earlier in the original thread, where most of the time seemed to be spent on the actors thumbnails.

I'd like to see debug log of 20.5 and 21 with NFS source, it has a bit more info in Kodi's log than with local drive/smb. And please advise if it's ethernet or wifi connection.
It's not necessary to see the entire scan, maybe 50 or so movies. And just in case, screenshot of your source/content settings.

There isn't much in your advanced settings that's relevant except maybe the thumbnail resolution. Not sure if that impacts processing time upwards or downwards though.

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link >> Updated - kittmaster - 2024-05-25

The original logs will not match the new as I modified the wifi and ethernet protocols and jumbo packet in the router.

I will do a new complete set to show what I see. I'm out right now.

Thanks for getting back to me.

Chris

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link >> Updated - kittmaster - 2024-05-26

Here is the video of it running via NFS with pretty much the same results. It is via WiFi and you will see the link speed at the end. Wireshark is running in real time so you can pause the video and review.

http://www.kittmaster.com/imagedump/kodi/skin/NexusOmega2ndScan.html

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link >> Updated - kittmaster - 2024-05-26

So when you mentioned it was hanging up on the actors, after I ran the last set for the video I did to show you via NFS you asked for, it sparked a question..... you noted how it was hanging up on the actors from the previous scan, so when I looked at the current scan I figured, oh, is it trying to cache, compress or move the actor images to thumbnails... I see that in the current thumbnails folders, there are 0 actor images in thumbnails 0-9 A-F.... so if Kodi (Omega) isn't doing anything with the images compression wise, movement across the network or anything else like it does with the posters, fanart, and other artwork..... then what in the heck is Omega hanging up on regarding the actors?

I could see if it was caching them and rescaling them and there are many actor files and that creates is a lot of small file hits due to their size, but that isn't happening. Just curious as to what you might think might be going on there since all my actor files are already downloaded and local. Also, I have tried the option in both setting "download local actors" as both on and off... doesn't change the outcome.

Hopefully you see something. Thx for your efforts.

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link >> Updated - CrystalP - 2024-05-26

Thanks, but that site/video doesn't work for me and I'm interested in the Kodi debug logs, to do some comparison between your 20.5 and 21 as well as with my own scanning.
It's not stuck on the actors but processing dozen of actors' pictures that seem to take over 100ms+ each adds up...
Another aspect that's not helping your performance is likely that your library consists mostly of dvd/bd folders it seems, which seems to unnecessarily cause an access to each file in the folders.
I don't know much about thumbnails creation and what could explain the lack of actors thumbnails in your local cache.
Are the poster/fanart/other thumbs generated correctly? If not during scan then maybe actor thumbs are generated when you open the info dialog on a movie?

I'm afraid that to get to the bottom of this, the most direct way may be to build your own Kodi, and to use git bisect to find the commit that causes things to go bad.
It's also possible to try what happens with the v21 alphas, betas, and the nightlies that haven't expired but it may not go back far enough (dev cycle started in Jan 2023)

RE: Synology NAS Nexus/Omega Library scan failure on Omega only, OK w/ TP-Link >> Updated - kittmaster - 2024-05-26

I will redo and get log data. There are no dvd/bd in my libraries ?????

Non of that exists anywhere within any of my folders or file sets. They are literally, the MP4 file of the movie, the mp4 file trailer, and Media Companion scrape of the artwork. There are no bluray signatures yet I see Omega scanning for it as if it were and you even mentioned it as well, but when you look at Nexus, that issue does not show up. I've taken a screen shot so you can see the files/folder and did a cmd dir of the physical files within as a small sample, all 1300+ are exactly the same format, no exceptions, so that is why I'm confused as to why the dvd/bd calls are being parsed and I think part of the issue at hand.

I've never built a Kodi, I guess I could try, but not sure if I will be be able to track the issue. I saw these issues in the RC builds, so not sure how far back I can go.

If I am wrong, tell me where you see the bluray aspect, and if it is something I need to correct on my end, let me know what that is, and maybe that is the fix?????? 

Anyway, here is a screenshot of the files and dir lists of the files within....

Image