fjguijarros Posted July 20, 2023 Share Posted July 20, 2023 Hello, The UNRAID server stopped working. I had two problems. The first with the USB drive. I have restored de USB Flash Drive and it works now. The second is that docker stopped working. I checked the disk array where I have a single drive and UNRAID says it can't mount the drive. That's why docker doesn't work either. What could have happened? How can I repair the disk? The drive is a Terabyte SSD. Thanks in advance nas-diagnostics-20230721-0144.zip Quote Link to comment
JorgeB Posted July 21, 2023 Share Posted July 21, 2023 Check filesystem on disk1 Quote Link to comment
fjguijarros Posted July 21, 2023 Author Share Posted July 21, 2023 Thanks for the information. I have run xfs_repair status in maintenance mode (the file system is XFS). From GUI with -nv parameters. The result is as follows: Quote "Phase 1 - find and verify superblock... - block cache size set to 363144 entries Phase 2 - using internal log - zero log... zero_log: head block 620616 tail block 620600 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_icount 64, counted 704 sb_ifree 7, counted 139 sb_fdblocks 242360679, counted 233241805 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Fri Jul 21 16:56:40 2023 Phase Start End Duration Phase 1: 07/21 16:56:40 07/21 16:56:40 Phase 2: 07/21 16:56:40 07/21 16:56:40 Phase 3: 07/21 16:56:40 07/21 16:56:40 Phase 4: 07/21 16:56:40 07/21 16:56:40 Phase 5: Skipped Phase 6: 07/21 16:56:40 07/21 16:56:40 Phase 7: 07/21 16:56:40 07/21 16:56:40 Total run time:" Then I start the matrix and the result is the same: unmountable disk present. Any other ideas? Thank you very much again. Quote Link to comment
JorgeB Posted July 21, 2023 Share Posted July 21, 2023 You need to run it again without -n or nothing will be done. Quote Link to comment
fjguijarros Posted July 21, 2023 Author Share Posted July 21, 2023 Thanks. This is the result (run it again without -n ) Quote Phase 1 - find and verify superblocks... Phase 2: Using the Internal Log - Zero Log... ERROR: The file system has valuable metadata changes in a record that need to be repeated. Mount the file system to replay the registry and unmount it before running xfs_repair again. If you cannot mount the file system, use the -L option to destroy the registry and attempt a repair. Note that destroying the registry can cause damage: try a file system mount before doing this. Quote Link to comment
Solution JorgeB Posted July 21, 2023 Solution Share Posted July 21, 2023 Use -L Quote Link to comment
fjguijarros Posted July 21, 2023 Author Share Posted July 21, 2023 It works! Thanks! Quote 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 64, counted 704 sb_ifree 7, counted 139 sb_fdblocks 242360679, counted 233241805 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 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:620600) is ahead of log (1:8). Format log to cycle 4. done I haven't lost information and Docker is correct. What could have caused that problem? Quote Link to comment
JorgeB Posted July 21, 2023 Share Posted July 21, 2023 Most often an unclean shutdown. Quote Link to comment
mrfly Posted July 21, 2023 Share Posted July 21, 2023 preclear the disk first helps also Quote Link to comment
JorgeB Posted July 22, 2023 Share Posted July 22, 2023 14 hours ago, mrfly said: preclear the disk first helps also Not sure what you mean, you cannot preclear an existing data disk, and it wouldn't help with fs issues anyway. 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.