New Application: unraid_info

[bubbaQ]

So what do you want added?

 

The problem with spinstatus for disks outside the array, is that it will confuse MOST users, due to the fact that the USB stick looks like a spun-up disk that doesn't report SMART.

 

The -a option will return the maximum temp over all drives -- in and out of the array -- that are reporting SMART.  You can spin them all up with the -w option.

[purko]

So what do you want added?

 

The problem with spinstatus for disks outside the array, is that it will confuse MOST users, due to the fact that the USB stick looks like a spun-up disk that doesn't report SMART.

 

I was not talaking about the USB stick.  It doesn't doesn't report SMART, so forget about it.

 

I have two hard disks outside the array, so my total count of SpunDown disks was 8. Your info reported 6. That's not what I would intuitively expect. 

 

It's likely that that MOST users who have hard disks outside the array would like to see the whole count at a glance.

 

[bubbaQ]

I was not talking about the USB stick.  It doesn't doesn't report SMART, so forget about it.

 

But it IS a disk device, as are other USB devices and things like CD/DVD drives, and I don't have a way to 100% reliably filter them out from other spinning disks outside the array (they are all type 6)  (I'm working on it though).

 

How about this:

================== unRAID Server Summary ==================

         Array State: STARTED
        Array Status: DEGRADED - 1 DISABLED DISK
    !!! DISK PROBLEM: Disk1 (sda) reports status DISK_DSBL
Total Space on Array: 504,023,312 KB (480.674 GB)
 Total Free on Array: 493,414,524 KB (470.557 GB)
        Percent Free: 97.90%
   Largest Freespace: 243,645,740 KB (232.359 GB) on disk3
   Last parity check: 0 days ago
  Hottest array temp: 29° (disk0) (/dev/sdb) WDC WD3200AAKS-0
Longest running disk: disk3 (/dev/hde) (10,206 hours / 1.17 years)
[color=blue]     Array Spin Status:  SpunUp:4   SpunDown:0[/color]
 Open files on array: 0

Highest temp outside array: 0°
   Disks outside the array: 3 ( /dev/hda /dev/hdb /dev/sdc )
[color=blue]   Spin Status outside array:  SpunUp:1   SpunDown:2[/color]

[purko]

    Array Spin Status:  SpunUp:4   SpunDown:0

 Open files on array: 0

 

Highest temp outside array: 0°

   Disks outside the array: 3 ( /dev/hda /dev/hdb /dev/sdc )

  Spin Status outside array:  SpunUp:1   SpunDown:2

[/code]

I really don't see what convinience you get from separating them into "Array Spin Status" and "Spin Status outside array".

Just give one total "Spin Status" and be done with it.  Simpler, easier to see at a glance, and less confusing.

 

I also want to make the same argument about separating the disk temperatures:

How comforting would it be to me to know that the Highest temp inside the array is 23°C, if my /dev/sdz outde the array is on fire?

A summary would be useful to me if it gives me a sumary of my server.

 

[bubbaQ]

I really don't see what convinience you get from separating them into "Array Spin Status" and "Spin Status outside array".

Just give one total "Spin Status" and be done with it.  Simpler, easier to see at a glance, and less confusing.

 

For one, you can't control spin status outside the array with the unRAID UI.... nor should you change spin status of drives inside the array except with unRAID.  If you reported them all together, you would ALWAYS have at least 1 spun down (the USB stick) as well as any other USB drives and any optical drives.  That is confusing.... much more confusing than reporting them bifurcated as in/outside the array.... particularly to the novice user.

 

I also want to make the same argument about separating the disk temperatures:

How comforting would it be to me to know that the Highest temp inside the array is 23°C, if my /dev/sdz outde the array is on fire?

A summary would be useful to me if it gives me a sumary of my server.

 

If you want to know the max temp of the entire system, use -a.  If you want just the max in the array, use -m.  You can write a script that sets off bells and whistles and calls the Marines of the max temp is over some thershold... just use -a.

 

I have different fans that cool the array then cool the non-array (system) drive.... so I need them separate.

 

But temps are bogus in a large degree... as a 29 on one drive may be fine, but a 23 on another is not.  That is why I'm going to the config file, where you can set action thresholds independently for each drive.

 

For example, you may have the global spindown in unRAID set to 1 hour.  But with what I am working on, you can set a faster spindown if a drive is above a threshold temperature, and there has been no I/O on that drive for say 5 minutes.  So the faster spindown timer will only kick in IF the temp is over a threshold you set for that drive

