mikkle

Perfect, thank you Jorge!!

Sorry I should have been more specific. What isn't clear is, can I rebuild both the parity drive and the data drive at the same time? Or do I need to rebuild the parity drive first, and then follow the same process with the data drive? Or vice versa? Thanks again.

Sounds good! This is the first time I've had both a data disk and a parity disk fail at the same time... Just to be safe, what are the steps I should follow in the UI to get the array back to full health?

Thanks, Jorge! I just started the array and here is a new diagnostics attached. eiffel-diagnostics-20240826-0147.zip

Hi, I started copying a large (120 GB) folder from MacOS FInder to a backup share yesterday before going to sleep. I woke up this morning to multiple warnings and alerts in Unraid. Specifically, both Parity 2 and Disk 2 were in error state. (I have a 10 disk array plus two parity drives, or 12 physical drives in total). I noticed on the Dashboard that the first four cores of the server CPU were stuck at 100%. I tried running a SMART short self-test on both drives, but could not get it to run at all. I tried stopping the array, and it took a very long time to unmount the disks (somewhere around 30 minutes or so). When the disks finally unmounted, I shut down the system and subsequently restarted it in order to run the SMART tests. Unfortunately, I did not think to capture the diagnostics before rebooting the server The SMART short test runs without errors on both of the disabled disks. I'm attaching a diagnostics run completed after reboot, even though it might not be helpful. What steps should I follow to get the server back in a healthy state? Thanks! eiffel-diagnostics-20240825-1458.zip

Thanks Jorge, I appreciate your help!

Thanks! Here is the output of the Check Filesystem commands, when run from the WebGUI without the -n parameter. Disk 1: Phase 1 - find and verify superblock... 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. Disk 5: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! 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... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair. I don't understand the specifics, but neither of these sound too promising

Thanks, Jorge! I downgraded to 6.12.4 and just ran the diagnostics again. I've attached them to this post. The syslog looks much cleaner. The same drives are showing as unmountable after the downgrade. Thanks again. diagnostics.zip

Hello! I have an Unraid array consisting of twelve 14 TB drives, driven by an Adaptec ASR-71605 controller in JBOD mode. The array is configured with xfs and 2-drive parity, and a cache pool with two SSDs. I've had this setup for about three years now, and the array is about halfway full. About two months ago, Unraid raised a warning that Disk 1 had a SMART error (UDMA CRC error count > 30) and disabled the drive. At the time things were crazy at work and I was not able to look into the problem, so I left the array with Disk 1 disabled (and its contents emulated via Parity). A few days ago however Unraid started complaining about a second drive due to read errors, and disabled that drive as well. I ran a SMART self-test on this drive (I believe it was Disk 7), and it came back successful with no errors. At this point I tried to fix the array -- probably incorrectly. I stopped the array, unassigned the two drives that had been disabled, and restarted the array. Once the array was back up, I stopped the array one more time, and re-added Disk 7 (which seemed to be healthy). I expected that the array would be re-built from Parity without Disk 1, however the array is now showing three drives with the status: "Unmountable: Unsupported or no file system." When I SSH into the system I can see all my shares, and a cursory look at them shows that most of the files are still there and accessible. I can't say for sure if all the files are there, or if a bunch of them are missing due to the unmountable disks. What is the correct way to get the array back to a healthy state, given the current state of things? Note that I updated Unraid from 6.12.3 to 6.12.6 a week ago. This is significant, because I just noticed today that there is an "Adaptec 7 Series HBA not compatible" known issue mentioned in the release notes. Looking at the attached diagnostics, I see a ton of aacraid warnings such as "Host adapter abort request" or "Outstanding commands." I wonder if this is the source of the above problems, and if I should go ahead and roll back to Unraid 6.12.4 before doing anything else. Thanks in advance for your help! diagnostics.zip

Ran into the same issue today, also on Unraid 6.11.5. I was unable to start up libvirt until I had shut down docker. Once docker was disabled, libvirt started up fine, and I re-enabled docker.

Thank you, it's working great now! I really appreciate your responsiveness.

After poking around a little more, I noticed that there seems to be a problematic symlink: [nobody@81e99f3f013c ~]$ ls -la total 8 drwxr-xr-x 1 nobody users 112 Jul 25 20:00 . drwxrwxr-x 1 nobody users 56 Jul 25 19:59 .. drwxrwxr-x 1 nobody users 30 Jul 20 02:46 .build drwxrwxr-x 1 nobody users 118 Jul 25 20:00 .cache drwxrwxr-x 1 nobody users 54 Jul 25 20:00 .config -rwxrwxr-x 1 nobody users 587 Jul 20 02:49 .gtkrc-2.0 drwxrwxr-x 1 nobody users 40 Jul 20 02:49 .icons drwxrwxrwx 1 nobody users 10 Jul 25 20:00 .local lrwxrwxrwx 1 nobody users 22 Jul 25 19:59 .MakeMKV -> /config/home/.MakeMKV/ drwxrwxr-x 1 nobody users 226 Jul 20 02:49 .themes [nobody@81e99f3f013c ~]$ cd .MakeMKV bash: cd: .MakeMKV: Too many levels of symbolic links [nobody@81e99f3f013c ~]$ cd /config/home/.MakeMKV bash: cd: /config/home/.MakeMKV: Too many levels of symbolic links Deleting this symlink allows me to save preferences in MakeMKV as expected -- that is, until the container is restarted and the symlink gets re-recreated by start.sh.

I don't see anyone who has run into this issue in the thread, so I'm guessing this is something I messed up After installing the container using the default settings, I can access the WebUI and MakeMKV seems to be running correctly. However, I'm unable to save any settings from the Preferences window, or even enter a registration key. MakeMKV throws a "Failed to save settings" error instead. I've also tried to set up the container with PID and GID of 0, with the same results. I don't see anything relevant in the log file. I'm at a loss... any idea what I should try? Thanks.