Unsolved
This post is more than 5 years old
5 Posts
0
2098
December 30th, 2018 05:00
MD3800i uncertified physical disks error
Please note that we have MD3800i with below specs, but we were not able to do any configuration with error message as below, pleas
OPERATING ENVIRONMENT DATA
Client system name: DESKTOP-GV0VMB2
Client OS: Windows 10
Application version: 11.25.0G06.0026
Storage array management version: 11.25.0G06.0026
Storage array name: Unavailable
Firmware version: 08.25.14.60
Management class: devmgr.v1125api15.Manager
**************************************************
ERROR DATA
Command sent to RAID controller module in slot: 0
Host name: 192.168.129.101
IP address: 192.168.129.101
Return code: Error 101 - The operation cannot complete because either there is a problem communicating with any of the physical disks in the storage array or there are currently no physical disks connected. Please correct the problem and then retry the operation.
Operation when error occurred: PROC_setSAUserLabel
Timestamp: Dec 30, 2018 4:12:34 PM
STACK DATA
devmgr.v1125api15.sam.jal.ManagementOperationFailedException: Error 101 - The operation cannot complete because either there is a problem communicating with any of the physical disks in the storage array or there are currently no physical disks connected. Please correct the problem and then retry the operation.
at devmgr.v1125api15.sam.jal.SYMbolClient.dispatchOperation(SYMbolClient.java:554)
at devmgr.v1125api15.sam.jal.StorageArrayFacade.issueCommand(StorageArrayFacade.java:10180)
at devmgr.v1125api15.sam.jal.StorageArrayFacade.sendCommandCommon(StorageArrayFacade.java:9736)
at devmgr.v1125api15.sam.jal.StorageArrayFacade.sendCommand(StorageArrayFacade.java:9633)
at devmgr.v1125api15.sam.jal.StorageArrayFacade.setSAUserLabel(StorageArrayFacade.java:5481)
at devmgr.v1125api15.sam.configuration.RenameStorageArrayDialogPanel.performCommitAction(RenameStorageArrayDialogPanel.java:115)
at devmgr.v1125api15.shared.wizard.DialogPanel$GenericCommitTask.doTask(DialogPanel.java:3040)
at devmgr.v1125api15.shared.wizard.DialogPanel$GenericCommitTask.doTask(DialogPanel.java:3011)
at devmgr.v1125api15.shared.task.AbstractTask$1.call(AbstractTask.java:127)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at devmgr.v1125api15.shared.task.AbstractTask.run(AbstractTask.java:446)
at devmgr.v1125api15.shared.task.TaskAction$PriorityEntry.run(TaskAction.java:420)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
THREAD DATA
Thread[Reference Handler,10,system]
Thread[Finalizer,8,system]
Thread[Signal Dispatcher,9,system]
Thread[Attach Listener,5,system]
Thread[Java2D Disposer,10,system]
Thread[AWT-Shutdown,5,system]
Thread[AWT-Windows,6,system]
Thread[TimerQueue,5,system]
Thread[Swing-Shell,6,system]
Thread[AWT-EventQueue-0,6,main]
Thread[DestroyJavaVM,5,main]
Thread[SwingWorker-pool-2-thread-1,5,main]
Thread[ChangeDetector,6,main]
Thread[PreferenceStoreChangeDetector,6,main]
Thread[LogMsgThread,6,main]
Thread[Np_Link_Monitor0,6,main]
Thread[DMVGarbageCollectorThread,6,main]
Thread[RecoveryProfile-32,6,main]
Thread[AEN-33,6,main]
Thread[Timer-0,6,main]
Thread[SwingWorker-pool-2-thread-2,5,main]
Thread[Thread-49,6,main]
Thread[SwingWorker-pool-2-thread-3,5,main]
Thread[SwingWorker-pool-2-thread-4,5,main]
Thread[SwingWorker-pool-2-thread-5,5,main]
Thread[pool-6-thread-12,5,main]
Note that All disks with below warning: (indicating incompatible but when we search the compatibility matrix we found the same Disks (ST6000NM0034) is supposed to be compatible ).
Storage array: Unnamed
Component reporting problem: Physical Disk in slot 2
Status: Incompatible
Location: RAID Controller Module/Expansion enclosure 0
Component requiring service: Physical Disk in slot 2
Service action (removal) allowed: Yes
Service action LED on component: No
Firmware Inventory
| MD Storage Manager® | |
| AMW Version: | 11.25.0G06.0026 |
| Report Date: | Sun Dec 30 15:52:18 AST 2018 |
| Storage Array | |
| Storage Array Name: | Unnamed |
| Current Package Version: | 08.25.14.60 |
| Current NVSRAM Version: | N2701-825890-004 |
| Staged Package Version: | None |
| Staged NVSRAM Version: | None |
| RAID Controller Modules | |
| Location: | Enclosure 0, Slot 0 |
| Current Package Version: | 08.25.14.60 |
| Current NVSRAM Version: | N2701-825890-004 |
| Board ID: | 2701 |
| Sub-Model ID: | 219 |
| Location: | Enclosure 0, Slot 1 |
| Current Package Version: | 08.25.14.60 |
| Current NVSRAM Version: | N2701-825890-004 |
| Board ID: | 2701 |
| Sub-Model ID: | 219 |
| Power Supplies | |
| Location: | Enclosure 0 Left |
| Firmware Version: | 01.00.05 |
| Location: | Enclosure 0 Right |
| Firmware Version: | 01.00.05 |
| Physical Disk |
| Enclosure, Drawer, Slot: | Manufacturer: | Product ID: | Physical Disk Type: | Capacity: | Physical Disk firmware version: | FPGA Version: (SSD only) |
| Enclosure 0, Slot 0 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 1 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 2 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 3 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E0B1 | Not Available |
| Enclosure 0, Slot 4 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 5 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 6 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 7 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 8 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 9 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 10 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E005 | Not Available |
| Enclosure 0, Slot 11 | SEAGATE | ST6000NM0034 | Serial Attached SCSI (SAS) | 5,589.029 GB | E0B1 | Not Available |


DELL-Josh Cr
Community Manager
•
9.7K Posts
•
43.3K Points
0
December 31st, 2018 07:00
Hi,
Were these drives working previously? Are they Dell drives?
M. AbuJubbah
5 Posts
0
December 31st, 2018 23:00
Hello Josh
Thanks for your reply,
Kindly know that this is a new storage , and this was the first setup for it.
I cannot see any Dell label on the drives as below photo for one of them.
What do you think?
M. AbuJubbah
5 Posts
0
January 3rd, 2019 09:00
Dear Dell support
Kindly advise for above issue?
DELL-Josh Cr
Community Manager
•
9.7K Posts
•
43.3K Points
0
January 3rd, 2019 11:00
It may not be a Dell drive, it doesn’t show that it is on there. Which could be why it doesn’t work. It should have the M2SE firmware https://downloads.dell.com/manuals/common/dell_powervault_md_series_support_matrix.pdf page 25
M. AbuJubbah
5 Posts
0
January 3rd, 2019 21:00
Thanks Josh
Do you think if we connect the drives to any server then update drivers firmware to M2SE then connect back to storage would work ?
As we tried to update firmware while connected to storage but there were no communication with disks.
DELL-Josh Cr
Community Manager
•
9.7K Posts
•
43.3K Points
0
January 4th, 2019 10:00
you can try it, but we typically require the drives to come from us.