Tag Archives: delay

Barracuda Green ST2000DL003

http://www.seagate.com/files/staticfiles/support/docs/manual/desktop/Barracuda%20Green/100649225c.pdf

Reformatted a bit to fit on page.

I have 6 of these (2TB) in each NAS Raid5 setup plus motherboard, AMD cpus, RAM etc.
This page is for researching a replacement PSU.

2.8.1 Power consumption
Power requirements for the drives are listed in Table 2 on page 15. Typical power measurements are based on an average of drives tested, under nominal conditions, using 5.0V and 12.0V input voltage at 25°C ambient temperature.

• Spinup power Spinup power is measured from the time of power-on to the time that the drive spindle reaches operating speed.

• Read/write power and current
Read/write power is measured with the heads on track, based on a 16-sector write followed by a 32-ms delay, then a 16-sector read followed by a 32-ms delay.

• Operating power and current
Operating power is measured using 40 percent random seeks, 40 percent read/write mode (1 write for each 10
reads) and 20 percent drive idle mode.

• Idle mode power
Idle mode power is measured with the drive up to speed, with servo electronics active and with the heads in a random track location.

• Standby mode
During Standby mode, the drive accepts commands, but the drive is not spinning, and the servo and read/write electronics are in power-down mode.

Table 2 DC power requirements
Avg (watts 25°C) Avg 5V typ amps Avg 12V typ amps
Spinup — — 2.1
Idle* † 4.5 0.151 0.303
Operating 5.8 0.440 0.300
Standby 0.50 0.085 0.01
Sleep 0.50 0.085 0.01

Avg (watts 25°C) Avg 5V typ amps Avg 12V typ amps
Spinup 2.1
Idle* † 4.5 0.151 0.303
Operating 5.8 0.440 0.300
Standby 0.50 0.085 0.01
Sleep 0.50 0.085 0.01

*During periods of drive idle, some offline activity may occur according to the S.M.A.R.T. specification, which may increase acoustic and power to operational levels.
†5W IDLE, Standby and Sleep,with DIPLM Enabled

Pi GPPS Clocks

Use Chris’ PPS kernel (until I have time or am compelled to compile my own).

Compile ntp 4.2.6p5 as follows (from aquarat):
But first: apt-get install libcap-dev

./configure --enable-ATOM --enable-NMEA --enable-linuxcaps; make; make install

Disable TTY on /dev/AMA0 in /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait

Set baud rate in /boot/config.txt
init_uart_baud=9600

and
Disable GPU sdram pause
# Disable GPU sdram mem pause
disable_pvt=1

Comment out getty in /etc/inittab:

#Spawn a getty on Raspberry Pi serial line
#T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100

Add pps-gpio to /etc/modules

Disable all but $GPRMC sentences (in rc.local in my case since I have no battery):

/bin/echo -e '$PMTK314,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0*29\r\n' > /dev/ttyAMA0
/etc/init.d/ntp restart

vi /etc/udev/rules.d/09.pps.rules

KERNEL=="ttyAMA0", SYMLINK+="gps0"
KERNEL=="pps0", OWNER="root", GROUP="tty", MODE="0777", SYMLINK+="gpspps0"

Be sure to restart ntp after reducing sentence output. Mine started drifting negative when I didn’t restart.

Here is my ntp.conf.
Some will argue about whether using stratum 1 sanity servers is necessary, noselect, on and on, yada yada.
This works for me and gets me pretty good stability.

I think the numbers speak for themselves. Bear in mind that I will have 2 different GPS clocks in the near future so I am less inclined to sync to an outside source. I keep some of the better known S1 clocks in there purely for my peace of mind. I’m part of the ntppool so I do not use them to sync in the event of a GPS failure. Again, opinions vary.

GPS1:
remote refid st t when poll reach delay offset jitter
==============================================================================
+tick.usno.navy. .IRIG. 1 u 28 64 377 63.014 -0.940 6.541
+ntp.okstate.edu .USNO. 1 u 23 64 377 49.207 -0.392 0.185
-navobs1.wustl.e .GPS. 1 u 14 64 377 49.768 -3.915 0.237
-tick.uh.edu .GPS. 1 u 16 64 377 56.676 5.286 0.388
oGPS_NMEA(0) .GPS1. 0 l 5 8 377 0.000 0.017 0.003
+hcpi002.lan.sid .GPS2. 1 u 8 64 377 0.850 0.157 0.126

GPS2:
remote refid st t when poll reach delay offset jitter
==============================================================================
+tick.usno.navy. .IRIG. 1 u 13 64 377 63.536 -0.624 0.249
+ntp.okstate.edu .USNO. 1 u 16 64 377 49.068 -0.524 0.161
-navobs1.wustl.e .GPS. 1 u 15 64 377 50.469 -4.109 0.163
-tick.uh.edu .GPS. 1 u 5 64 377 56.892 4.870 0.387
oGPS_NMEA(0) .GPS2. 0 l 2 8 377 0.000 -0.100 0.008
+hcpi001.lan.sid .GPS1. 1 u 13 64 377 0.809 -0.358 0.168

Note that the GPSes are still slewing since ntpd was recently restarted.

