Spydawg

Members
  • Posts

    99
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Spydawg's Achievements

Apprentice

Apprentice (3/14)

2

Reputation

  1. ok found the corrupted files and I deleted them and replaced them.. errors gone now.. Also I did a memtest ran it over night no errors.. I believe a power failure I had other day caused the corruption. I'll see if it happens again.. Thanks for the help..
  2. Can this be fixed without formatting the cache drive?
  3. I got these log errors, its on my cache drive for my unraid server. Should I be worried? Feb 25 02:01:08 Tower emhttpd: read SMART /dev/sdd Feb 25 02:01:08 Tower emhttpd: read SMART /dev/sde Feb 25 02:01:23 Tower emhttpd: read SMART /dev/sdl Feb 25 02:13:01 Tower emhttpd: read SMART /dev/sdi Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 27, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 28, gen 0 Feb 25 02:15:56 Tower shfs: copy_file: /mnt/cache/TV_Tower/Star Trek- Discovery/Season 4/Star Trek - Discovery - S04E10 - The Galactic Barrier.mkv /mnt/disk4/TV_Tower/Star Trek- Discovery/Season 4/Star Trek - Discovery - S04E10 - The Galactic Barrier.mkv.partial (5) Input/output error Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 29, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 30, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 31, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0 Feb 25 02:16:11 Tower emhttpd: read SMART /dev/sdb Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 33, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 34, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 35, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 36, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 37, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 38, gen 0 Feb 25 02:25:16 Tower emhttpd: read SMART /dev/sdf Feb 25 02:29:47 Tower crond[1421]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Feb 25 02:29:59 Tower emhttpd: read SMART /dev/sdj Feb 25 02:32:57 Tower kernel: mdcmd (63): set md_write_method 1 Feb 25 02:32:57 Tower kernel: Feb 25 03:10:47 Tower emhttpd: spinning down /dev/sdf Feb 25 03:12:58 Tower kernel: mdcmd (64): set md_write_method 0 Feb 25 03:12:58 Tower kernel: Feb 25 03:18:16 Tower emhttpd: spinning down /dev/sdg
  4. Ok np. Thanks for giving me a hand.
  5. oh ok will do. thanks
  6. thanks, installed it and when I click detect it doesn't detect anything.. Guess my board is not supported
  7. I just setup my new build for my unraid. Specs Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING AMD Ryzen 7 2700 Eight-Core @ 3200 MHz 16 gig DDR4 memory Its all up and running. Does unraid support cpu temps for AMD Ryzen? It's not showing any temps in my dashboard. Hard drive temps are showing up fine. Thanks
  8. Upgrade when great! Only hiccup was I replaced my cache ssd drive with a M.2 drive on my motherboard, and I forgot to copy my appdata folder for my dockers data. SO i had to connect the old ssd up mount it then copy the data to new M.2 cache drive thanks!
  9. My disk 5 was replaced not long ago. And was working fine until the usb key died. I did run the xfs-repair without -n and it came back up. But had no data on it afterwards. It only had a gig or 2 on it, and I had the data on my main computer still, so nothing lost. Thanks for all the help!
  10. ok this is results.. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata corruption detected at 0x4392a8, xfs_agf block 0x1/0x200 Metadata corruption detected at 0x4392a8, xfs_agf block 0x15d508ec9/0x200 Metadata corruption detected at 0x462fc0, xfs_agi block 0x2/0x200 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agf 0 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agi 0 would reset bad agf for ag 0 would reset bad agi for ag 0 bad uncorrected agheader 0, skipping ag... Metadata corruption detected at 0x4392a8, xfs_agf block 0x74702f99/0x200 Metadata corruption detected at 0x462fc0, xfs_agi block 0x15d508eca/0x200 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agf 3 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agi 3 would reset bad agf for ag 3 would reset bad agi for ag 3 bad uncorrected agheader 3, skipping ag... Metadata corruption detected at 0x462fc0, xfs_agi block 0x74702f9a/0x200 Metadata corruption detected at 0x4392a8, xfs_agf block 0xe8e05f31/0x200 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agf 1 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agi 1 would reset bad agf for ag 1 would reset bad agi for ag 1 bad uncorrected agheader 1, skipping ag... Metadata corruption detected at 0x462fc0, xfs_agi block 0xe8e05f32/0x200 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agf 2 bad uuid e0ba330f-b396-470f-8dfc-ee8c32745fe8 for agi 2 would reset bad agf for ag 2 would reset bad agi for ag 2 bad uncorrected agheader 2, skipping ag... sb_icount 64, counted 0 sb_ifree 61, counted 0 sb_fdblocks 976277675, counted 0 root inode chunk not found Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 UUID mismatch on inode 128 UUID mismatch on inode 129 UUID mismatch on inode 130 UUID mismatch on inode 131 UUID mismatch on inode 132 UUID mismatch on inode 133 UUID mismatch on inode 134 UUID mismatch on inode 135 UUID mismatch on inode 136 UUID mismatch on inode 137 UUID mismatch on inode 138 UUID mismatch on inode 139 UUID mismatch on inode 140 UUID mismatch on inode 141 UUID mismatch on inode 142 UUID mismatch on inode 143 UUID mismatch on inode 144 UUID mismatch on inode 145 UUID mismatch on inode 146 UUID mismatch on inode 147 UUID mismatch on inode 148 UUID mismatch on inode 149 UUID mismatch on inode 150 UUID mismatch on inode 151 UUID mismatch on inode 152 UUID mismatch on inode 153 UUID mismatch on inode 154 UUID mismatch on inode 155 UUID mismatch on inode 156 UUID mismatch on inode 157 UUID mismatch on inode 158 UUID mismatch on inode 159 UUID mismatch on inode 160 UUID mismatch on inode 161 UUID mismatch on inode 162 UUID mismatch on inode 163 UUID mismatch on inode 164 UUID mismatch on inode 165 UUID mismatch on inode 166 UUID mismatch on inode 167 UUID mismatch on inode 168 UUID mismatch on inode 169 UUID mismatch on inode 170 UUID mismatch on inode 171 UUID mismatch on inode 172 UUID mismatch on inode 173 UUID mismatch on inode 174 UUID mismatch on inode 175 UUID mismatch on inode 176 UUID mismatch on inode 177 UUID mismatch on inode 178 UUID mismatch on inode 179 UUID mismatch on inode 180 UUID mismatch on inode 181 UUID mismatch on inode 182 UUID mismatch on inode 183 UUID mismatch on inode 184 UUID mismatch on inode 185 UUID mismatch on inode 186 UUID mismatch on inode 187 UUID mismatch on inode 188 UUID mismatch on inode 189 UUID mismatch on inode 190 UUID mismatch on inode 191 UUID mismatch on inode 128 would clear root inode 128 UUID mismatch on inode 129 would clear realtime bitmap inode 129 UUID mismatch on inode 130 would clear realtime summary inode 130 UUID mismatch on inode 131 would have cleared inode 131 UUID mismatch on inode 132 would have cleared inode 132 UUID mismatch on inode 133 would have cleared inode 133 UUID mismatch on inode 134 would have cleared inode 134 UUID mismatch on inode 135 would have cleared inode 135 UUID mismatch on inode 136 would have cleared inode 136 UUID mismatch on inode 137 would have cleared inode 137 UUID mismatch on inode 138 would have cleared inode 138 UUID mismatch on inode 139 would have cleared inode 139 UUID mismatch on inode 140 would have cleared inode 140 UUID mismatch on inode 141 would have cleared inode 141 UUID mismatch on inode 142 would have cleared inode 142 UUID mismatch on inode 143 would have cleared inode 143 UUID mismatch on inode 144 would have cleared inode 144 UUID mismatch on inode 145 would have cleared inode 145 UUID mismatch on inode 146 would have cleared inode 146 UUID mismatch on inode 147 would have cleared inode 147 UUID mismatch on inode 148 would have cleared inode 148 UUID mismatch on inode 149 would have cleared inode 149 UUID mismatch on inode 150 would have cleared inode 150 UUID mismatch on inode 151 would have cleared inode 151 UUID mismatch on inode 152 would have cleared inode 152 UUID mismatch on inode 153 would have cleared inode 153 UUID mismatch on inode 154 would have cleared inode 154 UUID mismatch on inode 155 would have cleared inode 155 UUID mismatch on inode 156 would have cleared inode 156 UUID mismatch on inode 157 would have cleared inode 157 UUID mismatch on inode 158 would have cleared inode 158 UUID mismatch on inode 159 would have cleared inode 159 UUID mismatch on inode 160 would have cleared inode 160 UUID mismatch on inode 161 would have cleared inode 161 UUID mismatch on inode 162 would have cleared inode 162 UUID mismatch on inode 163 would have cleared inode 163 UUID mismatch on inode 164 would have cleared inode 164 UUID mismatch on inode 165 would have cleared inode 165 UUID mismatch on inode 166 would have cleared inode 166 UUID mismatch on inode 167 would have cleared inode 167 UUID mismatch on inode 168 would have cleared inode 168 UUID mismatch on inode 169 would have cleared inode 169 UUID mismatch on inode 170 would have cleared inode 170 UUID mismatch on inode 171 would have cleared inode 171 UUID mismatch on inode 172 would have cleared inode 172 UUID mismatch on inode 173 would have cleared inode 173 UUID mismatch on inode 174 would have cleared inode 174 UUID mismatch on inode 175 would have cleared inode 175 UUID mismatch on inode 176 would have cleared inode 176 UUID mismatch on inode 177 would have cleared inode 177 UUID mismatch on inode 178 would have cleared inode 178 UUID mismatch on inode 179 would have cleared inode 179 UUID mismatch on inode 180 would have cleared inode 180 UUID mismatch on inode 181 would have cleared inode 181 UUID mismatch on inode 182 would have cleared inode 182 UUID mismatch on inode 183 would have cleared inode 183 UUID mismatch on inode 184 would have cleared inode 184 UUID mismatch on inode 185 would have cleared inode 185 UUID mismatch on inode 186 would have cleared inode 186 UUID mismatch on inode 187 would have cleared inode 187 UUID mismatch on inode 188 would have cleared inode 188 UUID mismatch on inode 189 would have cleared inode 189 UUID mismatch on inode 190 would have cleared inode 190 UUID mismatch on inode 191 would have cleared inode 191 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... root inode would be lost - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 UUID mismatch on inode 128 would clear root inode 128 - agno = 1 UUID mismatch on inode 129 would clear realtime bitmap inode 129 UUID mismatch on inode 130 would clear realtime summary inode 130 UUID mismatch on inode 131 would have cleared inode 131 UUID mismatch on inode 132 would have cleared inode 132 UUID mismatch on inode 133 would have cleared inode 133 UUID mismatch on inode 134 would have cleared inode 134 UUID mismatch on inode 135 would have cleared inode 135 UUID mismatch on inode 136 would have cleared inode 136 UUID mismatch on inode 137 would have cleared inode 137 UUID mismatch on inode 138 would have cleared inode 138 UUID mismatch on inode 139 would have cleared inode 139 UUID mismatch on inode 140 would have cleared inode 140 UUID mismatch on inode 141 would have cleared inode 141 UUID mismatch on inode 142 would have cleared inode 142 UUID mismatch on inode 143 would have cleared inode 143 UUID mismatch on inode 144 would have cleared inode 144 UUID mismatch on inode 145 would have cleared inode 145 UUID mismatch on inode 146 would have cleared inode 146 UUID mismatch on inode 147 would have cleared inode 147 UUID mismatch on inode 148 would have cleared inode 148 UUID mismatch on inode 149 would have cleared inode 149 UUID mismatch on inode 150 would have cleared inode 150 UUID mismatch on inode 151 would have cleared inode 151 UUID mismatch on inode 152 would have cleared inode 152 UUID mismatch on inode 153 would have cleared inode 153 UUID mismatch on inode 154 would have cleared inode 154 UUID mismatch on inode 155 would have cleared inode 155 UUID mismatch on inode 156 would have cleared inode 156 UUID mismatch on inode 157 would have cleared inode 157 UUID mismatch on inode 158 would have cleared inode 158 UUID mismatch on inode 159 would have cleared inode 159 UUID mismatch on inode 160 would have cleared inode 160 UUID mismatch on inode 161 would have cleared inode 161 UUID mismatch on inode 162 would have cleared inode 162 UUID mismatch on inode 163 would have cleared inode 163 UUID mismatch on inode 164 would have cleared inode 164 UUID mismatch on inode 165 would have cleared inode 165 UUID mismatch on inode 166 would have cleared inode 166 UUID mismatch on inode 167 would have cleared inode 167 UUID mismatch on inode 168 would have cleared inode 168 UUID mismatch on inode 169 would have cleared inode 169 UUID mismatch on inode 170 would have cleared inode 170 UUID mismatch on inode 171 would have cleared inode 171 UUID mismatch on inode 172 would have cleared inode 172 UUID mismatch on inode 173 would have cleared inode 173 UUID mismatch on inode 174 would have cleared inode 174 UUID mismatch on inode 175 would have cleared inode 175 UUID mismatch on inode 176 would have cleared inode 176 UUID mismatch on inode 177 would have cleared inode 177 UUID mismatch on inode 178 would have cleared inode 178 UUID mismatch on inode 179 would have cleared inode 179 UUID mismatch on inode 180 would have cleared inode 180 UUID mismatch on inode 181 would have cleared inode 181 UUID mismatch on inode 182 would have cleared inode 182 UUID mismatch on inode 183 would have cleared inode 183 UUID mismatch on inode 184 would have cleared inode 184 UUID mismatch on inode 185 would have cleared inode 185 UUID mismatch on inode 186 would have cleared inode 186 UUID mismatch on inode 187 would have cleared inode 187 UUID mismatch on inode 188 would have cleared inode 188 UUID mismatch on inode 189 would have cleared inode 189 UUID mismatch on inode 190 would have cleared inode 190 UUID mismatch on inode 191 would have cleared inode 191 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... would reinitialize root directory would reinitialize realtime bitmap inode would reinitialize realtime summary inode - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.
  11. ok found it, i had to turn off array, change it's FS from auto to xfs. Then in maintenance mode I had check file system.. Its running now.
  12. Linux 4.19.24-Unraid. root@Tower:~# xfs_repair -v /dev/md5 Phase 1 - find and verify superblock... - block cache size set to 344096 entries Phase 2 - using internal log - zero log... * ERROR: mismatched uuid in log * SB : e0ba330f-b396-470f-8dfc-ee8c32745fe8 * log: ffa78544-b912-40c3-bc5e-641e4af1629b zero_log: head block 3452 tail block 3452 - scan filesystem freespace and inode maps... Metadata corruption detected at 0x4392a8, xfs_agf block 0xe8e05f31/0x200Metadata corruption detected at 0x4392a8, xfs_agf block 0x1/0x200 Metadata corruption detected at 0x4392a8, xfs_agf block 0x74702f99/0x200 Metadata corruption detected at 0x462fc0, xfs_agi block 0xe8e05f32/0x200 Metadata corruption detected at 0x462fc0, xfs_agi block 0x2/0x200Metadata corruption detected at 0x462fc0, xfs_agi block 0x74702f9a/0x200 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agf 2 Metadata corruption detected at 0x4392a8, xfs_agf block 0x15d508ec9/0x200 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agi 2 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agf 1 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agi 1 reset bad agf for ag 2 Metadata corruption detected at 0x462fc0, xfs_agi block 0x15d508eca/0x200 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agf 0 reset bad agi for ag 2 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agi 0 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agf 3 reset bad agf for ag 1 Metadata corruption detected at 0x438f70, xfs_agfl block 0xe8e05f33/0x200 bad uuid ffa78544-b912-40c3-bc5e-641e4af1629b for agi 3 reset bad agi for ag 1 reset bad agf for ag 0 reset bad agf for ag 3 Metadata corruption detected at 0x438f70, xfs_agfl block 0x74702f9b/0x200Metadata corruption detected at 0x453108, xfs_allocbt block 0xe8e05f38/0x1000 reset bad agi for ag 0 reset bad agi for ag 3 btree block 2/1 is suspect, error -117 Metadata corruption detected at 0x438f70, xfs_agfl block 0x3/0x200 Metadata corruption detected at 0x453108, xfs_allocbt block 0x74702fa0/0x1000 Metadata corruption detected at 0x438f70, xfs_agfl block 0x15d508ecb/0x200 Metadata corruption detected at 0x453108, xfs_allocbt block 0xe8e05f40/0x1000 Metadata corruption detected at 0x453108, xfs_allocbt block 0x8/0x1000 btree block 2/2 is suspect, error -117 btree block 1/1 is suspect, error -117 btree block 0/1 is suspect, error -117 Metadata corruption detected at 0x453108, xfs_allocbt block 0x15d508ed0/0x1000 btree block 3/1 is suspect, error -117 Metadata corruption detected at 0x453108, xfs_inobt block 0xe8e05f48/0x1000 Metadata corruption detected at 0x453108, xfs_allocbt block 0x10/0x1000 btree block 2/3 is suspect, error -117 Metadata corruption detected at 0x453108, xfs_allocbt block 0x74702fa8/0x1000 btree block 0/2 is suspect, error -117 btree block 1/2 is suspect, error -117 Metadata corruption detected at 0x453108, xfs_allocbt block 0x15d508ed8/0x1000 btree block 3/2 is suspect, error -117 Metadata corruption detected at 0x453108, xfs_inobt block 0xe8e05f50/0x1000Metadata corruption detected at 0x453108, xfs_inobt block 0x18/0x1000Metadata corruption detected at 0x453108, xfs_inobt block 0x74702fb0/0x1000 Metadata corruption detected at 0x453108, xfs_inobt block 0x15d508ee0/0x1000btree block 2/4 is suspect, error -117 btree block 1/3 is suspect, error -117 undiscovered finobt record, ino 4308048064 (2/13080768) btree block 0/3 is suspect, error -117 btree block 3/3 is suspect, error -117 Metadata corruption detected at 0x453108, xfs_inobt block 0x74702fb8/0x1000 btree block 1/4 is suspect, error -117 undiscovered finobt record, ino 2164250176 (1/16766528) Metadata corruption detected at 0x453108, xfs_inobt block 0x20/0x1000 Metadata corruption detected at 0x453108, xfs_inobt block 0x15d508ee8/0x1000 btree block 0/4 is suspect, error -117 btree block 3/4 is suspect, error -117 undiscovered finobt record, ino 8368384 (0/8368384) undiscovered finobt record, ino 6446617024 (3/4166080) sb_icount 64, counted 1088 sb_ifree 61, counted 106 sb_fdblocks 976277675, counted 873146780 root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... found inodes not in the inode allocation tree found inodes not in the inode allocation tree found inodes not in the inode allocation tree found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 UUID mismatch on inode 128 UUID mismatch on inode 129 UUID mismatch on inode 130 UUID mismatch on inode 131 UUID mismatch on inode 132 UUID mismatch on inode 133 UUID mismatch on inode 134 UUID mismatch on inode 135 UUID mismatch on inode 136 UUID mismatch on inode 137 UUID mismatch on inode 138 UUID mismatch on inode 139 UUID mismatch on inode 140 UUID mismatch on inode 141 UUID mismatch on inode 142 UUID mismatch on inode 143 UUID mismatch on inode 144 UUID mismatch on inode 145 UUID mismatch on inode 146 UUID mismatch on inode 147 UUID mismatch on inode 148 UUID mismatch on inode 149 UUID mismatch on inode 150 UUID mismatch on inode 151 UUID mismatch on inode 152 UUID mismatch on inode 153 UUID mismatch on inode 154 UUID mismatch on inode 155 UUID mismatch on inode 156 UUID mismatch on inode 157 UUID mismatch on inode 158 UUID mismatch on inode 159 UUID mismatch on inode 160 UUID mismatch on inode 161 UUID mismatch on inode 162 UUID mismatch on inode 163 UUID mismatch on inode 164 UUID mismatch on inode 165 UUID mismatch on inode 166 UUID mismatch on inode 167 UUID mismatch on inode 168 UUID mismatch on inode 169 UUID mismatch on inode 170 UUID mismatch on inode 171 UUID mismatch on inode 172 UUID mismatch on inode 173 UUID mismatch on inode 174 UUID mismatch on inode 175 UUID mismatch on inode 176 UUID mismatch on inode 177 UUID mismatch on inode 178 UUID mismatch on inode 179 UUID mismatch on inode 180 UUID mismatch on inode 181 UUID mismatch on inode 182 UUID mismatch on inode 183 UUID mismatch on inode 184 UUID mismatch on inode 185 UUID mismatch on inode 186 UUID mismatch on inode 187 UUID mismatch on inode 188 UUID mismatch on inode 189 UUID mismatch on inode 190 UUID mismatch on inode 191 UUID mismatch on inode 128 cleared root inode 128 UUID mismatch on inode 129 cleared realtime bitmap inode 129 UUID mismatch on inode 130 cleared realtime summary inode 130 UUID mismatch on inode 131 cleared inode 131 UUID mismatch on inode 132 cleared inode 132 UUID mismatch on inode 133 cleared inode 133 UUID mismatch on inode 134 cleared inode 134 UUID mismatch on inode 135 cleared inode 135 UUID mismatch on inode 136 cleared inode 136 UUID mismatch on inode 137 cleared inode 137 UUID mismatch on inode 138 cleared inode 138 UUID mismatch on inode 139 cleared inode 139 UUID mismatch on inode 140 cleared inode 140 UUID mismatch on inode 141 cleared inode 141 UUID mismatch on inode 142 cleared inode 142 UUID mismatch on inode 143 cleared inode 143 UUID mismatch on inode 144 cleared inode 144 UUID mismatch on inode 145 cleared inode 145 UUID mismatch on inode 146 cleared inode 146 UUID mismatch on inode 147 cleared inode 147 UUID mismatch on inode 148 cleared inode 148 UUID mismatch on inode 149 cleared inode 149 UUID mismatch on inode 150 cleared inode 150 UUID mismatch on inode 151 cleared inode 151 UUID mismatch on inode 152 cleared inode 152 UUID mismatch on inode 153 cleared inode 153 UUID mismatch on inode 154 cleared inode 154 UUID mismatch on inode 155 cleared inode 155 UUID mismatch on inode 156 cleared inode 156 UUID mismatch on inode 157 cleared inode 157 UUID mismatch on inode 158 cleared inode 158 UUID mismatch on inode 159 cleared inode 159 UUID mismatch on inode 160 cleared inode 160 UUID mismatch on inode 161 cleared inode 161 UUID mismatch on inode 162 cleared inode 162 UUID mismatch on inode 163 cleared inode 163 UUID mismatch on inode 164 cleared inode 164 UUID mismatch on inode 165 cleared inode 165 UUID mismatch on inode 166 cleared inode 166 UUID mismatch on inode 167 cleared inode 167 UUID mismatch on inode 168 cleared inode 168 UUID mismatch on inode 169 cleared inode 169 UUID mismatch on inode 170 cleared inode 170 UUID mismatch on inode 171 cleared inode 171 UUID mismatch on inode 172 cleared inode 172 UUID mismatch on inode 173 cleared inode 173 UUID mismatch on inode 174 cleared inode 174 UUID mismatch on inode 175 cleared inode 175 UUID mismatch on inode 176 cleared inode 176 UUID mismatch on inode 177 cleared inode 177 UUID mismatch on inode 178 cleared inode 178 UUID mismatch on inode 179 cleared inode 179 UUID mismatch on inode 180 cleared inode 180 UUID mismatch on inode 181 cleared inode 181 UUID mismatch on inode 182 cleared inode 182 UUID mismatch on inode 183 cleared inode 183 UUID mismatch on inode 184 cleared inode 184 UUID mismatch on inode 185 cleared inode 185 UUID mismatch on inode 186 cleared inode 186 UUID mismatch on inode 187 cleared inode 187 UUID mismatch on inode 188 cleared inode 188 UUID mismatch on inode 189 cleared inode 189 UUID mismatch on inode 190 cleared inode 190 UUID mismatch on inode 191 cleared inode 191 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... root inode lost - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... reinitializing root directory reinitializing realtime bitmap inode reinitializing realtime summary inode - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... resetting inode 128 nlinks from 1 to 2 XFS_REPAIR Summary Fri Mar 22 16:11:03 2019 Phase Start End Duration Phase 1: 03/22 16:11:02 03/22 16:11:03 1 second Phase 2: 03/22 16:11:03 03/22 16:11:03 Phase 3: 03/22 16:11:03 03/22 16:11:03 Phase 4: 03/22 16:11:03 03/22 16:11:03 Phase 5: 03/22 16:11:03 03/22 16:11:03 Phase 6: 03/22 16:11:03 03/22 16:11:03 Phase 7: 03/22 16:11:03 03/22 16:11:03 Total run time: 1 second done root@Tower:~#
  13. nope even in maintenance mode, no check disk option