# Plex adding media from share with erroneous dot (.) in path

**URL:** <https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473>\
**Category:** Metadata & Adding Files\
**Tags:** server-windows, library-management\
**Created:** [November 14, 2024, 10:27pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473 "2024-11-14T22:27:14Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eds89](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/eds89/32/120657_2.png) [@Eds89](https://forums.plex.tv/u/Eds89)\
**Post date:** [November 14, 2024, 10:27pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/1 "2024-11-14T22:27:14Z")

</div>

Server Version#: 1.41.2.9134  
Player Version#: 4.141.0  
I have a TV library with two shares:  
\Eds-FS\TV  
\Eds-FS2\TV

One is a copy of the other, so they have the exact same content in.  
Scanning my library files, an “unknown show” has been added with hundreds of unmatched files, and checking the info, they all seem to have an erroneous dot in the file path:

 ![image](https://global.discourse-cdn.com/plex/original/4X/4/8/e/48e8ee06d72ef16627448aea87eeb1ba48e997bb.png)  
Anyone have any idea what the heck is happening here?

I’m also now unable to remove either folder from the library folder list.

Thanks  
Eds

---

<div class="post-metadata">

**Author:** ![FordGuy61](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@FordGuy61](https://forums.plex.tv/u/FordGuy61)\
**Post date:** [November 15, 2024, 12:03am UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/2 "2024-11-15T00:03:47Z")

</div>

What is Eds-FS2 - Synology, Windows Server, etc.?

Does that file path actually exist on the server?

Wondering if the server has some hidden directories for snapshots, etc. and Plex is inadvertently searching them.

---

<div class="post-metadata">

**Author:** ![Eds89](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/eds89/32/120657_2.png) [@Eds89](https://forums.plex.tv/u/Eds89)\
**Post date:** [November 15, 2024, 7:40am UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/3 "2024-11-15T07:40:21Z")

</div>

It’s a TrueNAS scale SMB share.  
I’ve checked, and there is no directory called “.”  
I’ve had a look for hidden folders, and cannot see any.

Thanks  
Eds

---

<div class="post-metadata">

**Author:** ![Eds89](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/eds89/32/120657_2.png) [@Eds89](https://forums.plex.tv/u/Eds89)\
**Post date:** [November 15, 2024, 1:21pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/4 "2024-11-15T13:21:52Z")

</div>

I have had a look through some of the Plex log files, and whilst I’m not overly familiar with the structure and content, I did come across this in the Plex [Server log](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) file:

```auto

Nov 15, 2024 13:16:35.484 [5016] ERROR - SQLITE3:0x872f21dc, 11, database corruption at line 84326 of [a29f994989]
Nov 15, 2024 13:16:35.484 [5016] ERROR - SQLITE3:0x872f21dc, 11, statement aborts at 22: [SELECT DISTINCT di.`id` FROM directories di LEFT JOIN media_parts AS pt ON di.`id`=pt.`directory_id` LEFT JOIN media_items AS mi ON pt.`media_item_id`=mi.`id` WHERE mi.`section_location_id`=:C1] database disk image is malformed
Nov 15, 2024 13:16:35.485 [5016] WARN - Caught exception while scanning TV: Unknown exception
Nov 15, 2024 13:16:35.697 [5016] INFO - Notification: Library scan complete - Extra information may still be downloading from the Internet

```

I have disabled the Eds-FS2\TV share on the new storage box, to prevent Plex adding thousands of TV shows to this one unknown show.  
I wonder if this is what is preventing the scan from running?

Unfortunately I had no other choice, as I’m also unable to remove the extra folder from the library.  
If I try to remove the folder, I see these entries:

```auto
Nov 15, 2024 13:20:20.824 [7348] INFO - Request: [10.0.0.234:55934 (Allowed Network (Subnet))] PUT /library/sections/2?name=TV&type=show&agent=tv.plex.agents.series&scanner=Plex%20TV%20Series&language=en-US&importFromiTunes=&enableAutoPhotoTags=&location=%5C%5CEds-FS%5CTV (7 live) #6dc06 TLS GZIP Signed-in Token (Eds89) (Microsoft Edge)
Nov 15, 2024 13:20:21.915 [1364] WARN - [Req#6ec5a] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Nov 15, 2024 13:20:21.916 [1364] WARN - [Req#6ec5a] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Nov 15, 2024 13:20:23.125 [7348] ERROR - [Req#6dc06] SQLITE3:0x872f21dc, 779, index corruption at line 94622 of [a29f994989]
Nov 15, 2024 13:20:23.125 [7348] ERROR - [Req#6dc06] SQLITE3:0x872f21dc, 779, statement aborts at 26: [delete from media_parts where media_item_id=?] database disk image is malformed
Nov 15, 2024 13:20:23.125 [7348] ERROR - [Req#6dc06] Exception inside transaction (inside=1) (D:\gha\plex-media-server\plex-media-server\Library\MediaItem.cpp:911): sqlite3_statement_backend::loadOne: database disk image is malformed
Nov 15, 2024 13:20:23.154 [7348] ERROR - [Req#6dc06] Exception inside transaction (inside=1) (D:\gha\plex-media-server\plex-media-server\Library\Scanner\SectionLocation.cpp:52): sqlite3_statement_backend::loadOne: database disk image is malformed
Nov 15, 2024 13:20:23.154 [7348] ERROR - [Req#6dc06] Exception inside transaction (inside=1) (D:\gha\plex-media-server\plex-media-server\Library\LibrarySectionEndpointHandler.cpp:358): sqlite3_statement_backend::loadOne: database disk image is malformed
Nov 15, 2024 13:20:23.156 [7348] ERROR - Got exception from request handler: sqlite3_statement_backend::loadOne: database disk image is malformed
Nov 15, 2024 13:20:23.156 [5728] INFO - Completed: [10.0.0.234:55934] 500 PUT /library/sections/2?name=TV&type=show&agent=tv.plex.agents.series&scanner=Plex%20TV%20Series&language=en-US&importFromiTunes=&enableAutoPhotoTags=&location=%5C%5CEds-FS%5CTV (9 live) #6dc06 TLS GZIP 2331ms 530 bytes (pipelined: 1)

```

I do have a backup of the VM from a few days ago, before I started doing any migrations, so is it likely I will need to restore from backup?

Thanks  
Eds

---

<div class="post-metadata">

**Author:** ![JKalchik](https://avatars.discourse-cdn.com/v4/letter/j/8e8cbc/32.png) [@JKalchik](https://forums.plex.tv/u/JKalchik)\
**Post date:** [November 15, 2024, 1:22pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/5 "2024-11-15T13:22:10Z")

</div>

Ah… ha. And there it is.

Under \*ix/\*bsd, there are 2 entries in every directory, ‘.’ and ‘…’. The ‘…’ entry points to the parent, and the ‘.’ entry is a reference to itself (circular, if you will.) Running ls without a -a option customarily doesn’t show these 2 entries along with other hidden entries (directory names beginning with a ‘.’.)

---

<div class="post-metadata">

**Author:** ![dbirch](https://avatars.discourse-cdn.com/v4/letter/d/f19dbf/32.png) [@dbirch](https://forums.plex.tv/u/dbirch)\
**Post date:** [November 15, 2024, 1:36pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/6 "2024-11-15T13:36:49Z")

</div>

> [@Eds89](#):
>
> `Nov 15, 2024 13:20:23.125 [7348] ERROR - [Req#6dc06] SQLITE3:0x872f21dc, 779, statement aborts at 26: [delete from media_parts where media_item_id=?] database disk image is malformed`

You have a corrupt database see [GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases](https://github.com/ChuckPa/PlexDBRepair)

---

<div class="post-metadata">

**Author:** ![Eds89](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/eds89/32/120657_2.png) [@Eds89](https://forums.plex.tv/u/Eds89)\
**Post date:** [November 15, 2024, 1:51pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/7 "2024-11-15T13:51:56Z")

</div>

> [@JKalchik](#):
>
> Under \*ix/\*bsd, there are 2 entries in every directory, ‘.’ and ‘…’. The ‘…’ entry points to the parent, and the ‘.’ entry is a reference to itself (circular, if you will.)

Makes sense, however I don’t understand why Plex would see these to scan, when this is an SMB share and those entries aren’t visible (hidden or otherwise) when browsing the share?  
Also, the Plex server is running on Windows, so would ignore these anyway?

> [@dbirch](#):
>
> You have a corrupt database

Will take a look. Is it likely this could be the cause of the issues I’m seeing?

---

<div class="post-metadata">

**Author:** ![JKalchik](https://avatars.discourse-cdn.com/v4/letter/j/8e8cbc/32.png) [@JKalchik](https://forums.plex.tv/u/JKalchik)\
**Post date:** [November 15, 2024, 2:55pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/8 "2024-11-15T14:55:22Z")

</div>

> [@Eds89](#):
>
> Makes sense, however I don’t understand why Plex would see these to scan, when this is an SMB share and those entries aren’t visible (hidden or otherwise) when browsing the share?  
> Also, the Plex server is running on Windows, so would ignore these anyway?

And now that I’m sitting in front of Windows for the moment… as I thought I recalled, same behavior, both on NTFS and on SMB mounted shares (Synology NAS.)

IIRC, the native system calls in both environments return both dotted entries, it’s up to the process calling for the entries to decide how to handle the situation.

No argument that something odd is happening, and running @ChuckPA’s DB repair tool can’t hurt anything that I’m aware of (but make a backup first…) You won’t be able to remove the dotted entries either, I don’t think.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [November 15, 2024, 3:36pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/9 "2024-11-15T15:36:24Z")

</div>

If the root folder for the library is defined as `\\host\share\.`  
Everything found will have this prefixed.  
e.g `\\host\share\.\movies\Movie (year)`

Check the library section definition

If you use my tool to correct the Index Corruption error,  
Don’t use “Auto”, Jump straight to the REPAIR. function  
Also Reindex afterwards (the Index is what’s broken)

---

<div class="post-metadata">

**Author:** ![Eds89](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/eds89/32/120657_2.png) [@Eds89](https://forums.plex.tv/u/Eds89)\
**Post date:** [November 15, 2024, 6:18pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/10 "2024-11-15T18:18:37Z")

</div>

> [@ChuckPa](#):
>
> If the root folder for the library is defined as `\\host\share\.`

The library folder was defined as:

```auto
\\host\share

```

(No dot on the end)

I have run the DB repair, and am now able to start a scan of the library. 👍

I had attempted to remove the secondary share, but it said it couldn’t save settings. Oddly, now that the library is mid-scan, I went back in to take a screenshot to show you, and the secondary share has now disappeared 🤷‍♂️

 ![image](https://global.discourse-cdn.com/plex/original/4X/a/b/c/abc51c6e3a41f6d17bb2dc08819d735a0fde207a.png)

I think what I’ll do at this stage, is shutdown Plex, migrate my remaining data onto the new file server, rename the file server to the old file server name, and power Plex back on.  
Given I am replicating the content from one file server to another, I hope Plex will just pick up exactly where it left off, knowing nothing of the server change 🤞

Thanks everyone for your help and input.

Eds

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [February 13, 2025, 6:18pm UTC](https://forums.plex.tv/t/plex-adding-media-from-share-with-erroneous-dot-in-path/895473/11 "2025-02-13T18:18:54Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
