"Florian" == Florian Schmid via Toasters toasters@teaparty.net 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.
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 toasters@teaparty.net 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.
Guys, Is anyone else running into this problem with the latest MS patches breaking CIFS, especially on older OnTap versions and systems?
I can download various older releases, and I could even upgrade an old FAS8060 to a release which supposedly is fixed for this ... but the systems are out of support, but of course in production.
Anyone talk with Netapp about a one time support fee to bring some legacy systems up to snuff? Of course this seems to also just affect those people using older Domain Controllers with NTLMv1 and NTLMv2 still enabled and in use.
For those of you who haven't seen this, I've attached it here. Looks like a total cluster f*ck too... since there's so little time to address this issue.
Hello John,
I think there is a special GPO that could be enabled see https://support.microsoft.com/en-us/topic/how-to-manage-the-changes-in-netlo... in a separate OU where you could move your older Netapp clusters to "bypass" the requirements
Hope it helps
Rgds
Eric Leonard
On Sat, Jul 8, 2023 at 11:02 AM John Stoffel john@stoffel.org wrote:
Guys, Is anyone else running into this problem with the latest MS patches breaking CIFS, especially on older OnTap versions and systems?
I can download various older releases, and I could even upgrade an old FAS8060 to a release which supposedly is fixed for this ... but the systems are out of support, but of course in production.
Anyone talk with Netapp about a one time support fee to bring some legacy systems up to snuff? Of course this seems to also just affect those people using older Domain Controllers with NTLMv1 and NTLMv2 still enabled and in use.
For those of you who haven't seen this, I've attached it here. Looks like a total cluster f*ck too... since there's so little time to address this issue.
Toasters mailing list Toasters@teaparty.net https://www.teaparty.net/mailman/listinfo/toasters
-
Eric Leonard -
Florian Schmid -
John Stoffel