Bug#839672: debian-installer bug with drives in jbod
On Mon, Oct 03, 2016 at 05:30:09PM +0000, Brett Taylor wrote:
> Package: installation-reports
>
> Boot method: network
> Image version: <Full URL to image you downloaded is best>
> Date: Oct 3 2016 12pm
>
> Machine: supermicro SC826E16/MB-X9DRE-TF+
> Processor: E5-2680v2
> Memory: 36JSF2G72PZ / 36KSF2G72PZ
> Partitions:
>
> Output of lspci -knn (or lspci -nn):
[snip]
> Logic MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02)
> Oct 3 13:25:46 rx Subsystem: LSI Logic / Symbios Logic Device [1000:9363]
> Oct 3 13:25:46 rx Kernel driver in use: megaraid_sas
> Oct 3 13:25:46 rx ff:08.0 System peripheral [0880]: Intel Corporation Xeon
OK, so an LSI 3108 megaraid.
[snip]
> (0,7,0) (sda) - 480.1 GB ATA Micron_M500DC_MT
Micron M500DC SSDs.
[snip]
> Tainted: G B 3.16.0-4-amd64 #1 Debian 3.16.36-1+deb8u1
So Debian Jessie (your report didn't bother to say which debian version
you were trying to install which makes the report REALLY hard to do
anything about).
So you are using SSDs that support SED (self encrypting drive) as far
as I can tell. I found this kernel driver change from last year (which
is of course newer than the kernel in jessie):
commit 7497cde883b184ead109652f236df98d78090a90
Author: Sumit.Saxena@avagotech.com <Sumit.Saxena@avagotech.com>
Date: Mon Jan 5 20:06:03 2015 +0530
megaraid_sas: add support for secure JBOD
This patch adds support for Secure Encrypting Drives (SED) in JBOD mode:
1) If the firmware supports SED JBOD, all non read/write commands to JBODs
will be sent via firmware path, and read/write commands to JBODs will
be sent via fastpath.
2) If the firmware does not support SED JBOD, driver will fall back to the
old design, i.e. send all JBOD I/O via fastpath.
Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
Signed-off-by: Chaitra Basappa <chaitra.basappa@avagotech.com>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
I wonder if you have hit a problem with your SSDs in JBOD mode due to the
driver in 3.16 kernel in jessie not yet supporting that combination, while
almost certainly being on hardware new enough that it does support that.
Could you try booting the testing version of the installer just to see
if it survives? If it does, that would certainly point to the issue
being a problem in the megaraid driver on the older kernel in jessie.
The fact it works in non JBOD mode where the RAID hides details of the
drives certainly makes that seem possible too.
--
Len Sorensen
Reply to: