lime111

Thank you @JorgeB I removed the CPU heatsink, fully cleaned and reseated it with good quality paste and it seems to be working again. So appeared to be CPU overheating which makes sense. thanks again.

Hi, my server (6.9.2) is just turning itself off randomly, i'm really not sure how to troubleshoot why. It's an old rig by now but has been rock solid for so long. I had a spare power supply so i replaced that, so it's not the PSU causing the issues. Any assistance is greatly appreciated. PS yes noted disk 1 has read errors ill replace it once i know i can rely on the rig to stay up for long enough to write. all diagnostics files copied below. Thanks in advance. disk.cfg docker.cfg domain.cfg flash.cfg go.txt ident.cfg network.cfg c---e.cfg share.cfg smart-one.cfg super.dat syslog.txt appdata.cfg B----p.cfg D---------y.cfg d-t.cfg K--s.cfg M---------s.cfg M----s.cfg M---c.cfg T------s.cfg W------------------t.cfg Z-------------a.cfg Samsung_SSD_850_EVO_500GB_S2R9NX0H506978H-20220916-2205 cache (sdh).txt SanDisk_Cruzer_200625850209CAF3943F-0-0-20220916-2205 flash (sda).txt ST4000DM000-1F2168_Z300R2VS-20220916-2205 disk6 (sdg).txt ST4000VN008-2DR166_ZDH3S4Y0-20220916-2205 disk5 (sdf).txt ST8000VN0022-2EL112_ZA1CQJ46-20220916-2205 parity (sdd).txt WDC_WD40EFRX-68WT0N0_WD-WCC4E1651276-20220916-2205 disk3 (sdi).txt WDC_WD40EFRX-68WT0N0_WD-WCC4E2RTL03P-20220916-2205 disk4 (sde).txt WDC_WD40EFRX-68WT0N0_WD-WCC4E5JNKN2D-20220916-2205 disk1 (sdc).txt WDC_WD60EZRZ-00GZ5B1_WD-WX31D97ADZ6C-20220916-2205 disk2 (sdb).txt btrfs-usage.txt cmdline.txt df.txt ethtool.txt folders.txt ifconfig.txt loads.txt lscpu.txt lsmod.txt lsof.txt lspci.txt lsscsi.txt lsusb.txt meminfo.txt memory.txt motherboard.txt plugins.txt ps.txt top.txt vars.txt unraid-6.9.2.txt

Hi there, fix common problems told me i have an out of memory error and recommended i post my rig's diagnostics here. So here I am, diagnostics attached, thanks in advance. tower-diagnostics-20190408-1230.zip

Replaced failing drive and put in new SATA cable for cachce, array has returned to its old fine form, thanks again for helping out.

Thanks guys, ill sort out a new drive and new cable. It hasn't been a cheap month for my tower....

Thanks @testdasi I have bought a new SATA card, startechcom PEXSAT34RH , and managed to rebuild disk 6 and the array has started. So I do believe the problem was the sata port on the MB. However I now cannot start docker, or even upgrade any plugins. I've deleted the docker image in case it got corrupted, but that didn't make a difference and the array just takes forever to start services, and I think eventually it just times out. Thoughts...? Log attached, thanks... tower-diagnostics-20180903-0755.zip

Hi Guys, it's been a long time since i've had a reason to post. In the past my 6th sata port on my MB had a brand new WD red die very soon after I bought it, it seemed odd at the time. I decided not to use that port and bought a SATA expansion card as I needed extra expansion space for a cache. Just recently I have needed to expand my array, and my twin sata expansion card was full. I upgraded my existing, working, parity with a new 8tb, and put the previous parity into sata port 6. It initially worked, but then had multiple crc errors pretty soon afterwards. I've checked the server today and the disk in sata port 6 is disabled and being emulated. I've replaced the cable, no change. I'm now not even sure the disk is truly dead. Given multiple drives have failed on this one port, i can think it could only be the sata port, or the power into it, or am i missing something? It's a bit annoying that I can lose another working 4TB drive, and i have absolutely no idea as to why/what is happening. The only other variance with the array is disk 6 is formatted xfs, and every other disk is reiserfs. I normally don't go first to hardware faults, but this time i think it might actually be the case. I'm reluctant to buy another 4tb and would prefer to maybe buy a 4 port expansion card and never use sata port 6 again Any input or advice appreciated. tower-diagnostics-20180828-1940.zip

@trurl, many thanks, ill double check tonight. When I see this much red in my syslog (picture attached) I get a bit concerned.

Ok, parity finished ok and in the same time it usually does. I still have concerns that there is something other a disk 2 error. Updated syslog with a few extra errors and showing parity was completed. Any thoughts on whether I have anything to worry about much appreciated. Thanks tower-syslog-20160901-1112.zip

