WD PR4100 Unreachable after latest update

Server Version#: 1.16.6.1592
Player Version#: tried multiple
Logs: Plex Media Server Logs_2019-08-28_22-30-02.zip (308.4 KB)

If I’m on the non-beta release, I can’t do anything with my server, if I’m on the beta release I can see media in their categories, but I can’t play anything and my dashboard isn’t working at all.

This is one of the reasons I hate updating my server, cause it’s a 50/50 if something breaks and it’ll be a week before it’s fixed.

Logs are from an attempt with version 1.16.5.1554. It is impossible to connect to the server, EVEN FROM THE SERVER ITSELF when on the newest beta.

I had the same issue on my PR2100 when I updated (via “Beta Channel”) to (I think) 1.16.6.1559 a few days ago.

I downloaded 1.16.5.1554 from the Apps page and installed the “downgraded” version and all was working as before.

Obviously there is some kind of an issue/problem with the latest version of PMS for the WD My Cloud devices.

I tried this, but it only works partially. I can see my media on in my folders, but my dashboard is “Unreachable” and nothing is able to play. I’d wish Plex would keep like 10 versions at hand instead of 2.

Apparently they have discovered the flaw and issued a beta fix (as for me, I’ve gone off the Beta channel): [Plex Media Server]

Yeah, when I’m on this beta nothing works. It makes no sense.

I have included my logs in this post, eventhough it’s a bit late, I hope this’ll somehow help resolve the issue (This is NOT on the Beta version, so it’s 1.16.5.1554

Plex Media Server Logs_2019-08-28_22-30-02.zip (308.4 KB)

Thanks guys, I’ll take a look at your logs @Sword_Scream today :slight_smile:

1 Like

@Sword_Scream your logs indicate your PMS database is corrupt

Aug 28, 2019 22:10:39.766 [0x7f5aadfc5700] ERROR - SQLITE3:(nil), 11, database corruption at line 68035 of [bf8c1b2b7a]
Aug 28, 2019 22:10:39.766 [0x7f5aadfc5700] ERROR - SQLITE3:(nil), 11, statement aborts at 43: [insert into media_stream_settings (account_id,media_stream_id,extra_data,created_at,updated_at) values (:media_stream_settings_account_id,:media_stream_settings_media_stream_id,:media_
Aug 28, 2019 22:10:39.766 [0x7f5aadfc5700] ERROR - Exception inside transaction (inside=1) (../Library/MediaStreamSetting.cpp:36): sqlite3_statement_backend::loadOne: database disk image is malformed
Aug 28, 2019 22:10:39.766 [0x7f5aadfc5700] ERROR - Soci Exception handled: sqlite3_statement_backend::loadOne: database disk image is malformed

You can follow the LINUX section of our guide on how to repair this: https://support.plex.tv/articles/201100678-repair-a-corrupt-database/

You can find your database in;
/mnt/HD/HD_a2/plex_conf/Plex Media Server/Plug-in Support/Databases

Be sure to make a backup of your corrupt database before attempting repair.

If you run into issues I can attempt to repair it for you if you PM me your database.

Hey Wingman, this is on a WD PR4100, I don’t think I have any way of doing this, I’ve tried a clean reinstall of Plex and it’s the same issue! When I download my Database I get a 22 bytes zip file with nothing in it, as seen attatched here: Plex Media Server Databases_2018-07-11_15-15-16.zip (22 Bytes)

When you clean install, are you removing your old appdata?

If you like I can assist via TeamViewer to try and repair your database. If not I can assist with showing you how to remove the old app data to allow a fresh install. Please PM me and we can setup a time in the next hour or so to do this :smile:

1 Like

For anyone else watching, we solved this by removing the database that was not recoverable, setting up new libraries, and then ensuring database backups were configured and notifications enabled.

2 Likes

I too have a wd Pr4100 and have all sorts of problems with playback , what do these error messages mean?

Aug 29, 2019 21:55:33.152 [0x7fa7696ae700] Error — Error issuing curl_easy_perform(handle): 28
Aug 29, 2019 21:55:33.152 [0x7fa7696ae700] Error — SSDP: Error parsing device schema for http://192.168.100.3:49152/wps_device.xml
Aug 29, 2019 21:56:21.158 [0x7fa7696ae700] Error — Error issuing curl_easy_perform(handle): 28
Aug 29, 2019 21:56:21.158 [0x7fa7696ae700] Error — SSDP: Error parsing device schema for http://192.168.100.3:49152/wps_device.xml
Aug 29, 2019 21:56:58.435 [0x7fa71ae6b700] Error — LPE: unknown item 220519.
Aug 29, 2019 21:56:58.435 [0x7fa71ae6b700] Error — Sync: failed to generate query for path library://d75fe807-bae8-4b69-b2ae-41516686639f/directory/%2Flibrary%2Fmetadata%2F220519%2Fchildren in sync item 37955425
Aug 29, 2019 21:56:58.435 [0x7fa71ae6b700] Error — Sync: skipping items for sync list 33416389, sync item 37955425: unable to generate sync set query
Aug 29, 2019 21:57:10.166 [0x7fa7696ae700] Error — Error issuing curl_easy_perform(handle): 28
Aug 29, 2019 21:57:10.166 [0x7fa7696ae700] Error — SSDP: Error parsing device schema for http://192.168.100.3:49152/wps_device.xml
Aug 29, 2019 21:57:57.174 [0x7fa7696ae700] Error — Error issuing curl_easy_perform(handle): 28
Aug 29, 2019 21:57:57.174 [0x7fa7696ae700] Error — SSDP: Error parsing device schema for http://192.168.100.3:49152/wps_device.xml
Aug 29, 2019 21:58:44.180 [0x7fa7696ae700] Error — Error issuing curl_easy_perform(handle): 28
Aug 29, 2019 21:58:44.180 [0x7fa7696ae700] Error — SSDP: Error parsing device schema for http://192.168.100.3:49152/wps_device.xml
Aug 29, 2019 21:59:29.185 [0x7fa7696ae700] Error — Error issuing curl_easy_perform(handle): 28
Aug 29, 2019 21:59:29.185 [0x7fa7696ae700] Error — SSDP: Error parsing device schema for http://192.168.100.3:49152/wps_device.xml
Aug 29, 2019 22:00:15.205 [0x7fa7696ae700] Error — Error issuing curl_easy_perform(handle): 28
Aug 29, 2019 22:00:15.205 [0x7fa7696ae700] Error — SSDP: Error parsing device schema for http://192.168.100.3:49152/wps_device.xml

Where do i enter that to get to data base? i read the page on doing the repair and or tests but it is not in depth enough for me to follow . can you lay it out for me on what to do?
i am running windows 10 with the WD pr4100 attached

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