(unknown)

--===============3449666251849585440==
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 31K78579013475
 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <[email protected]>; Mon, 20 Feb 2023 07:08:07 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 9738183CF5;
 Mon, 20 Feb 2023 07:08:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ubimet.com;
 s=20200131mdel; t=1676876884;
 bh=h61YLqHTM3Jq1FgP51ibkXF6aRm8sK4HWRv0UnIM+0s=;
 h=Date:From:To:Cc:In-Reply-To:References:Subject:From;
 b=G/WrlxUFZKTU22Bja27Fmz/ocaZEKv85g133zNY6e+cgHR5U4j0XIVuDhlP5b+pb5
 U71/PNtuw+P+y49dHjTbhlbfkNCE218eFx0mOr7j9qm4TU2QkKjJh0JoT1BKm+z0+C
 3yzQMTgulcJ+8UbrOkjLXR5vIBtT2puoobK04gwe7S8FDM9WQ3jpNCKWyq/Jj3coxm
 V2yuPU2TecN3+co0hT7rp7wrtdl0xo0wO8+ReRzprc6lFEnSlEYz8QoeA6SMn5ivUH
 g0iY6/uChfOpgrEtRS4eDjdVJJTYIfO/VTvvukxMzCCZFTH5vEVHTxVTzq740HOuL6
 X6VmiT1uBj/JQ==
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 GqgiZHWoOWcm; Mon, 20 Feb 2023 07:08:04 +0000 (UTC)
Received: from zimbra-mta01.ext.dc.at.ubimet.com
 (zimbra-mta01.ext.dc.at.ubimet.com [10.1.18.22])
 by mx2-at.ubimet.com (Postfix) with ESMTPS id 82C7183CEA;
 Mon, 20 Feb 2023 07:08:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id DD83580501;
 Mon, 20 Feb 2023 07:08:00 +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 ohKAqUVHOuV2; Mon, 20 Feb 2023 07:07:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zimbra-mta01.ext.dc.at.ubimet.com (Postfix) with ESMTP id 9E5AF80509;
 Mon, 20 Feb 2023 07:07:59 +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 m8AMvkgukKiH; Mon, 20 Feb 2023 07:07:59 +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 7AAA080501;
 Mon, 20 Feb 2023 07:07:59 +0000 (UTC)
Date: Mon, 20 Feb 2023 07:07:59 +0000 (UTC)
From: Florian Schmid <[email protected]>
To: John Stoffel <[email protected]>
Cc: toasters <[email protected]>
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
 <[email protected]>
Subject: Re: 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.5]
X-Mailer: Zimbra 8.8.15_GA_4481 (ZimbraWebClient - GC109
 (Linux)/8.8.15_GA_4481)
Thread-Topic: Strange errors when inserting used X302A-R5 BSAS disk into
 DS4246 shelf
Thread-Index: XlpR+7UuiPgYkjD0Q6LA2XfTQdewAA==
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2
 (dormouse.teaparty.net [178.18.123.145]);
 Mon, 20 Feb 2023 07:08:08 +0000 (GMT)

Hi John,

thank you very much for your reply.

Yes, those FAS8060 are really great, unfortunately, NetApp doesn't support them anymore...

I have tried both disks, I had in this slot and both disks have produced the same errors.

I have some spares running in this shelf, so I will check, when I'm next time in Data Center, if another already running spare will work in this slot.

As far as I can remember, the former broken disk was reported, because normal spare disk maintenance has flagged it as broken. It was still recognized, when I have removed it.
So I would assume, that it was not the port, which has caused the initial failure of the disk, but this is too long ago, so I don't have logs anymore from this time.

I have 2 fully populated shelves with same disks (X302A-R5 BSAS) in the aggregate and several spares in it.


Best regards,
Florian

>>>>> "Florian" == Florian Schmid via Toasters <[email protected]> writes:

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

Those are rock solid heads for sure!  I've still got a pair in
production here. 

> 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.

How many shelves do you have?  And have you tried putting the disk
into a different slot?  

And when you say "broken spare disk on this port" are you talking
about the SAS port on the disk shelf, or about the disk slot in the
disk shelf?  

> 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.

This strongly implies to me that the physical slot in the disk shelf
is going bad, or has a bad connector.  Or that you just got a bad disk
from the vendor.  I'd have them replace it with a known good one.  

If you have another spare disk working in the system, I'd move it to
this slot and see what happens.  And of course move the un-recognized
disk there to check whether it's the shelf disk slot, or the disk
itself is bad.

> 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.

Bad disks happen.  

> 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...

We're still running 9.3... ugh.

--===============3449666251849585440==
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
--===============3449666251849585440==--