apool

Yes, also happens to me, can't login to the admin dashboard. I don't think there's an easy fix...

Absolute hero! Thanks

Well, I haven't had any luck with these. I had a SATA to DC adapter lying around, connected it to a faulty drive and started a parity check, also gave write errors at the end of the check. What's surprising to me is that I can add these drives as data devices and it'll eat it up with no complaints: I've purchased another 12TB one, different brand, and I'll use that one as parity, but it's really strange what happened with these drives

Hi OP, did you solve this? Having the same errors

I know, but the errors only pop up at the end of the check.

Yes, I changed everything. The only thing I haven't changed is the PSU. I have some DC to SATA converters, I'll power the disks with that and I'll report back... Is there any way to check the error without having to do a full parity-check? It takes 18 to 20 hours to complete

Fuck I don't have any SATA controller... Thanks for the answer though.

Officially no clue as to why this is happening, parity sync finishes with 168 errors on both disks. In the logs it says: "ANAS kernel: md: disk0 write error, sector=23437500872" a bunch of times. Does that mean BOTH drives are officially dead? I even changed SATA data cables, now I truly ran out of options! Is there anything I could do? anas-diagnostics-20251008-2212.zip Pinging @JorgeB

Hey xokia, did you solve your issue? I'm experiencing the same as you, I don't have any expansion card attached, I have two Seagate Exos x16 that are also failing parity and being disabled. Please answer, I don't know what else to do, besides purchasing an expansion card!!

Same result with the other disk, it's very strange that only happens with these disks, isn't it? I can't believe it, I think it also didn't pick up the messages for when the parity-sync finished, it was on 6th October at around 23:30, I went to sleep thinking it'd pick it up. Attaching the new diags just to be sure What else can I do? anas-diagnostics-20251007-0816.zip

Looks like it was on 3rd/4th, but the logs didn't pick it up. I'm finishing another parity-sync in around two hours, will post the results...

Yes, it was a parity sync, my fault. Now doing another one with the other disk...

Forgot to mention I'm on 6.12.9, should I update? I don't wanna break more things to be honest...

Already did that, ordered some official cables for my PSU just in case the ones I was using were bad but nothing changed. It's also very strange that BOTH disks present this error, I reseated the cables several times already...

@JorgeB Pinging you for this update. New official cables arrived, did a parity-check and still the parity device is disabled... I really don't know what else to do, the return window for these drives is over and I can't use them. Do I have to do anything else in order to use these devices? Do I have to do a New Config for this? There are 168 errors on the parity disk, is that something I should be worried about? I'm attaching new diags :( anas-diagnostics-20251005-1255.zip

Hi @JorgeB sorry to bother, ordered two new sata power cables, they still haven't arrived but I'll make sure to change them. In the meantime, I checked both drives and tried to build parity on both of them, to no avail. One of them even threw some write errors: Sep 24 17:10:53 ANAS kernel: ata2.00: error: { ABRT } Sep 24 17:10:54 ANAS kernel: I/O error, dev sdc, sector 3904 op 0x1:(WRITE) flags 0x0 phys_seg 32 prio class 2 Sep 24 17:10:54 ANAS kernel: md: disk0 write error, sector=3840Is it a bad drive? Maybe it's the PSU? I'm attaching again the diagnostics, can you tell me where do you look? diagnostics.zip

Hm... That's strange. Will do and report back.

Hi guys, straight to the point: I purchased two used 12TB drives and wanted to replace my 6TB ones with those. I plugged in one of those, let it build parity alongside the other, but when it finished it said "Parity drive is disabled", I naively thought it was because it was executing an extended SMART test, so I cancelled it and followed some advice on this sub: - First I precleared the drive, then let it rebuild parity again, same result. - Stopped array, set parity to "no device", then started array in maintenance mode, stopped it again and reassigned the drive to parity, start and let it build parity, same result - Checked psu and sata cables, nothing wrong with them - Now I'm preclearing the other drive just to check if there's something wrong with them I'm attaching the extended SMART test and diagnostics, if someone could help me I'd appreciate it. anas-diagnostics-and-SMART.zip

True, reduced it to 2GB, turned off any memory hungry docker containers and now it started. Guess I'll have to buy (or download) more RAM

Hi everyone, so I tried to emulate my first W10 VM in my server, but I can't seem to achieve it, the VM starts but is then killed by the OS: ANAS kernel: Out of memory: Killed process 1356 (qemu-system-x86) total-vm:4590632kB, anon-rss:1838268kB, file-rss:0kB, shmem-rss:6552kB, UID:0 pgtables:4024kB oom_score_adj:0 My system info: M/B: Micro-Star International Co., Ltd. H510I PRO WIFI (MS-7D16) Version 1.0 s/n 07D1610_L21D104832 BIOS: American Megatrends International, LLC. Version 1.80 Dated 06/07/2023 CPU: 11th Gen Intel® Core™ i5-11400 @ 2.60GHz HVM:Enabled IOMMU:Disabled Cache: L1 Cache: 288 KiB, L1 Cache: 192 KiB, L2 Cache: 3 MiB, L3 Cache: 12 MiB Memory: 8 GiB DDR4 (max. installable capacity 64 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 Kernel: Linux 6.1.82-Unraid x86_64 If I kill any docker apps using a lot of RAM (i.e. Valheim server), Unraid will crash and I have to manually power cycle the machine... Is there anything I can do? Thanks for your help anas-diagnostics-20240707-2220.zip

Been having the same exact issues as OP, random total freezes and having to manually power cycle (even have to take the power cord out as sometimes even a forced shutdown wouldn't restart the pc properly). Had already the option of exclusive shares enabled, and still keeps happening. I'm trying to figure out how to switch all the containers to use /mnt/cache/appdata but I don't know how to do it, as some of them have an "appdata" field I can change but other have not. Is there any setting to change that globally? If anyone could help I'd be eternally grateful. Anybody would care to explain how why that change? If enabling exclusive shares, shares become symlinks so /mnt/cache/appdata and /mnt/user/appdata are the same thing right? I'm sorry if this is too basic but I don't have much expertise in this

So yeah, I have gotten ahold of another cpu + mobo that could support it and Unraid is running fine as of now, so I think I may have a bad CPU

Tried a different RAM stick, no changes. I do have a spare mobo and CPU, I'll try with that and report back. EDIT: CPU is 11th gen and my mobos only support 10th gen, I'm out of options. No one can help me here?

I do not have a spare stick, I could get one from my PC though. Will try in a few hours

Done that already, ran for 6 hours, no errors, had to stop it. I'll update #1