hayt

I don't have much more time today to do stuff on the the system, but yes it's mountable. If you have methods, to get things restored more easily and simpler I am all ears though.

The numbers are what is reported on the bottom, when I browse the lost + found directory in the webinterface. The compute says 185GB are on disk 2 so the 158mb is just the 23 files. I will see what I can restore with the old drive. I also have monthly backups so I can use that too. It's not really about the data loss but more about the hassle to get stuff running again. But anyways thanks for the help

Here are the new diagnostics: Here is the lost + found count: 10920 objects: 10897 directories, 23 files (158 MB total) that seems like quite a lot. Any tips on what to do here except manually reviewing all files? kermit-diagnostics-20221223-1449.zip

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... bad magic number Metadata CRC error detected at 0x468740, xfs_agi block 0x1ffffffe2/0x200 agi has bad CRC for ag 4 bad on-disk superblock 4 - bad magic number primary/secondary superblock 4 conflict - AG superblock geometry info conflicts with filesystem geometry zeroing unused portion of secondary superblock (AG #4) bad magic # 0x34deeb9d for agi 4 bad version # 1531445257 for agi 4 bad sequence # -716317536 for agi 4 bad length # -1277553578 for agi 4, should be 268435455 bad uuid d9b6b4ee-0892-ec2f-f16e-6802fd29f122 for agi 4 reset bad sb for ag 4 reset bad agi for ag 4 Metadata CRC error detected at 0x43cfe4, xfs_agfl block 0x1ffffffe3/0x200 agfl has bad CRC for ag 4 bad agbno 894547253 in agfl, agno 4 bad agbno 4159444983 in agfl, agno 4 bad agbno 520280968 in agfl, agno 4 bad levels 29117136 for inobt root, agno 4 bad agbno 3482637960 for inobt root, agno 4 bad levels 2373943897 for finobt root, agno 4 bad agbno 2420389513 for finobt root, agno 4 agi_count 3697549462, counted 0 in ag 4 agi_freecount 3938748600, counted 0 in ag 4 agi_freecount 3938748600, counted 0 in ag 4 finobt agi unlinked bucket 0 is 705553259 in ag 4 (inode=9295487851) agi unlinked bucket 1 is 2707392411 in ag 4 (inode=11297327003) agi unlinked bucket 2 is 2344811596 in ag 4 (inode=10934746188) agi unlinked bucket 3 is 1017071274 in ag 4 (inode=9607005866) agi unlinked bucket 4 is 3083963081 in ag 4 (inode=11673897673) agi unlinked bucket 5 is 913517105 in ag 4 (inode=9503451697) agi unlinked bucket 6 is 3718358708 in ag 4 (inode=12308293300) agi unlinked bucket 7 is 4020826587 in ag 4 (inode=12610761179) agi unlinked bucket 8 is 3471417887 in ag 4 (inode=12061352479) agi unlinked bucket 9 is 1210129345 in ag 4 (inode=9800063937) agi unlinked bucket 10 is 2016807716 in ag 4 (inode=10606742308) agi unlinked bucket 11 is 3687245362 in ag 4 (inode=12277179954) agi unlinked bucket 12 is 3562826584 in ag 4 (inode=12152761176) agi unlinked bucket 13 is 2444986274 in ag 4 (inode=11034920866) agi unlinked bucket 14 is 234962767 in ag 4 (inode=8824897359) agi unlinked bucket 15 is 2731057314 in ag 4 (inode=11320991906) agi unlinked bucket 16 is 1835190428 in ag 4 (inode=10425125020) agi unlinked bucket 17 is 1419321291 in ag 4 (inode=10009255883) agi unlinked bucket 18 is 143996265 in ag 4 (inode=8733930857) agi unlinked bucket 19 is 2698497086 in ag 4 (inode=11288431678) agi unlinked bucket 20 is 2893715605 in ag 4 (inode=11483650197) agi unlinked bucket 21 is 483208939 in ag 4 (inode=9073143531) agi unlinked bucket 22 is 1438293514 in ag 4 (inode=10028228106) agi unlinked bucket 23 is 2015860805 in ag 4 (inode=10605795397) agi unlinked bucket 24 is 2862864100 in ag 4 (inode=11452798692) agi unlinked bucket 25 is 975935132 in ag 4 (inode=9565869724) agi unlinked bucket 26 is 3241408529 in ag 4 (inode=11831343121) agi unlinked bucket 27 is 3653783234 in ag 4 (inode=12243717826) agi unlinked bucket 28 is 2115218165 in ag 4 (inode=10705152757) agi unlinked bucket 29 is 4124816067 in ag 4 (inode=12714750659) agi unlinked bucket 30 is 1592746561 in ag 4 (inode=10182681153) agi unlinked bucket 31 is 2673121948 in ag 4 (inode=11263056540) agi unlinked bucket 32 is 4190090535 in ag 4 (inode=12780025127) agi unlinked bucket 33 is 4028628253 in ag 4 (inode=12618562845) agi unlinked bucket 34 is 211101245 in ag 4 (inode=8801035837) agi unlinked bucket 35 is 118343197 in ag 4 (inode=8708277789) agi unlinked bucket 36 is 3373164529 in ag 4 (inode=11963099121) agi unlinked bucket 37 is 2590450032 in ag 4 (inode=11180384624) agi unlinked bucket 38 is 2850293810 in ag 4 (inode=11440228402) agi unlinked bucket 39 is 2062236043 in ag 4 (inode=10652170635) agi unlinked bucket 40 is 871636593 in ag 4 (inode=9461571185) agi unlinked bucket 41 is 4181298954 in ag 4 (inode=12771233546) agi unlinked bucket 42 is 1034301487 in ag 4 (inode=9624236079) agi unlinked bucket 43 is 839867808 in ag 4 (inode=9429802400) agi unlinked bucket 44 is 422446125 in ag 4 (inode=9012380717) agi unlinked bucket 45 is 3629031069 in ag 4 (inode=12218965661) agi unlinked bucket 46 is 2977964009 in ag 4 (inode=11567898601) agi unlinked bucket 47 is 3015901546 in ag 4 (inode=11605836138) agi unlinked bucket 48 is 3613871846 in ag 4 (inode=12203806438) agi unlinked bucket 49 is 2544229767 in ag 4 (inode=11134164359) agi unlinked bucket 50 is 2866768911 in ag 4 (inode=11456703503) agi unlinked bucket 51 is 3309899709 in ag 4 (inode=11899834301) agi unlinked bucket 52 is 800074859 in ag 4 (inode=9390009451) agi unlinked bucket 53 is 30446653 in ag 4 (inode=8620381245) agi unlinked bucket 54 is 492017744 in ag 4 (inode=9081952336) agi unlinked bucket 55 is 3268812972 in ag 4 (inode=11858747564) agi unlinked bucket 56 is 3364116434 in ag 4 (inode=11954051026) agi unlinked bucket 57 is 1490019661 in ag 4 (inode=10079954253) agi unlinked bucket 58 is 12047351 in ag 4 (inode=8601981943) agi unlinked bucket 59 is 327664156 in ag 4 (inode=8917598748) agi unlinked bucket 60 is 1298525349 in ag 4 (inode=9888459941) agi unlinked bucket 61 is 2018134332 in ag 4 (inode=10608068924) agi unlinked bucket 62 is 1579211094 in ag 4 (inode=10169145686) agi unlinked bucket 63 is 2692258424 in ag 4 (inode=11282193016) sb_icount 197376, counted 164736 sb_ifree 230, counted 194 - 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 data fork in ino 7260275105 claims free block 1105549980 data fork in ino 7260373537 claims free block 1128620519 - agno = 4 - agno = 5 - 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 = 5 - agno = 2 - agno = 4 entry "minecraft" in shortform directory 128 references non-existent inode 9581565827 junking entry "minecraft" in directory inode 128 - agno = 3 corrected i8 count in directory 128, was 7, now 6 entry "Hausplanung" at block 0 offset 336 in directory inode 4294967424 references non-existent inode 9581565847 clearing inode number in entry at offset 336... entry "f" in shortform directory 6446709184 references non-existent inode 9581535678 junking entry "f" in directory inode 6446709184 corrected i8 count in directory 6446709184, was 2, now 1 entry "5" in shortform directory 6446709185 references non-existent inode 9581535679 junking entry "5" in directory inode 6446709185 corrected i8 count in directory 6446709185, was 2, now 1 entry "c" in shortform directory 6446709186 references non-existent inode 9581535552 junking entry "c" in directory inode 6446709186 corrected i8 count in directory 6446709186, was 2, now 1 [... lots of stuff like that again ... ] resetting inode 7643984874 nlinks from 3 to 2 resetting inode 7643984875 nlinks from 3 to 2 resetting inode 7643984876 nlinks from 3 to 2 resetting inode 7643984889 nlinks from 3 to 2 resetting inode 7643984890 nlinks from 3 to 2 resetting inode 7643984891 nlinks from 3 to 2 resetting inode 7643984892 nlinks from 3 to 2 resetting inode 7643984893 nlinks from 3 to 2 resetting inode 7643984894 nlinks from 7 to 2 done

I probably worded that wrong. Yeah I first want to get the emulated disk running. I am aware a preclear deletes all the data on the drive. Here is the log output Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... bad magic number Metadata CRC error detected at 0x468740, xfs_agi block 0x1ffffffe2/0x200 agi has bad CRC for ag 4 bad on-disk superblock 4 - bad magic number primary/secondary superblock 4 conflict - AG superblock geometry info conflicts with filesystem geometry would zero unused portion of secondary superblock (AG #4) would fix compat feature mismatch in AG 4 super, 0x0 != 0xe7ce54ba would fix incompat feature mismatch in AG 4 super, 0x3 != 0x81a4a9 would fix ro compat feature mismatch in AG 4 super, 0x5 != 0x858a0d94 would fix log incompat feature mismatch in AG 4 super, 0x0 != 0xc1e3422e bad magic # 0x34deeb9d for agi 4 bad version # 1531445257 for agi 4 bad sequence # -716317536 for agi 4 bad length # -1277553578 for agi 4, should be 268435455 bad uuid d9b6b4ee-0892-ec2f-f16e-6802fd29f122 for agi 4 would reset bad sb for ag 4 would reset bad agi for ag 4 bad uncorrected agheader 4, skipping ag... sb_icount 197376, counted 164736 sb_ifree 230, counted 194 sb_fdblocks 429421538, counted 351456670 - 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 - agno = 4 - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 4 - agno = 3 - agno = 5 entry "Hausplanung" at block 0 offset 336 in directory inode 4294967424 references non-existent inode 9581565847 would clear inode number in entry at offset 336... - agno = 1 entry "minecraft" in shortform directory 128 references non-existent inode 9581565827 would have junked entry "minecraft" in directory inode 128 would have corrected i8 count in directory 128 from 7 to 6 entry "f" in shortform directory 6446709184 references non-existent inode 9581535678 would have junked entry "f" in directory inode 6446709184 would have corrected i8 count in directory 6446709184 from 2 to 1 entry "5" in shortform directory 6446709185 references non-existent inode 9581535679 would have junked entry "5" in directory inode 6446709185 would have corrected i8 count in directory 6446709185 from 2 to 1 entry "c" in shortform directory 6446709186 references non-existent inode 9581535552 [... there is a lot more of that ... ] entry "2" in shortform directory 6446716590 references non-existent inode 9581535541 entry ".." at block 0 offset 80 in directory inode 4884485971 references non-existent inode 9581544389 would have junked entry "2" in directory inode 6446716590 would have corrected i8 count in directory 6446716590 from 2 to 1 entry "a" in shortform directory 6446716591 references non-existent inode 9581535542 would have junked entry "a" in directory inode 6446716591 [ ... and that ... ] entry "4b" in directory inode 101101554 points to non-existent inode 9582584996, would junk entry entry "f9" in directory inode 101101554 points to non-existent inode 9582625919, would junk entry entry "e8" in directory inode 101101554 points to non-existent inode 9582629786, would junk entry entry "e9" in directory inode 101101554 points to non-existent inode 9582666106, would junk entry entry "67" in directory inode 101101554 points to non-existent inode 9582693322, would junk entry entry "d5" in directory inode 101101554 points to non-existent inode 9582604469, would junk entry entry "55" in directory inode 101101554 points to non-existent inode 9582604472, would junk entry [ ... and that ... ] disconnected dir inode 122739195, would move to lost+found disconnected dir inode 122739199, would move to lost+found disconnected dir inode 149731733, would move to lost+found disconnected dir inode 149731767, would move to lost+found disconnected dir inode 249521025, would move to lost+found disconnected dir inode 249521033, would move to lost+found disconnected dir inode 249521039, would move to lost+found disconnected dir inode 249521054, would move to lost+found [.... and that ... ] [... here is the end ...] would have reset inode 7643984893 nlinks from 3 to 2 would have reset inode 7643984894 nlinks from 7 to 2 No modify flag set, skipping filesystem flush and exiting.

it's disk TOSHIBA_HDWN160_11S1K2LLFAXG. The issue seemed to be the sata cable, at least it's back after switching the cable but I want to run a preclear to be sure. I would just like to have the disk 2 emulated while I do that, so I can continue using the array.

here you go. I assume the issue is the "unmountable filesystem" on disk 2? just for the future: Is there any way to check for things like this before I start the array in normal mode? I have some services running, and don't want them or their databases to go inconsistent when it starts the array with some files missing. kermit-diagnostics-20221223-1352.zip

Here are the diagnostics. It's currently running in maintenance mode. kermit-diagnostics-20221223-1332.zip

hey everyone, maybe I am misunderstanding what unraid actually does but I just want to ask for clarification anyways. I have a raid with 5 x 6TB drives. 2 For parity 3 for data. so total capacity is 18 TB. Now I had one drive fail so I stopped array, shutdown the system, removed the faulty disk (to run some checks) and started up the array again with the Disk 2 as "no device" and it shows up as simulated. But the total capacity of the array is now shown as 12 TB and files are missing. So it looks to me like the data from the missing disk is not simulated at all. Is the parity just there to help a rebuild or am I missing something? I had the issue once before and thought I was just doing something wrong. Now I have sync jobs, who write files again to the array and when I insert the missing disks these files will probably be on the system twice as different versions on different hard drives. So yeah, am I missing a step or is unraid not made to be able to run a functional array with a missing disk, when I have parity disks?