From owner-freebsd-scsi@freebsd.org Thu Jan 5 13:20:41 2017 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25343CA0DA2 for ; Thu, 5 Jan 2017 13:20:41 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Received: from mel0.ec-m.fr (melout.ec-m.fr [147.94.19.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C42DD1861 for ; Thu, 5 Jan 2017 13:20:40 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Subject: Re: scsi error at SEAGATE ST1200MM0088 TT31 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=centrale-marseille.fr; s=smtp0; t=1483622432; bh=g0BiDvXKjhlYkI/e1IC9Cfupfwz1apRI9Lo9uv7wB20=; h=Subject:To:References:From:Date:In-Reply-To; b=UC19B6si7NbopFG5RUkrSnHCCuNFC0VgiLpRW9U8dTp0CY+NrprA2tUOpQbqfXuY1 4RKPiI6yfqyjQq5G6tDXUZmoEosIi4t4NkAS9iyDD9HeKAk+wNvbQCabc2fcYiq52e GzuXQfoIMpBznbGz137UDF8SxT665Mz+34ZIMxbqvbLXbc6YF66TJB5gFA+Vro7aLT EIo6Dja5Za3KpgWyf9vngVY1/N9psWo7aQm1CybVoZ3inuYIG+vvqvrXZdF8qOZJd7 jCxYNpsRWum2xFn4tC74lkFmHA3yNrlda4GWGD1cII1YGAg8ETXVTO1vx58BnOtGlV DDQ1iB79uTq3g== To: freebsd-scsi@freebsd.org References: <718e64f1-ae4b-1090-5d51-49625b3fd7ea@gmail.com> From: geoffroy desvernay Message-ID: Date: Thu, 5 Jan 2017 14:20:31 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 13:20:41 -0000 On 01/03/2017 23:19, geoffroy desvernay wrote: > Sorry for the 'me too' style, I won't bring a response here… But it > seems there is something to catch here, I'm just adding my case's details: > > These "ILLEGAL REQUEST asc:20,0" seems identical to the thread 'mpr(4) > bug ?' (2016/12/12) this wasn't a mpr(4) bug. > > Same symptoms: disks seems ok, but real use fails… Now trying to > "sg_format" them… to be continued … > It worked for me® :) just `sg_format --format daX` each drive to disable 'type 2 protection' Many thanks for the workaround baris ! > Here we have 24 SEAGATE ST2000NX0433 NS02 drives in a md1420 enclosure > connected via a sas3008 adapter. Setup tested working with debian 8 and > centos 7. > > sg_readcap --16 returns: > Read Capacity results: > Protection: prot_en=1, p_type=1, p_i_exponent=0 [type 2 protection] > Logical block provisioning: lbpme=0, lbprz=0 > Last logical block address=3907029167 (0xe8e088af), Number of logical > blocks=3907029168 > Logical block length=512 bytes > Logical blocks per physical block exponent=0 > Lowest aligned logical block address=0 > Hence: > Device size: 2000398934016 bytes, 1907729.1 MiB, 2000.40 GB > > Yours, > > On 12/22/2016 07:39 AM, baris.cavus wrote: >> I have found the same issue here: >> >> https://bugs.freenas.org/issues/14517 >> >> `sg_readcap --16 da16` reported "type 2 protection" >> >> Protection: prot_en=1, p_type=1, p_i_exponent=0 [type 2 protection] >> >> Then we formatted all disks at night and it worked >> >> sg_format --format /dev/da16 -f0 >> >> >> Normally DPICZ bit set to 1 in control mode page states it doesn't check >> the protection but this doesn't work. >> I would be happy to learn if someone find any other workaround. >> >> Thanks, >> >> >> On 21-12-2016 17:42, baris.cavus wrote: >>> I have "1.2 TB SEAGATE ST1200MM0088 TT31" on my enclosures connected >>> with lsa 3008 hba . I can't write to disks on Freebsd 10 but I can in >>> centos 7. Any idea what is the reason ?. >>> >>> (da2:mpr0:0:10:0): CAM status: SCSI Status Error >>> (da2:mpr0:0:10:0): SCSI status: Check Condition >>> (da2:mpr0:0:10:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid >>> command operation code) >>> (da2:mpr0:0:10:0): Error 22, Unretryable error >>> (da2:mpr0:0:10:0): READ(10). CDB: 28 00 00 00 02 00 00 01 00 00 >>> (da2:mpr0:0:10:0): CAM status: SCSI Status Error >>> (da2:mpr0:0:10:0): SCSI status: Check Condition >>> (da2:mpr0:0:10:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid >>> command operation code) >>> (da2:mpr0:0:10:0): Error 22, Unretryable error >>> (da2:mpr0:0:10:0): READ(10). CDB: 28 00 8b ba 08 00 00 01 00 00 >>> (da2:mpr0:0:10:0): CAM status: SCSI Status Error >>> (da2:mpr0:0:10:0): SCSI status: Check Condition >>> (da2:mpr0:0:10:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid >>> command operation code) >>> (da2:mpr0:0:10:0): Error 22, Unretryable error >>> (da2:mpr0:0:10:0): READ(10). CDB: 28 00 8b ba 0a 00 00 01 00 00 >>> (da2:mpr0:0:10:0): CAM status: SCSI Status Error >>> (da2:mpr0:0:10:0): SCSI status: Check Condition >>> (da2:mpr0:0:10:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid >>> command operation code) >>> (da2:mpr0:0:10:0): Error 22, Unretryable error >>> >> >> _______________________________________________ >> freebsd-scsi@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-scsi >> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > -- *geoffroy desvernay* C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille