Jump to content

Help : Array Fault Mail


manny

Recommended Posts

Hi,

 

I just started with my unRaid build and successfully completed preclear on my two 2TB WD Red HDD. I made both of them as a data disk and yet to get a hdd for parity. As soon as I added them as data drives I am getting "The unRaid array needs attention. One or more disks are disabled or invalid" error message. I started getting email notification which I have pasted below. I manually started the array and copied files and it seems to be working fine. But i do get the same warning when I log into the admin console (with simple features). I attaching the syslog with this, please let me know if I need to be worried.

 

Thanks a bunch.

This message is a status update for unRAID  Manitower
-----------------------------------------------------------------
Server Name: Manitower
Status: The unRaid array needs attention. One or more disks are disabled or invalid.
Date: Thu Jan  3 00:52:38 IST 2013

Disk Temperature Status
-----------------------------------------------------------------
Parity Disk [sdb]: Spun-Down (DiskId: WDC_WD20EFRX-68AX9N0_WD-WMC300201500)
Disk 1 [sda]: Spun-Down (DiskId: WDC_WD20EFRX-68AX9N0_WD-WMC300130454)

Disk SMART Health Status
-----------------------------------------------------------------
Parity Disk Spun-Down (DiskId: WDC_WD20EFRX-68AX9N0_WD-WMC300201500)
Disk 1 Spun-Down (DiskId: WDC_WD20EFRX-68AX9N0_WD-WMC300130454)

Output of /proc/mdcmd:
-----------------------------------------------------------------
sbName=/boot/config/super.dat
sbVersion=2.1.4
sbCreated=1357026077
sbUpdated=1357147388
sbEvents=7
sbState=0
sbNumDisks=3
sbSynced=0
sbSyncErrs=0
mdVersion=2.1.4
mdState=STARTED
mdNumProtected=3
mdNumDisabled=1
mdDisabledDisk=0
mdNumInvalid=1
mdInvalidDisk=0
mdNumMissing=0
mdMissingDisk=0
mdNumNew=0
mdResync=0
mdResyncCorr=0
mdResyncPos=0
mdResyncDt=0
mdResyncDb=0
diskNumber.0=0
diskName.0=
diskSize.0=0
diskState.0=4
diskId.0=
rdevNumber.0=0
rdevStatus.0=DISK_DSBL_NP
rdevName.0=
rdevSize.0=0
rdevId.0=
rdevNumErrors.0=0
rdevLastIO.0=0
rdevSpinupGroup.0=0
diskNumber.1=1
diskName.1=md1
diskSize.1=1953514552
diskState.1=7
diskId.1=WDC_WD20EFRX-68AX9N0_WD-WMC300201500
rdevNumber.1=1
rdevStatus.1=DISK_OK
rdevName.1=sdb
rdevSize.1=1953514552
rdevId.1=WDC_WD20EFRX-68AX9N0_WD-WMC300201500
rdevNumErrors.1=0
rdevLastIO.1=0
rdevSpinupGroup.1=0
diskNumber.2=2
diskName.2=md2
diskSize.2=1953514552
diskState.2=7
diskId.2=WDC_WD20EFRX-68AX9N0_WD-WMC300130454
rdevNumber.2=2
rdevStatus.2=DISK_OK
rdevName.2=sda
rdevSize.2=1953514552
rdevId.2=WDC_WD20EFRX-68AX9N0_WD-WMC300130454
rdevNumErrors.2=0
rdevLastIO.2=0
rdevSpinupGroup.2=0

syslog.txt

Link to comment

If you are getting a disk0 removed message, isit possible you assigned it at one point?

 

If so, and you have no parity disk currently,you just need to set a new disk configuration. (without the parity disk assigned)

 

Right now, it is not starting because it thinks your parity disk has failed.

 

Joe L.

Link to comment

Thanks a lot for the reply Joe. Yes before preclear I did assign the disk but not sure if I assigned them to parity or not. I tired clearing the current config from admin utility and add them back as two data disk. The array is starting and I am able to copy the files but I still get the error message stating "The unRaid array needs attention. One or more disks are disabled or invalid".

 