[purko]

For one, you can't control spin status outside the array with the unRAID UI....

nor should you change spin status of drives inside the array except with unRAID.

 

Now that's not true. The spindown logic in 4.5.3 seems to be badly broken.

Many people on these boards reported the same problems with the unRAID's spindown like what I saw on my server.

So, I've disabled the unRAID's spindown functionality altogether, and I take care of spinning down my disks myself.

I'm not even going to bother checking whether they'll ever fix that bug.

 

I have different fans that cool the array then cool the non-array (system) drive.... so I need them separate.

 

You say you need them separate, that's a reason good enough for me.

 

But the Summary screen is only one part of your unraid_info's functionality. I'm sure your fan control won't be parsing the Sumary screen.

You can still have all that stuff separately, yet display one unified and simplified, humanly radable Summary screen.

 

Please don't misunderstand me: I am not arguing. I'll be happy wichever way you decide to go at the end.

This is already shaping up to be one very useful tool!

 

[purko]

Spun-up disk with longest time since last I/O: /dev/hdz (1,236 minutes)

 

[bubbaQ]

Now that's not true. The spindown logic in 4.5.3 seems to be badly broken.

 

unraid_info is designed to run on ALL recent versions, not just 4.5.3, so I have to take into account a lot more than what's broken in 4.5.3.

 

how about I add a --purko flag that combines them all together?

 

BTW, no one has commented on the filename/location for the config file.... so I am using /config/unraid_info.ini as the default unless someone has a better idea.

 

[DEFAULT]
; [DEFAULT] is the defaults for the drives (duh)
; [drive-id] is the section header for drive-specific information where drive-id
;   is the drive ID from unRAID (make and model concantinated together with _)
; At MIN_FAN_TEMP or below, fans will be set to the minimum
; At MIN_FAN_TEMP or above, fans will be set to the maximum
; At a temp between MAN and MAX, fans will be set to
;    an interpolated value between MIN and MAX for the fan
; At or above ALERT_TEMP, a drive alert is generated
; At or above ALARM_TEMP, the system alarm (speaker) is activated
; At or above SPIN_DOWN_TEMP, the drive will be spun down if there
;    has been no drive activity within 300 seconds (5 minutes)
; If READ_SMART_WHEN_SPUN_DOWN is set to Y, then SMART will be read 
;    from the drive regardless of spinstatus of the drive
; If READ_SMART_WHEN_SPUN_DOWN is set to N, then SMART will NOT read 
;    from the drive unless it is spun up
; If READ_SMART_WHEN_SPUN_DOWN is set to *, then the program will use its
;   internal table of capable drives to decde to read SMART or not
; PURCHASED and WARRANTY are text fields for the user to record any info.
; When SMART parameter for POWER_ON_HOURS is larger than REPLACE_HOURS 
;    an alert is generated that the drive has exceeded its lifetime
; When the current date is after REPLACE_DATE, an alert is generated 
;    that the drive has exceeded its lifetime
;
; So what is an alert?  By using the -A flag, unraid_info will only
; print text regarding something that is out of spec (an alert) and if all
; drives are within spec, then nothing will be printed.
;
; A default copy of this file can be created by uraid_info with the -X command.
; At some point, I'll have a nice GIU interface to editing this file.
MIN_FAN_TEMP=28
MAX_FAN_TEMP=40
ALERT_TEMP=44
ALARM_TEMP=49
SPIN_DOWN_TEMP=45
READ_SMART_WHEN_IDLE=*
PURCHASED=
WARRANTY=
REPLACE_HOURS=26280
REPLACE_DATE=

[sAMSUNG999999999]
MIN_FAN_TEMP=17
MAX_FAN_TEMP=29
READ_SMART_WHEN_SPUN_DOWN=Y


; Fan settings are not yet implemented, but this is what I am working on:
[FAN1]
FAN_NUMBER=1
FAN_NAME=Chassis Fan Header1
FAN_SPEED_PORT=/sys/devices/platform/it87.552/fan2_input
FAN_PWM_PORT=/sys/devices/platform/it87.552/pwm2
FAN_PWM_PORT_ENABLE=/sys/devices/platform/it87.552/pwm2_enable
FAN_LOW_SPEED=110
FAN_HIGH_SPEED=195

 

