bwv1058
-
Posts
38 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by bwv1058
-
-
Dear community,
All of a sudden my docker containers stopped working. Upon inspection, I noticed that the dedicated section in the Dashboard has disappeared and that my VM was "paused".
Has my Cache disk decided to give up the ghost?
Thank you in advance for any advice! -
On 4/21/2023 at 5:20 AM, apandey said:
What path are you giving to the VM?
Correction of my previous answer: the path is /mnt/user/domains/Windows 10/vdisk1.img
-
Dear apandey,
Thank you very much for your reply!
13 hours ago, apandey said:can you describe what paths you have mounted to krusader and which paths are you moving across?
My host path is /mnt/user and from Krusader's perspective what I'm trying to do is to move Root/media/MYSHARE/MYFOLDER/MYSUBFOLDER/.../TARGETFOLDER to Root/media/MYSHARE/MYFOLDER/MYOTHERSUBFOLDER/.../TARGETFOLDER
13 hours ago, apandey said:mover will not move any open files. you can use open files plugin to verify
Thank you for the suggestion! The two specific folders that are still located in the cache don't appear anywhere in the open file's list of files.
14 hours ago, apandey said:you can run a btrfs scrub to check.
Here is my scrub output. Rather reassuring, but unfortunately it does not explain the problems I'm having....
UUID: 89902bd6-9beb-4dac-976b-a39d2e4e8fc4 Scrub started: Fri Apr 21 19:23:32 2023 Status: finished Duration: 0:02:11 Total to scrub: 341.19GiB Rate: 2.60GiB/s Error summary: no errors found14 hours ago, apandey said:What path are you giving to the VM?
The path for my crashing Windows VM would be: /mnt/user/isos/virtio-win-0.1.160-1.iso
Thank you again for your help!
-
Dear community,
I have recently tried to move files from one folder of a Share to another using Krusader. Interestingly, Krusader will move the folder as instructed, but if I then look up my share, the folder structure will remain unaltered...
In addition to that, this share seems to have some files on the cache drive. I have repeatedly invoked the "mover" (with cache set to "yes"), but nothing happens, and some files will just remain, it seems, on the cache drive...On a side note, whenever I start a VM stored on the cache drive, it will automatically shut down after a few minutes. Maybe this issue is completely unrelated, but maybe something is wrong with the cache drive... How would I check and repair that?
Many thanks! -
Dear JorgeB
Thank you very much for your continued support! You were absolutely right: one restart later the issue seems to be gone. I don't know what caused it in the first place, but I have installed the swapfile plugin, just in case.
Thank you again!
-
1
-
-
Dear community members,
I've recently had to copy many files following various corruptions and issues on some of my array disks. Today, while copying some files, I noticed that my virtual machine, which takes care of syncing the more important data with my cloud provider froze. After I tried to edit it, it gave me an error, stating that some file in /etc/libvirt/ was readonly. I went looking for it on the console only to be greeted by another error message:reading directory '/etc/libvirt/': Input/output errorAfter that my virtual machine disappeared completely and I could not recreate it (because of the same aforementioned errors).
I noticed, that my cache drive was completely full, so I started mover, which apparently completed its operations without any problems.
Meanwhile I've noticed, that my docker containers stopped working....I then ran "Fix Common Problems", which reported the following:
Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forumsI'm now very much at a loss...
tower-diagnostics-20230410-2156.zipEdit: as I was writing this post, a new error message popped up:
Docker Image either full or corrupted. Investigate Here: -
14 hours ago, JorgeB said:
The UD plugin has a filesystem repair option, IIRC it looks like a little flash.
Many thanks, I found it.
Alright, seems that at last everything has returned to normality. Let's hope it stays that way...
Many thanks to all moderators who provided support. To anyone interested: the unreliable behaviour referenced in this thread might have been caused by a faulty PSU and/or cables. I have now replaced everything in the hope that no more drives will randomly disconnect or experience file system corruption.-
1
-
-
9 hours ago, JorgeB said:
Are you using FIrefox? If yes use a different browser.
Dear JorgeB, yes, I am using Firefox. I thought it would be the closest match to the browser Unraid's own GUI uses...
How can I repair the filesystem on my unassigned drive? Should I follow the instructions to execute xfs_repair in the console? If so, is it enough to run
xfs_repair -v /dev/sdb?
Thank you all again
-
8 hours ago, trurl said:
Your automount Unassigned Device sdb is corrupt
I see, how could I repair it? I don't see any xfs_repair option when I click on the device name (as would be the case for disk within the array).
8 hours ago, trurl said:Close all tabs and browsers to your Unraid webUI on all devices
Apparently, one restart later, the interface shows up correctly...
-
Dear moderators,
I've finally replaced the psu and cables (apparently shipments to my region take a while). However, following the procedure to rebuild data on drive 7, I've found that the array won't start up but the data rebuild seems to be proceeding anyway.
Is this behaviour normal? I remember that on my old Unraid version the data rebuild would begin immediately upon array start... Now I'm really confused.
-
5 hours ago, trurl said:
Mover won't replace files, so if some appdata files exist on cache and array you will have to clean that up yourself. Install Dynamix File Manager plugin.
Understood! Thank you for pointing it out!
5 hours ago, trurl said:Disk7 is mounted now and over half full. Check the contents of your lost+found share for things repair couldn't figure out.
Yes, but it is emulated. Should I rebuild it onto itself (as I did before with disk 2)? The fact that it would be the second time in a week (plus the filesystem corruption on the same disk) is not very confidence-inspiring. Should I wait and replace the power supply first?
-
2 minutes ago, trurl said:
Did you do the repair from the webUI or the command line? Easy to get the command wrong.
I did it from the webUI, first with the -nv, then the -v flag.
2 minutes ago, trurl said:You have to disable Docker and VM Manager in Settings to get the "default" shares moved.
I did just that, as you suggested in your previous post: disabled vm and docker and ran mover, then waited until mover was done. Anyway, will try again.
I updated the OS and am sharing the diagnostics after the reboot.
-
8 minutes ago, JorgeB said:
PSU could be failing, or the HBA
Dear JorgeB, I doubt it is the HBA. At the start of this thread I had disk 7 attached directly to the motherboard, and... it still failed. I bought the PSU two years ago, could it seriously be the culprit?
8 minutes ago, JorgeB said:Please post the output of xfs_repair.
Sure, it is long...
Phase 1 - find and verify superblock... - block cache size set to 1503416 entries Phase 2 - using internal log - zero log... zero_log: head block 1077 tail block 1077 - scan filesystem freespace and inode maps... agf_freeblks 54907654, counted 54645507 in ag 13 invalid start block 260046872 in record 1 of cnt btree block 15/4 agf_freeblks 61039719, counted 9 in ag 15 agf_longest 61039709, counted 9 in ag 15 inode chunk claims used block, inobt block - agno 15, bno 16, inopb 8 ir_freecount/free mismatch, inode chunk 13/32755392, freecount 2 nfree 4 inode chunk claims used block, finobt block - agno 15, bno 16, inopb 8 agi_freecount 37, counted 43 in ag 15 agi_freecount 37, counted 43 in ag 15 finobt finobt ir_freecount/free mismatch, inode chunk 13/32755392, freecount 2 nfree 4 agi_freecount 29, counted 51 in ag 13 agi_freecount 29, counted 51 in ag 13 finobt agi_freecount 36, counted 34 in ag 12 agi_freecount 36, counted 34 in ag 12 finobt Metadata CRC error detected at 0x46b78d, xfs_finobt block 0x12b4facb8/0x1000 btree block 10/17224543 is suspect, error -74 bad magic # 0xefa7e5ef in finobt block 10/17224543 agi_freecount 27, counted 0 in ag 10 finobt Metadata CRC error detected at 0x46b78d, xfs_finobt block 0x147b81f58/0x1000 btree block 11/15752775 is suspect, error -74 bad magic # 0x3e0d0a3c in finobt block 11/15752775 agi_freecount 23, counted 0 in ag 11 finobt Metadata CRC error detected at 0x43cfad, xfs_bnobt block 0xea41a370/0x1000 btree block 8/2889998 is suspect, error -74 bad magic # 0x32375841 in btbno block 8/2889998 Metadata CRC error detected at 0x43cfad, xfs_cntbt block 0xec9306e0/0x1000 btree block 8/7751036 is suspect, error -74 bad magic # 0x70b021e in btcnt block 8/7751036 agf_freeblks 1514911, counted 0 in ag 8 agf_longest 1508010, counted 0 in ag 8 Metadata CRC error detected at 0x46b78d, xfs_finobt block 0xea41a368/0x1000 btree block 8/2889997 is suspect, error -74 bad magic # 0x14634749 in finobt block 8/2889997 agi_count 4064, counted 3872 in ag 8 agi_freecount 60, counted 6 in ag 8 agi_freecount 60, counted 0 in ag 8 finobt sb_ifree 433, counted 454 sb_fdblocks 355758814, counted 292942049 - 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 Metadata corruption detected at 0x435c43, xfs_inode block 0xec930700/0x4000 - agno = 8 imap claims a free inode 4352548412 is in use, correcting imap and clearing inode cleared inode 4352548412 bad CRC for inode 4356975616 bad magic number 0x8d03 on inode 4356975616 bad version number 0xffffffea on inode 4356975616 inode identifier 10414733055754289 mismatch on inode 4356975616 bad CRC for inode 4356975617 bad magic number 0x8 on inode 4356975617 bad version number 0x0 on inode 4356975617 inode identifier 34058991880437873 mismatch on inode 4356975617 bad CRC for inode 4356975618 bad magic number 0x1 on inode 4356975618 bad version number 0x0 on inode 4356975618 inode identifier 28429462278045744 mismatch on inode 4356975618 bad CRC for inode 4356975619 bad magic number 0xc on inode 4356975619 bad version number 0x77 on inode 4356975619 inode identifier 28710945844953187 mismatch on inode 4356975619 bad CRC for inode 4356975620 bad magic number 0x25 on inode 4356975620 bad version number 0x54 on inode 4356975620 inode identifier 19703596266618962 mismatch on inode 4356975620 bad CRC for inode 4356975621 bad magic number 0x72 on inode 4356975621 bad version number 0x0 on inode 4356975621 inode identifier 2251804192538624 mismatch on inode 4356975621 bad CRC for inode 4356975622 bad magic number 0x2100 on inode 4356975622 bad version number 0x0 on inode 4356975622 inode identifier 32088598324183161 mismatch on inode 4356975622 bad CRC for inode 4356975623 bad magic number 0x800 on inode 4356975623 bad version number 0xa on inode 4356975623 inode identifier 32651548277211239 mismatch on inode 4356975623 bad CRC for inode 4356975624 bad magic number 0x456c on inode 4356975624 bad version number 0x68 on inode 4356975624 bad next_unlinked 0x0 on inode 4356975624 inode identifier 16718487716706123776 mismatch on inode 4356975624 bad CRC for inode 4356975625 bad magic number 0x2a2a on inode 4356975625 bad version number 0x50 on inode 4356975625 inode identifier 7854384404691430912 mismatch on inode 4356975625 bad CRC for inode 4356975626 bad magic number 0x65 on inode 4356975626 bad version number 0x0 on inode 4356975626 inode identifier 23644349022404709 mismatch on inode 4356975626 bad CRC for inode 4356975627 bad magic number 0x65 on inode 4356975627 bad version number 0x0 on inode 4356975627 inode identifier 28429397857206386 mismatch on inode 4356975627 bad CRC for inode 4356975628 bad magic number 0x7400 on inode 4356975628 bad version number 0x61 on inode 4356975628 inode identifier 18446507678709585928 mismatch on inode 4356975628 bad CRC for inode 4356975629 bad magic number 0x0 on inode 4356975629 inode identifier 4378853376 mismatch on inode 4356975629 bad CRC for inode 4356975630 bad magic number 0x72 on inode 4356975630 bad version number 0x0 on inode 4356975630 inode identifier 32370120537931844 mismatch on inode 4356975630 bad CRC for inode 4356975631 bad magic number 0xd901 on inode 4356975631 bad version number 0x73 on inode 4356975631 inode identifier 281612415729692 mismatch on inode 4356975631 bad CRC for inode 4356975632 bad magic number 0x0 on inode 4356975632 bad version number 0x1 on inode 4356975632 inode identifier 5306852512366799043 mismatch on inode 4356975632 bad CRC for inode 4356975633 bad magic number 0x0 on inode 4356975633 bad version number 0x4 on inode 4356975633 bad next_unlinked 0xd90146b6 on inode 4356975633 inode identifier 29555345007575151 mismatch on inode 4356975633 bad CRC for inode 4356975634 bad magic number 0x78 on inode 4356975634 bad version number 0x0 on inode 4356975634 inode identifier 15636857130650990618 mismatch on inode 4356975634 bad CRC for inode 4356975635 bad magic number 0x5c on inode 4356975635 bad version number 0x0 on inode 4356975635 inode identifier 76965830725632 mismatch on inode 4356975635 bad CRC for inode 4356975636 bad magic number 0x50 on inode 4356975636 bad version number 0x0 on inode 4356975636 bad next_unlinked 0x2a2a0000 on inode 4356975636 inode identifier 432347763250825216 mismatch on inode 4356975636 bad CRC for inode 4356975637 bad magic number 0x74 on inode 4356975637 bad version number 0x0 on inode 4356975637 inode identifier 26422638812416 mismatch on inode 4356975637 bad CRC for inode 4356975638 bad magic number 0x10f on inode 4356975638 bad version number 0x0 on inode 4356975638 inode identifier 22799769471680512 mismatch on inode 4356975638 bad CRC for inode 4356975639 bad magic number 0x69 on inode 4356975639 bad version number 0x0 on inode 4356975639 inode identifier 292062298195 mismatch on inode 4356975639 bad CRC for inode 4356975640 bad magic number 0x0 on inode 4356975640 bad version number 0x6 on inode 4356975640 inode identifier 2251859943292932 mismatch on inode 4356975640 bad CRC for inode 4356975641 bad magic number 0xf00 on inode 4356975641 bad version number 0x1 on inode 4356975641 inode identifier 960111579358232693 mismatch on inode 4356975641 bad CRC for inode 4356975642 bad magic number 0x13 on inode 4356975642 bad version number 0xffffffff on inode 4356975642 inode identifier 28992356400496716 mismatch on inode 4356975642 bad CRC for inode 4356975643 bad magic number 0x69 on inode 4356975643 bad version number 0x0 on inode 4356975643 inode identifier 449518836342128905 mismatch on inode 4356975643 bad CRC for inode 4356975644 bad magic number 0x55 on inode 4356975644 bad version number 0x0 on inode 4356975644 inode identifier 577346683864129 mismatch on inode 4356975644 bad CRC for inode 4356975645 bad magic number 0x52 on inode 4356975645 bad version number 0x0 on inode 4356975645 bad next_unlinked 0x0 on inode 4356975645 inode identifier 28429466572030053 mismatch on inode 4356975645 bad CRC for inode 4356975646 bad magic number 0x72 on inode 4356975646 bad version number 0x0 on inode 4356975646 inode identifier 32651462378192997 mismatch on inode 4356975646 bad CRC for inode 4356975647 bad magic number 0x54 on inode 4356975647 bad version number 0x0 on inode 4356975647 inode identifier 19140788049477750 mismatch on inode 4356975647 - agno = 9 - agno = 10 - agno = 11 imap claims a free inode 6030170295 is in use, correcting imap and clearing inode cleared inode 6030170295 imap claims a free inode 6030170296 is in use, correcting imap and clearing inode cleared inode 6030170296 - agno = 12 imap claims a free inode 6494002155 is in use, correcting imap and clearing inode cleared inode 6494002155 - agno = 13 imap claims in-use inode 7012077283 is free, correcting imap imap claims in-use inode 7012077301 is free, correcting imap imap claims in-use inode 7012077302 is free, correcting imap imap claims in-use inode 7012077303 is free, correcting imap imap claims a free inode 7018071948 is in use, correcting imap and clearing inode cleared inode 7018071948 imap claims in-use inode 7018071951 is free, correcting imap imap claims in-use inode 7018071952 is free, correcting imap imap claims in-use inode 7018071953 is free, correcting imap imap claims in-use inode 7018071954 is free, correcting imap imap claims in-use inode 7018071955 is free, correcting imap imap claims in-use inode 7018071956 is free, correcting imap imap claims in-use inode 7018071957 is free, correcting imap imap claims in-use inode 7018071958 is free, correcting imap imap claims in-use inode 7018071959 is free, correcting imap imap claims in-use inode 7018071960 is free, correcting imap imap claims in-use inode 7018071961 is free, correcting imap imap claims in-use inode 7018071962 is free, correcting imap imap claims in-use inode 7018071963 is free, correcting imap imap claims in-use inode 7018071964 is free, correcting imap imap claims in-use inode 7018071965 is free, correcting imap imap claims in-use inode 7018071966 is free, correcting imap imap claims in-use inode 7018071967 is free, correcting imap imap claims in-use inode 7018071968 is free, correcting imap imap claims in-use inode 7018071969 is free, correcting imap imap claims in-use inode 7018071970 is free, correcting imap - agno = 14 - agno = 15 - process newly discovered inodes... 14793d2a5700: Badness in key lookup (length) bp=(bno 0xec930700, len 16384 bytes) key=(bno 0xec930700, len 4096 bytes) Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 0 - agno = 4 - agno = 5 - agno = 7 - agno = 6 entry "5" in shortform directory 2147483828 references non-existent inode 8053063823 junking entry "5" in directory inode 2147483828 corrected i8 count in directory 2147483828, was 2, now 1 - agno = 2 entry "artwork" at block 0 offset 96 in directory inode 3804986635 references non-existent inode 4356975621 clearing inode number in entry at offset 96... entry "Lasso Stilkopien" in shortform directory 3804986656 references non-existent inode 4356975631 junking entry "Lasso Stilkopien" in directory inode 3804986656 corrected i8 count in directory 3804986656, was 1, now 0 corrected directory 3804986656 size, was 56, now 48 entry "3" in shortform directory 3804986658 references non-existent inode 4356975634 junking entry "3" in directory inode 3804986658 corrected i8 count in directory 3804986658, was 1, now 0 corrected directory 3804986658 size, was 10, now 6 entry "c" in shortform directory 3804986666 references non-existent inode 4356975635 junking entry "c" in directory inode 3804986666 corrected i8 count in directory 3804986666, was 1, now 0 corrected directory 3804986666 size, was 10, now 6 entry "c" in shortform directory 3804986668 references non-existent inode 4356975637 junking entry "c" in directory inode 3804986668 corrected i8 count in directory 3804986668, was 1, now 0 corrected directory 3804986668 size, was 10, now 6 entry "624176" in shortform directory 3804986669 references non-existent inode 4356975638 junking entry "624176" in directory inode 3804986669 corrected i8 count in directory 3804986669, was 1, now 0 corrected directory 3804986669 size, was 10, now 6 entry "2" in shortform directory 3804986670 references non-existent inode 4356975639 junking entry "2" in directory inode 3804986670 corrected i8 count in directory 3804986670, was 1, now 0 corrected directory 3804986670 size, was 10, now 6 entry "e" in shortform directory 3804986674 references non-existent inode 4356975641 junking entry "e" in directory inode 3804986674 corrected i8 count in directory 3804986674, was 1, now 0 corrected directory 3804986674 size, was 10, now 6 - agno = 8 entry "7" in shortform directory 4315102411 references non-existent inode 8053063811 junking entry "7" in directory inode 4315102411 corrected i8 count in directory 4315102411, was 3, now 2 - agno = 9 - agno = 10 - agno = 11 - agno = 12 entry "b" in shortform directory 6442451092 references non-existent inode 4356975636 junking entry "b" in directory inode 6442451092 corrected i8 count in directory 6442451092, was 5, now 4 - agno = 13 entry "Bounces" at block 0 offset 96 in directory inode 6030170294 references free inode 6494002155 clearing inode number in entry at offset 96... entry "Mosaic Teaser.mov" at block 0 offset 176 in directory inode 6030170294 references free inode 6030170295 clearing inode number in entry at offset 176... entry "Mosaic Teaser.vcache" at block 0 offset 208 in directory inode 6030170294 references free inode 6030170296 clearing inode number in entry at offset 208... - agno = 14 entry "4" in shortform directory 7516192896 references non-existent inode 8053063808 junking entry "4" in directory inode 7516192896 corrected i8 count in directory 7516192896, was 2, now 1 entry "1" in shortform directory 7516192897 references non-existent inode 8053063809 junking entry "1" in directory inode 7516192897 corrected i8 count in directory 7516192897, was 2, now 1 entry "d" in shortform directory 7516192898 references non-existent inode 8053063810 junking entry "d" in directory inode 7516192898 corrected i8 count in directory 7516192898, was 2, now 1 entry "9" in shortform directory 7516192900 references non-existent inode 8053063812 junking entry "9" in directory inode 7516192900 corrected i8 count in directory 7516192900, was 2, now 1 entry "625121" in shortform directory 7516192901 references non-existent inode 8053063813 junking entry "625121" in directory inode 7516192901 corrected i8 count in directory 7516192901, was 2, now 1 entry "9" in shortform directory 7516192902 references non-existent inode 8053063814 junking entry "9" in directory inode 7516192902 corrected i8 count in directory 7516192902, was 1, now 0 corrected directory 7516192902 size, was 10, now 6 entry "625343" in shortform directory 7516192903 references non-existent inode 8053063815 junking entry "625343" in directory inode 7516192903 corrected i8 count in directory 7516192903, was 2, now 1 entry "e" in shortform directory 7516192904 references non-existent inode 8053063816 junking entry "e" in directory inode 7516192904 corrected i8 count in directory 7516192904, was 1, now 0 corrected directory 7516192904 size, was 23, now 15 entry "a" in shortform directory 7516192905 references non-existent inode 8053063817 junking entry "a" in directory inode 7516192905 corrected i8 count in directory 7516192905, was 2, now 1 entry "6" in shortform directory 7516192906 references non-existent inode 8053063818 junking entry "6" in directory inode 7516192906 corrected i8 count in directory 7516192906, was 1, now 0 corrected directory 7516192906 size, was 10, now 6 entry "c" in shortform directory 7516192907 references non-existent inode 8053063819 junking entry "c" in directory inode 7516192907 corrected i8 count in directory 7516192907, was 2, now 1 entry "e" in shortform directory 7516192908 references non-existent inode 8053063820 junking entry "e" in directory inode 7516192908 corrected i8 count in directory 7516192908, was 2, now 1 entry "6" in shortform directory 7516192909 references non-existent inode 8053063821 junking entry "6" in directory inode 7516192909 corrected i8 count in directory 7516192909, was 1, now 0 corrected directory 7516192909 size, was 10, now 6 entry "c" in shortform directory 7516192910 references non-existent inode 8053063822 junking entry "c" in directory inode 7516192910 corrected i8 count in directory 7516192910, was 2, now 1 entry "6" in shortform directory 7516192912 references non-existent inode 8053063824 junking entry "6" in directory inode 7516192912 corrected i8 count in directory 7516192912, was 2, now 1 entry "625893" in shortform directory 7516192913 references non-existent inode 8053063825 junking entry "625893" in directory inode 7516192913 corrected i8 count in directory 7516192913, was 2, now 1 entry "7" in shortform directory 7516192914 references non-existent inode 8053063826 junking entry "7" in directory inode 7516192914 corrected i8 count in directory 7516192914, was 2, now 1 entry "8" in shortform directory 7516192915 references non-existent inode 8053063827 junking entry "8" in directory inode 7516192915 corrected i8 count in directory 7516192915, was 1, now 0 corrected directory 7516192915 size, was 10, now 6 entry "d" in shortform directory 7516192916 references non-existent inode 8053063828 junking entry "d" in directory inode 7516192916 corrected i8 count in directory 7516192916, was 2, now 1 - agno = 15 entry "4352548412" at block 4 offset 3112 in directory inode 118303122 references free inode 4352548412 clearing inode number in entry at offset 3112... entry "4356975628" at block 4 offset 3136 in directory inode 118303122 references non-existent inode 4356975628 clearing inode number in entry at offset 3136... entry "d" in shortform directory 2237215510 references non-existent inode 4356975640 junking entry "d" in directory inode 2237215510 corrected i8 count in directory 2237215510, was 1, now 0 corrected directory 2237215510 size, was 36, now 24 entry "Michael Lauterbach" in shortform directory 2249864432 references non-existent inode 4356975618 junking entry "Michael Lauterbach" in directory inode 2249864432 corrected i8 count in directory 2249864432, was 4, now 3 Phase 5 - rebuild AG headers and trees... - 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 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 entry "6488906477" in dir inode 118303122 inconsistent with .. value (3221225601) in ino 6488906477 will clear entry "6488906477" entry "6488906487" in dir inode 118303122 inconsistent with .. value (4345579226) in ino 6488906487 will clear entry "6488906487" entry "6488906488" in dir inode 118303122 inconsistent with .. value (4345579226) in ino 6488906488 will clear entry "6488906488" entry "6488906495" in dir inode 118303122 inconsistent with .. value (3804780544) in ino 6488906495 will clear entry "6488906495" rebuilding directory inode 118303122 - agno = 1 - agno = 2 - agno = 3 - agno = 4 fixing ftype mismatch (1/2) in directory/child inode 2237215510/2692158256 fixing ftype mismatch (0/2) in directory/child inode 2237215510/2274165027 - agno = 5 - agno = 6 - agno = 7 bad hash table for directory inode 3804986635 (no data entry): rebuilding rebuilding directory inode 3804986635 fixing ftype mismatch (0/1) in directory/child inode 3804986656/3804986657 - agno = 8 bad hash table for directory inode 4328950968 (no data entry): rebuilding rebuilding directory inode 4328950968 - agno = 9 - agno = 10 - agno = 11 bad hash table for directory inode 6030170294 (no data entry): rebuilding rebuilding directory inode 6030170294 - agno = 12 - agno = 13 - agno = 14 fixing ftype mismatch (1/2) in directory/child inode 7516192904/2692194663 - agno = 15 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 119649557, moving to lost+found disconnected dir inode 119649558, moving to lost+found disconnected dir inode 119649559, moving to lost+found disconnected dir inode 119649560, moving to lost+found disconnected dir inode 119649561, moving to lost+found disconnected dir inode 119649563, moving to lost+found disconnected dir inode 119649565, moving to lost+found disconnected dir inode 119649566, moving to lost+found disconnected dir inode 119649567, moving to lost+found disconnected dir inode 119649568, moving to lost+found disconnected dir inode 119649569, moving to lost+found disconnected dir inode 119649570, moving to lost+found disconnected dir inode 119649571, moving to lost+found disconnected dir inode 119649572, moving to lost+found disconnected dir inode 119649573, moving to lost+found disconnected dir inode 119649575, moving to lost+found disconnected dir inode 119649576, moving to lost+found disconnected dir inode 119649577, moving to lost+found disconnected inode 4352548413, moving to lost+found disconnected inode 4352548414, moving to lost+found disconnected inode 4352548415, moving to lost+found disconnected dir inode 4868724854, moving to lost+found disconnected dir inode 4868724857, moving to lost+found disconnected dir inode 4868731400, moving to lost+found disconnected dir inode 4868731401, moving to lost+found disconnected dir inode 4868731402, moving to lost+found disconnected dir inode 4868731404, moving to lost+found disconnected dir inode 4868731405, moving to lost+found disconnected dir inode 4868731406, moving to lost+found disconnected dir inode 6488906477, moving to lost+found disconnected dir inode 6488906487, moving to lost+found disconnected dir inode 6488906488, moving to lost+found disconnected dir inode 6488906495, moving to lost+found disconnected inode 6494002156, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 2147483828 nlinks from 6 to 5 resetting inode 4315102411 nlinks from 4 to 3 resetting inode 3804986635 nlinks from 3 to 2 resetting inode 3804986656 nlinks from 3 to 2 resetting inode 3804986658 nlinks from 3 to 2 resetting inode 3804986666 nlinks from 3 to 2 resetting inode 3804986668 nlinks from 3 to 2 resetting inode 3804986669 nlinks from 3 to 2 resetting inode 3804986670 nlinks from 3 to 2 resetting inode 3804986674 nlinks from 3 to 2 resetting inode 6442451092 nlinks from 10 to 9 resetting inode 7516192896 nlinks from 6 to 5 resetting inode 7516192897 nlinks from 3 to 2 resetting inode 7516192898 nlinks from 3 to 2 resetting inode 7516192900 nlinks from 3 to 2 resetting inode 7516192901 nlinks from 3 to 2 resetting inode 7516192902 nlinks from 3 to 2 resetting inode 7516192903 nlinks from 3 to 2 resetting inode 7516192904 nlinks from 4 to 3 resetting inode 7516192905 nlinks from 3 to 2 resetting inode 7516192906 nlinks from 3 to 2 resetting inode 7516192907 nlinks from 3 to 2 resetting inode 7516192908 nlinks from 3 to 2 resetting inode 7516192909 nlinks from 3 to 2 resetting inode 7516192910 nlinks from 3 to 2 resetting inode 7516192912 nlinks from 3 to 2 resetting inode 7516192913 nlinks from 3 to 2 resetting inode 7516192914 nlinks from 3 to 2 resetting inode 7516192915 nlinks from 3 to 2 resetting inode 7516192916 nlinks from 3 to 2 resetting inode 6030170294 nlinks from 5 to 4 resetting inode 2237215510 nlinks from 5 to 4 resetting inode 2249864432 nlinks from 8 to 7 resetting inode 118303122 nlinks from 594 to 618 Maximum metadata LSN (1643860431:58251) is ahead of log (1643860431:1077). Format log to cycle 1643860434. XFS_REPAIR Summary Mon Feb 20 19:42:37 2023 Phase Start End Duration Phase 1: 02/20 19:41:06 02/20 19:41:06 Phase 2: 02/20 19:41:06 02/20 19:41:09 3 seconds Phase 3: 02/20 19:41:09 02/20 19:41:55 46 seconds Phase 4: 02/20 19:41:55 02/20 19:41:55 Phase 5: 02/20 19:41:55 02/20 19:41:57 2 seconds Phase 6: 02/20 19:41:57 02/20 19:42:12 15 seconds Phase 7: 02/20 19:42:12 02/20 19:42:12 Total run time: 1 minute, 6 seconds done -
Dear JorgeB, dear trurl,
I have again (feels like the 10th time) physically checked the connections. Everything is fine. I'm using a 750W modular psu from Gigabyte that has three sata slots. All three are taken and I've had drives failing on two out of the three... There are no splitters beyond the four connectors on each rail.
I've again run xfs-repair, but this time the drive still remains unmountable....
1 hour ago, trurl said:Unrelated, your appdata has some files on disk2. Why are you still on 6.9.2?
I've actually run mover with appdata set to "prefer" after the drive issues seemed fixed... Not sure why there are still some files on disk 2...
I'm on 6.9.2 because I was never presented with a prompt to update... Can I update manually?
Thank you all! -
Some days have passed and now drive 7 has metadata corruption and is in error state...
What is going on? This server feels almost cursed... -
Dear community,
I'm looking for a way to bidirectionally sync my main Unraid server, with another nas. Until now I was using rsync to copy my main server's files to the backup nas. However, recently the filesystem of one of my drives got corrupted, and now some files are in the lost+found folder (full story here). I'm afraid that continuing to use rsync would delete the files rsync no longer finds in the source from the destination.
Is there any way to use rsync (or similar tool) to keep the good files on the backup and even restore them to my main server?
Many thanks! -
Alright, seems that the rebuild finished without problems.
After running xfs-repair on disk 7, the lost+found folder was created and, as far as I understand, anything inside of it represents corrupted data on disk 7. Since data rebuild is based on bit patterns of all drives, wouldn't rebuilding disk 2 also be affected by the corruption of disk 7? Would dual parity prevent that from happening? Do you recommend it?
I've very frequently had drives getting disabled in the past few months and I'm still not sure what is causing it, but after this experience it might be either the cables coming from the power supply or a pci usb controller card that I removed while replacing the cable. Would it be possible for a pci card to interfere with power delivery to the rest of the system?Are there any recommended reliable psu cables for modular power supplies?
Thanks to all the wonderful moderators who assisted!
-
23 minutes ago, itimpi said:
check all cabling (power and SATA)
Thank you all for your replies. I've checked the cables and everything was absolutely fine in terms of physical connection. However. The SATA power connector was the last of a rail of 4. I'm not sure if this should affect its performance, but I went ahead and used another one from a different cable coming from my power supply. Now (fingers crossed) it seems that data rebuild has started.
But the question is: could this really have been the problem? And why would this happen?
-
Dear trurl,
I've followed the instructions you posted for rebuilding a drive onto itself. However when I start the array after reassigning disk 2, I still only get a red cross. I've tried again starting in maintenance mode and pressing sync but the data rebuild immediately switches to "paused 0.0%".Any idea what could be wrong?
-
Dear trurl,
Thank you again! After running xfs-repair disk 7 seems to have come back.As expected, a lost+found folder was created with many files in it that I will have to assess individually... Is there any chance that other files beside those in the lost+found folder might have been corrupted in the process?
Since I'm normally rsyncing the most important folders on this server with another nas, what rsync flags should I use to avoid overwriting the other nas with corrupted or missing data (i.e. deleting the backup)? Is there any way I could use rsync to perform a bidirectional sync, so that any "healthy" files on the backup would be restored to my Unraid server? I realise that these questions might potentially be better addressed in a separate topic. Let me know if that would be preferable.
What should I do next about my "missing" disk 2?Your help means a lot!
-
3 minutes ago, trurl said:
It doesn't attempt to mount any drives in maintentance mode
Yes, obvious mistake on my part... or maybe just wishful thinking!
After restarting the array normally, I'm back to square one.
4 minutes ago, trurl said:appdata is prefer, system is no
Alright, will do as you suggested after I can fix the drive issues.
I'm still getting the aforementioned error message. I don't recall reading it some weeks ago. -
Dear trurl,
Thank you for your continued support!I've now attached the drive to my sas controller, which has so far proved to be more reliable than the motherboard's internal sata ports. After starting the array in maintenance mode, drive 7 no longer shows "unmountable", which I guess is good news. Also, the log does not seem to report any connection errors any longer. However, I'm getting spammed with "FastCGI sent in stderr", which is an error I've never seen before and have no idea what it stands for.
Should I still run xfs repair? And what are my next steps after that?
And, by the way, thank you for pointing out the problem with the appdata and system files. I thought I had set both folders to "prefer", but I will check. -
I am now again able to access my server and after checking, it seems that one of the sata cables had indeed come loose (although I'm not 100% sure about that, it might just be from my poking into the system). However, upon rebooting the system freezes up:
EDIT:
Following the instructions on this link and renaming vfio-pci.cfg solved the issue but I still have an unmountable drive (disk 7) and a disabled one (disk 2, see diagnostics). What are the next steps going to be?
Thank you all in advance! -
Dear trurl,
Thank you for the link! I seriously hope that disk7 turns out to have a bad power cable. Should that not be the case and should I still be left with one drive disabled and the other unmountable, what options do I have to retrieve as much data as possible? Also, how can I avoid such a scenario from happening again? Ever since last year, I've had drives randomly being disabled and I never could figure out what was causing the problem... I have replaced cables time and time again and have installed a SAS controller to avoid the onboard Sata connectors, but nothing seems to work reliably.
Docker images disappeared, VMs "paused"
in General Support
Posted
Dear JorgeB,
Thank you for your quick reply!
I don't really know what to say. One restart later, everything seems back to normal... The frustrating thing is, I'm not quite sure what caused the problem in the first place, or how I could prevent it from happening again in the future.