Bug 10413
Summary: | (mptbase) Possible incompatibility between SATA and SAS | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Arthur (artur) |
Component: | SCSI | Assignee: | linux-scsi (linux-scsi) |
Status: | CLOSED OBSOLETE | ||
Severity: | high | CC: | alan, devzero |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.24 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Arthur
2008-04-07 04:31:47 UTC
The Distribution is not Lenny, it is Debian etch x86_64 When I connect all 5 drives to SAS, I get A LOT of the above mentioned messages during the startup and after it. Running checkarray causes a reboot. (percents completed may vary up to ten). With one drive connected to SAS I was able to complete the array check and even work for 1-2 days. I recompiled the kernel (2.6.24) with the driver given on LSI download page (mptlinux-4.00.21.00-src.tar.gz). Now it is 4.00.21 insted of default 3.06.05. All 5 hard drives are connected to SAS. host1: ioc0: fw=01.23.00.00 bios=06.12.00.00 driver=4.00.21.00 mpi=105 LSISAS1068 B1: board_name=N/A assembly=ASUSTek tracer=N/A nvdata_persistent=2b00h nvdata_default=2b00h io_delay=00 device_delay=00 debug_level=00000000h But symptoms remained the same, I still get a lot of error messages: Apr 9 13:42:31 localhost kernel: ReiserFS: dm-1: found reiserfs format "3.6" with standard journal Apr 9 13:42:31 localhost kernel: ReiserFS: dm-1: using ordered data mode Apr 9 13:42:31 localhost kernel: ReiserFS: dm-1: journal params: device dm-1, size 8192, journal first block 18, max trans len 1024, max batch 900, max co mmit age 30, max trans age 30 Apr 9 13:42:31 localhost kernel: ReiserFS: dm-1: checking transaction log (dm-1) Apr 9 13:42:31 localhost kernel: ReiserFS: dm-1: Using r5 hash to sort names Apr 9 13:43:23 localhost kernel: md: data-check of RAID array md0 Apr 9 13:43:23 localhost kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk. Apr 9 13:43:23 localhost kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for data-check. Apr 9 13:43:23 localhost kernel: md: using 128k window, over a total of 976759936 blocks. Apr 9 13:43:23 localhost mdadm: RebuildStarted event detected on md device /dev/md0 Apr 9 13:43:26 localhost kernel: mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) Apr 9 13:43:56 localhost last message repeated 79 times Apr 9 13:44:57 localhost last message repeated 73 times Apr 9 13:44:57 localhost last message repeated 8 times Apr 9 13:45:26 localhost kernel: mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, SubCode(0x3000) Apr 9 13:45:26 localhost last message repeated 12 times when I run /usr/share/mdadm/checkarray --cron --all --quiet first off, i would not recommend combining different drives or same disks via different paths into a raid volume. see http://www.howtofixcomputers.com/forums/scsi/sas-sata-arrays-one-controller-lsisas1068-17428-3.html anyhow, that doesn`t explain why you also have issues with 5 drives via sas. i would recommend asking here: LSILOGIC MPT FUSION DRIVERS (FC/SAS/SPI) P: Eric Moore M: Eric.Moore@lsi.com M: support@lsi.com L: DL-MPTFusionLinux@lsi.com L: linux-scsi@vger.kernel.org W: http://www.lsilogic.com/support S: Supported |