Popple2000 Posted March 13, 2022 Share Posted March 13, 2022 (edited) Hey guys, I received "Your flash drive has possible corruption on /boot/config/plugins/plexmediaserver/settings.ini" today from Fix Common Problems after formatting a disk and restarting the array. I've attached the diag and was hoping someone could tell me if I should panic or not. beafy-diagnostics-20220313-1502.zip Many thanks in advance! Edited March 13, 2022 by Popple2000 Spelling Quote Link to comment
Solution trurl Posted March 13, 2022 Solution Share Posted March 13, 2022 You don't have a plex media server plugin, must be left over from before the days of docker on Unraid. Just delete the file. 1 Quote Link to comment
trurl Posted March 13, 2022 Share Posted March 13, 2022 In fact, just delete the whole folder /boot/config/plugins/plexmediaserver 1 Quote Link to comment
Popple2000 Posted March 13, 2022 Author Share Posted March 13, 2022 Wow, in my panic I didn't even realize it was referencing that fossil of a plugin. Thanks so much! Quote Link to comment
Popple2000 Posted March 13, 2022 Author Share Posted March 13, 2022 Just now, trurl said: In fact, just delete the whole folder /boot/config/plugins/plexmediaserver I will, thanks so much! Quote Link to comment
trurl Posted March 13, 2022 Share Posted March 13, 2022 Any idea what this is about? Mar 9 21:35:39 Beafy emhttpd: unclean shutdown detected Quote Link to comment
trurl Posted March 13, 2022 Share Posted March 13, 2022 Looks like you let it complete the automatic parity check after the unclean shutdown. Do you have any sync errors? The reason I ask is because of another warning from FCP. Mar 13 15:01:37 Beafy root: Fix Common Problems: Warning: Docker Update Check not enabled ** Ignored Mar 13 15:01:37 Beafy root: Fix Common Problems: Warning: Scheduled Parity Checks are not enabled ** Ignored Mar 13 15:01:39 Beafy root: Fix Common Problems: Error: Blacklisted plugin speedtest.plg Mar 13 15:01:42 Beafy root: Fix Common Problems: Warning: Docker application Bitwarden has moderator comments listed ** Ignored Mar 13 15:01:42 Beafy root: Fix Common Problems: Warning: Docker application openvpn-as has moderator comments listed Mar 13 15:01:44 Beafy root: Fix Common Problems: Warning: preclear.disk.plg Not Compatible with Unraid version 6.9.2 Mar 13 15:01:46 Beafy flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 13 15:01:49 Beafy root: Fix Common Problems: Other Warning: Unassigned Devices Plus not installed Mar 13 15:01:50 Beafy root: Fix Common Problems: Error: /boot/config/plugins/plexmediaserver/settings.ini corrupted Personally, the only one of those I would set to "ignore" is the one about Unassigned Devices Plus if you don't need its functionality. Disk2 is the one you formatted. Why did you format it? Are you converting from ReiserFS? Also cache2 may have problems, maybe you noticed Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 Sense Key : 0x5 [current] Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 ASC=0x21 ASCQ=0x0 Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Mar 13 04:35:40 Beafy kernel: blk_update_request: critical target error, dev sdj, sector 484642784 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 Mar 13 04:35:40 Beafy kernel: BTRFS warning (device sdj1): failed to trim 1 device(s), last error -121 Quote Link to comment
Popple2000 Posted March 13, 2022 Author Share Posted March 13, 2022 17 minutes ago, trurl said: Any idea what this is about? Mar 9 21:35:39 Beafy emhttpd: unclean shutdown detected I was using unbalance to move files off a disk and I must have miss-clicked something because it started deleting everything off the disk instead and I couldn't get it to stop, so I initiated a reboot from the unraid GUI. When the server came back up from it's reboot it was running a parity check on it's own so I assume something went wrong with the reboot. Quote Link to comment
Popple2000 Posted March 13, 2022 Author Share Posted March 13, 2022 (edited) 44 minutes ago, trurl said: Looks like you let it complete the automatic parity check after the unclean shutdown. Do you have any sync errors? The reason I ask is because of another warning from FCP. Mar 13 15:01:37 Beafy root: Fix Common Problems: Warning: Docker Update Check not enabled ** Ignored Mar 13 15:01:37 Beafy root: Fix Common Problems: Warning: Scheduled Parity Checks are not enabled ** Ignored Mar 13 15:01:39 Beafy root: Fix Common Problems: Error: Blacklisted plugin speedtest.plg Mar 13 15:01:42 Beafy root: Fix Common Problems: Warning: Docker application Bitwarden has moderator comments listed ** Ignored Mar 13 15:01:42 Beafy root: Fix Common Problems: Warning: Docker application openvpn-as has moderator comments listed Mar 13 15:01:44 Beafy root: Fix Common Problems: Warning: preclear.disk.plg Not Compatible with Unraid version 6.9.2 Mar 13 15:01:46 Beafy flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Mar 13 15:01:49 Beafy root: Fix Common Problems: Other Warning: Unassigned Devices Plus not installed Mar 13 15:01:50 Beafy root: Fix Common Problems: Error: /boot/config/plugins/plexmediaserver/settings.ini corrupted Personally, the only one of those I would set to "ignore" is the one about Unassigned Devices Plus if you don't need its functionality. Disk2 is the one you formatted. Why did you format it? Are you converting from ReiserFS? Also cache2 may have problems, maybe you noticed Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 Sense Key : 0x5 [current] Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 ASC=0x21 ASCQ=0x0 Mar 13 04:35:40 Beafy kernel: sd 1:0:2:0: [sdj] tag#836 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Mar 13 04:35:40 Beafy kernel: blk_update_request: critical target error, dev sdj, sector 484642784 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0 Mar 13 04:35:40 Beafy kernel: BTRFS warning (device sdj1): failed to trim 1 device(s), last error -121 Hey, I had no sync errors. I'll go ahead and update to UDP. I was emptying the drive to convert it to XFS and then swap in a 14tb i have sitting here. As far as sdj1 is concerned, can I do anything to remedy the trim error? Should I be concerned?beafy-diagnostics-20220313-1624.zip *edit* Perhaps you were talking about the critical target error... I assume this is bad? Should I replace the drive? *edit 2* I ran a scrub and balance, updated everything, cleaned up the errors I could, rebooted the server and attached a new diag. Edited March 13, 2022 by Popple2000 *edit* Quote Link to comment
Popple2000 Posted March 15, 2022 Author Share Posted March 15, 2022 On 3/13/2022 at 3:47 PM, Popple2000 said: Hey, I had no sync errors. I'll go ahead and update to UDP. I was emptying the drive to convert it to XFS and then swap in a 14tb i have sitting here. As far as sdj1 is concerned, can I do anything to remedy the trim error? Should I be concerned?beafy-diagnostics-20220313-1624.zip *edit* Perhaps you were talking about the critical target error... I assume this is bad? Should I replace the drive? *edit 2* I ran a scrub and balance, updated everything, cleaned up the errors I could, rebooted the server and attached a new diag. @trurl I moved the second cache drive off the LSI HBA and onto the onboard sata and i think that solved the trim issue(I read somewhere that could be the culprit) Im pretty sure the rest of my issues are solved for now as well. Thanks for your help! Cheers beafy-diagnostics-20220315-0838.zip Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.