[queeg]

    Array Spin Status:  SpunUp:4   SpunDown:0

 Open files on array: 0

 

Highest temp outside array: 0°

   Disks outside the array: 3 ( /dev/hda /dev/hdb /dev/sdc )

  Spin Status outside array:  SpunUp:1   SpunDown:2

[/code]

I really don't see what convinience you get from separating them into "Array Spin Status" and "Spin Status outside array".

Just give one total "Spin Status" and be done with it.  Simpler, easier to see at a glance, and less confusing.

 

I also want to make the same argument about separating the disk temperatures:

How comforting would it be to me to know that the Highest temp inside the array is 23°C, if my /dev/sdz outde the array is on fire?

A summary would be useful to me if it gives me a sumary of my server.

 

I like them separate.  Since I have non-array drives it helps me know where to go to effect any changes.  I can spin down my non-array drives from unMenu but would otherwise just use the unRAID page.  Anyone who has non-array drives should intuit the separate status.  Anyone without non-array drives won't see anything to be confused about.

Just my $.02

[starcat]

bubbaQ, when is the fan control going to work and do you have any hints regarding the X7SBE mainboard?

[Msan]

I am currently running a parity check and my array is fine, but the output from unraid_info -S shows me this:

 

================== unRAID Server Summary ==================

 

          Array State: STARTED

        Array Status: DEGRADED - 1 DISABLED DISK

Total Space on Array: 8,790,859,800 KB (8383.617 GB)

  Total Free on Array: 5,476,823,740 KB (5223.106 GB)

        Percent Free: 62.30%

    Largest Freespace: 976,699,896 KB (931.454 GB) on disk9

    Last parity check: 2 days ago

  Hottest array temp: 37° (disk6) (/dev/sdc) WDC WD1001FALS-0

Longest running disk: disk1 (/dev/sdf) (10,827 hours / 1.24 years)

          Spin Status:  SpunUp:10  SpunDown:0

  Open Files on array: 3

 

Highest temp outside array: 29°

    Disks outside the array: 2 ( /dev/sdh /dev/sdi )

 

Why would it show up as degraded? All my disks are fine..

[Joe L.]

I am currently running a parity check and my array is fine, but the output from unraid_info -S shows me this:

 

================== unRAID Server Summary ==================

 

          Array State: STARTED

         Array Status: DEGRADED - 1 DISABLED DISK

Total Space on Array: 8,790,859,800 KB (8383.617 GB)

  Total Free on Array: 5,476,823,740 KB (5223.106 GB)

         Percent Free: 62.30%

    Largest Freespace: 976,699,896 KB (931.454 GB) on disk9

    Last parity check: 2 days ago

   Hottest array temp: 37° (disk6) (/dev/sdc) WDC WD1001FALS-0

Longest running disk: disk1 (/dev/sdf) (10,827 hours / 1.24 years)

          Spin Status:  SpunUp:10   SpunDown:0

  Open Files on array: 3

 

Highest temp outside array: 29°

    Disks outside the array: 2 ( /dev/sdh /dev/sdi )

 

Why would it show up as degraded? All my disks are fine..

It is not smart enough to know it is the parity disk that is being rebuilt?

 

You might want to post the output of

/root/mdcmd status | strings

 

[bubbaQ]

"Degraded" is a term commonly used for arrays, when the array as a unit is still functioning, but at a reduced level of protection due to a disk failure.

[purko]

I am currently running a parity check and my array is fine, but the output from unraid_info -S shows me this:

 

================== unRAID Server Summary ==================

 

         Array State: STARTED

        Array Status: DEGRADED - 1 DISABLED DISK

 

"DEGRADED - 1 DISABLED DISK" doesn't sound good/

When I start parity check I get this:

================== unRAID Server Summary ==================

 

         Array State: STARTED

        Array Status: -unknown-

 

[Msan]

I am currently running a parity check and my array is fine, but the output from unraid_info -S shows me this:

 

================== unRAID Server Summary ==================

 

         Array State: STARTED

        Array Status: DEGRADED - 1 DISABLED DISK

Total Space on Array: 8,790,859,800 KB (8383.617 GB)

 Total Free on Array: 5,476,823,740 KB (5223.106 GB)

        Percent Free: 62.30%

   Largest Freespace: 976,699,896 KB (931.454 GB) on disk9

   Last parity check: 2 days ago

  Hottest array temp: 37° (disk6) (/dev/sdc) WDC WD1001FALS-0