GPS1 ntp.conf:
driftfile /var/log/ntpstats/ntp.drift
statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

# Sanity Servers
server tick.usno.navy.mil iburst
server ntp.okstate.edu iburst
server navobs1.wustl.edu iburst
server tick.uh.edu iburst

restrict default nomodify noquery
restrict 127.0.0.1
restrict 10.1.1.0 mask 255.255.255.0 nomodify

server 127.127.20.0 mode 17 minpoll 3 prefer #use $GPRMC only!
fudge 127.127.20.0 flag1 1 time2 0.350 refid GPS1

peer gps2.lan.side

GPS2 ntp.conf:
driftfile /var/log/ntpstats/ntp.drift
statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

# Sanity Servers
server tick.usno.navy.mil iburst
server ntp.okstate.edu iburst
server navobs1.wustl.edu iburst
server tick.uh.edu iburst

restrict default nomodify noquery
restrict 127.0.0.1
restrict 10.1.1.0 mask 255.255.255.0 nomodify

server 127.127.20.0 mode 17 minpoll 3 prefer #use $GPRMC only!
fudge 127.127.20.0 flag1 1 time2 0.350 refid GPS2

peer gps1.lan.side

FreeNAS Debian UPS Specs

Initially the UPS was being monitored by a FreeNAS installation, this was changed due to performance issues unrelated to the UPS monitoring software. Details on the migration are still being compiled, meanwhile, read this.

How come I feel there was a lot of time wasted?!

Here are the readings from the UPS. I am disappointed that it is not reporting battery voltage, but at least I am getting % charged.

battery.charge: 100                     Battery charge (percent of full)
battery.charge.low: 28			Remaining battery level when UPS switches to LB (%)
driver.name: powerpanel			Driver name
driver.parameter.pollinterval: 2	
driver.parameter.port: /dev/ttyS0	Serial or USB port
driver.version: 2.2.2			Driver version - NUT release		
driver.version.internal: 0.23		Internal driver version
input.frequency: 60.3			Input line frequency (Hz)		
input.frequency.nominal: 60		Nominal input line frequency (Hz)
input.transfer.high: 145		High voltage transfer point (V)
input.transfer.low: 90			Low voltage transfer point (V)
input.voltage: 123			Input voltage (V)
input.voltage.nominal: 120		Nominal input voltage (V)
output.voltage: 0			Output voltage (V)
output.voltage.nominal: 120		Nominal output voltage (V)
ups.beeper.status: enabled		UPS beeper status
ups.delay.shutdown: 0			Shutdown with delay command (seconds)
ups.delay.start: 45			Wait before (re)starting (seconds)
ups.firmware: 5.100			UPS firmware
ups.load: 46				Load on UPS (percent of full)
ups.mfr: CyberPower			UPS manufacturer
ups.model: OP1500			UPS model
ups.serial: [unknown]			UPS serial number
ups.status: OL				UPS status
ups.temperature: 35.3			UPS temperature (degrees C)

NTP: ntpq output explained

Host1:~# ntpq -p
remote refid st t when poll reach delay offset jitter
==========================================================
-navobs1.oar.net .USNO. 1 u 958 1024 377 89.425 -6.073 0.695
*navobs1.gatech. .GPS. 1 u 183 1024 375 82.102 1.639 0.281
-NAVOBS1.MIT.EDU .PSC. 1 u 895 1024 377 90.912 -0.207 0.368
+navobs1.wustl.e .GPS. 1 u 48 1024 377 76.890 1.093 0.525
-bigben.cac.wash .USNO. 1 u 924 1024 377 113.327 0.028 0.326
+tick.ucla.edu .GPS. 1 u 107 1024 377 102.470 2.032 0.482
-ntp.alaska.edu .GPS. 1 u 881 1024 377 168.741 5.180 5.157
-tock.mhpcc.hpc. .GPS. 1 u 933 1024 377 174.518 -1.094 0.054

Host2# ntpq -p
remote refid st t when poll reach delay offset disp
==========================================================
+128.252.19.1 .GPS. 1 u 495 1024 377 30.90 -6.366 8.26
*139.78.133.139 .USNO. 1 u 936 1024 377 48.43 -2.906 5.20

Columns Defined:
remote: peers speficified in the ntp.conf file
* = current time source
# = source selected, distance exceeds maximum value
o = source selected, Pulse Per Second (PPS) used
+ = source selected, included in final set
x = source false ticker
. = source selected from end of candidate list
– = source discarded by cluster algorithm
blank = source discarded high stratum, failed sanity

refid: remote source’s synchronization source

stratum: stratum level of the source

t: types available
l = local (such as a GPS, WWVB)
u = unicast (most common)
m = multicast
b = broadcast
– = netaddr

when: number of seconds passed since last response

poll: polling interval, in seconds, for source

reach: indicates success/failure to reach source, 377 all attempts successful

delay: indicates the roundtrip time, in milliseconds, to receive a reply

offset: indicates the time difference, in milliseconds, between the client server and source

disp/jitter: indicates the difference, in milliseconds, between two samples

Quick Update:
Here is a more in-depth reference:
https://pthree.org/2013/11/05/real-life-ntp/