[NVME drives throwing errors, filling logs instantly. How to resolve?]

I'm very glad to know it works.   

 

I was researching the error / mask 00000001/0000e000 in the message, and found out it had to do with the PCI end device not responding to an ASPM command.

 

So while turning off AER masks the problem by not logging the errors, it doesn't solve the actual PCI errors.

 

  So then started going down the rabbit hole of what ASPM is all about, ( https://en.wikipedia.org/wiki/Active_State_Power_Management ) and saw there is a kernel boot flag to turn off the feature.. I dont think we need it anyways seeing as my server is running 24h/day and never goes to sleep mode.

 

I figured it might help avoid the error altogether if the unused feature is disabled.   I'll check my own server next time it reboots!  

[NVME drives throwing errors, filling logs instantly. How to resolve?]

Could you try pcie_aspm=off  .  This seems to disable power management mode which is throwing the error.. I've put it in my config for next time I reboot

[NVME drives throwing errors, filling logs instantly. How to resolve?]

Let me know how it works out for you.  I have 1 of 4 SK Hynix NVMEs on an Asus HYPER M.2 X16 GEN 4 CARD throwing this constantly.

[Plex 1.27 broke with unRaid 6.10]

It appears there's a schema upgrade screwup when moving to the latest Plex.  I'm told on the Plex website that it's due to a corrupted DB, but I get the same behavior on DB backups as well.. Appears I'm not alone in this boat.

 

See: 

https://forums.plex.tv/t/loading-libraries-fails-error-got-exception-from-request-handler-bad-cast/795400

[Plex 1.27 broke with unRaid 6.10]

I updated to the latest Plex Server 1.27 ( 1.27.0.5849-99e933842 )and the libraries were gone when starting.  Checked for permission issues but that wasn't the case.

 

The log files are now filled with (libc++ errors?) these messages whenever a transaction occurs:

got exception from request handler: std::bad_cast

 

I reverted back to Plex Server 1.26 ( PlexMediaServer-1.26.0.5715-8cf78dab ) and the issue disappears.  Same filesystem, same plex database.

 

example output:

Jun 02, 2022 10:55:21.399 [0x7f7e37163b38] DEBUG - [com.plexapp.system] HTTP reply status 200, with 0 bytes of content.
Jun 02, 2022 10:55:21.399 [0x7f7e37d1eb38] DEBUG - Completed: [127.0.0.1:38308] 200 GET /system/messaging/clear_events/com.plexapp.agents.fanarttv (4 live) GZIP 7ms 280 bytes
Jun 02, 2022 10:55:21.472 [0x7f7e36433b38] ERROR - Got exception from request handler: std::bad_cast
 

Seems like every transaction gets this error or:
Jun 02, 2022 10:55:21.611 [0x7f7e37140b38] ERROR - Got exception from request handler: Cannot convert data to std::tm.

 

 

[How many TB's is your Unraid Server?]

Currently 193TB in a Chenbro NR40700 enclosure converted into a JBOD box attached to a LSI 9206-16e

4x 960GB NVME SSDs in a BTRFS cache

Misc disk mounts for DB, Plex, Docker images, etc.