Longest running disk: disk1 (/dev/sdf) (10,827 hours / 1.24 years)

         Spin Status:  SpunUp:10   SpunDown:0

 Open Files on array: 3

 

Highest temp outside array: 29°

   Disks outside the array: 2 ( /dev/sdh /dev/sdi )

 

Why would it show up as degraded? All my disks are fine..

It is not smart enough to know it is the parity disk that is being rebuilt?

 

You might want to post the output of

/root/mdcmd status | strings

 

 

ok, here is the output:

 

root@Tower:~# /root/mdcmd status | strings
cmdOper=status
cmdResult=ok
sbName=/boot/config/super.dat
sbVersion=0.95.4
sbCreated=1272937386
sbUpdated=1273183115
sbEvents=9
sbState=0
sbNumDisks=10
sbSynced=1272975200
sbSyncErrs=0
mdVersion=0.95.4
mdState=STARTED
mdNumProtected=10
mdNumDisabled=0
mdDisabledDisk=0
mdNumInvalid=0
mdInvalidDisk=0
mdNumMissing=0
mdMissingDisk=0
mdNumNew=0
mdResync=1953514552
mdResyncPos=1424530508
mdResyncPrcnt=72.9
mdResyncFinish=113.0
mdResyncSpeed=77985
diskNumber.0=0
diskName.0=
diskSize.0=1953514552
diskState.0=7
diskModel.0=WDC WD20EADS-32S
diskSerial.0=WD-WCAVY3124724
diskId.0=WDC_WD20EADS-32S_WD-WCAVY3124724
rdevNumber.0=0
rdevStatus.0=DISK_OK
rdevName.0=sda
rdevSize.0=1953514552
rdevModel.0=WDC WD20EADS-32S
rdevSerial.0=WD-WCAVY3124724
rdevId.0=WDC_WD20EADS-32S_WD-WCAVY3124724
rdevNumErrors.0=0
rdevLastIO.0=1273203724
rdevSpinupGroup.0=64
diskNumber.1=1
diskName.1=md1
diskSize.1=976762552
diskState.1=7
diskModel.1=ST31000340AS
diskSerial.1=9QJ1KGS1
diskId.1=ST31000340AS_9QJ1KGS1
rdevNumber.1=1
rdevStatus.1=DISK_OK
rdevName.1=sdf
rdevSize.1=976762552
rdevModel.1=ST31000340AS
rdevSerial.1=9QJ1KGS1
rdevId.1=ST31000340AS_9QJ1KGS1
rdevNumErrors.1=0
rdevLastIO.1=1273203180
rdevSpinupGroup.1=0
diskNumber.2=2
diskName.2=md2
diskSize.2=976762552
diskState.2=7
diskModel.2=WDC WD10EADS-00M
diskSerial.2=WD-WCAV50067727
diskId.2=WDC_WD10EADS-00M_WD-WCAV50067727
rdevNumber.2=2
rdevStatus.2=DISK_OK
rdevName.2=sdj
rdevSize.2=976762552
rdevModel.2=WDC WD10EADS-00M
rdevSerial.2=WD-WCAV50067727
rdevId.2=WDC_WD10EADS-00M_WD-WCAV50067727
rdevNumErrors.2=0
rdevLastIO.2=0
rdevSpinupGroup.2=0
diskNumber.3=3
diskName.3=md3
diskSize.3=976762552
diskState.3=7
diskModel.3=ST31000340AS
diskSerial.3=9QJ1LQMA
diskId.3=ST31000340AS_9QJ1LQMA
rdevNumber.3=3
rdevStatus.3=DISK_OK
rdevName.3=sdg
rdevSize.3=976762552
rdevModel.3=ST31000340AS
rdevSerial.3=9QJ1LQMA
rdevId.3=ST31000340AS_9QJ1LQMA
rdevNumErrors.3=0
rdevLastIO.3=0
rdevSpinupGroup.3=0
diskNumber.4=4
diskName.4=md4
diskSize.4=976762552
diskState.4=7
diskModel.4=WDC WD10EADS-00L
diskSerial.4=WD-WCAU45365397
diskId.4=WDC_WD10EADS-00L_WD-WCAU45365397
rdevNumber.4=4
rdevStatus.4=DISK_OK
rdevName.4=sdl
rdevSize.4=976762552
rdevModel.4=WDC WD10EADS-00L
rdevSerial.4=WD-WCAU45365397
rdevId.4=WDC_WD10EADS-00L_WD-WCAU45365397
rdevNumErrors.4=0
rdevLastIO.4=1273202813
rdevSpinupGroup.4=0
diskNumber.5=5
diskName.5=md5
diskSize.5=976762552
diskState.5=7
diskModel.5=WDC WD1001FALS-0
diskSerial.5=WD-WMATV2056218
diskId.5=WDC_WD1001FALS-0_WD-WMATV2056218
rdevNumber.5=5
rdevStatus.5=DISK_OK
rdevName.5=sdb
rdevSize.5=976762552
rdevModel.5=WDC WD1001FALS-0
rdevSerial.5=WD-WMATV2056218
rdevId.5=WDC_WD1001FALS-0_WD-WMATV2056218
rdevNumErrors.5=0
rdevLastIO.5=1273203723
rdevSpinupGroup.5=0
diskNumber.6=6
diskName.6=md6
diskSize.6=976761496
diskState.6=7
diskModel.6=WDC WD1001FALS-0
diskSerial.6=WD-WMATV2065706
diskId.6=WDC_WD1001FALS-0_WD-WMATV2065706
rdevNumber.6=6
rdevStatus.6=DISK_OK
rdevName.6=sdc
rdevSize.6=976761496
rdevModel.6=WDC WD1001FALS-0
rdevSerial.6=WD-WMATV2065706
rdevId.6=WDC_WD1001FALS-0_WD-WMATV2065706
rdevNumErrors.6=0
rdevLastIO.6=1273198392
rdevSpinupGroup.6=1
diskNumber.7=7
diskName.7=md7
diskSize.7=976761496
diskState.7=7
diskModel.7=WDC WD1001FALS-0
diskSerial.7=WD-WMATV2065452
diskId.7=WDC_WD1001FALS-0_WD-WMATV2065452
rdevNumber.7=7
rdevStatus.7=DISK_OK
rdevName.7=sdd
rdevSize.7=976761496
rdevModel.7=WDC WD1001FALS-0
rdevSerial.7=WD-WMATV2065452
rdevId.7=WDC_WD1001FALS-0_WD-WMATV2065452
rdevNumErrors.7=0
rdevLastIO.7=0
rdevSpinupGroup.7=0
diskNumber.8=8
diskName.8=md8
diskSize.8=976761496
diskState.8=7
diskModel.8=WDC WD1001FALS-0
diskSerial.8=WD-WMATV2066956
diskId.8=WDC_WD1001FALS-0_WD-WMATV2066956
rdevNumber.8=8
rdevStatus.8=DISK_OK
rdevName.8=sde
rdevSize.8=976761496
rdevModel.8=WDC WD1001FALS-0
rdevSerial.8=WD-WMATV2066956
rdevId.8=WDC_WD1001FALS-0_WD-WMATV2066956
rdevNumErrors.8=0
rdevLastIO.8=0
rdevSpinupGroup.8=0
diskNumber.9=9
diskName.9=md9
diskSize.9=976762552
diskState.9=7
diskModel.9=WDC WD10EADS-00M
diskSerial.9=WD-WCAV50050779
diskId.9=WDC_WD10EADS-00M_WD-WCAV50050779
rdevNumber.9=9
rdevStatus.9=DISK_OK
rdevName.9=sdk
rdevSize.9=976762552
rdevModel.9=WDC WD10EADS-00M
rdevSerial.9=WD-WCAV50050779
rdevId.9=WDC_WD10EADS-00M_WD-WCAV50050779
rdevNumErrors.9=0
rdevLastIO.9=0
rdevSpinupGroup.9=0

 

