Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

sohailoo

Members
  • Joined

  • Last visited

Everything posted by sohailoo

  1. oh, sorry just noticed the option. I'll give it a shit and get back to you. thanks btw
  2. just to be sure, by safe mode you mean Maintenace mode? if so, i booted into Maintenace mode and when checking the log there was no errors other than these three. Jul 1 14:32:49 Tower kernel: I/O error, dev sdf, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2 Jul 1 14:32:49 Tower kernel: I/O error, dev sdf, sector 136 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Jul 1 14:32:49 Tower kernel: I/O error, dev sdf, sector 88 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 when enabling docker service I get this error: docker service failed to start Couldn't create socket: [2] No such file or directory.
  3. did that yesterday and it ddin't seem to help. my logs seems to be filled with the same errors over and over tower-diagnostics-20230701-0616.zip
  4. rebooting solve the problem temporarily but it happens again
  5. can't figure out what is causing this error, any help is appreciated tower-diagnostics-20230628-0449.zip
  6. after updating to 6.12 and reformatting my cache to zfs , vms stopped working. tower-diagnostics-20230621-0547.zip
  7. so i updated unraid to 6.12 for 6.11.5, and i'm trying to move everything from my pools to the array to format the pools to zfs. the problem is the mover is REALLY slow, i change the write method to reconstruct write , but it didn't make any difference. as you can see in the picture the speed is 19.4 mb/s but the problem is it stays like this for a second and then go to zero for a couple of second and be something between 2 mb/s and 22mb/s for a second and go back to zero again. is this normal? i recall when moving 400 gigs from the download ssd it didn't take too long to do it maybe an hour or 2 max. now i've been running mover for almost 3 hours and it only moved around 50-70 gigs i disabled docker and vm so the mover doesn't run into problems when moving the appdata tower-diagnostics-20230620-0702.zip
  8. Thanks i just changed the primary vdisk bus from virtio to sata and it booted up successfully. was i supposed to have my vms on sata?
  9. yup i'm sure since if i was booting from the iso i would get the install windows window not startup repair nonetheless i removed the iso and tried again and i'm still not getting the startup settings option when i try looking for the disks using diskpart i get there are no fixed disks to show.
  10. anyone have any clue about how i can fix this or at least extract the data from the .img?
  11. tried that and still no startup settings
  12. i don't have an option for safe mode
  13. i expanded my windows 10 vm a month ago and it was working perfectly fine. today i installed docker on the vm, restarted it and it stopped working now i'm stuck at a loop of startup repair i've entered the cmd in the advanced settings and tried to check DISKPART but when i try list disk, i get "There Are No Fixed Disks to Show" is there any way to repair the img or at least recover some stuff that wasn't saved to the array?
  14. oh the drive seems to be mounted just fine when i started the array in normal mode. just a couple of questions 1- it seems that the drive is empty with no data on it other than lost+found folder which the repair thingy created. did the procedure delete everything on the drive ? ( i can't seem to remember if there was anything on the drive since i installed it like 2 days ago) 2- what might've caused the problem? i only noticed it after i deleted a bunch of .zip files (1.8 tb) so I don't know if it was cause by the deleting of the files or something else. 3- when i replaced the drive i didn't go to tools and made new config. could that be the cause of it, and should I go do the new config? 4- in case the fixing thingy did delete files or corrupt some of it, is there a way to know exactly which files got deleted or corrupted? tower-diagnostics-20230524-1506.zip
  15. just did that and it's still unmountable. Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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... Metadata CRC error detected at 0x43d440, xfs_agf block 0x1/0x200 agf has bad CRC for ag 0 Metadata CRC error detected at 0x468740, xfs_agi block 0x2/0x200 agi has bad CRC for ag 0 clearing needsrepair flag and regenerating metadata bad magic # 0x0 for agf 0 bad version # 0 for agf 0 bad length 0 for agf 0, should be 268435455 bad uuid 00000000-0000-0000-0000-000000000000 for agf 0 bad magic # 0x0 for agi 0 bad version # 0 for agi 0 bad length # 0 for agi 0, should be 268435455 bad uuid 00000000-0000-0000-0000-000000000000 for agi 0 reset bad agf for ag 0 reset bad agi for ag 0 bad levels 0 for btbno root, agno 0 bad agbno 0 for btbno root, agno 0 bad levels 0 for btbcnt root, agno 0 bad agbno 0 for btbcnt root, agno 0 bad levels 0 for refcountbt root, agno 0 bad agbno 0 for refcntbt root, agno 0 bad levels 0 for inobt root, agno 0 bad agbno 0 for inobt root, agno 0 bad levels 0 for finobt root, agno 0 bad agbno 0 for finobt root, agno 0 agi unlinked bucket 0 is 0 in ag 0 (inode=0) agi unlinked bucket 1 is 0 in ag 0 (inode=0) agi unlinked bucket 2 is 0 in ag 0 (inode=0) agi unlinked bucket 3 is 0 in ag 0 (inode=0) agi unlinked bucket 4 is 0 in ag 0 (inode=0) agi unlinked bucket 5 is 0 in ag 0 (inode=0) agi unlinked bucket 6 is 0 in ag 0 (inode=0) agi unlinked bucket 7 is 0 in ag 0 (inode=0) agi unlinked bucket 8 is 0 in ag 0 (inode=0) agi unlinked bucket 9 is 0 in ag 0 (inode=0) agi unlinked bucket 10 is 0 in ag 0 (inode=0) agi unlinked bucket 11 is 0 in ag 0 (inode=0) agi unlinked bucket 12 is 0 in ag 0 (inode=0) agi unlinked bucket 13 is 0 in ag 0 (inode=0) agi unlinked bucket 14 is 0 in ag 0 (inode=0) agi unlinked bucket 15 is 0 in ag 0 (inode=0) agi unlinked bucket 16 is 0 in ag 0 (inode=0) agi unlinked bucket 17 is 0 in ag 0 (inode=0) agi unlinked bucket 18 is 0 in ag 0 (inode=0) agi unlinked bucket 19 is 0 in ag 0 (inode=0) agi unlinked bucket 20 is 0 in ag 0 (inode=0) agi unlinked bucket 21 is 0 in ag 0 (inode=0) agi unlinked bucket 22 is 0 in ag 0 (inode=0) agi unlinked bucket 23 is 0 in ag 0 (inode=0) agi unlinked bucket 24 is 0 in ag 0 (inode=0) agi unlinked bucket 25 is 0 in ag 0 (inode=0) agi unlinked bucket 26 is 0 in ag 0 (inode=0) agi unlinked bucket 27 is 0 in ag 0 (inode=0) agi unlinked bucket 28 is 0 in ag 0 (inode=0) agi unlinked bucket 29 is 0 in ag 0 (inode=0) agi unlinked bucket 30 is 0 in ag 0 (inode=0) agi unlinked bucket 31 is 0 in ag 0 (inode=0) agi unlinked bucket 32 is 0 in ag 0 (inode=0) agi unlinked bucket 33 is 0 in ag 0 (inode=0) agi unlinked bucket 34 is 0 in ag 0 (inode=0) agi unlinked bucket 35 is 0 in ag 0 (inode=0) agi unlinked bucket 36 is 0 in ag 0 (inode=0) agi unlinked bucket 37 is 0 in ag 0 (inode=0) agi unlinked bucket 38 is 0 in ag 0 (inode=0) agi unlinked bucket 39 is 0 in ag 0 (inode=0) agi unlinked bucket 40 is 0 in ag 0 (inode=0) agi unlinked bucket 41 is 0 in ag 0 (inode=0) agi unlinked bucket 42 is 0 in ag 0 (inode=0) agi unlinked bucket 43 is 0 in ag 0 (inode=0) agi unlinked bucket 44 is 0 in ag 0 (inode=0) agi unlinked bucket 45 is 0 in ag 0 (inode=0) agi unlinked bucket 46 is 0 in ag 0 (inode=0) agi unlinked bucket 47 is 0 in ag 0 (inode=0) agi unlinked bucket 48 is 0 in ag 0 (inode=0) agi unlinked bucket 49 is 0 in ag 0 (inode=0) agi unlinked bucket 50 is 0 in ag 0 (inode=0) agi unlinked bucket 51 is 0 in ag 0 (inode=0) agi unlinked bucket 52 is 0 in ag 0 (inode=0) agi unlinked bucket 53 is 0 in ag 0 (inode=0) agi unlinked bucket 54 is 0 in ag 0 (inode=0) agi unlinked bucket 55 is 0 in ag 0 (inode=0) agi unlinked bucket 56 is 0 in ag 0 (inode=0) agi unlinked bucket 57 is 0 in ag 0 (inode=0) agi unlinked bucket 58 is 0 in ag 0 (inode=0) agi unlinked bucket 59 is 0 in ag 0 (inode=0) agi unlinked bucket 60 is 0 in ag 0 (inode=0) agi unlinked bucket 61 is 0 in ag 0 (inode=0) agi unlinked bucket 62 is 0 in ag 0 (inode=0) agi unlinked bucket 63 is 0 in ag 0 (inode=0) sb_icount 0, counted 64 sb_ifree 0, counted 63 sb_fdblocks 1952984857, counted 1684549400 root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 Metadata corruption detected at 0x4379a3, xfs_inode block 0x80/0x4000 Metadata corruption detected at 0x4379a3, xfs_inode block 0xa0/0x4000 bad CRC for inode 128 bad magic number 0x0 on inode 128 bad version number 0x0 on inode 128 bad next_unlinked 0x0 on inode 128 inode identifier 0 mismatch on inode 128 bad CRC for inode 129 bad magic number 0x0 on inode 129 bad version number 0x0 on inode 129 bad next_unlinked 0x0 on inode 129 inode identifier 0 mismatch on inode 129 bad CRC for inode 130 bad magic number 0x0 on inode 130 bad version number 0x0 on inode 130 bad next_unlinked 0x0 on inode 130 inode identifier 0 mismatch on inode 130 bad CRC for inode 131 bad magic number 0x0 on inode 131 bad version number 0x0 on inode 131 bad next_unlinked 0x0 on inode 131 inode identifier 0 mismatch on inode 131 bad CRC for inode 132 bad magic number 0x0 on inode 132 bad version number 0x0 on inode 132 bad next_unlinked 0x0 on inode 132 inode identifier 0 mismatch on inode 132 bad CRC for inode 133 bad magic number 0x0 on inode 133 bad version number 0x0 on inode 133 bad next_unlinked 0x0 on inode 133 inode identifier 0 mismatch on inode 133 bad CRC for inode 134 bad magic number 0x0 on inode 134 bad version number 0x0 on inode 134 bad next_unlinked 0x0 on inode 134 inode identifier 0 mismatch on inode 134 bad CRC for inode 135 bad magic number 0x0 on inode 135 bad version number 0x0 on inode 135 bad next_unlinked 0x0 on inode 135 inode identifier 0 mismatch on inode 135 bad CRC for inode 136 bad magic number 0x0 on inode 136 bad version number 0x0 on inode 136 bad next_unlinked 0x0 on inode 136 inode identifier 0 mismatch on inode 136 bad CRC for inode 137 bad magic number 0x0 on inode 137 bad version number 0x0 on inode 137 bad next_unlinked 0x0 on inode 137 inode identifier 0 mismatch on inode 137 bad CRC for inode 138 bad magic number 0x0 on inode 138 bad version number 0x0 on inode 138 bad next_unlinked 0x0 on inode 138 inode identifier 0 mismatch on inode 138 bad CRC for inode 139 bad magic number 0x0 on inode 139 bad version number 0x0 on inode 139 bad next_unlinked 0x0 on inode 139 inode identifier 0 mismatch on inode 139 bad CRC for inode 140 bad magic number 0x0 on inode 140 bad version number 0x0 on inode 140 bad next_unlinked 0x0 on inode 140 inode identifier 0 mismatch on inode 140 bad CRC for inode 141 bad magic number 0x0 on inode 141 bad version number 0x0 on inode 141 bad next_unlinked 0x0 on inode 141 inode identifier 0 mismatch on inode 141 bad CRC for inode 142 bad magic number 0x0 on inode 142 bad version number 0x0 on inode 142 bad next_unlinked 0x0 on inode 142 inode identifier 0 mismatch on inode 142 bad CRC for inode 143 bad magic number 0x0 on inode 143 bad version number 0x0 on inode 143 bad next_unlinked 0x0 on inode 143 inode identifier 0 mismatch on inode 143 bad CRC for inode 144 bad magic number 0x0 on inode 144 bad version number 0x0 on inode 144 bad next_unlinked 0x0 on inode 144 inode identifier 0 mismatch on inode 144 bad CRC for inode 145 bad magic number 0x0 on inode 145 bad version number 0x0 on inode 145 bad next_unlinked 0x0 on inode 145 inode identifier 0 mismatch on inode 145 bad CRC for inode 146 bad magic number 0x0 on inode 146 bad version number 0x0 on inode 146 bad next_unlinked 0x0 on inode 146 inode identifier 0 mismatch on inode 146 bad CRC for inode 147 bad magic number 0x0 on inode 147 bad version number 0x0 on inode 147 bad next_unlinked 0x0 on inode 147 inode identifier 0 mismatch on inode 147 bad CRC for inode 148 bad magic number 0x0 on inode 148 bad version number 0x0 on inode 148 bad next_unlinked 0x0 on inode 148 inode identifier 0 mismatch on inode 148 bad CRC for inode 149 bad magic number 0x0 on inode 149 bad version number 0x0 on inode 149 bad next_unlinked 0x0 on inode 149 inode identifier 0 mismatch on inode 149 bad CRC for inode 150 bad magic number 0x0 on inode 150 bad version number 0x0 on inode 150 bad next_unlinked 0x0 on inode 150 inode identifier 0 mismatch on inode 150 bad CRC for inode 151 bad magic number 0x0 on inode 151 bad version number 0x0 on inode 151 bad next_unlinked 0x0 on inode 151 inode identifier 0 mismatch on inode 151 bad CRC for inode 152 bad magic number 0x0 on inode 152 bad version number 0x0 on inode 152 bad next_unlinked 0x0 on inode 152 inode identifier 0 mismatch on inode 152 bad CRC for inode 153 bad magic number 0x0 on inode 153 bad version number 0x0 on inode 153 bad next_unlinked 0x0 on inode 153 inode identifier 0 mismatch on inode 153 bad CRC for inode 154 bad magic number 0x0 on inode 154 bad version number 0x0 on inode 154 bad next_unlinked 0x0 on inode 154 inode identifier 0 mismatch on inode 154 bad CRC for inode 155 bad magic number 0x0 on inode 155 bad version number 0x0 on inode 155 bad next_unlinked 0x0 on inode 155 inode identifier 0 mismatch on inode 155 bad CRC for inode 156 bad magic number 0x0 on inode 156 bad version number 0x0 on inode 156 bad next_unlinked 0x0 on inode 156 inode identifier 0 mismatch on inode 156 bad CRC for inode 157 bad magic number 0x0 on inode 157 bad version number 0x0 on inode 157 bad next_unlinked 0x0 on inode 157 inode identifier 0 mismatch on inode 157 bad CRC for inode 158 bad magic number 0x0 on inode 158 bad version number 0x0 on inode 158 bad next_unlinked 0x0 on inode 158 inode identifier 0 mismatch on inode 158 bad CRC for inode 159 bad magic number 0x0 on inode 159 bad version number 0x0 on inode 159 bad next_unlinked 0x0 on inode 159 inode identifier 0 mismatch on inode 159 bad CRC for inode 160 bad magic number 0x0 on inode 160 bad version number 0x0 on inode 160 bad next_unlinked 0x0 on inode 160 inode identifier 0 mismatch on inode 160 bad CRC for inode 161 bad magic number 0x0 on inode 161 bad version number 0x0 on inode 161 bad next_unlinked 0x0 on inode 161 inode identifier 0 mismatch on inode 161 bad CRC for inode 162 bad magic number 0x0 on inode 162 bad version number 0x0 on inode 162 bad next_unlinked 0x0 on inode 162 inode identifier 0 mismatch on inode 162 bad CRC for inode 163 bad magic number 0x0 on inode 163 bad version number 0x0 on inode 163 bad next_unlinked 0x0 on inode 163 inode identifier 0 mismatch on inode 163 bad CRC for inode 164 bad magic number 0x0 on inode 164 bad version number 0x0 on inode 164 bad next_unlinked 0x0 on inode 164 inode identifier 0 mismatch on inode 164 bad CRC for inode 165 bad magic number 0x0 on inode 165 bad version number 0x0 on inode 165 bad next_unlinked 0x0 on inode 165 inode identifier 0 mismatch on inode 165 bad CRC for inode 166 bad magic number 0x0 on inode 166 bad version number 0x0 on inode 166 bad next_unlinked 0x0 on inode 166 inode identifier 0 mismatch on inode 166 bad CRC for inode 167 bad magic number 0x0 on inode 167 bad version number 0x0 on inode 167 bad next_unlinked 0x0 on inode 167 inode identifier 0 mismatch on inode 167 bad CRC for inode 168 bad magic number 0x0 on inode 168 bad version number 0x0 on inode 168 bad next_unlinked 0x0 on inode 168 inode identifier 0 mismatch on inode 168 bad CRC for inode 169 bad magic number 0x0 on inode 169 bad version number 0x0 on inode 169 bad next_unlinked 0x0 on inode 169 inode identifier 0 mismatch on inode 169 bad CRC for inode 170 bad magic number 0x0 on inode 170 bad version number 0x0 on inode 170 bad next_unlinked 0x0 on inode 170 inode identifier 0 mismatch on inode 170 bad CRC for inode 171 bad magic number 0x0 on inode 171 bad version number 0x0 on inode 171 bad next_unlinked 0x0 on inode 171 inode identifier 0 mismatch on inode 171 bad CRC for inode 172 bad magic number 0x0 on inode 172 bad version number 0x0 on inode 172 bad next_unlinked 0x0 on inode 172 inode identifier 0 mismatch on inode 172 bad CRC for inode 173 bad magic number 0x0 on inode 173 bad version number 0x0 on inode 173 bad next_unlinked 0x0 on inode 173 inode identifier 0 mismatch on inode 173 bad CRC for inode 174 bad magic number 0x0 on inode 174 bad version number 0x0 on inode 174 bad next_unlinked 0x0 on inode 174 inode identifier 0 mismatch on inode 174 bad CRC for inode 175 bad magic number 0x0 on inode 175 bad version number 0x0 on inode 175 bad next_unlinked 0x0 on inode 175 inode identifier 0 mismatch on inode 175 bad CRC for inode 176 bad magic number 0x0 on inode 176 bad version number 0x0 on inode 176 bad next_unlinked 0x0 on inode 176 inode identifier 0 mismatch on inode 176 bad CRC for inode 177 bad magic number 0x0 on inode 177 bad version number 0x0 on inode 177 bad next_unlinked 0x0 on inode 177 inode identifier 0 mismatch on inode 177 bad CRC for inode 178 bad magic number 0x0 on inode 178 bad version number 0x0 on inode 178 bad next_unlinked 0x0 on inode 178 inode identifier 0 mismatch on inode 178 bad CRC for inode 179 bad magic number 0x0 on inode 179 bad version number 0x0 on inode 179 bad next_unlinked 0x0 on inode 179 inode identifier 0 mismatch on inode 179 bad CRC for inode 180 bad magic number 0x0 on inode 180 bad version number 0x0 on inode 180 bad next_unlinked 0x0 on inode 180 inode identifier 0 mismatch on inode 180 bad CRC for inode 181 bad magic number 0x0 on inode 181 bad version number 0x0 on inode 181 bad next_unlinked 0x0 on inode 181 inode identifier 0 mismatch on inode 181 bad CRC for inode 182 bad magic number 0x0 on inode 182 bad version number 0x0 on inode 182 bad next_unlinked 0x0 on inode 182 inode identifier 0 mismatch on inode 182 bad CRC for inode 183 bad magic number 0x0 on inode 183 bad version number 0x0 on inode 183 bad next_unlinked 0x0 on inode 183 inode identifier 0 mismatch on inode 183 bad CRC for inode 184 bad magic number 0x0 on inode 184 bad version number 0x0 on inode 184 bad next_unlinked 0x0 on inode 184 inode identifier 0 mismatch on inode 184 bad CRC for inode 185 bad magic number 0x0 on inode 185 bad version number 0x0 on inode 185 bad next_unlinked 0x0 on inode 185 inode identifier 0 mismatch on inode 185 bad CRC for inode 186 bad magic number 0x0 on inode 186 bad version number 0x0 on inode 186 bad next_unlinked 0x0 on inode 186 inode identifier 0 mismatch on inode 186 bad CRC for inode 187 bad magic number 0x0 on inode 187 bad version number 0x0 on inode 187 bad next_unlinked 0x0 on inode 187 inode identifier 0 mismatch on inode 187 bad CRC for inode 188 bad magic number 0x0 on inode 188 bad version number 0x0 on inode 188 bad next_unlinked 0x0 on inode 188 inode identifier 0 mismatch on inode 188 bad CRC for inode 189 bad magic number 0x0 on inode 189 bad version number 0x0 on inode 189 bad next_unlinked 0x0 on inode 189 inode identifier 0 mismatch on inode 189 bad CRC for inode 190 bad magic number 0x0 on inode 190 bad version number 0x0 on inode 190 bad next_unlinked 0x0 on inode 190 inode identifier 0 mismatch on inode 190 bad CRC for inode 191 bad magic number 0x0 on inode 191 bad version number 0x0 on inode 191 bad next_unlinked 0x0 on inode 191 inode identifier 0 mismatch on inode 191 bad CRC for inode 128, will rewrite bad magic number 0x0 on inode 128, resetting magic number bad version number 0x0 on inode 128, resetting version number bad next_unlinked 0x0 on inode 128, resetting next_unlinked inode identifier 0 mismatch on inode 128 cleared root inode 128 bad CRC for inode 129, will rewrite bad magic number 0x0 on inode 129, resetting magic number bad version number 0x0 on inode 129, resetting version number bad next_unlinked 0x0 on inode 129, resetting next_unlinked inode identifier 0 mismatch on inode 129 cleared realtime bitmap inode 129 bad CRC for inode 130, will rewrite bad magic number 0x0 on inode 130, resetting magic number bad version number 0x0 on inode 130, resetting version number bad next_unlinked 0x0 on inode 130, resetting next_unlinked inode identifier 0 mismatch on inode 130 cleared realtime summary inode 130 bad CRC for inode 131, will rewrite bad magic number 0x0 on inode 131, resetting magic number bad version number 0x0 on inode 131, resetting version number bad next_unlinked 0x0 on inode 131, resetting next_unlinked inode identifier 0 mismatch on inode 131 cleared inode 131 bad CRC for inode 132, will rewrite bad magic number 0x0 on inode 132, resetting magic number bad version number 0x0 on inode 132, resetting version number bad next_unlinked 0x0 on inode 132, resetting next_unlinked inode identifier 0 mismatch on inode 132 cleared inode 132 bad CRC for inode 133, will rewrite bad magic number 0x0 on inode 133, resetting magic number bad version number 0x0 on inode 133, resetting version number bad next_unlinked 0x0 on inode 133, resetting next_unlinked inode identifier 0 mismatch on inode 133 cleared inode 133 bad CRC for inode 134, will rewrite bad magic number 0x0 on inode 134, resetting magic number bad version number 0x0 on inode 134, resetting version number bad next_unlinked 0x0 on inode 134, resetting next_unlinked inode identifier 0 mismatch on inode 134 cleared inode 134 bad CRC for inode 135, will rewrite bad magic number 0x0 on inode 135, resetting magic number bad version number 0x0 on inode 135, resetting version number bad next_unlinked 0x0 on inode 135, resetting next_unlinked inode identifier 0 mismatch on inode 135 cleared inode 135 bad CRC for inode 136, will rewrite bad magic number 0x0 on inode 136, resetting magic number bad version number 0x0 on inode 136, resetting version number bad next_unlinked 0x0 on inode 136, resetting next_unlinked inode identifier 0 mismatch on inode 136 cleared inode 136 bad CRC for inode 137, will rewrite bad magic number 0x0 on inode 137, resetting magic number bad version number 0x0 on inode 137, resetting version number bad next_unlinked 0x0 on inode 137, resetting next_unlinked inode identifier 0 mismatch on inode 137 cleared inode 137 bad CRC for inode 138, will rewrite bad magic number 0x0 on inode 138, resetting magic number bad version number 0x0 on inode 138, resetting version number bad next_unlinked 0x0 on inode 138, resetting next_unlinked inode identifier 0 mismatch on inode 138 cleared inode 138 bad CRC for inode 139, will rewrite bad magic number 0x0 on inode 139, resetting magic number bad version number 0x0 on inode 139, resetting version number bad next_unlinked 0x0 on inode 139, resetting next_unlinked inode identifier 0 mismatch on inode 139 cleared inode 139 bad CRC for inode 140, will rewrite bad magic number 0x0 on inode 140, resetting magic number bad version number 0x0 on inode 140, resetting version number bad next_unlinked 0x0 on inode 140, resetting next_unlinked inode identifier 0 mismatch on inode 140 cleared inode 140 bad CRC for inode 141, will rewrite bad magic number 0x0 on inode 141, resetting magic number bad version number 0x0 on inode 141, resetting version number bad next_unlinked 0x0 on inode 141, resetting next_unlinked inode identifier 0 mismatch on inode 141 cleared inode 141 bad CRC for inode 142, will rewrite bad magic number 0x0 on inode 142, resetting magic number bad version number 0x0 on inode 142, resetting version number bad next_unlinked 0x0 on inode 142, resetting next_unlinked inode identifier 0 mismatch on inode 142 cleared inode 142 bad CRC for inode 143, will rewrite bad magic number 0x0 on inode 143, resetting magic number bad version number 0x0 on inode 143, resetting version number bad next_unlinked 0x0 on inode 143, resetting next_unlinked inode identifier 0 mismatch on inode 143 cleared inode 143 bad CRC for inode 144, will rewrite bad magic number 0x0 on inode 144, resetting magic number bad version number 0x0 on inode 144, resetting version number bad next_unlinked 0x0 on inode 144, resetting next_unlinked inode identifier 0 mismatch on inode 144 cleared inode 144 bad CRC for inode 145, will rewrite bad magic number 0x0 on inode 145, resetting magic number bad version number 0x0 on inode 145, resetting version number bad next_unlinked 0x0 on inode 145, resetting next_unlinked inode identifier 0 mismatch on inode 145 cleared inode 145 bad CRC for inode 146, will rewrite bad magic number 0x0 on inode 146, resetting magic number bad version number 0x0 on inode 146, resetting version number bad next_unlinked 0x0 on inode 146, resetting next_unlinked inode identifier 0 mismatch on inode 146 cleared inode 146 bad CRC for inode 147, will rewrite bad magic number 0x0 on inode 147, resetting magic number bad version number 0x0 on inode 147, resetting version number bad next_unlinked 0x0 on inode 147, resetting next_unlinked inode identifier 0 mismatch on inode 147 cleared inode 147 bad CRC for inode 148, will rewrite bad magic number 0x0 on inode 148, resetting magic number bad version number 0x0 on inode 148, resetting version number bad next_unlinked 0x0 on inode 148, resetting next_unlinked inode identifier 0 mismatch on inode 148 cleared inode 148 bad CRC for inode 149, will rewrite bad magic number 0x0 on inode 149, resetting magic number bad version number 0x0 on inode 149, resetting version number bad next_unlinked 0x0 on inode 149, resetting next_unlinked inode identifier 0 mismatch on inode 149 cleared inode 149 bad CRC for inode 150, will rewrite bad magic number 0x0 on inode 150, resetting magic number bad version number 0x0 on inode 150, resetting version number bad next_unlinked 0x0 on inode 150, resetting next_unlinked inode identifier 0 mismatch on inode 150 cleared inode 150 bad CRC for inode 151, will rewrite bad magic number 0x0 on inode 151, resetting magic number bad version number 0x0 on inode 151, resetting version number bad next_unlinked 0x0 on inode 151, resetting next_unlinked inode identifier 0 mismatch on inode 151 cleared inode 151 bad CRC for inode 152, will rewrite bad magic number 0x0 on inode 152, resetting magic number bad version number 0x0 on inode 152, resetting version number bad next_unlinked 0x0 on inode 152, resetting next_unlinked inode identifier 0 mismatch on inode 152 cleared inode 152 bad CRC for inode 153, will rewrite bad magic number 0x0 on inode 153, resetting magic number bad version number 0x0 on inode 153, resetting version number bad next_unlinked 0x0 on inode 153, resetting next_unlinked inode identifier 0 mismatch on inode 153 cleared inode 153 bad CRC for inode 154, will rewrite bad magic number 0x0 on inode 154, resetting magic number bad version number 0x0 on inode 154, resetting version number bad next_unlinked 0x0 on inode 154, resetting next_unlinked inode identifier 0 mismatch on inode 154 cleared inode 154 bad CRC for inode 155, will rewrite bad magic number 0x0 on inode 155, resetting magic number bad version number 0x0 on inode 155, resetting version number bad next_unlinked 0x0 on inode 155, resetting next_unlinked inode identifier 0 mismatch on inode 155 cleared inode 155 bad CRC for inode 156, will rewrite bad magic number 0x0 on inode 156, resetting magic number bad version number 0x0 on inode 156, resetting version number bad next_unlinked 0x0 on inode 156, resetting next_unlinked inode identifier 0 mismatch on inode 156 cleared inode 156 bad CRC for inode 157, will rewrite bad magic number 0x0 on inode 157, resetting magic number bad version number 0x0 on inode 157, resetting version number bad next_unlinked 0x0 on inode 157, resetting next_unlinked inode identifier 0 mismatch on inode 157 cleared inode 157 bad CRC for inode 158, will rewrite bad magic number 0x0 on inode 158, resetting magic number bad version number 0x0 on inode 158, resetting version number bad next_unlinked 0x0 on inode 158, resetting next_unlinked inode identifier 0 mismatch on inode 158 cleared inode 158 bad CRC for inode 159, will rewrite bad magic number 0x0 on inode 159, resetting magic number bad version number 0x0 on inode 159, resetting version number bad next_unlinked 0x0 on inode 159, resetting next_unlinked inode identifier 0 mismatch on inode 159 cleared inode 159 imap claims inode 160 is present, but inode cluster is sparse, correcting imap imap claims inode 161 is present, but inode cluster is sparse, correcting imap imap claims inode 162 is present, but inode cluster is sparse, correcting imap imap claims inode 163 is present, but inode cluster is sparse, correcting imap imap claims inode 164 is present, but inode cluster is sparse, correcting imap imap claims inode 165 is present, but inode cluster is sparse, correcting imap imap claims inode 166 is present, but inode cluster is sparse, correcting imap imap claims inode 167 is present, but inode cluster is sparse, correcting imap imap claims inode 168 is present, but inode cluster is sparse, correcting imap imap claims inode 169 is present, but inode cluster is sparse, correcting imap imap claims inode 170 is present, but inode cluster is sparse, correcting imap imap claims inode 171 is present, but inode cluster is sparse, correcting imap imap claims inode 172 is present, but inode cluster is sparse, correcting imap imap claims inode 173 is present, but inode cluster is sparse, correcting imap imap claims inode 174 is present, but inode cluster is sparse, correcting imap imap claims inode 175 is present, but inode cluster is sparse, correcting imap imap claims inode 176 is present, but inode cluster is sparse, correcting imap imap claims inode 177 is present, but inode cluster is sparse, correcting imap imap claims inode 178 is present, but inode cluster is sparse, correcting imap imap claims inode 179 is present, but inode cluster is sparse, correcting imap imap claims inode 180 is present, but inode cluster is sparse, correcting imap imap claims inode 181 is present, but inode cluster is sparse, correcting imap imap claims inode 182 is present, but inode cluster is sparse, correcting imap imap claims inode 183 is present, but inode cluster is sparse, correcting imap imap claims inode 184 is present, but inode cluster is sparse, correcting imap imap claims inode 185 is present, but inode cluster is sparse, correcting imap imap claims inode 186 is present, but inode cluster is sparse, correcting imap imap claims inode 187 is present, but inode cluster is sparse, correcting imap imap claims inode 188 is present, but inode cluster is sparse, correcting imap imap claims inode 189 is present, but inode cluster is sparse, correcting imap imap claims inode 190 is present, but inode cluster is sparse, correcting imap imap claims inode 191 is present, but inode cluster is sparse, correcting imap - 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... root inode lost - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 5 - agno = 7 - agno = 1 - agno = 4 - agno = 6 Phase 5 - rebuild AG headers and trees... - 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 ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 2830832128, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 131 nlinks from 2 to 3 Maximum metadata LSN (1:2352245) is ahead of log (1:2). Format log to cycle 4. done
  16. i started the array in maintaince mode and checked the file system and i got this Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 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. the drive shows as unmountable in the main page. is there a way to mount it or should i just run with -L
  17. i had a failing drive(already moved all data to the other drives ) and replaced it with a new one (precleared using unassigned disk ). it was working fine for a couple of days but today it says "Unmountable: Wrong or no file system" on the new drive. should i format it ? and what about the data already on the drive ? tower-diagnostics-20230524-1018.zip
  18. I have a couple of vm and around 52 containers running. 1- Fedora server 2048M 2- windows 10 8192M I noticed there 2 errors in syslog multiple times. May 7 18:55:05 Tower kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/docker/0b9eed17e56913bb118e5ea5caa32daa2554902534d65e5712794d4239e20ac0,task=python3,pid=25945,uid=99 May 7 18:55:05 Tower kernel: Out of memory: Killed process 25945 (python3) total-vm:12733772kB, anon-rss:8578584kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:17464kB oom_score_adj:0 do I really need to upgrade the ram or is there some kind of problem with my system? tower-diagnostics-20230507-1857.zip
  19. cpu: 12600k motherboard: z690-p d4 gpu: nvidia 1060 6gb when using legacy boot, the igpu disappear from system devices and i can't use it anymore. is this normal ? even in bios i can't do anything to enable the igpu unless i disable legacy and use UEFI
  20. will uninstalling the plugin uninstall the drivers or is there something else I should do to uninstall the drivers?
  21. i just installed scrutiny and noticed an insanely high value on my parity drive 188 smart value its a brand new drive and with only 5 days of time powered on i ordered 3 of them ,the other 2 are fine should i freak out or is there a way to reset this
  22. lets start with SSDs are much much faster , I think everybody knows that by now. I just ordered the parts for my server so this post is basically me wanting to be sure that I don't need to buy more stuff when I build the server and to make sure that I'm utilizing the drives as much as possible before going into the problem. these are the drives I have : 1x1tb nvme - probably plex metadata 1x500 SSD - cache, docker and VMs 2x4tb ,2x1tb and 1x12tb all hdd for the array 1x12tb parity I have a pretty large plex library, that's why I have the 1tb nvme, but if I notice that I overestimated plex metadata I'll probably move both docker containers and VMs to the nvme with plex metadata. what I want to do is have 1x4tb hdd just for downloads (torrent, usenet...). I probably don't need that much space for the downloads drive but the reason I chose 4 tb is that I will be remuxing everything that's downloaded ( adding subtitles ) and I want to move out my 2x4tb over time and repurpose them for something else in unraid other than storage. I'll be using the 4tb hdd because I already have it and it will get a ton of read/writes. I don't want to wear out an ssd for downloading and unpacking. especially in the first couple of months I might be downloading 4tb a month. so is my train of thought correct or is there a better way to do this ?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.