wgstarks

Yes. It’s why some people use this plugin for stress testing new drives.

With parity protected data everything will involve writes to parity.

Thanks. I ran the test in safe mode with SMB/AFP disabled. Also disabled syslog server. Set mover to run monthly since there is no “disabled” setting for it. Not sure how to eliminate any other internal processes that might be running. Dont have any expanders not shown in the report. The Dell H310 SAS controller is installed in an X8 slot so I don’t think that is limiting speed although it may be that the H310 is slow as you say. I haven’t seen any reports of this though. Same thing is true for the SuperMicro X10SLL-F motherboard. I’ll give Diskspeed a shot, but if it’s really just slow components I don’t think any amount of tweaking will change that.

@Pauven Any thoughts on this test? XtraLongSyncTestReport_2019_08_15_1841.txt.zip

Had the same version in mine. Tested and it works though if you want to add this to your initial post.

I wondered the same thing. Was thinking I would look and see what version nerdpack is installing once the test is finished and I can boot back into the normal mode.

I don’t still have the exact output, but it appeared to install without any errors and opened a brief summary of what screen does. After I got the error when trying to launch screen I attempted the install again but got a message that screen was already installed.

Yeah. Not really a big deal. The issues with screen are possibly more important. I just gave up on it and ran the script from console, but I’m sure there are quite a few users running headless systems that would benefit from it, if it can be made to work in safe mode. Or maybe this problem was unique to my system. Has anyone else tried to actually install and run screen in safe mode?

This is what I am getting- unRAID Server: Notice [BRUNNHILDE] - Parity check started Event: Unraid Parity check Subject: Notice [BRUNNHILDE] - Parity check started Description: Size: 8 TB Importance: warning

The “block” option also doesn’t seem to work. I got one parity check started notification about 30 minutes after starting this script and then a second one maybe 10 hours later. Perhaps I’m misunderstanding how this option works?

Still doesn't work though. root@Brunnhilde:/boot/scripts/utt# screen -bash: /usr/bin/screen: No such file or directory

Confirmed

This doesn't work- root@Brunnhilde:/boot/scripts/utt# wget https://packages.slackware.com/?r=slackware-current&p=screen-4.6.2-i586-2.txz [1] 3581 root@Brunnhilde:/boot/scripts/utt# Redirecting output to ‘wget-log’. upgradepkg --install-new screen-4.6.2-i586-2.txz Cannot install screen-4.6.2-i586-2.txz: file not found [1]+ Exit 3 wget https://packages.slackware.com/?r=slackware-current root@Brunnhilde:/boot/scripts/utt# Looks like the txz file doesn't get downloaded so the upgradepkg fails.

Did you actually configure the fans in settings?

What about other computers that access the network shares?

I started a new test today with 4.1. Rebooted my server into safe mode as was recommended. When I started the script I got a notice that I should be running screen, but in safe mode nerdpack plugin is disabled so screen isn’t available. How are people running screen in safe mode?

You’ll need to modify the commands to the version you download.

Backup your flash (just in case). Download 6.7.7. Unpack the zip. Replace the bz files and syslinux on your flash with the ones in the downloaded folder. Reboot. Sorry, typo 6.7.7 should have been 6.6.7.

Have you tried just manually adding the file to appdata and restarting the docker.

Right. Developers beta currently. Not unusual for Apple to impose special restrictions/limitations for these.

6.6.7 is still available. https://unraid.net/download

LT has been investigating this issue. Many people in the thread I linked have been downgrading unRAID as a work around until the cause of the problem is determined.

Thanks again.

If you search CA you should find glass ISC DHCP server. Never used it so cant make any recommendations, but it’s there if you want to try it.

Thanks. After my previous post I was doing a little reading about .bash_profile vs .bashrc. Just want to confirm that the aliases need to be added to .bash_profile to work in the built in terminal window?