Hi, i've recently upgraded from a rock solid for years v5 to v6, and am having some dramas. It's been years since i've had to post here. I see a lot of red lines in my latest log and believe my disk2 needs to be rebuilt. I'm concerned it might be more than that and don't want to start a rebuild only to find a gremlin means my array is not protected. Some background on recent changes. Previously running v5, which was running 24/7 just fine. System is ASRock 880GM-LE FX, Athlon II X2 250, 4GB corsair RAM. HVM Enabled IOMMU Disabled. Running unraid 6.1.9. My last successful parity was August 25. On August 30 I ran a parity which normally takes 12 hours, this check was still going 24 hours later showing 21 days to complete. This check was cancelled and I ran a new parity after reboot last night, under 2 hours to go, fingers crossed, and disk 2 was spun down. I had a PCIe expansion card with an SSD for cache (no cache or card under v5 build). This was working, but every now and again the server would turn itself off. This expansion card and SSD has now been removed as I troubleshoot and may be subject of further help topic. Basically the SSD was no longer visibile as a drive just prior to these problems, i think problems were due to the PCIe card but then this popped up which I want to solve first. Mentioned for completeness. Disk 5 recently failed, it was replaced with a brand new WD RED 4TB, which failed within 2 months. This was was rebuilt. I know this happens, but odd for a WD RED to fail so early, Mentioned for completeness. I have recently rebuilt disk 1, it was getting very old, old age/prefail reports, rebuilt with WD Red no problems. Plugins are Powerdown Package/Fix Common Problems/Community Apps/Dynamix Cache Directories, all but the last were installed after problems occurred. All Dockers are on the cache drive which mentioned above I have removed from the system. SMART report on disk 2 shows it passes but subject to old age/prefail, but logs show a lot of disk 2 read errors, as well as other errors I don't understand. I'm RMA'ing the failed WD Red today, so can rebuild disk 2 after work if that is the real problem. As mentioned I believe from my reading of the logs disk 2 should be rebuilt, but if it is more than that I won't like to put the array at risk. Many thanks for having a quick look for me! tower-diagnostics-20160901-0543.zip

This is not of immediate help, but if the disks are both bad, i would return them to where you got them for a refund or replacement, depending on the consumer protection rules on where you live of course. I use crystaldiskinfo (and even provided its reports as proof of disk failure) to substantiate the failure to the retailer. I've done this on disks less than 12 months old successfully.

Again, thanks to everyone that helped, the array parity checked fine, i reactivated plugins and the user shares are working.

So far the Parity Sync appears successful, and with all green dots, I now have a parity check underway. Oddly, this new disk 3 doesn't seem to have populated my user share folder structure, and when trying to copy a file across (under the user share) limits it doesn't default to this disk as it should under the high water setting. Is this a bug, should i just recreate the folder structure manually? Thanks again, I think i am nearly there.

@DaleWilliams & @garycase Firstly I am most grateful for your assistances. Where I am at is that I disabled all plugins, checked the new drive size versus the parity (it was the same), checked the BIOS (read further comments below), and put the old disk 3 into my main PC and copied its contents to an external harddrive for double protection. Then I ran with @garycase's suggestion of a new config, and rebuilding parity, and i have all green dots except for parity which is now yellow, and it tells me parity is being rebuilt. Assuming parity is rebuilt I will copy over the contents of old disk 3 back on to the array. further comments For the sake of completeness on the forums, and for the fact and in particular the comments around my plugins, i only run 4 plugins, all of which i have taken from the forums here. 1. Playstation Media Server, which is the go script query that came up more than once. This is taken straight from this link, http://lime-technology.com/wiki/index.php/PS3_Media_Server and has always worked great. I don't really need it these days, but in the past it was really helpful. 2. Cache directories 3. Sickbeard + SABNZBD+. these really bring my NAS to life, and are installed on disc 5. Funnily enough, this is the disc that @dalewilliams indicated looked funny and took ages to mount, which was always my experience and I had always attributed to thes two plugins. These plugins *might* have caused the issue, or alternatively, when reviewing the BIOS, the "sata operation mode" for all disks was set to IDE, not AHCI. I didn't change anything because everything has been working fine and I believe in the rule that if it isn't broken, don't try and fix it. These comments only added for completeness. I will update this thread once more information is available. Thanks again community - I hope you are enjoying your weekend!

Currently copying data from old disk 3 to an external hard drive. Would be grateful for some guidance from ppl that might have had this sort of thing before. Does anyone think replacing the flash drive might be of use? Anyone know of a way to ignore the new parity drive setting so i can rebuild my disk 3? If i can't find a solution and disk 3 is backed up I might just have to roll the dice and click run parity check.