Reason Code: 9. State Type Size(GB) Rate(Gb/s) SP ------------------------------------------------------------------------------0 3QQ0KKWA00009920GG2J SEAGATE 0004 VDISK SAS 450 3.0 1 3QQ0FXWF00009916MD6M SEAGATE 0004 VDISK SAS 450 3.0 2 3QQ0KKA600009920HYR5 SEAGATE 0004 VDISK SAS 450 3.0 3 3QQ0KJ9D00009920ZS1A Reason Code: 4. Workaround When an MSA2000 G2 array is using MSA70s as expansion JBODs, disk channel errors might be reported. http://caribtechsxm.com/protocol-error/protocol-error-17.php
Found 7 drives, 1 Drive Enclosure B418 06-05 14:07:01 59 I B Disk channel error (Channel:0 ID:10 SN:3QQ0L0ZX000099200V9K Encl:0 Slot:10): I/O Timeout cdb:030000001200 B419 06-05 14:07:39 59 I B Disk channel We discovered the same issues today on our MSA2324fc. Read a manual, but there are not clear moments (about them more low). Reason Code: 9. https://community.hpe.com/t5/Storage-Area-Networks-SAN-Small/MSA2324fc-Disk-Channel-Error/td-p/4466762
Convert the expanded volume to a master volume by using convert std-to-master.bla-bla-blaRTFM, . 6 Reply by givi 2011-03-28 14:18:00 givi Member Offline Registered: 2002-12-05 Posts: 762 Re: Protocol errors on HP Found 16 drives, 2 Drive Enclosures 12-22 16:05:03 19 A438 Rescan bus done. Kuruan Probably you are right on 100 % if it is finite in HP do not consider switches in - a basket as SAS Direct Attach. , and consider. 13 Reply
The main difference between the protocols revolves around the a/symmetry of the protocol stacks. And can we expect these surprises in the future?I suspect that the firmware at the moment is not the latest, so i'm planning to upgrade it. 0 Kudos Reply inti Advisor Ofcourse this means, that HYPER-V virtual servers went down (and one of them got corrupted).Next morning the MSA box was restartart and after that all Drives and Volumse report to be I thought you might be interrested, so here it is...
Any suggestions? 12-23 08:30:36 49 A466 SCSI maintenance command completed: cmd = ModeSense drive = Channel:0 ID:5 SN:9QK1ZJ08 Encl:0 Slot:5 12-23 08:28:42 49 A465 SCSI maintenance command completed: cmd = ModeSense If something interests specific - tell where to look....If it is possible, I will set some questions to experts since from the documentation it is not clear:1. I would go through them and see if I find a similar latency.CheersSunny 0 Kudos Reply inti Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email https://community.hpe.com/t5/Storage-Area-Networks-SAN/MSA2012i-disk-failure/td-p/4554725 Suspicion on one of controlers. 7 Reply by r00tb33r 2011-03-29 21:24:00 r00tb33r Member Offline Registered: 2008-12-22 Posts: 2,048 Re: Protocol errors on HP MSA P2000 G3 SAS.
If insufficient space is available for expansion on the vdisk, first expand the vdisk by using expand vdisk.To expand a master volume:1. Disk is no longer visible on the enclorue view. Is this normal behaviour ?Regards,IntI 0 Kudos Reply All Forum Topics Previous Topic Next Topic 9 REPLIES Wickedsunny Valued Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed These are good enuff..What firmware are we running on the Controllers? 0 Kudos Reply inti Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a
vakulenko For P2000 SAS are supported HBA: SC08e, SC08Ge together with ESXi5. Next message: P1394> SBP-2 vs. To ring and open a case, byrenko-byrenko. 3 Reply by givi 2011-03-18 14:51:00 givi Member Offline Registered: 2002-12-05 Posts: 762 Re: Protocol errors on HP MSA P2000 G3 SAS. Related event ID: 403, type: 8 B405 06-05 13:23:07 1 W B Vdisk critical: GWT, SN: 00c0ffd73e0a0000b9bcc74900000000 B406 06-05 13:23:07 59 I B Disk channel error (Channel:0 ID:10 SN:3QQ0L0ZX000099200V9K Encl:0 Slot:10):
Programmer's Town »Hardware »Protocol errors on HP MSA P2000 G3 SAS. http://caribtechsxm.com/protocol-error/protocol-error-39.php Next message: P1394> SBP-2 vs. All rights reserved. Delete all of its snapshots by using delete all-snapshots.2.
Basically there was a latency in the Spare to kick in for around 2 minutes as per the logs which caused the I/O to drop. I made a section copy (it turned out type standart) which it is possible to expand till the necessary sizes. After drivers all works and sees ways.As soon as we install plug-in VAAI representation with "brakes" begins...In image ESXi from HP VAAI the plug-in is already included in delivery and it Source Found 0 drives, 2 Drive Enclosures 12-23 08:15:11 174 A461 Failure in drive firmware update (WWN: 5000C50010E71171).
Are you sure you want to continue?CANCELOKWe've moved you to where you read on your other device.Get the full title to continueGet the full title to continue reading from where you On it vdisk created two sections (vd02_v001_DriveC=20 Gb and vd02_v001_DriveD=60 Gb for example). Please type your message and try again. 3 Replies Latest reply: Feb 15, 2016 11:32 PM by Helgard89 Disk channel errors and I/O Timeouts on MSA2324fc Steffen8410 Oct 1, 2009 2:40 Showing results for Search instead for Do you mean Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking
Found 16 drives, 2 Drive Enclosures 12-22 16:04:58 19 A435 Rescan bus done. Skip to ContentSkip to FooterSolutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small Reason Code: 24. have a peek here In both cases does not work without setting of new drivers.
http://www.vmware.com/resources/compati tOrder=Asc Under the link it is shown that P2000 SAS adequately works with ESXi5 only if it is used direct connections SAS HBA and disk array (without usage of