Looks OK to me..

 

It's still checking parity, once it's finished I'll run unraid_info again..

[bubbaQ]

Unraid_info does know when you are rebuilding parity, and it shows the progress.  It does not show progress when rebuilding a a data disk.

 

Your mdcmd status does not match the unraid_info output.

 

If unraid_info says "DEGRADED - 1 disabled disk " then that means the output from mdcmd has a reported

mdNumDisabled ==1  

 

If mdNumDisabled ==1  and diskState == 6, then that is a parity rebuild, and unraid_info will display progress.

 

If any disk is labeled as "DISK_INVALID"  on the next line, unraid_info will say which disk that is

 

          Array State: STARTED
        Array Status: DEGRADED - 1 DISABLED DISK
    !!! DISK PROBLEM: Disk2 (sdf) reports status DISK_INVALID

 

unraid_info can not display "DEGRADED - 1 disabled disk " unless  mdNumDisabled ==1

[Joe L.]

unraid_info can not display "DEGRADED - 1 disabled disk " unless  mdNumDisabled ==1

I've never stopped believing bug reports from users of my code. 

 

(They tend to find branches through the code that normal flow analysis just does not consider  )

 

It is why I asked for the output of mdcmd status... in case it held a clue. 

Too bad it, and the unraid_info command, were not run in quick succession.

 

