tillo

Ow, well that explains it... Strange that no other computer turned off at that time. But awesome help! What file did you find that information in?

Hi, as the text describes I just did a sync and it gave me 3812 errors. I don't know what to do at this point. See diagnostic file

How meany would be an "okey" number of allocated blocks?

Downloaded the S.M.A.R.T. data after running a check on the drive. nano-smart-20180424-0747.zip

Hi, I just got this message. (reallocated sector ct is 1) I understand the message, the question I am asking myself is: how sever is it, and should I be concerned? Should I take any action? It is from my cache disk.

@unevent Thanx for the reply. I switched to Mode 0 (balanced-rr), I did not see any performance gain, I am using windows 8 with a 10gbit connection, and I am transferring between two ssd drives (unraid Cash disk). I have confirmed that the Windows machine is capable to do transfers of upp to almost 4gbit to my ISCSi server that have a LAG of 4x1gbit nics. Might I be missing any setting within unraid and balanced-RR that I should configure?

Hi, I am using Unraid setup with dual nic in the following configuration (see image below). It looks like I am only able to achieve 1 gbit per file transfer. I wanna achieve 2 gbit. Switch is set up to accept LACP from the unraid server.

I am running 6.5.0 Stable, is that also affected ?

* mover runs every day. * I will look into the minimum space settings. * How do I disable mover logging?

No. Array is: XFS Cash is: btrfs

Hi, my SHFS uses up to 100% all of the time. What do I do?

Okey, I will do that, thanx for now. Many thanx to you Johnnie and trurl for all the help. Lets hope that everything works now :-D If not you will soon know

Okey, I did it one more time "xfs_repair -n /dev/md1 && echo ${PIPESTATUS[0]}". this returned the exit code 0 (Se printout above) Is it anything else I should look into. Or should I re-run the parity check, and accept all the error (for this time).And then continue as normal, if no more errors occur after that?

When I did it from within unraids webGUI according to the instructions provided by @trurl, I get this output for disk 1.

@johnnie.black My bad, I tried, but since I recived an error that I could not run on that device, I googled and it sugested that I would do it with "sde1". So I just asume that that was the correct way to do it :-p I will put unraid in maintenance mode and give it a try within an hour, and we will see if that gives an other result. Just to confirm: have i in anyway damaged the file-system by running xfs_repair on sde1 (note, sde1 is Data Disk 1)

@trurl Okey, when running sudo xfs_repair -n /dev/md1 I get an error that the disk is mounted and not accessible? How should I proceed in order to do an xfs_repair correctly?

Okey, So should I re-run the parity check, and accept all the error (for this time). And then continue as normal, if no more errors occur after that? or should I continue to investigate the motherboard, CPU and PSU?

I could run it without -n but in any case it showed a exit code of 0 and that would indicate no errors? 0=no corruption detected ? Would it be a different if I run it without the -n flag?

This is the output that I get.

It's frequently difficult to identify if there are filesystem issues or not by only looking at the output of xfs_repair, you either need to check the exit code after running with -n (1=corruption detected, 0=no corruption detected) or just run it without -n (no modify flag) so any issues found are repaired. So I should run an "xfs_repair -n" or an "xfs_repair". Just to confirm, non of them will with the -n flag, or no flag at all, change the files of my system ("non correcting/altering checks") Is this correct? Could I run the test from the web terminal from unraid? I have currently started the array and I am running a parity sync (without writing any corrections, just to get an ide on how extensive the errors are) I will upload the diagnostic file when it is done. The NMI errors can be caused by PSU or board, but hard to confirm unless you have spares, board especially, maybe you can test with a PSU from another system, also, if you havn't yet check the system event log, there might be some clues there. I got a spare board, and a spare PSU. The PSU is a Seasonic PRIME ULTRA TITANIUM. I rather not pull the board or PSU out at this point. I will let it run for a few days and then check the log file.

Okey, I have done a complete teardown of the server. 1* I ran "xfs_repair -nv" Disk1, it did not show any faults or errors. 2* I ran memtest on the RAM memtest86 7.5 version, it showed no errors except on Test 10 (Fade test). Reading about that test in different forums threads, a few error during that test seemed to be normal depending on firmware and motherboard. 3* I checked the cables, they are all good (Original Super Micro cables with a built in lock feature) 4* I am total at a loss currently. What would be the next step?

Okey, could the first one be related to the new RAM modules I installed? The other problem, Corrupt data on Disk 1. what should I do ith that, Unmount and run xfs_repair? Should I replace it? replace cables?

I have: 316785 errors during the sync. Is that amount expected after an unclean shutdown? Also, minimum spacing setting, how would that affect the share cash?

@johnnie.black Logfile. Today, I got a whole ton of sync errors! (It is still running the syn, and had made it about 50% when I downloaded the diagnostic file

I started a new thread regarding the Parity errors and checksum errors. I will keep this thread updated with more information about the problems with the of memory errors, after that I have installed additional modules of ram into the server.