SKAntoniou

sorry had work, ok so it doesn't crash when I do it on other drives (log below) also some progress, I did -L today and it didn't crash but I think the message at the bottom was because it stopped it for some reason. let me know what to do as don't want it to crash as it is some progress. I don't mind it crashing at the moment if we need to try something else. Thanks for the continued support, this is a very strange situation that I can't find online. Linux 4.19.107-Unraid. root@unBaud:~# xfs_repair -V /dev/md1 xfs_repair version 5.4.0 root@unBaud:~# xfs_repair -v /dev/md1 Phase 1 - find and verify superblock... - block cache size set to 3055776 entries Phase 2 - using internal log - zero log... zero_log: head block 1041894 tail block 1041894 - scan filesystem freespace and inode maps... - 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 - 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 = 1 - agno = 3 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Wed Mar 17 19:09:52 2021 Phase Start End Duration Phase 1: 03/17 19:09:48 03/17 19:09:48 Phase 2: 03/17 19:09:48 03/17 19:09:49 1 second Phase 3: 03/17 19:09:49 03/17 19:09:50 1 second Phase 4: 03/17 19:09:50 03/17 19:09:50 Phase 5: 03/17 19:09:50 03/17 19:09:50 Phase 6: 03/17 19:09:50 03/17 19:09:51 1 second Phase 7: 03/17 19:09:51 03/17 19:09:51 Total run time: 3 seconds done root@unBaud:~# xfs_repair -v /dev/md2 Phase 1 - find and verify superblock... - block cache size set to 3055776 entries Phase 2 - using internal log - zero log... zero_log: head block 769341 tail block 769337 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. root@unBaud:~# xfs_repair -L /dev/md2 Phase 1 - find and verify superblock... 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.

Hey so tried xfs repair, other options crashed at step 1, -L crashed at step 2, this is the log Linux 4.19.107-Unraid. Last login: Tue Mar 16 22:15:11 +0000 2021 on /dev/pts/0. root@unBaud:~# xfs_repair -L /dev/md2 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log...

Also both my cache drives now seem to have CRC error count to 1, one is literally brand new (like few days old) so don't understand that

Thanks but not sure how to do that, on shares, it doesn't show anything. the logs were a bit interesting. There are 2 drives emulated at the moment. 1 has a bunch of errors and the other looks normal which is weird. I have attached the logs so it easier to read. The parity one is the error full one. Disk 1 (Parity Disk 1) Log.rtf Disk 4 (Array Disk Emulated) Log.rtf

Just checked maintenance mode works, what do you suggest I do from here? I did the diagnostics but do you know how to download them?

sadly it freezes instantly when I start the array, I just tried pulling up the console in another tab and doing it but it already froze and I couldn't type anything. it was letting me type right before I started the array. thanks though, anything I can try is useful

thanks, yeh didn't know how to get into the diagnostics. Found logs but no errors would show up on the log. unbaud-diagnostics-20210316-1858.zip

Hey, so my server wasn't working as it crashed and I was trying to troubleshoot it with no luck. As title says, I can only boot into safe mode and can not turn on the array. Never had this issue before. Also 2 of my drives went to being emulated even though the smart system says they passed. I can not replace these drives as I can not start the array. I tried doing memtest+ and ram has no errors. I tried plugging in different sata and power cables and nothing worked. One drive is on the motherboard and the other is connected to a sata card so doubt they would be the problem. I had two parity drives so I haven't lost anything yet but can't get it working. All the drives are less than 2 years old so should really happen. Any advice would be great, thanks.