n0stalghia

I was not aware that parity is real-time, I always assumed it computes it during check. TIL. Well this is great news. On a "fun" side note, I tried to get a list of all data using find . -print > files.txt and the file got corrupted and threw even more mistakes - I took the server offline and already got an RMA procedure running. Thank you for the help.

Can the drive handle one more parity check, or should I power down and replace immediately? I'd lose like 3 TV series, so no big deal (all important data is backed up to the cloud every Monday)

The drive's serial number is WDC_WD80EFAX-68KNBN0_VAGY3XYL - is this one of the 7200 RPM drives that were marketed as 5400 RPM? My parity has a different number, seems to be unaffected.

SMART test is still running, EDIT: Just realized that this message also killed the extended SMART test. Errors occured - Check SMART report. I just got this message about "current pending sector" being 8. I assume nothing good? The drive is 2.17 years old, so should still be under warranty (3 years). EDIT: Added a second SMART report, this one only contains one file for some reason. uxie-smart-20210712-1725.zip

Thanks, the fast test reported no errors, the extended one will be done in 14 hours.

I've got a 2.5 years old 8TB Western Digital that has had three errors today when reading from a sector. This has never happened before. I'm not experienced in this. Is this some small random error? Is the drive dying? It's not been used too much, so this comes as a surprise to me. Are there some tests that I should run on it? Is there a shell script I can execute to try and read from those specific sectors again to confirm that the error is persistent? The disk in question is disk1 in the diagnostics. uxie-diagnostics-20210712-1628.zip

xckd 979 mitigation: I installed an i3-7350K into the machine, and indeed, the slots are working as intended now. It does indeed seem like the chipset/CPU incompatibility was the issue. Thanks for the help Johnnie Black! Wouldn't have solved this without your help.

Hell, it’s running for a year already, fascinating.

Just got another X11SSL-F, still no device working in the two PCIe slots. Processor incompatibility? It’s a Celeron G4920

Should be a real one, here's the Amazon link. Anyway, I tried my WiFi card. When in the PCH x4 slot, this showed up in Tools > System Devices: [168c:002e] 03:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01) When in the CPU x8 slot, this entry was missing. May I assume that the board is faulty at this point or could there be other reasons for this not working?

So, I updated both things to the same version you're using and took the CMOS battery out (the time in the BIOS did reset, so I assume it worked). Unraid still doesn't see HBA/drives. From what I can piece together in Tools > System Devices, the slots are loaded correctly: [8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 08) [8086:1905] 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 08) so I'm not sure where the issue is. Is there some BIOS setting? Maybe something in motherboard's settings (the ones accessible via IMPI?) EDIT: I have a spare PCIe WiFi card from TP-Link, I'll try it in both slots to try and test if the motherboard is faulty

Could you look up the BIOS and LSI firmware versions for your hardware? I agree that it should work, there is no reason for it not to, but I've had this issue since Day 1 of this system (been running with the HBA in PCH slot for a year now because PCI x4 is enough for now, but decided to take another look at the system and try to resolve the issue) The CPU also supports up to 16 lanes (Intel Celeron G4920), so it should be working, but yet it doesn't EDIT: could the be a faulty motherboard, maybe?

My HBA (LSI 9207-8i) is not recognized in some of my PCIe slots. The HBA is connected to two HDDs. The array is working just fine when the HBA is in the PCIe slot PCH - SLOT 5 - PCI-E 3.0 x4 (in x8 slot), but when I put it into any of the other two slots (CPU - SLOT 6 - PCI-E 3.0 x8 (in x16 slot) and CPU - SLOT 7 - PCI-E 3.0 x8), the drives don't show up in unRAID. Motherboard is Supermicro X11SSL-F. Anybody ever had anything similar before? I've went through the BIOS several times and can't find any settings that might affect this... EDIT: Since this is not a unRAID issue, I decided to post it here; please move the topic to the correct forum if this is not the right place.

EDIT: I was able to fix this by running a Tools > New Permissions job on the share. This topic can be considered resolved. Hi, I am unable to modify/delete a single folder from within my share because of the permission error I specified in the post title. Upon further inspection, it looks like this folder, unlike others in the same directory, has a user "nobody (TOWER\nobody)" with Full control of this folder, whereas my standard user nost (part of "users (Unix Group\users)") only has Read & execute permissions.) In other folders my nost user has Full Control of the folders, not just Read & execute. I need to gain access of this folder back to modify/delete it as I see fit. The only anomaly that I can see that makes this folder different from others (which I still have full control of) is presence of a "desktop.ini" file with following contents: I have no idea what program created this file. Things I've tried: * Rebooting Windows/reconnecting the share in Windows Explorer * Rebooting the server and restarting the array * changing the username of my unRAID share user to not match the username of my windows user and re-connecting to the drive using the new credentials * trying to delete the folder from another operating system (macOS)

Resolved for me as well