loungelizard Posted August 21, 2022 Share Posted August 21, 2022 Hi guys, I am trying to explain what happened and am desperately seeking your advice. This is the setup in question: Quote [0:0:0:0] disk SanDisk' Cruzer Fit 1.00 /dev/sda [1:0:0:0] disk ATA ST4000LM024-2AN1 0001 /dev/sdb [1:0:3:0] disk ATA ST16000NE000-2RW EN02 /dev/sdf [1:0:4:0] disk ATA ST16000NE000-2RW EN02 /dev/sdg [1:0:5:0] disk ATA ST16000NE000-2RW EN02 /dev/sdh [1:0:9:0] disk ATA ST16000NM001G-2K SN03 /dev/sdd [1:0:10:0] disk ATA ST16000NM001G-2K SN02 /dev/sde [6:0:0:0] disk ATA Colorful SL500 5 6A0 /dev/sdc sdg is my parity sdf disk 1 sdi disk 2 sdb disk 4 sdj disk 5 sdh is my old disk 1 After my disk1 repeatedly got disabled, I purchasd a new replacement disk. After pre-clearing I started the rebuild of the missing disk. After a day I went back to check that it had only rebuild 0.7% and the system seemed stuck. The log show some read errors on disk 5 (which so far did not cause any problems) but the system was not responding. Halting, rebooting, nothing worked, also not downloading diagnostics. So after trying to figure out the stuck process for some time I gave up and maybe did an unclever thing by forcing a power down. The system then came back up with, after I started the array it stated 4 disks unmountable. I switched back to maintenance mode, tried to get xfs-repair to show me what may be an issue, but it stopped with superblock errors on all disks in question. The Log file is now showing these messages... 1 - 2 - 5 all in succession, ever minute. Aug 21 18:19:01 bigpool kernel: Buffer I/O error on dev md1, logical block 3906469856, async page read Aug 21 18:20:01 bigpool kernel: Buffer I/O error on dev md2, logical block 3906469856, async page read Aug 21 18:20:01 bigpool kernel: Buffer I/O error on dev md5, logical block 3906469856, async page read Aug 21 18:20:01 bigpool kernel: Buffer I/O error on dev md1, logical block 3906469856, async page read Now I am stuck again as in what I can even try to do. Trying to run xfs-repair give me this, on all disks 1,2,5 Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error Now I am "somewhat stuck in a maintenance mode" but it doesn't respond, shut down, stop the array or anything. Since I am unable to download any diagnostics, what can I do manually so some of you has an idea how to recover the disks and data on it? cheers, Florian Quote Link to comment
plantsandbinary Posted August 21, 2022 Share Posted August 21, 2022 Try and Google a couple of ways to repair your superblock. The data is very likely still there, but you've lost your metadata and the system doesn't know what to do with the files (let alone what they even are). I had the same issue due to a freak error that occured with my motherboard model. Not due to an unclean shutdown during rebuild. I'm just going to be really honest with you. If you cannot fix your superblocks, the only option you have is professional data recovery service. An unclean shutdown during a rebuild is one of the worst things that can happen to your array and you should always consult the pros before ever killing power. At the earlier stage you could have backed up your superblocks at the very least before killing the power. Often-times the best thing is to just stop the process, do a disk image and then try again. It's a lot more difficult if you have totally borked disks as you need to remember during a rebuild everything is being overwritten with what's in parity. I "lost" 11TB of data from the same thing, irrecoverable superblocks. Those drives are in my cupboard now waiting until a day when I bother to fork over a few thousand dollars to have the data restored or until some "magic" machine learning can fix it for me. The data is still there on the disks but nothing can tell me what it even is, how to organize it, etc. there's no metadata whatsoever. It's worse than just an accidental delete because I could recover from that. Good luck. P.S. Remember that every write operation potentially makes you data harder to get back. So pick your next steps incredibly carefully. P.P.S. I guess it does not need to be said but UNRAID is not a backup solution and you should always have a backup of the backup. The 3, 2, 1 method works. Quote Link to comment
loungelizard Posted August 21, 2022 Author Share Posted August 21, 2022 Thanks, I am aware of the problems it has caused and the most super critical data is safely stored in multiple other locations, so if it's all gone in the end it will be painful but not life threating However the issue I am having is that at the moment I am completely stuck as to which command to run to at least unmount the arrays again to even try to recover any data or repair any superblock, if that is even the issue... For the last 2 hours it just kept writing the I/O-error to the log every minute, doesn't shut down or pretty much does anything else.... anyone else with some ideas as to how to continue? Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 attach diagnostics to your NEXT post in this thread Have you tried from the command line? Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 2 hours ago, loungelizard said: Trying to run xfs-repair Exactly how did you do this? From webUI or from command line? Quote Link to comment
loungelizard Posted August 21, 2022 Author Share Posted August 21, 2022 37 minutes ago, trurl said: Exactly how did you do this? From webUI or from command line? tried from the command-line, but disks were no longer found... Could not get diagnostics from webUI to deliver me data, couldn't tell where the process got stuck. Quote Link to comment
itimpi Posted August 21, 2022 Share Posted August 21, 2022 24 minutes ago, loungelizard said: tried from the command-line, In which case exactly what command did you use? the symptoms are not unusual if you get the command slightly wrong. Quote Link to comment
trurl Posted August 21, 2022 Share Posted August 21, 2022 3 hours ago, loungelizard said: Could not get diagnostics from webUI Did you try to get diagnostics from the command line? What is the exact command you used for check filesystem? Do you have encrypted disks? Quote Link to comment
loungelizard Posted August 26, 2022 Author Share Posted August 26, 2022 (edited) sorry, I was on business trip the last days and couldn't continue checking. I was able to shutdown the server properly last time and now retrieved new diagnostics today as well as one from last Sunday before the unclean shutdown. Again any help appreciated. Thanks for your help and patience. bigpool-diagnostics-20220826-0659.zip bigpool-diagnostics-20220821-0718.zip Edited August 26, 2022 by loungelizard Update diagnostics Quote Link to comment
JorgeB Posted August 26, 2022 Share Posted August 26, 2022 There are disk errors in multiple disks since boot, check all cables, could also be bad power. Quote Link to comment
loungelizard Posted August 27, 2022 Author Share Posted August 27, 2022 Thanks, question is how to proceed now. I am back in the state where the array is in maintenance mode, i am unable to download any new diagnostics or stop the array again. All that is now showing is the read errors on disks 1,2,5 Aug 27 07:29:02 bigpool kernel: Buffer I/O error on dev md2, logical block 3906469856, async page read Aug 27 07:29:02 bigpool kernel: Buffer I/O error on dev md5, logical block 3906469856, async page read Aug 27 07:29:02 bigpool kernel: Buffer I/O error on dev md1, logical block 3906469856, async page read I have taken out the old disk1 from the array to not drain any additional power, that is the same setup that has been running for months now. I'm uncertain how to even try to diagnose or try to correct the problem at this stage... any pointers? Quote Link to comment
JorgeB Posted August 27, 2022 Share Posted August 27, 2022 Check all cables and/or try with a different PSU. Quote Link to comment
itimpi Posted August 27, 2022 Share Posted August 27, 2022 It could also be worth checking that any HBA you have is properly seated in the motherboard. Quote Link to comment
loungelizard Posted August 27, 2022 Author Share Posted August 27, 2022 Thanks for your continuous support. all HBA are fixed and cables are fixed. At the moment, I am unable to try with a different PSU. As I mentioned initially, all I did was try to rebuild on a new disk, the entire setup has been running flawlessly for over a year so far. When I reboot in safe mode (shutdown works), and try to run xfs-check on the disks in problem, i get errors like this in the first run, a second run is not possible due to i/o errors. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 4851860573 no . entry for directory 4851860573 no .. entry for directory 4851860573 problem with directory contents in inode 4851860573 would have cleared inode 4851860573 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 4851860604 no . entry for directory 4851860604 no .. entry for directory 4851860604 problem with directory contents in inode 4851860604 would have cleared inode 4851860604 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5124536740 no . entry for directory 5124536740 no .. entry for directory 5124536740 problem with directory contents in inode 5124536740 would have cleared inode 5124536740 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5125040217 no . entry for directory 5125040217 no .. entry for directory 5125040217 problem with directory contents in inode 5125040217 would have cleared inode 5125040217 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5125040233 no . entry for directory 5125040233 no .. entry for directory 5125040233 problem with directory contents in inode 5125040233 would have cleared inode 5125040233 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5125040249 no . entry for directory 5125040249 no .. entry for directory 5125040249 problem with directory contents in inode 5125040249 would have cleared inode 5125040249 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5125666493 no . entry for directory 5125666493 no .. entry for directory 5125666493 problem with directory contents in inode 5125666493 would have cleared inode 5125666493 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5126194197 no . entry for directory 5126194197 no .. entry for directory 5126194197 problem with directory contents in inode 5126194197 would have cleared inode 5126194197 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5126194211 no . entry for directory 5126194211 no .. entry for directory 5126194211 problem with directory contents in inode 5126194211 would have cleared inode 5126194211 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5126194233 no . entry for directory 5126194233 no .. entry for directory 5126194233 problem with directory contents in inode 5126194233 would have cleared inode 5126194233 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5126814403 no . entry for directory 5126814403 no .. entry for directory 5126814403 problem with directory contents in inode 5126814403 would have cleared inode 5126814403 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5126814418 no . entry for directory 5126814418 no .. entry for directory 5126814418 problem with directory contents in inode 5126814418 would have cleared inode 5126814418 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5126814432 no . entry for directory 5126814432 no .. entry for directory 5126814432 problem with directory contents in inode 5126814432 would have cleared inode 5126814432 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5127416517 no . entry for directory 5127416517 no .. entry for directory 5127416517 problem with directory contents in inode 5127416517 would have cleared inode 5127416517 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5127416533 no . entry for directory 5127416533 no .. entry for directory 5127416533 problem with directory contents in inode 5127416533 would have cleared inode 5127416533 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5127416546 no . entry for directory 5127416546 no .. entry for directory 5127416546 problem with directory contents in inode 5127416546 would have cleared inode 5127416546 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5127416567 no . entry for directory 5127416567 no .. entry for directory 5127416567 problem with directory contents in inode 5127416567 would have cleared inode 5127416567 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5128291725 no . entry for directory 5128291725 no .. entry for directory 5128291725 problem with directory contents in inode 5128291725 would have cleared inode 5128291725 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5128291740 no . entry for directory 5128291740 no .. entry for directory 5128291740 problem with directory contents in inode 5128291740 would have cleared inode 5128291740 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5128291752 no . entry for directory 5128291752 no .. entry for directory 5128291752 problem with directory contents in inode 5128291752 would have cleared inode 5128291752 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5128291764 xfs_repair: read failed: Input/output error can't read block 1 for directory inode 5128291764 xfs_repair: read failed: Input/output error can't read block 2 for directory inode 5128291764 no . entry for directory 5128291764 no .. entry for directory 5128291764 problem with directory contents in inode 5128291764 would have cleared inode 5128291764 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5128770108 no . entry for directory 5128770108 no .. entry for directory 5128770108 problem with directory contents in inode 5128770108 would have cleared inode 5128770108 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5131898445 xfs_repair: read failed: Input/output error can't read block 1 for directory inode 5131898445 no . entry for directory 5131898445 no .. entry for directory 5131898445 problem with directory contents in inode 5131898445 would have cleared inode 5131898445 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5140237856 no . entry for directory 5140237856 no .. entry for directory 5140237856 problem with directory contents in inode 5140237856 would have cleared inode 5140237856 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5145803332 no . entry for directory 5145803332 no .. entry for directory 5145803332 problem with directory contents in inode 5145803332 would have cleared inode 5145803332 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5145803368 no . entry for directory 5145803368 no .. entry for directory 5145803368 problem with directory contents in inode 5145803368 would have cleared inode 5145803368 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5146272820 no . entry for directory 5146272820 no .. entry for directory 5146272820 problem with directory contents in inode 5146272820 would have cleared inode 5146272820 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5146288900 no . entry for directory 5146288900 no .. entry for directory 5146288900 problem with directory contents in inode 5146288900 would have cleared inode 5146288900 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5146288916 no . entry for directory 5146288916 no .. entry for directory 5146288916 problem with directory contents in inode 5146288916 would have cleared inode 5146288916 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5146288926 no . entry for directory 5146288926 no .. entry for directory 5146288926 problem with directory contents in inode 5146288926 would have cleared inode 5146288926 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5146288946 no . entry for directory 5146288946 no .. entry for directory 5146288946 problem with directory contents in inode 5146288946 would have cleared inode 5146288946 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5147106944 no . entry for directory 5147106944 no .. entry for directory 5147106944 problem with directory contents in inode 5147106944 would have cleared inode 5147106944 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5147106954 no . entry for directory 5147106954 no .. entry for directory 5147106954 problem with directory contents in inode 5147106954 would have cleared inode 5147106954 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5147106971 no . entry for directory 5147106971 no .. entry for directory 5147106971 problem with directory contents in inode 5147106971 would have cleared inode 5147106971 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5147106984 no . entry for directory 5147106984 no .. entry for directory 5147106984 problem with directory contents in inode 5147106984 would have cleared inode 5147106984 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5148528769 no . entry for directory 5148528769 no .. entry for directory 5148528769 problem with directory contents in inode 5148528769 would have cleared inode 5148528769 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5148528788 no . entry for directory 5148528788 no .. entry for directory 5148528788 problem with directory contents in inode 5148528788 would have cleared inode 5148528788 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5148528796 no . entry for directory 5148528796 no .. entry for directory 5148528796 problem with directory contents in inode 5148528796 would have cleared inode 5148528796 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5149320007 no . entry for directory 5149320007 no .. entry for directory 5149320007 problem with directory contents in inode 5149320007 would have cleared inode 5149320007 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5149320041 no . entry for directory 5149320041 no .. entry for directory 5149320041 problem with directory contents in inode 5149320041 would have cleared inode 5149320041 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5150606547 no . entry for directory 5150606547 no .. entry for directory 5150606547 problem with directory contents in inode 5150606547 would have cleared inode 5150606547 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5150606574 no . entry for directory 5150606574 no .. entry for directory 5150606574 problem with directory contents in inode 5150606574 would have cleared inode 5150606574 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5151341396 no . entry for directory 5151341396 no .. entry for directory 5151341396 problem with directory contents in inode 5151341396 would have cleared inode 5151341396 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5151341437 no . entry for directory 5151341437 no .. entry for directory 5151341437 problem with directory contents in inode 5151341437 would have cleared inode 5151341437 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5152195535 no . entry for directory 5152195535 no .. entry for directory 5152195535 problem with directory contents in inode 5152195535 would have cleared inode 5152195535 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5152195547 no . entry for directory 5152195547 no .. entry for directory 5152195547 problem with directory contents in inode 5152195547 would have cleared inode 5152195547 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5152195561 no . entry for directory 5152195561 no .. entry for directory 5152195561 problem with directory contents in inode 5152195561 would have cleared inode 5152195561 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5152195577 no . entry for directory 5152195577 no .. entry for directory 5152195577 problem with directory contents in inode 5152195577 would have cleared inode 5152195577 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5152962569 no . entry for directory 5152962569 no .. entry for directory 5152962569 problem with directory contents in inode 5152962569 would have cleared inode 5152962569 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5152962595 no . entry for directory 5152962595 no .. entry for directory 5152962595 problem with directory contents in inode 5152962595 would have cleared inode 5152962595 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5152962609 no . entry for directory 5152962609 no .. entry for directory 5152962609 problem with directory contents in inode 5152962609 would have cleared inode 5152962609 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5154055966 no . entry for directory 5154055966 no .. entry for directory 5154055966 problem with directory contents in inode 5154055966 would have cleared inode 5154055966 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5154055985 no . entry for directory 5154055985 no .. entry for directory 5154055985 problem with directory contents in inode 5154055985 would have cleared inode 5154055985 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5156226251 no . entry for directory 5156226251 no .. entry for directory 5156226251 problem with directory contents in inode 5156226251 would have cleared inode 5156226251 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5156226263 no . entry for directory 5156226263 no .. entry for directory 5156226263 problem with directory contents in inode 5156226263 would have cleared inode 5156226263 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5156226283 no . entry for directory 5156226283 no .. entry for directory 5156226283 problem with directory contents in inode 5156226283 would have cleared inode 5156226283 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5156226298 no . entry for directory 5156226298 no .. entry for directory 5156226298 problem with directory contents in inode 5156226298 would have cleared inode 5156226298 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5156939327 no . entry for directory 5156939327 no .. entry for directory 5156939327 problem with directory contents in inode 5156939327 would have cleared inode 5156939327 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5158171721 no . entry for directory 5158171721 no .. entry for directory 5158171721 problem with directory contents in inode 5158171721 would have cleared inode 5158171721 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5158171735 no . entry for directory 5158171735 no .. entry for directory 5158171735 problem with directory contents in inode 5158171735 would have cleared inode 5158171735 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5158171753 no . entry for directory 5158171753 no .. entry for directory 5158171753 problem with directory contents in inode 5158171753 would have cleared inode 5158171753 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5158659713 no . entry for directory 5158659713 no .. entry for directory 5158659713 problem with directory contents in inode 5158659713 would have cleared inode 5158659713 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5158792846 no . entry for directory 5158792846 no .. entry for directory 5158792846 problem with directory contents in inode 5158792846 would have cleared inode 5158792846 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5158792875 no . entry for directory 5158792875 no .. entry for directory 5158792875 problem with directory contents in inode 5158792875 would have cleared inode 5158792875 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5158792889 no . entry for directory 5158792889 no .. entry for directory 5158792889 problem with directory contents in inode 5158792889 would have cleared inode 5158792889 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5159967305 no . entry for directory 5159967305 no .. entry for directory 5159967305 problem with directory contents in inode 5159967305 would have cleared inode 5159967305 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5159967327 no . entry for directory 5159967327 no .. entry for directory 5159967327 problem with directory contents in inode 5159967327 would have cleared inode 5159967327 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5159967340 no . entry for directory 5159967340 no .. entry for directory 5159967340 problem with directory contents in inode 5159967340 would have cleared inode 5159967340 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5219165389 no . entry for directory 5219165389 no .. entry for directory 5219165389 problem with directory contents in inode 5219165389 would have cleared inode 5219165389 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5219165406 no . entry for directory 5219165406 no .. entry for directory 5219165406 problem with directory contents in inode 5219165406 would have cleared inode 5219165406 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5219165427 no . entry for directory 5219165427 no .. entry for directory 5219165427 problem with directory contents in inode 5219165427 would have cleared inode 5219165427 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5256723536 no . entry for directory 5256723536 no .. entry for directory 5256723536 problem with directory contents in inode 5256723536 would have cleared inode 5256723536 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5256723563 no . entry for directory 5256723563 no .. entry for directory 5256723563 problem with directory contents in inode 5256723563 would have cleared inode 5256723563 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5256725537 no . entry for directory 5256725537 no .. entry for directory 5256725537 problem with directory contents in inode 5256725537 would have cleared inode 5256725537 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5256859987 no . entry for directory 5256859987 no .. entry for directory 5256859987 problem with directory contents in inode 5256859987 would have cleared inode 5256859987 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5256859988 no . entry for directory 5256859988 no .. entry for directory 5256859988 problem with directory contents in inode 5256859988 would have cleared inode 5256859988 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5256859994 no . entry for directory 5256859994 no .. entry for directory 5256859994 problem with directory contents in inode 5256859994 would have cleared inode 5256859994 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5256907254 no . entry for directory 5256907254 no .. entry for directory 5256907254 problem with directory contents in inode 5256907254 would have cleared inode 5256907254 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5257158026 no . entry for directory 5257158026 no .. entry for directory 5257158026 problem with directory contents in inode 5257158026 would have cleared inode 5257158026 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5257176623 no . entry for directory 5257176623 no .. entry for directory 5257176623 problem with directory contents in inode 5257176623 would have cleared inode 5257176623 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5344999122 no . entry for directory 5344999122 no .. entry for directory 5344999122 problem with directory contents in inode 5344999122 would have cleared inode 5344999122 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5344999148 no . entry for directory 5344999148 no .. entry for directory 5344999148 problem with directory contents in inode 5344999148 would have cleared inode 5344999148 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 5344999158 no . entry for directory 5344999158 no .. entry for directory 5344999158 problem with directory contents in inode 5344999158 would have cleared inode 5344999158 - agno = 3 xfs_repair: read failed: Input/output error cannot read inode 6442451072, disk block 6442451048, cnt 32 does that give any pointers as to what I can attempt in order to fix the broken disks? Quote Link to comment
JorgeB Posted August 27, 2022 Share Posted August 27, 2022 1 minute ago, loungelizard said: As I mentioned initially, all I did was try to rebuild on a new disk, the entire setup has been running flawlessly for over a year so far. It might have been, but it's not now, would not recommended trying to rebuild a disk or fix any filesystem with constant disk errors, there's a chance of making things worse. Quote Link to comment
loungelizard Posted August 27, 2022 Author Share Posted August 27, 2022 1 hour ago, JorgeB said: It might have been, but it's not now, would not recommended trying to rebuild a disk or fix any filesystem with constant disk errors, there's a chance of making things worse. ok understood, it will take me some time to organize. So assuming changing my PSU or cables does not bring any solution, what would be an attempt to bring back the data? I was planning to replace my hardware anyway... So would it be wise to start with a fresh array (knowing the original of my replacement disk may still have issues or corrupt data), plugging in the data drives in the new configuration and just ask to rebuild the parity disk? Question is, what are the right steps to look into in an attempt to save the data on the disks, if the simple changes to the same hardware do not bring any solutions? cheers, Florian Quote Link to comment
trurl Posted August 27, 2022 Share Posted August 27, 2022 On 8/21/2022 at 7:29 PM, trurl said: What is the exact command you used for check filesystem? Never did get an answer to this 28 minutes ago, loungelizard said: save the data Do you have backups of anything important and irreplaceable? Quote Link to comment
loungelizard Posted August 27, 2022 Author Share Posted August 27, 2022 1 hour ago, trurl said: Never did get an answer to this Do you have backups of anything important and irreplaceable? Sorry. Just tried check xfs with the -n option - so not trying any changes. My important data is safe in multiple locations 😂 but if at all possible I would like to retain my other data. It can be reorganized but it's a pain in the ass.. Quote Link to comment
JonathanM Posted August 27, 2022 Share Posted August 27, 2022 27 minutes ago, loungelizard said: Just tried check xfs with the -n option What was the exact command? The /dev portion? Quote Link to comment
trurl Posted August 27, 2022 Share Posted August 27, 2022 38 minutes ago, loungelizard said: Sorry. Just tried check xfs with the -n option That isn't the exact command. There is a reason we asked for the exact command (3 times now) On 8/21/2022 at 4:01 PM, itimpi said: exactly what command did you use? the symptoms are not unusual if you get the command slightly wrong. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.