Morning all,

 

I started a parity check as i went to bed last night (my first one on a new server)

 

the parity HDD is an 8tb seagate ironwolf.

2x 4TB seagate ironwolf array drives

 

server is a HP Proliant DL165

AMD Opteron™ 6212 @ 2600 MHz

24GiB DDR3

 

below is the status

 

8 TB

Elapsed time: 8 hours, 17 minutes

Current position: 2.42 TB (30.3 %)

Estimated speed: 90.3 MB/sec

Estimated finish: 17 hours, 9 minutes

Sync errors corrected: 0

 

is this very slow, or is this about right?.

Do i have to change a setting somewhere to speed this up?

Or is it just this long because its the first check and its a lot of new data to go through? 

 

apologies for all the questions, I'm new to Unraid and just trying to learn

3 hours ago, Barnoe said:

is this very slow, or is this about right?.

Looks about right, it will speed up once it finish reading the 4TB disks, disks are always much faster on the outer tracks and slow down as they go through the inner tracks.

Ahh ok, thats good then

The wife has text me from home and said the server is beeping??
Ive logged into it from work and checked the log.

 

not sure if this is why its beeping .....
Apr 10 17:48:50 Titan nginx: 2022/04/10 17:48:50 [error] 3911#3911: *295335 connect() to unix:/var/tmp/flaresolverr.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.102, server: , request: "GET /dockerterminal/flaresolverr/token HTTP/1.1", upstream: "http://unix:/var/tmp/flaresolverr.sock:/token", host: "192.168.1.200", referrer: "http://192.168.1.200/dockerterminal/flaresolverr/"

 

I installed the flaresolverr app to go with prowlerr but not set it up yet... looks like its not happy so i have stopped the docker for now.

 

also need to sort the time out on the log, as its obviously the wrong time its 11am?

45 minutes ago, Barnoe said:

the server is beeping??

That's not Unraid, possibly some hardware issue like overtemp or a failed fan.

 

45 minutes ago, Barnoe said:

also need to sort the time out on the log

Settings -> Date and Time: set correct timezone.

Thanks Jorge, you was correct with it speeding up after 4tb

 

Current position: 4.03 TB (50.4 %)

Estimated speed: 196.7 MB/sec

 

temps parity drive is 28c while others are 20 and 21c

when i tried to log in from work initially i entered the wrong password....twice!

would that cause a beep?

i will test that theory when i get home in 4 hrs

 

 

21 minutes ago, Barnoe said:

would that cause a beep?

nope.