Yes, you are right- I am trying to open up the RAID volumes in a backup server.
The Windows versions are different, i was using Server 2012 in the crashed server and the backup server which we are trying to connect is Windows Server 2016. Would this be a cause for the issue ?
As you correctly mentioned, i am also suspecting some kind of access issue here since the RAID and all related configs are visible through MDSM.
Attaching couple of screenshots to make a clarity here. Please check if you can make out something from these. I am happy to share more details if you prefer. I am in really need of a solution, please help.
Trying to understand the situation. So you're trying to present the 2 RAID volumes, 6 and 0 to the back up server, but in Disk Management (Windows) it is showing Unallocated Space? Is both Windows the same version? Do you have a screenshot of the message?
I don't think there is any configuration issue on the storage but in Windows. But in Windows, we're unsure which configurations that we need to look at. It might be an access issue.
From MDSM's screenshot, it seems to correct. IQN status showing connected with 2 iSCSI initiators. Although, I notice that you mentioned you only have 2 RAID volumes? Screenshot on the disk management is showing more than 10 volumes, is that correct? To me it looks like a MPIO configuration issue, unsure but it could be. And yeah, the volumes are showing unallocated which is new to me. Have you tried contacting Microsoft to check if it's an issue with the OS configuration?
Most probably, if those volumes was previously formatted to NTFS, windows2016server, and windows2012server works different with NTFS deduplication and volumes won't mountable properly, or Efi partition id was changed. Easy to check if you install and run any basic DataRecovery software and check those volumes through them.
jnskjs
2 Posts
0
June 20th, 2022 00:00
Hello @DELL-Joey C ,
Thanks for the response.
Yes, you are right- I am trying to open up the RAID volumes in a backup server.
The Windows versions are different, i was using Server 2012 in the crashed server and the backup server which we are trying to connect is Windows Server 2016. Would this be a cause for the issue ?
As you correctly mentioned, i am also suspecting some kind of access issue here since the RAID and all related configs are visible through MDSM.
Attaching couple of screenshots to make a clarity here. Please check if you can make out something from these. I am happy to share more details if you prefer. I am in really need of a solution, please help.
1> iSCSI initiator connectivity stats:
2> MDSM Host Mappings
3> Disk Management Error
DELL-Joey C
Moderator
•
4.1K Posts
0
June 20th, 2022 00:00
Hi @jnskjs,
Trying to understand the situation. So you're trying to present the 2 RAID volumes, 6 and 0 to the back up server, but in Disk Management (Windows) it is showing Unallocated Space? Is both Windows the same version? Do you have a screenshot of the message?
I don't think there is any configuration issue on the storage but in Windows. But in Windows, we're unsure which configurations that we need to look at. It might be an access issue.
DELL-Joey C
Moderator
•
4.1K Posts
0
June 20th, 2022 02:00
Hi @jnskjs,
From MDSM's screenshot, it seems to correct. IQN status showing connected with 2 iSCSI initiators. Although, I notice that you mentioned you only have 2 RAID volumes? Screenshot on the disk management is showing more than 10 volumes, is that correct? To me it looks like a MPIO configuration issue, unsure but it could be. And yeah, the volumes are showing unallocated which is new to me. Have you tried contacting Microsoft to check if it's an issue with the OS configuration?
dr-kiev
1 Rookie
•
13 Posts
0
June 26th, 2022 10:00
Most probably, if those volumes was previously formatted to NTFS, windows2016server, and windows2012server works different with NTFS deduplication and volumes won't mountable properly, or Efi partition id was changed. Easy to check if you install and run any basic DataRecovery software and check those volumes through them.