Update: i have disabled some CPU power saving features in the bios, and it is running stable now.
Update: i have disabled some CPU power saving features in the bios, and it is running stable now.
Unfortunately the box crashed again last night. But now i have some errors in the log:
This points to an hardware error. The raid controller has been replaced so it seems the backplane is not working properly.Code:2011-04-12 01:59:10 scsi cmnd aborted, scsi_cmnd(0xffff88012c6d4700), cmnd[0x8a,0x 0,0x 0,0x 0,0x 0,0x 1,0xb0,0x9e,0xf8,0x 0,0x... (0/1) 2011-04-12 01:58:40 scsi cmnd aborted, scsi_cmnd(0xffff88012c6d4340), cmnd[0x8a,0x 0,0x 0,0x 0,0x 0,0x 1,0xb0,0x9e,0xf7,0x 0,0x... (1/1) 2011-04-12 01:58:10 scsi cmnd aborted, scsi_cmnd(0xffff88012c6d45c0), cmnd[0x8a,0x 0,0x 0,0x 0,0x 0,0x 1,0xb0,0x9e,0xf6,0x 0,0x... (1/1) 2011-04-12 01:57:40 scsi cmnd aborted, scsi_cmnd(0xffff88012c6d40c0), cmnd[0x8a,0x 0,0x 0,0x 0,0x 0,0x 1,0xb0,0x9e,0xf5,0x 0,0x... (0/1)
did you ever adjust for the values I mentioned above?
Please try the values that Gr-R mentioned to you, also did you checked for your RAID Controller health ?
The Raid controller sometimes times out accessing drives in the enclosure. It's not the same drive everytime so it must be something with the backplane.
I've changed the ISCSI values mentioned on all initiators and targets this morning. So let's see how long it keeps running this time![]()
Good, also try to remove all settings in your initiators, and reset them all again, even if you have to remove the initiators and reinstall them again.
Try updating to the latest Areca firmware I believe its 1.49. It may help with your drive timeouts.Originally Posted by welnet
I was going to suggest the same thing... backplane failure would be odd. not impossible, but odd.Originally Posted by EricD
I've updated to the latest 1.49FW, unfortunately it shows the same error as as the previous controller which was returned to the dealer.
On boot-up it sometimes fails drives randomly (red flashing light next to drive) when detecting the drives and array. It requires a complete cold shutdown to reset the drive error. There is nothing wrong with the drives as far as i can see. Sometimes it also hangs indefinitely when detecting the controller card with the message 'please wait for the F/W to be ready...'.
Seems to point more and more to an incompatibility between the Areca 1880 drive and the 836-E1 SAS enclosure with LSI expander.
To be continued..