blakeslade Posted March 20, 2022 Share Posted March 20, 2022 Hello! I'm a basic Unraid user and have run into some trouble with my server. As the title reads, I have a data disk (with data on it) that is being reported as unmountable and another disk with errors reported when building a new config. I have attached the tower diagnostics the downloaded smart report for sdh and sdf and a screen shot of Tower Main. What I have done: - Ran a full smart diagnostic which passes on the unmountable disk (sdh) - Mounted array in Maintenance Mode and ran xfs_repair (through GUI) with arguments removed on both disks (sdh and sdf) I don't know what steps to take next? A little back story for some context: A Defective PSU has been giving random HDD errors off and on over the past year. I didn't realize it was the PSU and kept changing SATA cables, SATA headders and PCIe slots for the LSI SATA card, and SATA brake out cables. This would work for a little while then errors would appear again. Only this past week did I make the connection, but not before I went to Tools and selected "New Config" and all hell broke loose. HDD's were disappearing with every boot and errors in parity. In hind sight I should have made a post here in the forums and saved myself a whole lot of trouble. I really appreciate your help! tower-diagnostics-20220320-1536.zip tower-smart-20220319-2009.zip xfs_repair_output.txt tower-smart-20220320-1739-sdf.zip Quote Link to comment
JorgeB Posted March 21, 2022 Share Posted March 21, 2022 Please reboot and post new diags after arrays start. Quote Link to comment
blakeslade Posted March 21, 2022 Author Share Posted March 21, 2022 Thanks for joining the thread JorgeB! I rebooted the server and started the array and all drives are mounted and no errors have appeared... yet. Before I cheer, is there anything I should do next? Run parity check again with the now mounted disk2? Thanks again! tower-diagnostics-20220321-1739.zip Quote Link to comment
blakeslade Posted March 21, 2022 Author Share Posted March 21, 2022 Update: Now the plugin FixCommonProblems has discovered that disk 5 is being reported as full, but it is not (2.66Tb / 6Tb used). Additionally, I cannot connect to any of my dockers. What should I do? Quote Link to comment
ChatNoir Posted March 22, 2022 Share Posted March 22, 2022 You should check filesystem on disk5. Quote Link to comment
blakeslade Posted March 22, 2022 Author Share Posted March 22, 2022 Here is the xfs_repair -n result: 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 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... agf_freeblks 205949954, counted 205949590 in ag 3 agf_longest 205932767, counted 205934435 in ag 3 agi_freecount 1226, counted 1258 in ag 3 agf_freeblks 170272000, counted 170277590 in ag 4 agf_longest 170236487, counted 170233465 in ag 4 agf_freeblks 138193913, counted 143248099 in ag 1 agf_longest 138049324, counted 143132200 in ag 1 agi_freecount 1342, counted 1447 in ag 1 agf_freeblks 164830396, counted 164843628 in ag 2 agf_longest 164786646, counted 164788526 in ag 2 agf_freeblks 123306136, counted 127540887 in ag 0 agf_longest 121943290, counted 127191054 in ag 0 agi_freecount 1195, counted 1320 in ag 2 agf_freeblks 23442946, counted 23447163 in ag 5 agf_longest 23432351, counted 23436698 in ag 5 agi_freecount 1253, counted 1323 in ag 5 agi_freecount 1395, counted 1483 in ag 4 sb_ifree 7760, counted 8180 sb_fdblocks 825995421, counted 835307033 - 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 imap claims a free inode 2098448 is in use, would correct imap and clear inode imap claims a free inode 2099020 is in use, would correct imap and clear inode imap claims a free inode 16051712 is in use, would correct imap and clear inode imap claims a free inode 16052347 is in use, would correct imap and clear inode imap claims a free inode 16052417 is in use, would correct imap and clear inode imap claims a free inode 16053297 is in use, would correct imap and clear inode imap claims a free inode 16053307 is in use, would correct imap and clear inode imap claims a free inode 16053553 is in use, would correct imap and clear inode imap claims a free inode 16053683 is in use, would correct imap and clear inode imap claims a free inode 16053685 is in use, would correct imap and clear inode imap claims a free inode 16072524 is in use, would correct imap and clear inode imap claims a free inode 16075264 is in use, would correct imap and clear inode imap claims a free inode 16075280 is in use, would correct imap and clear inode imap claims a free inode 16075298 is in use, would correct imap and clear inode imap claims a free inode 16075315 is in use, would correct imap and clear inode imap claims a free inode 16075332 is in use, would correct imap and clear inode imap claims a free inode 16077061 is in use, would correct imap and clear inode imap claims a free inode 16077067 is in use, would correct imap and clear inode imap claims a free inode 16077068 is in use, would correct imap and clear inode imap claims a free inode 16077069 is in use, would correct imap and clear inode imap claims a free inode 16077070 is in use, would correct imap and clear inode imap claims a free inode 16077071 is in use, would correct imap and clear inode imap claims a free inode 16077072 is in use, would correct imap and clear inode imap claims a free inode 16077073 is in use, would correct imap and clear inode imap claims a free inode 16077074 is in use, would correct imap and clear inode imap claims a free inode 16077075 is in use, would correct imap and clear inode imap claims a free inode 16077076 is in use, would correct imap and clear inode imap claims a free inode 16077077 is in use, would correct imap and clear inode imap claims a free inode 16077080 is in use, would correct imap and clear inode imap claims a free inode 16077081 is in use, would correct imap and clear inode imap claims a free inode 16077083 is in use, would correct imap and clear inode imap claims a free inode 16077108 is in use, would correct imap and clear inode imap claims a free inode 16077116 is in use, would correct imap and clear inode imap claims a free inode 16077187 is in use, would correct imap and clear inode imap claims a free inode 16077195 is in use, would correct imap and clear inode imap claims a free inode 16077894 is in use, would correct imap and clear inode imap claims a free inode 16077903 is in use, would correct imap and clear inode imap claims a free inode 16077904 is in use, would correct imap and clear inode imap claims a free inode 16077905 is in use, would correct imap and clear inode imap claims a free inode 16077906 is in use, would correct imap and clear inode imap claims a free inode 16077907 is in use, would correct imap and clear inode imap claims a free inode 16077913 is in use, would correct imap and clear inode imap claims a free inode 16077919 is in use, would correct imap and clear inode imap claims a free inode 16077922 is in use, would correct imap and clear inode imap claims a free inode 16077923 is in use, would correct imap and clear inode imap claims a free inode 16077945 is in use, would correct imap and clear inode imap claims a free inode 16078016 is in use, would correct imap and clear inode imap claims a free inode 16078018 is in use, would correct imap and clear inode imap claims a free inode 16078034 is in use, would correct imap and clear inode imap claims a free inode 16078036 is in use, would correct imap and clear inode imap claims a free inode 16078043 is in use, would correct imap and clear inode imap claims a free inode 16078044 is in use, would correct imap and clear inode imap claims a free inode 16078066 is in use, would correct imap and clear inode imap claims a free inode 16078068 is in use, would correct imap and clear inode imap claims a free inode 16078069 is in use, would correct imap and clear inode imap claims a free inode 16337485 is in use, would correct imap and clear inode imap claims a free inode 16339328 is in use, would correct imap and clear inode imap claims a free inode 16339382 is in use, would correct imap and clear inode imap claims a free inode 16344633 is in use, would correct imap and clear inode imap claims a free inode 16344635 is in use, would correct imap and clear inode imap claims a free inode 16344636 is in use, would correct imap and clear inode imap claims a free inode 16344639 is in use, would correct imap and clear inode imap claims a free inode 16350482 is in use, would correct imap and clear inode imap claims a free inode 16772427 is in use, would correct imap and clear inode imap claims a free inode 16772428 is in use, would correct imap and clear inode imap claims a free inode 16772429 is in use, would correct imap and clear inode imap claims a free inode 16772430 is in use, would correct imap and clear inode imap claims a free inode 16772444 is in use, would correct imap and clear inode imap claims a free inode 16782277 is in use, would correct imap and clear inode imap claims a free inode 16793899 is in use, would correct imap and clear inode imap claims a free inode 16795088 is in use, would correct imap and clear inode imap claims a free inode 16795089 is in use, would correct imap and clear inode imap claims a free inode 16795090 is in use, would correct imap and clear inode imap claims a free inode 16795091 is in use, would correct imap and clear inode imap claims a free inode 16795092 is in use, would correct imap and clear inode imap claims a free inode 16795093 is in use, would correct imap and clear inode imap claims a free inode 16795094 is in use, would correct imap and clear inode imap claims a free inode 16795095 is in use, would correct imap and clear inode imap claims a free inode 16795096 is in use, would correct imap and clear inode imap claims a free inode 16795098 is in use, would correct imap and clear inode imap claims a free inode 16795100 is in use, would correct imap and clear inode imap claims a free inode 16795126 is in use, would correct imap and clear inode imap claims a free inode 16795127 is in use, would correct imap and clear inode imap claims a free inode 16799166 is in use, would correct imap and clear inode imap claims a free inode 16799167 is in use, would correct imap and clear inode - agno = 1 - agno = 2 - agno = 3 data fork in ino 6446624915 claims free block 826511721 - agno = 4 data fork in ino 8589935586 claims free block 1073743179 imap claims in-use inode 8589935586 is free, would correct imap data fork in ino 8589935648 claims free block 1073747565 data fork in ino 8589935654 claims free block 1073771920 data fork in ino 8589935663 claims free block 1073769938 data fork in ino 8589935670 claims free block 1073769000 data fork in ino 8589935676 claims free block 1089399469 imap claims a free inode 8589936110 is in use, would correct imap and clear inode - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (4,1700-1701) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 4 - agno = 5 - agno = 1 entry "ab85caaf60cf88419b9ee0e186964d62b8555915.jpg" at block 0 offset 96 in directory inode 152 references free inode 16077068 would clear inode number in entry at offset 96... entry "ab40142fee35c21a40c06c295ce520d0ff834c59.jpg" at block 0 offset 2600 in directory inode 152 references free inode 16077083 would clear inode number in entry at offset 2600... entry "0ea283db8e6159d20f7b0d132795fd2c7aeaafc0.jpg" at block 0 offset 1480 in directory inode 154 references free inode 16053685 would clear inode number in entry at offset 1480... entry "0e3ed499d60c1076079398dafafd63553c1c21ad.jpg" at block 0 offset 1640 in directory inode 154 references free inode 16077067 would clear inode number in entry at offset 1640... entry "d85e09e88e80aefb1d8db1beedbfeb1ff602d509.jpg" at block 0 offset 1008 in directory inode 162 references free inode 16077072 would clear inode number in entry at offset 1008... entry "d832b71fe3d94c45ff77cabb70060ace72487519.jpg" at block 0 offset 1168 in directory inode 162 references free inode 16077919 would clear inode number in entry at offset 1168... entry "d8e8e1c8c41870e670c0cba2381e7d83b9b08e8c.jpg" at block 0 offset 1328 in directory inode 162 references free inode 16072524 would clear inode number in entry at offset 1328... entry "d86c31a996a1069f7d5fab174b601b19bb52bb46.jpg" at block 0 offset 1488 in directory inode 162 references free inode 16078069 would clear inode number in entry at offset 1488... entry "bf3a85ff86cd9418b505ddd8d081cb5406ac0d49.jpg" at block 0 offset 200 in directory inode 164 references free inode 16077922 would clear inode number in entry at offset 200... entry "1483362e6c55544f07434795e203458c182b4739.jpg" at block 0 offset 1272 in directory inode 168 references free inode 16077894 would clear inode number in entry at offset 1272... entry "14cba337c807d0920c3ae20f8aeca9f0e393c5f2.jpg" at block 0 offset 1432 in directory inode 168 references free inode 16077923 would clear inode number in entry at offset 1432... entry "bc913203d55aaec203c5b26f9aaccc7da2b0c419.jpg" at block 0 offset 360 in directory inode 170 references free inode 16077906 would clear inode number in entry at offset 360... entry "b68e061138fbf8b7ee4a20dc853f4c5fca3359b4.jpg" at block 0 offset 1216 in directory inode 172 references free inode 16077071 would clear inode number in entry at offset 1216... entry "b692af99fcf4c38cee822a7ca8522405ee9346a4.jpg" at block 0 offset 1376 in directory inode 172 references free inode 16077116 would clear inode number in entry at offset 1376... entry "b6d23bd199ec5bbc5e0ce2e1d0f3ed8aec584dad.jpg" at block 0 offset 1536 in directory inode 172 references free inode 16078034 would clear inode number in entry at offset 1536... entry "7f2a38fb22e677bb5126216c49e36f29f97fa469.jpg" at block 0 offset 1696 in directory inode 174 references free inode 16077069 would clear inode number in entry at offset 1696... entry "7f7d3ce62f301f8318327d000633a5dec5f06414.jpg" at block 0 offset 1856 in directory inode 174 references free inode 16077073 would clear inode number in entry at offset 1856... entry "297c4ef8b8cc413ea720652112b1ced0b802b14c.jpg" at block 0 offset 1480 in directory inode 176 references free inode 16077108 would clear inode number in entry at offset 1480... entry "dbc19db6486a6d91980bc061fa21a8d729b68744.jpg" at block 0 offset 520 in directory inode 180 references free inode 16075264 would clear inode number in entry at offset 520... entry "db8c2402eee5053fb7b61d38f49a7e4f8fecd59c.jpg" at block 0 offset 680 in directory inode 180 references free inode 16078016 would clear inode number in entry at offset 680... entry "db2ef792dc74372a49a6c5380e8d183558befdd5.jpg" at block 0 offset 840 in directory inode 180 references free inode 16078018 would clear inode number in entry at offset 840... entry "9afc7958d465a732da528e46e8870dfa1c1e5dbd.jpg" at block 0 offset 416 in directory inode 182 references free inode 16075280 would clear inode number in entry at offset 416... entry "9ae2ff9f80888b89751a070b74a65b7c63cb654d.jpg" at block 0 offset 576 in directory inode 182 references free inode 16078036 would clear inode number in entry at offset 576... entry "75f97cb41375527482ce73d3397b918b1604a25d.jpg" at block 0 offset 2072 in directory inode 184 references free inode 16077904 would clear inode number in entry at offset 2072... entry "86508a98a89e28df4bcb78ff7c13cc990988c5dc.png" in shortform directory 191 references free inode 16078068 would have junked entry "86508a98a89e28df4bcb78ff7c13cc990988c5dc.png" in directory inode 191 entry "md.log" in shortform directory 8589935659 references free inode 8589954248 would have junked entry "md.log" in directory inode 8589935659 entry "frame159.xtc" in shortform directory 8589935659 references free inode 8589954252 would have junked entry "frame159.xtc" in directory inode 8589935659 entry "checkpt.crc" in shortform directory 8589935659 references free inode 8589954255 would have junked entry "checkpt.crc" in directory inode 8589935659 entry "state_prev.cpt" in shortform directory 8589935659 references free inode 8589942499 would have junked entry "state_prev.cpt" in directory inode 8589935659 would have corrected i8 count in directory 8589935659 from 10 to 6 setting reflink flag on inode 6446624915 setting reflink flag on inode 8589935238 setting reflink flag on inode 8589935266 setting reflink flag on inode 8589935321 setting reflink flag on inode 8589935550 setting reflink flag on inode 8589935558 setting reflink flag on inode 8589935650 setting reflink flag on inode 6446884318 Missing reference count record for (4/146) len 1 count 2 setting reflink flag on inode 8589935658 setting reflink flag on inode 8589935661 Missing reference count record for (3/21205309) len 44 count 2 setting reflink flag on inode 8589935662 Missing reference count record for (4/154) len 1 count 2 Missing reference count record for (4/179) len 1 count 2 Missing reference count record for (4/536) len 1 count 2 Missing reference count record for (4/561) len 1 count 2 Missing reference count record for (4/2092) len 5 count 2 setting reflink flag on inode 8589935664 setting reflink flag on inode 8589935670 setting reflink flag on inode 8589935671 Missing reference count record for (4/27175) len 1 count 2 setting reflink flag on inode 8589938573 setting reflink flag on inode 8589939264 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting. and then again with xfs_repair -v: Quote Phase 1 - find and verify superblock... - block cache size set to 715704 entries Phase 2 - using internal log - zero log... zero_log: head block 4131029 tail block 4131017 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. When array is started the drive is mounted but I cannot browse the content. How do I replay the log? Or do I use xfs_repair -L to destroy the log? Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 3 minutes ago, blakeslade said: Or do I use xfs_repair -L to destroy the log? This, usually it's not a problem. Quote Link to comment
blakeslade Posted March 22, 2022 Author Share Posted March 22, 2022 Thank you JorgeB. And now I have a question about the dockers, I am unable to connect to any of them. Is this as simple as redoing the settings files? When I upgraded the MB, CPU, RAM and PSU the server got a new ip address. Should I tell the router to set the old one? Thanks! Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 Do you mean you can't connect to them using the GUI? Quote Link to comment
blakeslade Posted March 22, 2022 Author Share Posted March 22, 2022 Initially none of them worked at all using the GUI. I am not familiar with how to connect via console. I am now only having issues with two dockers: Nextcloud (unable to connect initially then internal server error) and Transmission client (unable to connect). How to connect via console? Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 Sorry, can't really help with that, if you can't fix it best to start a new thread with an appropriate title. Quote Link to comment
blakeslade Posted March 22, 2022 Author Share Posted March 22, 2022 Yes of course. Thank you! 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.