I extracted last few lines from log before crash: Sep 09, 2022 14:37:59.015 [21996] DEBUG - Extras: Checked extra ‘The Divergent Series: Allegiant: LA Strada Per Il Futuro (Italian)’ and found matched: 1 Media matched: 1 Sep 09, 2022 14:37:59.016 [21996] DEBUG - Loading information from media bundle for part ID 64383 from “C:\Users\ameel\AppData\Local\Plex Media Server\Media\localhost\5\41fec3214516ce8a92985f4af565359e8c464c1.bundle\Contents\Plex Movie” Sep 09, 2022 14:37:59.018 [21996] DEBUG - Loading information from media bundle for part ID 173058 from “C:\Users\ameel\AppData\Local\Plex Media Server\Media\localhost\5\c75e6005f33a7c6b62482b853e0ba70e597be4a.bundle\Contents\Plex Movie” Sep 09, 2022 14:37:59.018 [21996] DEBUG - Loaded metadata for Allegiant (ID 7724) in 262ms Sep 09, 2022 14:37:59.018 [21996] DEBUG - Doing expensive tags write for ‘Allegiant’ because something changed. Sep 09, 2022 14:37:59.111 [21996] ERROR - SQLITE3:0x5bb30e4e, 267, statement aborts at 87: [update tags set parent_id=:tags_parent_id,metadata_item_id=:tags_metadata_item_id,tag=:tags_tag,key=:tags_key,tag_type=:tags_tag_type,tag_value=:tags_tag_value,user_thumb_url=:tags_use
I sent 2 batches of logs but have not received any response.
I appreciate you may be busy and working on various things, and would be grateful if you could provide an acknowledgement that the message and files have been received and a rough timeframe when you can provide an update.
I’m seeing disk i/o errors in your log. That typically means an issue with your drive where the Plex database is stored. It’s not a constant error, so it could be your drive is slowly starting to die and PMS is just running into this due to it accessing the database a lot.
Do you have another local hard drive installed? If so you can try moving your Plex AppData folder there and see if the crashes stop.
Thank you for the prompt analysis. Interesting. I can’t find any issues on my disks except for one (which does not run PMS). From the logs, can you tell which disk is giving i/o errors? I’ll try move PMS onto a new hdd in a couple of days.
On another note, some files are not matching correctly, and from console I can see the error: [Req#1dc3] SQLITE3:0x4eedec8, 267, statement aborts at 60: [insert into tags (parent_id,metadata_item_id,tag,key,tag_type,tag_value,user_thumb_url,user_art_url,user_music_url,created_at,updated_at,extra_data) values (:tags_parent_id,:tags_metad [Req#1dc3] Exception inside transaction (inside=1) (E:\jenkins\server\3582595338\Library\Tag.cpp:224): sqlite3_statement_backend::loadOne: database disk image is malformed [Req#1dc3] Exception inside transaction (inside=1) (E:\jenkins\server\3582595338\Library\MetadataItem.cpp:7525): sqlite3_statement_backend::loadOne: database disk image is malformed [Req#1dc3] Activity: Ended activity d9511943-9710-47d1-a88c-afb6634bca40. Thread: Uncaught exception running async task which was spawned by thread 12576: sqlite3_statement_backend::loadOne: database disk image is malformed
there should be similar issues in the logs provided. Do you know how I can fix that?
Now this database damage may have been very well caused by either a dying hard drive or having almost no free space left.
Check for both before attempting a repair.