REV3RSE

Update: I re-ran the xfs_repair with the -L flag (I thought I had already done this but tried again). The drive is now mounted! All shares seem to be intact, and I don’t see a lost+found folder. I will replace the SATA cable anyways this evening.

Attached is the Diagnostics file. tower-diagnostics-20240423-0722.zip

Yesterday I updated from 6.12.8 to 6.12.10. After the update, one of my disks says: Unmountable: Unsupported or no file system I have attached the SMART report from the disk. I don't necessarily have a ton of experience looking at this type of report, but I know the disk is old. I have already tried going into Maintenance Mode and run an XFS_repair Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata Metadata CRC error detected at 0x44228d, xfs_bnobt block 0x5f998cd8/0x1000 btree block 6/17342363 is suspect, error -74 bad magic # 0x561bfe36 in btbno block 6/17342363 Metadata CRC error detected at 0x44228d, xfs_cntbt block 0x5f999da0/0x1000 btree block 6/17342900 is suspect, error -74 bad magic # 0x596663e6 in btcnt block 6/17342900 Metadata corruption detected at 0x441fa0, xfs_bnobt block 0x6baa1ba8/0x1000 btree block 7/12119669 is suspect, error -117 bad magic # 0x41423343 in btbno block 7/12119669 agf_freeblks 4778986, counted 4777979 in ag 6 agf_btreeblks 4, counted 2 in ag 6 agf_freeblks 2854307, counted 2624931 in ag 3 agf_longest 216074, counted 112978 in ag 3 agf_freeblks 7888810, counted 7954346 in ag 5 Metadata CRC error detected at 0x44228d, xfs_cntbt block 0x6baaa928/0x1000 btree block 7/12124197 is suspect, error -74 bad magic # 0x5d2f42c6 in btcnt block 7/12124197 agf_freeblks 7638459, counted 7637887 in ag 7 agf_btreeblks 22, counted 20 in ag 7 sb_fdblocks 239046614, counted 239045031 - 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 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - 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 - agno = 7 - agno = 12 - agno = 13 - agno = 15 - agno = 9 - agno = 10 - agno = 5 - agno = 11 - agno = 6 - agno = 14 - agno = 8 - agno = 4 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 (2053203701:1284914176) is ahead of log (8:458752). Format log to cycle 2053203704. done I see errors above but the repair does not seem to solve anything. I tried making sure the SATA cable was properly plugged into drive and mobo. When booting, the drive was removed from the array for some reason, and re-adding it caused a data-rebuild. After the data-rebuild, same error showed. My guess is that the corruption happened a while ago and was written to the parity? I probably need to replace this drive at some point due to old age, but is there any way to fix my array and get data back first? tower-smart-20240423-0004.zip

Got it. I assumed that the older minecraft versions would work on the latest version of java, that does not seem to be the case. All of my servers were working on the default java version before I updated the docker container. I was unaware multiple versions of java were installed in the container as well. I set the java path of my 1.16.5 server to /usr/lib/jvm/java-8-openjdk/jre/bin/java and it loaded up properly!

My 1.17 server seemed to launch, but my 1.16.5 server as well as my servers with older versions of minecraft seemed to not launch.