Joe L.

[bubbaQ]

Me either, but in this case there is only one very small piece of code that can return "DEGRADED"

 

		if (this->mdNumDisabled ==1 ) {
		return "DEGRADED - 1 DISABLED DISK";
	}

	if (this->mdNumDisabled >1 || this->mdNumMissing > 1) {
		return "FAILED - MULTIPLE DISABLED OR MISSING DISKS";
	}

	return "-unknown-";

 

It is unlikely that the parsing would have an incorrect value either, since everything else was parsed correctly, and parsing is based on exact string match from the mdcmd output.

[Msan]

Parity check is finished and the output looks ok now:

 

root@Tower:~# /boot/custom/unraid_info -S

================== unRAID Server Summary ==================

 

          Array State: STARTED

        Array Status: OK

Total Space on Array: 8,790,859,800 KB (8383.617 GB)

  Total Free on Array: 5,476,823,076 KB (5223.105 GB)

        Percent Free: 62.30%

    Largest Freespace: 976,699,896 KB (931.454 GB) on disk9

    Last parity check: 0 days ago

  Hottest array temp: 35° (disk7) (/dev/sdd) WDC WD1001FALS-0

Longest running disk: disk1 (/dev/sdf) (10,843 hours / 1.24 years)

          Spin Status:  SpunUp:10  SpunDown:0

  Open Files on array: 3

 

Highest temp outside array: 28°

    Disks outside the array: 2 ( /dev/sdh /dev/sdi )

 

Beats me why it showed as degraded.. maybe I'll start another parity check

[Msan]

Ok, started another parity check..

 

root@Tower:~# /boot/custom/unraid_info -S

================== unRAID Server Summary ==================

 

         Array State: STARTED

        Array Status: DEGRADED - 1 DISABLED DISK

Total Space on Array: 8,790,859,800 KB (8383.617 GB)

 Total Free on Array: 5,476,823,076 KB (5223.105 GB)

        Percent Free: 62.30%

   Largest Freespace: 976,699,896 KB (931.454 GB) on disk9

   Last parity check: 0 days ago

  Hottest array temp: 35° (disk7) (/dev/sdd) WDC WD1001FALS-0

Longest running disk: disk1 (/dev/sdf) (10,843 hours / 1.24 years)

         Spin Status:  SpunUp:10   SpunDown:0

 Open Files on array: 3

 

Highest temp outside array: 29°

   Disks outside the array: 2 ( /dev/sdh /dev/sdi )

 

 

output from mdcmd:

 

