zmanfarlee Posted August 12 Share Posted August 12 I have multiple issues I am fixing but right now I can't get some dockers to run and am getting the following error: PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] PMS: failure detected. Read/write access is required for path: /config/Library/Application Support/Plex Media Server kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Fix common problems says: Unable to write to disk2Drive mounted read-only or completely full. Begin Investigation Here The cache is now almost empty but I cant even edit min free space (see pic) Anyone know how to fix this? tower-syslog-20240812-2223.zip Quote Link to comment
zmanfarlee Posted August 13 Author Share Posted August 13 tower-diagnostics-20240812-2019.zip Quote Link to comment
JorgeB Posted August 13 Share Posted August 13 Check filesystem on disk2, run it without -n Quote Link to comment
zmanfarlee Posted August 13 Author Share Posted August 13 Thank you fo rlooking at this. This is the output I got: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. ____________ Is this saying Restart in non-maintanence mode then start in maitanence mode again and check the filesystem status again? Quote Link to comment
zmanfarlee Posted August 13 Author Share Posted August 13 oh crud it shows disk 2 is unmountable or no file system Quote Link to comment
zmanfarlee Posted August 13 Author Share Posted August 13 do I do the -L option? Quote Link to comment
zmanfarlee Posted August 13 Author Share Posted August 13 9 hours ago, JorgeB said: Yes, use -L this was the output: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 96064, counted 76224 sb_ifree 1954, counted 5733 sb_fdblocks 1854068584, counted 1851387458 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:1964882) is ahead of log (1:2). Format log to cycle 4. done _________________________ Was able to mount drive 2 but still cant use plex cause of this: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] [fix-attrs.d] applying ownership & permissions fixes...kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... Plex Media Server first run setup complete [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Error: Unable to set up server: sqlite3_statement_backend::prepare: malformed database schema (2) - orphan index for SQL: PRAGMA cache_size=2048 (N4soci10soci_errorE) Stopping Plex Media Server. Starting Plex Media Server. Error: Unable to set up server: sqlite3_statement_backend::prepare: malformed database schema (2) - orphan index for SQL: PRAGMA cache_size=2048 (N4soci10soci_errorE) Stopping Plex Media Server. Starting Plex Media Server. Error: Unable to set up server: sqlite3_statement_backend::prepare: malformed database schema (2) - orphan index for SQL: PRAGMA cache_size=2048 (N4soci10soci_errorE) Stopping Plex Media Server. Starting Plex Media Server. Error: Unable to set up server: sqlite3_statement_backend::prepare: malformed database schema (2) - orphan index for SQL: PRAGMA cache_size=2048 (N4soci10soci_errorE) Stopping Plex Media Server. Starting Plex Media Server. ___________________________________________ I think I will delete config and rescan plex? Quote Link to comment
zmanfarlee Posted August 13 Author Share Posted August 13 10 hours ago, JorgeB said: Yes, use -L THANK YOU!!!! Was able to reinstate plex and delete the old files and am rescanning. It works!!!! 1 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.