Adaptec RAID 71605Q with maxCache 3.0 - not supported ?

Printable View

11-26-2012, 04:34 PM
TomJ

Adaptec RAID 71605Q with maxCache 3.0 - not supported ?

Well after years of good service I unplugged Areca raid card and installed Adaptec RAID 71605Q.
Ouch! :( It's not recognized by DSS7.
In hardware setting is just " Adaptec Unknown device 028c (rev 01) ".
According this webcast http://vimeo.com/37887260 I assumed it could be working.

Unsupported or bios misconfiguration ? Ideas ?

Help appreciated.
11-26-2012, 05:03 PM
Al-S

The webcast is done with :
RAID controller: Adaptec ASR-6805Q ( Adaptec Series 6 not 7 ).
SSD Cache: STEC MACH16

And as you can check in our compatible list:
http://www.open-e.com/service-and-su...vanced-search/

The Adaptec Series 7 is still not supported yet. But it's in our developing list now, and it should be available soon. The issue is related to Adaptec itself as they start to create a very huge size drivers which cause all it's partners a lot of time to deal with.
04-24-2013, 02:36 PM
spamx

Is DSS 7 already supports both controllers Adaptec Series 7Q like 7005Q, 71605Q?
04-24-2013, 03:06 PM
To-M

We have a small update for the Adaptec for V7 but for releases that are for up07 and not for up10. We are working on this for either the next release or the one after. If you want the small update send an email to anyone of our moderators.
05-29-2013, 05:35 AM
gsmail

Asr 71605q

Where it is possible to download a patch for ASR 71605Q
DSS v7 Demo
05-29-2013, 07:17 AM
gsmail

Where it is possible to download updating for Adaptec 71605Q.
DSS v7 Demo
05-29-2013, 09:24 AM
Al-S

The small update files cannot be downloaded, we send them through the support tickets.
Please send our pre-sales team an email with details, pre(dash)sales(at)open-e(dot)com.And mention this Forum post in your email too.
06-11-2013, 09:03 PM
gsmail

Here such errors of times in three days and everything falls.
Adaptec 71605Q.
DSS v7 Demo.

At old Adaptec Worked steadily.
Whether it is possible to undertake something?

2013/06/11 21:05:01 I/O Errors detected. To prevent data loss it is recommended to shut... (148/148)
2013/06/11 20:57:26 [297993.980678] Pid: 11898, comm: flush-253:18... (1/1)
2013/06/11 20:57:26 [297993.980680] Call... (1/1)
2013/06/11 20:57:26 [297993.980683] [<ffffffff81138131>]... (1/1)
2013/06/11 20:57:26 [297993.980685] [<ffffffff81138131>]... (1/1)
2013/06/11 20:57:26 [297993.980689] [<ffffffff8104590c>]... (1/1)
2013/06/11 20:57:26 [297993.980692] [<ffffffff81138131>]... (1/1)
2013/06/11 20:57:26 [297993.980695] [<ffffffff8109a8fa>]... (1/1)
2013/06/11 20:57:26 [297993.980697] [<ffffffff8109ac06>]... (1/1)
2013/06/11 20:57:26 [297993.980699] [<ffffffff8109a8f0>]... (1/1)
06-11-2013, 10:21 PM
To-M

With I/O Errors detected I would be concerned. Check controller logs and the DSS logs in the dmesg2 logs to see which sdx device is having issues incase you have more then one array.
06-12-2013, 05:55 AM
gsmail

We have one array.
May you look and solve problems, we at a stage of adoption of the decision on purchase.
logs: http:// mirror.adman.com/TRL00030_[7637]_logs_2013-06-12_06-53.tar.gz
06-12-2013, 02:32 PM
To-M

I am not able to get to this link. Ask Adaptec to look into there logs from the RAID controller.
06-12-2013, 07:00 PM
Al-S

From the lines you past above, this seems to be a CALL TRACE issue, and also there is I/O error detected, so this mostly could be an issue with one of your units.
To prevent data loss it is recommended to shut down the system. Please contact your hard drive vendor for further support.
And in such cases, checking the RAID controller, checking the storage disks, are recommended.
06-12-2013, 10:45 PM
Gr-R

from your log files:

===
2013/06/11 20:57:21|I/O Errors detected on unit S001. To prevent data loss it is recommended to shut down the system.

2013/06/11 20:57:26|[297993.980680] Call Trace:
2013/06/11 20:57:26|[297993.980683] [<ffffffff81138131>] ? ext3_ordered_writepage+0x1e1/0x200
2013/06/11 20:57:26|[297993.980685] [<ffffffff81138131>] ? ext3_ordered_writepage+0x1e1/0x200
2013/06/11 20:57:26|[297993.980689] [<ffffffff8104590c>] ? warn_slowpath_common+0x8c/0xc0
2013/06/11 20:57:26|[297993.980692] [<ffffffff81138131>] ? ext3_ordered_writepage+0x1e1/0x200
2013/06/11 20:57:26|[297993.980695] [<ffffffff8109a8fa>] ? __writepage+0xa/0x30
2013/06/11 20:57:26|[297993.980697] [<ffffffff8109ac06>] ? write_cache_pages+0x1a6/0x350
2013/06/11 20:57:26|[297993.980699] [<ffffffff8109a8f0>] ? __writepage+0x0/0x30
2013/06/11 20:57:26|[297993.980703] [<ffffffff8117faef>] ? journal_stop+0x1af/0x290
2013/06/11 20:57:26|[297993.980706] [<ffffffff810ee975>] ? writeback_single_inode+0xc5/0x2d0
2013/06/11 20:57:26|[297993.980708] [<ffffffff810eee3c>] ? writeback_sb_inodes+0xac/0x130
2013/06/11 20:57:26|[297993.980710] [<ffffffff810ef40b>] ? writeback_inodes_wb+0xfb/0x130
2013/06/11 20:57:26|[297993.980712] [<ffffffff810ef631>] ? wb_writeback+0x1f1/0x260
2013/06/11 20:57:26|[297993.980714] [<ffffffff810ef7f5>] ? wb_do_writeback+0x155/0x160
2013/06/11 20:57:26|[297993.980717] [<ffffffff810ef837>] ? bdi_writeback_task+0x37/0x130
2013/06/11 20:57:26|[297993.980720] [<ffffffff81592695>] ? _raw_spin_lock+0x5/0x10
2013/06/11 20:57:26|[297993.980723] [<ffffffff810a7060>] ? bdi_start_fn+0x0/0x100
2013/06/11 20:57:26|[297993.980725] [<ffffffff810a70e4>] ? bdi_start_fn+0x84/0x100
2013/06/11 20:57:26|[297993.980727] [<ffffffff810a7060>] ? bdi_start_fn+0x0/0x100
2013/06/11 20:57:26|[297993.980730] [<ffffffff8105c4b6>] ? kthread+0x96/0xa0
2013/06/11 20:57:26|[297993.980734] [<ffffffff8100aa64>] ? kernel_thread_helper+0x4/0x10
2013/06/11 20:57:26|[297993.980736] [<ffffffff8105c420>] ? kthread+0x0/0xa0
2013/06/11 20:57:26|[297993.980738] [<ffffffff8100aa60>] ? kernel_thread_helper+0x0/0x10
===

This is likely an issue with the file system on the boot media. You can verify if is the data array or not by checking which unit is being used for your volume group in the webGUI, CONFIGURATION-->Volume manager.

If it is the boot media, run the repair file system command from the console at CNTRL+ALT+X menu.
If this does not help consider re-installing the OS and/or replacing the boot drive.
===
Disk /dev/sda: 250.0 GB, 250059350016 bytes
39 heads, 62 sectors/track, 201983 cylinders
Units = cylinders of 2418 * 512 = 1238016 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1616 1953125 c W95 FAT32 (LBA)
===
06-12-2013, 11:11 PM
Gr-R

from your log files:

===
2013/06/11 20:57:21|I/O Errors detected on unit S001. To prevent data loss it is recommended to shut down the system.

2013/06/11 20:57:26|[297993.980680] Call Trace:
2013/06/11 20:57:26|[297993.980683] [<ffffffff81138131>] ? ext3_ordered_writepage+0x1e1/0x200
2013/06/11 20:57:26|[297993.980685] [<ffffffff81138131>] ? ext3_ordered_writepage+0x1e1/0x200
2013/06/11 20:57:26|[297993.980689] [<ffffffff8104590c>] ? warn_slowpath_common+0x8c/0xc0
2013/06/11 20:57:26|[297993.980692] [<ffffffff81138131>] ? ext3_ordered_writepage+0x1e1/0x200
2013/06/11 20:57:26|[297993.980695] [<ffffffff8109a8fa>] ? __writepage+0xa/0x30
2013/06/11 20:57:26|[297993.980697] [<ffffffff8109ac06>] ? write_cache_pages+0x1a6/0x350
2013/06/11 20:57:26|[297993.980699] [<ffffffff8109a8f0>] ? __writepage+0x0/0x30
2013/06/11 20:57:26|[297993.980703] [<ffffffff8117faef>] ? journal_stop+0x1af/0x290
2013/06/11 20:57:26|[297993.980706] [<ffffffff810ee975>] ? writeback_single_inode+0xc5/0x2d0
2013/06/11 20:57:26|[297993.980708] [<ffffffff810eee3c>] ? writeback_sb_inodes+0xac/0x130
2013/06/11 20:57:26|[297993.980710] [<ffffffff810ef40b>] ? writeback_inodes_wb+0xfb/0x130
2013/06/11 20:57:26|[297993.980712] [<ffffffff810ef631>] ? wb_writeback+0x1f1/0x260
2013/06/11 20:57:26|[297993.980714] [<ffffffff810ef7f5>] ? wb_do_writeback+0x155/0x160
2013/06/11 20:57:26|[297993.980717] [<ffffffff810ef837>] ? bdi_writeback_task+0x37/0x130
2013/06/11 20:57:26|[297993.980720] [<ffffffff81592695>] ? _raw_spin_lock+0x5/0x10
2013/06/11 20:57:26|[297993.980723] [<ffffffff810a7060>] ? bdi_start_fn+0x0/0x100
2013/06/11 20:57:26|[297993.980725] [<ffffffff810a70e4>] ? bdi_start_fn+0x84/0x100
2013/06/11 20:57:26|[297993.980727] [<ffffffff810a7060>] ? bdi_start_fn+0x0/0x100
2013/06/11 20:57:26|[297993.980730] [<ffffffff8105c4b6>] ? kthread+0x96/0xa0
2013/06/11 20:57:26|[297993.980734] [<ffffffff8100aa64>] ? kernel_thread_helper+0x4/0x10
2013/06/11 20:57:26|[297993.980736] [<ffffffff8105c420>] ? kthread+0x0/0xa0
2013/06/11 20:57:26|[297993.980738] [<ffffffff8100aa60>] ? kernel_thread_helper+0x0/0x10
===

This is likely an issue with the file system on the boot media. You can verify if is the data array or not by checking which unit is being used for your volume group in the webGUI, CONFIGURATION-->Volume manager.

If it is the boot media, run the repair file system command from the console at CNTRL+ALT+X menu.
If this does not help consider re-installing the OS and/or replacing the boot drive.
===
Disk /dev/sda: 250.0 GB, 250059350016 bytes
39 heads, 62 sectors/track, 201983 cylinders
Units = cylinders of 2418 * 512 = 1238016 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1616 1953125 c W95 FAT32 (LBA)
===