TigerStorms

It didn't, last night I attempted to stop the array and was unable to. Whatever corrupted files that came over from the old drive was clearly causing the whole thing to not work right. So this morning I flashed the USB after backup up what I had, copied over the key and changed nothing. At this time I know the parity's already been rebuilt with the drives in a certain order so I know parity is valid and just started off fresh with nothing but the key carried over from the last install. I did have to reinstall my Apps but my Docker and VM were unaffected. I took screenshots of ever page I could that was working to make sure all settings could be restored quickly. making sure to select the shares to their respective drives so far I don't seem to be running in to any of the old issues after doing this. but the next parity check might change that.

okay, I've deleted my flash.cfg because it's completely unreadable in nodepad++ so whatever is in there is lost already. While also adding the "&" to the end of my 'go' file because that's not in the default one #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp is how it looks from the unRAIDServer-6.12.10-x86_64 files I get from unraid. my CPU/RAM aren't getting maxed out like some of the other's were having and my log under the dashboard doesn't get higher than 2%. tower-diagnostics-20240525-1032.zip

Yes, the issues are still present. I have no pending app installs but I read up on this before posting and I'm not seeing any weirdness on my monitor script. I haven't changed moving the log to the ram yet but for the moment I'm not too worried about that. I've personally made no changes to any kind to any scripts in the system other than what might happen with apps that have been installed. But this only happened after the update with the same apps from before, The only thing I haven't tried is starting off completely fresh install on my system. Also I haven't messed around with coding in years so I honestly wouldn't know how to make many of these changes they are talking about with some how messing up the system more. Is there a way to get working versions of the files? I'm less worried about the log spamming as I am about the fact I cannot see any data about anything on my WebUI about my drives.

I've rebooted and here are the updated diags afterwards. tower-diagnostics-20240524-2321.zip

I have already deleted it, i can reboot it later tonight in my maintenance window. it does seem to also spam this error, "May 24 08:53:01 Tower crond[1546]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null" every minute as well.

Hello, I've recently recovered from a USB failure while doing an upgrade to Unraid. This was going from 6.12.6 to 6.12.10. I didn't have a copy of where the drives were located so I rebuilt parity because I also didn't have any backups of my flash that were recent. After it finished rebuilding parity, the drives no longer show up in the web UI and I keep getting a notification every minute that the two Parity disks "Have returned to normal operation". I had to move from an old USB drive to a new one was able to copy the key over sadly it seems some of the files were corrupted. After I got the online back up working I tried to restore from it and the issues still persist. I'm assuming it must have backed up the corrupted files. Below are the notifications I get. Below them what I see in the webUI. The server appears to be running normally otherwise. Lastly, I ran Common Problems and it says the flash.cfg is corrupted, I'm not sure how to go about fixing that at this moment since the forum post tells me to ask for help here. tower-diagnostics-20240524-1035.zip

ahhhh, that's a bummer. thank you for your help.

Hello there, I feel kind of dumb but I'm at my wits ends here on trying to install 3 new hard drives to my array. The three drives are Seagate 16TB HDD Exos hard drives model ST16000NM001G. before replacing one of my array drives that was failing I started with upgrading one of my 2 parity drives. After the rebuild I've attempted to swap/add the other two and I keep getting the error "the parity drive must be the largest". However all drives are the same size and same byte count according to the system. Is there a way to format the drives or trick unraid/linux in to thinking these two are even 100mb smaller so i can use them? The only info I find online is "just use the bigger drive" which clearly when one is formatted as parity it becomes smaller somehow to the system and refuses to let me load the others. Any help is appreciated. tower-diagnostics-20220502-0653.zip