Other than this I don't see any error message in Syslog other than some ACPI errors. How can get rid of this warning/error message notification? I use simple features and every time I log into the console it gives me this message.

 

Also unMenu says there are 3 disks in array when I have only 2 data disks and no parity. I am thinking I will buy one more 2 TB disk and add it as parity? will this fix the problem.

 

Please let me know and thanks again for your help....

Link to comment

hey thanks, but I was wondering if adding a parity drive will fix the error I'm getting invalid/missing drive? Looks like something went wrong and unRaid is thinking I have 3 disks when there are only two. Unmenu keeps saying have 3 drives when there are two. Other than this no issues, array is starting without any issues...

 

Anyone had this issue?

Link to comment

hey thanks, but I was wondering if adding a parity drive will fix the error I'm getting invalid/missing drive? Looks like something went wrong and unRaid is thinking I have 3 disks when there are only two. Unmenu keeps saying have 3 drives when there are two. Other than this no issues, array is starting without any issues...

 

Anyone had this issue?

I already explained... you must set a new disk configuration, that way unRAID will know you only have two disks attached.

 

If you are running unRAID 5.X you can stop the array and use

Utils->New Config

in the management interface.

 

If using 4.7, the equivalent is the

initconfig

command

Joe L.

Link to comment

Thanks Joe, I did that couple of time already but still getting the same error message. I got a new 2TB HDD and preclearing it to add it as a Parity drive, hopefully this will stop the message. But Utils -> New Config did not help....

 

Please let me know if you can do something else, or i will wait for couple of days to get my preclear done and add parity drive...

Link to comment

Sorry for bugging you all, but any suggestions? I tired resetting the config multiple times and still getting the same error message. My parity disk's preclear is in progress but I am not sure if that will solve the problem. As I mentioned earlier somehow the systems says there are 3 disks when there are one two...

 

Output of /proc/mdcmd:
-----------------------------------------------------------------
sbName=/boot/config/super.dat
sbVersion=2.1.4
sbCreated=1357404226
sbUpdated=1357404228
sbEvents=1
sbState=0
sbNumDisks=3
sbSynced=0
sbSyncErrs=0
mdVersion=2.1.4
mdState=STARTED
mdNumProtected=3
mdNumDisabled=1
mdDisabledDisk=0
mdNumInvalid=1
mdInvalidDisk=0
mdNumMissing=0
mdMissingDisk=0
mdNumNew=0
mdResync=0
mdResyncCorr=1
mdResyncPos=0
mdResyncDt=0
mdResyncDb=0
diskNumber.0=0
diskName.0=
diskSize.0=0
diskState.0=4
diskId.0=
rdevNumber.0=0
rdevStatus.0=DISK_DSBL_NP
rdevName.0=
rdevSize.0=0
rdevId.0=
rdevNumErrors.0=0
rdevLastIO.0=0
rdevSpinupGroup.0=0
diskNumber.1=1
diskName.1=md1
diskSize.1=1953514552
diskState.1=7
diskId.1=WDC_WD20EFRX-68AX9N0_WD-WMC300130454
rdevNumber.1=1
rdevStatus.1=DISK_OK
rdevName.1=sdb
rdevSize.1=1953514552
rdevId.1=WDC_WD20EFRX-68AX9N0_WD-WMC300130454
rdevNumErrors.1=0
rdevLastIO.1=0
rdevSpinupGroup.1=0
diskNumber.2=2
diskName.2=md2
diskSize.2=1953514552
diskState.2=7
diskId.2=WDC_WD20EFRX-68AX9N0_WD-WMC300201500
rdevNumber.2=2
rdevStatus.2=DISK_OK
rdevName.2=sdc
rdevSize.2=1953514552
rdevId.2=WDC_WD20EFRX-68AX9N0_WD-WMC300201500
rdevNumErrors.2=0
rdevLastIO.2=0
rdevSpinupGroup.2=0
[code]

Link to comment

Finally solved the issue.  As I mentioned got a new 2TB disk for Parity , precleared it twice and enabled parity. As soon as the parity build is completed unRaid reported that the array is "OK". Finally got to see Array Ok messages :-) Thanks for the help and suggestions....

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...