(unknown)

--===============1138080808887241173==
Content-Type: message/rfc822
Content-Disposition: inline

Received: from mx2-at.ubimet.com (mx2-at.ubimet.com [141.98.226.72])
 by dormouse.teaparty.net (8.14.7/8.14.7) with ESMTP id 31H7AxF1031529
 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <[email protected]>; Fri, 17 Feb 2023 07:11:01 GMT
Authentication-Results: dormouse.teaparty.net;
 spf=pass [email protected]
 smtp.helo=mx2-at.ubimet.com
Received: from localhost (localhost [127.0.0.1])
 by mx2-at.ubimet.com (Postfix) with ESMTP id 1366E835B6
 for <[email protected]>; Fri, 17 Feb 2023 07:10:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ubimet.com;
 s=20200131mdel; t=1676617858;
 bh=xlNfFvUPlhEiJNO35KHBN1tz7oL2rDL33vodp6r4VDc=;
 h=Date:From:To:Subject:From;
 b=ko6LMfb/8wzNPSZbZj5TYzmATdZaioy7q68CSPoS5aQtnF9NGgJ41B5m44kCZutdP
 iaqJR+71GQwPx7dWx54Yh6drX8GEmkW+2kQHedT4qRsTfU93j/jE46RnW6XMh5/qvn
 SFHx7u4XspMmqe3AG436qB6T07DKPUx32+daKNryBjWcbPnSy/hkMefX3y5jpj2oSZ
 tHvzCx1o8dVAbSwkMMnD+xOgMOnnihdq69H2Zu5pYxnxUcJ3XoAGM0Vjk5YTkQrywI
 fOx632FtuK4KjWMoCgv+xwqK0Bk888bf0uasv9ILpAmA8JRZd36oqjZ4arBc9jahq6
 2n/LNl+d5oXjQ==
Received: from mx2-at.ubimet.com ([127.0.0.1])
 by localhost (mx02.dmz.dc.at.ubimet.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id OsTTIchuHXL7 for <[email protected]>;
 Fri, 17 Feb 2023 07:10:58 +0000 (UTC)
Received: from zimbra-mta01.ext.dc.at.ubimet.com (webmail-dc.at.ubimet.com
 [10.1.18.22])
 by mx2-at.ubimet.com (Postfix) with ESMTPS id 06F1A83591
 for <[email protected]>; Fri, 17 Feb 2023 07:10:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id F247480439
 for <[email protected]>; Fri, 17 Feb 2023 07:10:57 +0000 (UTC)
Received: from zimbra-mta01.ext.dc.at.ubimet.com ([127.0.0.1])
 by localhost (zimbra-mta01.ext.dc.at.ubimet.com [127.0.0.1]) (amavisd-new,
 port 10032) with ESMTP id FNl5-r0NWoJZ for <[email protected]>;
 Fri, 17 Feb 2023 07:10:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id DA9F58043E
 for <[email protected]>; Fri, 17 Feb 2023 07:10:56 +0000 (UTC)
X-Virus-Scanned: amavisd-new at zimbra-mta01.ext.dc.at.ubimet.com
Received: from zimbra-mta01.ext.dc.at.ubimet.com ([127.0.0.1])
 by localhost (zimbra-mta01.ext.dc.at.ubimet.com [127.0.0.1]) (amavisd-new,
 port 10026) with ESMTP id 3h7qpQzwnCve for <[email protected]>;
 Fri, 17 Feb 2023 07:10:56 +0000 (UTC)
Received: from zimbra-store02.ext.dc.at.ubimet.com
 (zimbra-store02.ext.dc.at.ubimet.com [10.1.18.23])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id BD75080439
 for <[email protected]>; Fri, 17 Feb 2023 07:10:56 +0000 (UTC)
Date: Fri, 17 Feb 2023 07:10:56 +0000 (UTC)
From: Florian Schmid <[email protected]>
To: toasters <[email protected]>
Message-ID: <[email protected]>
Subject: Strange errors when inserting used X302A-R5 BSAS disk into DS4246
 shelf
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.6.1]
X-Mailer: Zimbra 8.8.15_GA_4481 (ZimbraWebClient - GC109
 (Linux)/8.8.15_GA_4481)
Thread-Index: KiKJcZGrv8Rd0gJqGSfWHlvUv9e5Sw==
Thread-Topic: Strange errors when inserting used X302A-R5 BSAS disk into
 DS4246 shelf
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2
 (dormouse.teaparty.net [178.18.123.145]);
 Fri, 17 Feb 2023 07:11:01 +0000 (GMT)

Hi,

we have an old NetApp dev cluster containing a pair of FAS 8060 nodes and several DS4246 shelves with 1TB X302A-R5 BSAS disk.

I have replaced several disks already over the last years and never had issues to do so, but this time, I have tried 2 disks and both have reported the same strange issues on this shelf port.
The port of the shelf I would think, is fine, because NetApp has reported a broken spare disk on this port, but nothing special.

When I look on NetApp site, I don't find a real solution here, so I hope someone of you can help me here?

This errors I'm getting:
2/14/2023 18:24:45  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(9997).
2/14/2023 18:22:06  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:20:01  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:19:01  node-01         ERROR         scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:17:56  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:16:06  node-01         ERROR         scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:15:51  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:14:01  node-01         ERROR         scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:13:46  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:11:41  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:09:36  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:09:01  node-01         ERROR         scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:07:31  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:05:26  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:04:01  node-01         ERROR         scsi.cmd.checkCondition: Unknown device 1a.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).
2/14/2023 18:03:21  node-02         ERROR         scsi.cmd.checkCondition: Unknown device 0d.11.10: Check Condition: CDB 0x12: Sense Data SCSI:illegal request -  (0x5 - 0x20 0x0 0x0)(0).


disk show -disk 2.11.10
There are no entries matching your query.



The disk is not recognized and NetApp is throwing this errors...

Both disks have been bought from a known second hand shop, where we never had issues in the past with "used" parts.

We are running 9.7 on the cluster with a relatively new disk qualification package. I would also say, that those old disks haven't got any firmware updates for the last 3 years or so...

Thank you very much in advance.

Best regards,
Florian


--===============1138080808887241173==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Toasters mailing list
[email protected]
https://www.teaparty.net/mailman/listinfo/toasters
--===============1138080808887241173==--