root@Tower:~# /root/mdcmd status | strings
cmdOper=status
cmdResult=ok
sbName=/boot/config/super.dat
sbVersion=0.95.4
sbCreated=1272937386
sbUpdated=1273244313
sbEvents=11
sbState=0
sbNumDisks=10
sbSynced=1273211783
sbSyncErrs=0
mdVersion=0.95.4
mdState=STARTED
mdNumProtected=10
mdNumDisabled=0
mdDisabledDisk=0
mdNumInvalid=0
mdInvalidDisk=0
mdNumMissing=0
mdMissingDisk=0
mdNumNew=0
mdResync=1953514552
mdResyncPos=1629496
mdResyncPrcnt=0.0
mdResyncFinish=379.3
mdResyncSpeed=85762
diskNumber.0=0
diskName.0=
diskSize.0=1953514552
diskState.0=7
diskModel.0=WDC WD20EADS-32S
diskSerial.0=WD-WCAVY3124724
diskId.0=WDC_WD20EADS-32S_WD-WCAVY3124724
rdevNumber.0=0
rdevStatus.0=DISK_OK
rdevName.0=sda
rdevSize.0=1953514552
rdevModel.0=WDC WD20EADS-32S
rdevSerial.0=WD-WCAVY3124724
rdevId.0=WDC_WD20EADS-32S_WD-WCAVY3124724
rdevNumErrors.0=0
rdevLastIO.0=1273244333
rdevSpinupGroup.0=64
diskNumber.1=1
diskName.1=md1
diskSize.1=976762552
diskState.1=7
diskModel.1=ST31000340AS
diskSerial.1=9QJ1KGS1
diskId.1=ST31000340AS_9QJ1KGS1
rdevNumber.1=1
rdevStatus.1=DISK_OK
rdevName.1=sdf
rdevSize.1=976762552
rdevModel.1=ST31000340AS
rdevSerial.1=9QJ1KGS1
rdevId.1=ST31000340AS_9QJ1KGS1
rdevNumErrors.1=0
rdevLastIO.1=1273244333
rdevSpinupGroup.1=0
diskNumber.2=2
diskName.2=md2
diskSize.2=976762552
diskState.2=7
diskModel.2=WDC WD10EADS-00M
diskSerial.2=WD-WCAV50067727
diskId.2=WDC_WD10EADS-00M_WD-WCAV50067727
rdevNumber.2=2
rdevStatus.2=DISK_OK
rdevName.2=sdj
rdevSize.2=976762552
rdevModel.2=WDC WD10EADS-00M
rdevSerial.2=WD-WCAV50067727
rdevId.2=WDC_WD10EADS-00M_WD-WCAV50067727
rdevNumErrors.2=0
rdevLastIO.2=1273244333
rdevSpinupGroup.2=0
diskNumber.3=3
diskName.3=md3
diskSize.3=976762552
diskState.3=7
diskModel.3=ST31000340AS
diskSerial.3=9QJ1LQMA
diskId.3=ST31000340AS_9QJ1LQMA
rdevNumber.3=3
rdevStatus.3=DISK_OK
rdevName.3=sdg
rdevSize.3=976762552
rdevModel.3=ST31000340AS
rdevSerial.3=9QJ1LQMA
rdevId.3=ST31000340AS_9QJ1LQMA
rdevNumErrors.3=0
rdevLastIO.3=1273244333
rdevSpinupGroup.3=0
diskNumber.4=4
diskName.4=md4
diskSize.4=976762552
diskState.4=7
diskModel.4=WDC WD10EADS-00L
diskSerial.4=WD-WCAU45365397
diskId.4=WDC_WD10EADS-00L_WD-WCAU45365397
rdevNumber.4=4
rdevStatus.4=DISK_OK
rdevName.4=sdl
rdevSize.4=976762552
rdevModel.4=WDC WD10EADS-00L
rdevSerial.4=WD-WCAU45365397
rdevId.4=WDC_WD10EADS-00L_WD-WCAU45365397
rdevNumErrors.4=0
rdevLastIO.4=1273244333
rdevSpinupGroup.4=0
diskNumber.5=5
diskName.5=md5
diskSize.5=976762552
diskState.5=7
diskModel.5=WDC WD1001FALS-0
diskSerial.5=WD-WMATV2056218
diskId.5=WDC_WD1001FALS-0_WD-WMATV2056218
rdevNumber.5=5
rdevStatus.5=DISK_OK
rdevName.5=sdb
rdevSize.5=976762552
rdevModel.5=WDC WD1001FALS-0
rdevSerial.5=WD-WMATV2056218
rdevId.5=WDC_WD1001FALS-0_WD-WMATV2056218
rdevNumErrors.5=0
rdevLastIO.5=1273244333
rdevSpinupGroup.5=0
diskNumber.6=6
diskName.6=md6
diskSize.6=976761496
diskState.6=7
diskModel.6=WDC WD1001FALS-0
diskSerial.6=WD-WMATV2065706
diskId.6=WDC_WD1001FALS-0_WD-WMATV2065706
rdevNumber.6=6
rdevStatus.6=DISK_OK
rdevName.6=sdc
rdevSize.6=976761496
rdevModel.6=WDC WD1001FALS-0
rdevSerial.6=WD-WMATV2065706
rdevId.6=WDC_WD1001FALS-0_WD-WMATV2065706
rdevNumErrors.6=0
rdevLastIO.6=1273244333
rdevSpinupGroup.6=1
diskNumber.7=7
diskName.7=md7
diskSize.7=976761496
diskState.7=7
diskModel.7=WDC WD1001FALS-0
diskSerial.7=WD-WMATV2065452
diskId.7=WDC_WD1001FALS-0_WD-WMATV2065452
rdevNumber.7=7
rdevStatus.7=DISK_OK
rdevName.7=sdd
rdevSize.7=976761496
rdevModel.7=WDC WD1001FALS-0
rdevSerial.7=WD-WMATV2065452
rdevId.7=WDC_WD1001FALS-0_WD-WMATV2065452
rdevNumErrors.7=0
rdevLastIO.7=1273244333
rdevSpinupGroup.7=0
diskNumber.8=8
diskName.8=md8
diskSize.8=976761496
diskState.8=7
diskModel.8=WDC WD1001FALS-0
diskSerial.8=WD-WMATV2066956
diskId.8=WDC_WD1001FALS-0_WD-WMATV2066956
rdevNumber.8=8
rdevStatus.8=DISK_OK
rdevName.8=sde
rdevSize.8=976761496
rdevModel.8=WDC WD1001FALS-0
rdevSerial.8=WD-WMATV2066956
rdevId.8=WDC_WD1001FALS-0_WD-WMATV2066956
rdevNumErrors.8=0
rdevLastIO.8=1273244333
rdevSpinupGroup.8=0
diskNumber.9=9
diskName.9=md9
diskSize.9=976762552
diskState.9=7
diskModel.9=WDC WD10EADS-00M
diskSerial.9=WD-WCAV50050779
diskId.9=WDC_WD10EADS-00M_WD-WCAV50050779
rdevNumber.9=9
rdevStatus.9=DISK_OK
rdevName.9=sdk
rdevSize.9=976762552
rdevModel.9=WDC WD10EADS-00M
rdevSerial.9=WD-WCAV50050779
rdevId.9=WDC_WD10EADS-00M_WD-WCAV50050779
rdevNumErrors.9=0
rdevLastIO.9=1273244333
rdevSpinupGroup.9=0

 

Syslog output from point of start parity check:

 

May 7 07:58:33 Tower kernel: mdcmd (38941): check CORRECT
May 7 07:58:33 Tower kernel: md: recovery thread woken up ...
May 7 07:58:33 Tower kernel: md: recovery thread checking parity...
May 7 07:58:33 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.

 

All commands within a minute of starting parity check..

 

EDIT: Canceled Parity check and ran unraid _info again and all is fine..

 

root@Tower:~# /boot/custom/unraid_info -S                                      

================== unRAID Server Summary ==================

 

         Array State: STARTED

        Array Status: OK

Total Space on Array: 8,790,859,800 KB (8383.617 GB)

 Total Free on Array: 5,476,823,076 KB (5223.105 GB)

        Percent Free: 62.30%

   Largest Freespace: 976,699,896 KB (931.454 GB) on disk9

   Last parity check: 0 days ago

  Hottest array temp: 36° (disk7) (/dev/sdd) WDC WD1001FALS-0

Longest running disk: disk1 (/dev/sdf) (10,843 hours / 1.24 years)

         Spin Status:  SpunUp:10   SpunDown:0

 Open Files on array: 3

 

Highest temp outside array: 29°

   Disks outside the array: 2 ( /dev/sdh /dev/sdi )

 

 

[Joe L.]

It is unlikely that the parsing would have an incorrect value either, since everything else was parsed correctly, and parsing is based on exact string match from the mdcmd output.

based on the last post... You're not taking bets on that?

 

unRAID users are very resourceful... 

 

Joe L.

[Joe L.]

 

I also posted the source at http://www.tcpatools.com/bubba/unraid_info.cpp

 

 

Sorry if it's a stupid question, but what's the command to compile this file?

 

 

I would cd to the directory with the source and then type:

make unraid_info

 

Assuming you have the compiler and "make" installed it will probably do it.

[bubbaQ]

The source is C++, not C.

[prostuff1]

The source is C++, not C.

I get exactly the same result when I use the c++ command:

0 root@VbTower:/tmp/unraid_info# c++ -o unraid_info unraid_info.cpp
In file included from unraid_info.cpp:81:
ata.h:477: error: 'u8' does not name a type
ata.h:479: error: 'u8' does not name a type
ata.h:481: error: 'u8' does not name a type
ata.h:482: error: 'u8' does not name a type
...

 

What command should I use, please?

 

 

 

to compile c++ code you need to use g++

[jk2587]

I realize this is an old post, but the original download link is broken, any chance of getting it put somewhere else? I'm working out some fan control stuff and this app would be a big help.

 

Thanks!