The purpose of this blog post is to provide a detailed guide on how to check RAID configuration on Windows Server 2016. RAID, which stands for Redundant Array of Independent Disks, is a data storage technology that combines multiple physical drives into a single logical unit for improved performance, data redundancy, and fault tolerance. Understanding the RAID configuration of your server is crucial for managing and troubleshooting storage issues.
In this article, we will explore different methods for checking the RAID configuration on Windows Server 2016. We will discuss the necessary steps and precautions for each method, as well as the pros and cons of using these methods. By the end of this article, you will have a comprehensive understanding of how to check RAID configuration on your server.
Video Tutorial:
What’s Needed
Before we dive into the methods for checking RAID configuration, there are a few things you will need:
- A Windows Server 2016 machine with RAID configured.
- Administrator access to the server.
- Basic knowledge of server management and storage concepts.
Once you have these prerequisites in place, you can proceed with checking the RAID configuration on your Windows Server 2016 machine.
What Requires Your Focus?
When checking the RAID configuration on your Windows Server 2016 machine, it’s important to focus on the following key aspects:
- The RAID level used: RAID can be configured in different levels such as RAID 0, RAID 1, RAID 5, etc. Each RAID level offers different benefits and trade-offs, so understanding the RAID level used on your server is crucial.
- The number and type of physical drives: RAID requires multiple physical drives to function. Make sure to identify the number and type of drives used in your RAID configuration.
- Data redundancy and fault tolerance: RAID provides redundancy and fault tolerance by storing data across multiple drives. Ensure that your RAID configuration is properly set up to provide data protection in case of drive failures.
Keeping these focus areas in mind will help you effectively manage and troubleshoot any RAID-related issues on your Windows Server 2016 machine.
Method 1: Using the RAID Controller Software
One of the most common methods for checking RAID configuration on Windows Server 2016 is by using the RAID controller software. Most servers come with built-in RAID controllers that provide an interface for managing and monitoring the RAID configuration.
To check the RAID configuration using the RAID controller software, follow these steps:
- Boot up your Windows Server 2016 machine and log in as an administrator.
- Open the RAID controller software by either accessing the BIOS settings during the boot process or via a dedicated software utility provided by the server manufacturer.
- Navigate to the RAID configuration section within the software.
- Here, you should be able to see a summary of your RAID configuration, including the RAID level, physical drives, and other relevant details.
- Take note of the RAID level, number and type of physical drives, and any other information that might be useful for troubleshooting or future reference.
| Pros | Cons |
|---|---|
| 1. Provides detailed information about the RAID configuration. | 1. Requires server reboot to access the RAID controller software. |
| 2. Allows for easy management and monitoring of the RAID configuration. | 2. Software interface may vary depending on the server manufacturer. |
| 3. Provides options for configuring RAID settings and performing maintenance tasks. | 3. Limited to servers with built-in RAID controllers. |
Method 2: Via Disk Management
Another method for checking RAID configuration on Windows Server 2016 is by using the Disk Management utility. Disk Management is a built-in Windows tool that allows you to manage and monitor the storage devices connected to your server.
To check the RAID configuration via Disk Management, follow these steps:
- Go to the Start menu and search for “Disk Management.”
- Open the Disk Management utility from the search results.
- You should see a list of all the disks connected to your server, including the RAID volumes.
- Identify the RAID volumes by their size and type.
- Right-click on a RAID volume and select “Properties.”
- In the Properties window, you will find detailed information about the RAID configuration, such as the RAID level, status, and health.
- Note down the RAID level and any other relevant information for future reference.
| Pros | Cons |
|---|---|
| 1. No server reboot required. | 1. Limited detailed information compared to RAID controller software. |
| 2. Easy access on any Windows Server 2016 machine. | 2. May not detect some RAID configurations. |
| 3. Allows for basic management and monitoring of RAID volumes. | 3. Limited to RAID volumes recognized by the Windows operating system. |
Method 3: Using Command-Line Tools
If you prefer a command-line approach, you can check the RAID configuration on Windows Server 2016 using command-line tools. These tools provide a more technical and in-depth view of your RAID setup.
To check the RAID configuration using command-line tools, follow these steps:
- Open the Command Prompt as an administrator.
- Run the command “wmic diskdrive get deviceid,model,size” to get a list of all the physical drives connected to your server.
- Note down the device ID and model of each drive.
- Run the command “wmic diskdrive get status” to check the status of each drive. Make sure all drives are in a “OK” status.
- Run the command “wmic diskdrive get deviceid,mediatype” to identify the type of each drive, whether it’s a hard disk drive (HDD) or a solid-state drive (SSD).
- Run the command “wmic diskdrive get deviceid,interfacetype” to check the interface type of each drive, such as SATA, SAS, or NVMe.
- Use the information gathered to infer the RAID configuration, such as the RAID level and number of drives.
| Pros | Cons |
|---|---|
| 1. Provides detailed technical information about the physical drives. | 1. Requires familiarity with command-line tools and commands. |
| 2. No additional software or utilities required. | 2. May not provide clear indication of RAID configuration. |
| 3. Can be used on any Windows Server 2016 machine. | 3. Limited to detecting physical drives only, may not recognize RAID volumes. |
Method 4: Via Third-Party Software
If the methods mentioned above don’t provide the desired level of information or if your server doesn’t have built-in RAID controller software, you can consider using third-party software to check the RAID configuration on your Windows Server 2016 machine.
There are several third-party software solutions available that offer advanced RAID monitoring and management features. These software solutions provide more extensive information about the RAID configuration, performance monitoring, and alerting capabilities.
The specific steps for checking the RAID configuration via third-party software will vary depending on the software you choose. However, most third-party RAID monitoring software offer intuitive interfaces and easy-to-follow instructions.
Make sure to research and choose a reputable and reliable third-party software solution that supports your RAID controller and meets your specific requirements.
| Pros | Cons |
|---|---|
| 1. Provides advanced RAID monitoring and management capabilities. | 1. Requires additional software installation and configuration. |
| 2. More detailed information about the RAID configuration and performance. | 2. May incur additional costs for purchasing the software. |
| 3. Offers more flexibility and customization options. | 3. Limited to compatibility with specific RAID controllers and software versions. |
Why Can’t I Check RAID Configuration?
There could be several reasons why you are unable to check the RAID configuration on your Windows Server 2016 machine:
1. Missing RAID controller software: If your server doesn’t have built-in RAID controller software or if the software is not installed, you won’t be able to check the RAID configuration using the method mentioned in Method 1.
2. Unsupported RAID controller: Some RAID controller software may not be compatible with Windows Server 2016 or specific versions of the operating system. Make sure to check the compatibility of your RAID controller software before attempting to check the RAID configuration.
3. Physical drive failure: If one or more of your physical drives have failed, it can affect the RAID configuration and prevent you from accessing or checking it. In this case, you will need to replace the failed drive and rebuild the RAID array before checking the configuration.
To fix these issues and check the RAID configuration, you can:
1. Install the RAID controller software: If your server doesn’t have built-in RAID controller software, you can download and install the software from the manufacturer’s website.
2. Update the RAID controller firmware: Updating the RAID controller firmware can often resolve compatibility issues and allow you to check the RAID configuration. Check the manufacturer’s website for the latest firmware version and update instructions.
3. Replace the failed drive: If you have experienced a physical drive failure, replace the failed drive with a new one of the same specifications and rebuild the RAID array according to the manufacturer’s instructions. Once the rebuild is complete, you should be able to check the RAID configuration.
Implications and Recommendations
After understanding how to check RAID configuration on Windows Server 2016, there are a few implications and recommendations to keep in mind:
- Regular monitoring: Monitoring the RAID configuration is essential for identifying potential issues and ensuring optimal performance. Make it a habit to regularly check and monitor the RAID configuration on your Windows Server 2016 machine.
- Backup and recovery: While RAID provides data redundancy, it is not a substitute for regular backups. Implement a comprehensive backup and recovery strategy to protect your data in case of catastrophic failures.
- Keep RAID controller firmware up to date: Updating the firmware of your RAID controller can improve performance, stability, and compatibility. Check the manufacturer’s website regularly for firmware updates and apply them as recommended.
5 FAQs about Checking RAID Configuration on Windows Server 2016
Q1: Can I check RAID configuration without rebooting the server?
A: Yes, you can check RAID configuration using methods like Disk Management or command-line tools without rebooting the server.
Q2: How can I identify the RAID level used in the configuration?
A: The RAID level can usually be identified through the RAID controller software, Disk Management, or third-party software solutions. These tools provide information about the RAID configuration, including the RAID level.
Q3: What should I do if I encounter a failed physical drive in my RAID configuration?
A: If a physical drive fails in your RAID configuration, replace the failed drive with a new one of the same specifications and initiate a rebuild process to restore the RAID array. Follow the manufacturer’s instructions for replacing and rebuilding a failed drive.
Q4: How often should I monitor the RAID configuration?
A: It is recommended to monitor the RAID configuration regularly, such as on a weekly or monthly basis, to identify potential issues and ensure data integrity. Additionally, monitor the configuration after any changes or updates to the server’s hardware or software.
Q5: Is RAID a substitute for regular backups?
A: No, RAID is not a substitute for regular backups. While RAID provides data redundancy and fault tolerance, it does not protect against data loss due to other factors such as accidental deletion, software corruption, or catastrophic events. Implement a comprehensive backup strategy to ensure data protection.
Final Words
Checking the RAID configuration on your Windows Server 2016 machine is essential for managing and troubleshooting storage issues. By following the methods outlined in this article, you can gain valuable insights into your RAID setup, including the RAID level, number and type of physical drives, and other relevant configuration details.
Remember to regularly monitor the RAID configuration, keep your RAID controller firmware up to date, and maintain a comprehensive backup strategy to ensure data integrity and protection. With a clear understanding of your RAID configuration, you can effectively manage and troubleshoot any storage-related challenges that may arise.
{“@context”:”https://schema.org”,”@type”:”FAQPage”,”mainEntity”:[{“@type”:”Question”,”name”:”Q1: Can I check RAID configuration without rebooting the server?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”A: Yes, you can check RAID configuration using methods like Disk Management or command-line tools without rebooting the server.”}},{“@type”:”Question”,”name”:”Q2: How can I identify the RAID level used in the configuration?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”A: The RAID level can usually be identified through the RAID controller software, Disk Management, or third-party software solutions. These tools provide information about the RAID configuration, including the RAID level.”}},{“@type”:”Question”,”name”:”Q3: What should I do if I encounter a failed physical drive in my RAID configuration?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”A: If a physical drive fails in your RAID configuration, replace the failed drive with a new one of the same specifications and initiate a rebuild process to restore the RAID array. Follow the manufacturer’s instructions for replacing and rebuilding a failed drive.”}},{“@type”:”Question”,”name”:”Q4: How often should I monitor the RAID configuration?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”A: It is recommended to monitor the RAID configuration regularly, such as on a weekly or monthly basis, to identify potential issues and ensure data integrity. Additionally, monitor the configuration after any changes or updates to the server’s hardware or software.”}},{“@type”:”Question”,”name”:”Q5: Is RAID a substitute for regular backups?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”A: No, RAID is not a substitute for regular backups. While RAID provides data redundancy and fault tolerance, it does not protect against data loss due to other factors such as accidental deletion, software corruption, or catastrophic events. Implement a comprehensive backup strategy to ensure data protection.”}}]}
Время на прочтение4 мин
Количество просмотров25K
Всем привет!
За последние годы мы привыкли что можно и нужно все мониторить, множество инструментов начиная от простых логов, заканчивая Zabbix и все можно связать. Microsoft в свою очередь тоже дала нам отличный инструмент WinRM, с помощью которого мы можем отслеживать состояние операционных систем и не только. Но как всегда есть ложка дегтя, собственно об «обходе» этой ложки дегтя и пойдет речь.
Как выше было сказано, мы имеем все необходимые инструменты для мониторинга IT структуры, но так сложилось что мы не имеем «автоматизированный» инструмент для мониторинга состояния Intel raid массивов в Windows core. Обращаю Ваше внимание на то, что речь идет об обычном «желтом железе».
Все мы знаем что есть софт от Intel, rapid и matrix storage, но к сожалению на стандартном Windows core он не работает, также есть утилита raidcfg32, она работает в режиме командной строки, умеет обслуживать в ручном режиме и показывать статус, тоже в ручном режиме. Думаю Америку не для кого не открыл.
Постоянно в ручном режиме проверять состояние raid или ждать выхода из строя сервера виртуализации не самый лучший выбор.
Для реализации коварного плана по автоматизации мониторинга Intel raid мы используем
основные инструменты:
- Powershell
- EventLog
- Raidcfg32.exe
- Вспомогательные:
- WinRM
- Rsyslog
- LogAnalyzer
Первым делом нужно установить драйвер для raid контроллера:
cmd.exe pnputil.exe -i -a [путь до *.inf]
Копируем raidcfg32.exe в c:\raidcfg32\
Проверяем корректно ли установлен драйвер:
cmd.exe C:\raidcfg32\raidcfg32.exe /stv
Если получаем состояние raid и дисков, то все ок.
Создаем источник в журнале application:
*Дальше все выполняется в powershell
New-EventLog -Source "RAID" -LogName "Application"
Выполняем запрос состояния raid, удаляем кавычки для упрощения парсинга, подключаем содержимое файла.
c:\RAIDCFG32\RAIDCFG32.exe /stv > c:\RAIDCFG32\raidcfgStatus.txt
Get-Content "c:\RAIDCFG32\raidcfgStatus.txt" | ForEach-Object {$_ -replace ('"'),' '} > c:\RAIDCFG32\raidstatus.txt
$1 = Get-Content c:\RAIDCFG32\raidstatus.txt
$2 = "$1"
Ищем ключевые слова, если одно из слов ниже будет найдено, то в файле errorRAID.txt появится значение true, это будет говорить о наличии ошибки, если совпадений не найдено, то будет записано значение false.
$2 -match "failed" > c:\RAIDCFG32\errorRAID.txt
$2 -match "disabled" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "degraded" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "rebuild" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "updating" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "critical" >> c:\RAIDCFG32\errorRAID.txt
Подключаем файл с записаными true и false, ищем в файле true, если true найдено то заменяем его на Error, заменяем false на Information.
Записывам результат в EntryType.txt
$3 = Get-Content c:\RAIDCFG32\errorRAID.txt
$4 = "$3"
$5 = $4 -match "true"
$6 = "$5"
$7 = $6 -replace "true", "Error" > c:\RAIDCFG32\EntryType.txt
$8 = $6 -replace "false", "Information" >> c:\RAIDCFG32\EntryType.txt
Подключаем содержимое файла EntryType.txt и удаляем в нем False, тем самым выводим корректный -EntryType что в свою очередь и является «Уровнем» сообщения.
Записываем в EventLog сообщение, где в случае если будут найдены ключевые слова, уровень сообщения будет Error, если не будут найдены, то Information.
$9 = Get-Content c:\RAIDCFG32\EntryType.txt
$10 = "$9"
$11 = $10 -replace "False"
Write-EventLog -LogName Application -Source "RAID" -EventID 9999 -EntryType "$11" -Message "$1"
exit
Сохраняем код в *.ps1
Создаем в планировщике задание на запуск скрипта, я запускаю задание 1 раз в сутки и при каждой загрузке.
Если будет производится сбор логов другой Windows ОС в Eventlog, то на коллекторе логов необходимо создать источник «RAID», пример есть выше.
Мы транспортируем логи в rsyslog через Adison rsyslog для Windows.
На выходе получается вот такая картинка:
UPD.
По поводу использования store space, все сервера с windows core на борту используются в филиалах, в филиале установлен только 1 сервер и для получения «бесплатного» гипервизора и уменьшения стоимости лицензии используется именно core.
для windows логов
c:\RAIDCFG32\RAIDCFG32.exe /stv > c:\RAIDCFG32\raidcfgStatus.txt
Get-Content "c:\RAIDCFG32\raidcfgStatus.txt" | ForEach-Object {$_ -replace ('"'),' '} > c:\RAIDCFG32\raidstatus.txt
$1 = Get-Content c:\RAIDCFG32\raidstatus.txt
$2 = "$1"
$2 -match "failed" > c:\RAIDCFG32\errorRAID.txt
$2 -match "disabled" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "degraded" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "rebuild" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "updating" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "critical" >> c:\RAIDCFG32\errorRAID.txt
$3 = Get-Content c:\RAIDCFG32\errorRAID.txt
$4 = "$3"
$5 = $4 -match "true"
$6 = "$5"
$7 = $6 -replace "true", "Error" > c:\RAIDCFG32\EntryType.txt
$8 = $6 -replace "false", "Information" >> c:\RAIDCFG32\EntryType.txt
$9 = Get-Content c:\RAIDCFG32\EntryType.txt
$10 = "$9"
$11 = $10 -replace "False"
Write-EventLog -LogName Application -Source "RAID" -EventID 9999 -EntryType "$11" -Message "$1"
UPD2.
В zabbix конфиг на клиенте вносим:
UserParameter=raid.status,powershell c:\raidcfg32\raidstatusZabbix.ps1
В zabbix добавляем новый элемент данных raid.status, числовой. Создаём триггер — если 0 то всё хорошо, если 1 то беда.
Скрипт ps2 немного меняется:
для zabbix
c:\RAIDCFG32\RAIDCFG32.exe /stv > c:\RAIDCFG32\raidcfgStatus.txt
Get-Content "c:\RAIDCFG32\raidcfgStatus.txt" | ForEach-Object {$_ -replace ('"'),' '} > c:\RAIDCFG32\raidstatus.txt
$1 = Get-Content c:\RAIDCFG32\raidstatus.txt
$2 = "$1"
$2 -match "failed" > c:\RAIDCFG32\errorRAID.txt
$2 -match "disabled" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "degraded" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "rebuild" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "updating" >> c:\RAIDCFG32\errorRAID.txt
$2 -match "critical" >> c:\RAIDCFG32\errorRAID.txt
$3 = Get-Content c:\RAIDCFG32\errorRAID.txt
$4 = "$3"
$5 = $4 -match "true"
$6 = "$5"
$7 = $6 -replace "true", "1" > c:\RAIDCFG32\EntryType.txt
$8 = $6 -replace "false", "0" >> c:\RAIDCFG32\EntryType.txt
$9 = Get-Content c:\RAIDCFG32\EntryType.txt
$10 = "$9"
$11 = $10 -replace "False"
$11
Появился у нас новый сервер Supermicro. На сервере установлен RAID контроллер AVAGO MegaRAID SAS 9460-8i, в котором два NVMe диска собраны в RAID 1. В качестве операционной системы у нас выступает Windows Server 2016.
Естественно, Supermicro и Windows не видят диски, а следить за железом как-то нужно. Windows видит только массив.
Для управления контроллером и дисками воспользуемся утилитой StorCLI.
StorCLI
Утилиту для управления RAID контроллерами LSI, Avago, Broadcom можно скачать с сайта https://www.broadcom.com/support. Находим по модели свой контроллер. Утилиту ищем в секции DOWNLOADS.
Скачиваю утилиту storcli. Доступна версия MR 7.19.
Это очень мощная утилита по управлению RAID контроллером. Сегодня нам понадобится минимум функционала для просмотра информации о дисках. Данную утилиту я планирую использовать для автоматизированного мониторинга за дисками сервера.
В архиве имеются версии storcli для разных операционных систем. Нас интересует папка Windows. Копирую оттуда утилиту storcli64.exe в удобную для себя директорию C:\zabbix\scripts.
Работать с утилитой следует с помощью командной строки.
storcli64.exe helpВызов справки.
storcli64.exe showДанная команда выведет детальную информацию.
C:\zabbix\scripts>storcli64.exe show
CLI Version = 007.1907.0000.0000 Sep 13, 2021
Operating system = Windows Server 2016
Status Code = 0
Status = Success
Description = None
Number of Controllers = 1
Host Name = DL-1C00
Operating System = Windows Server 2016
StoreLib IT Version = 07.2000.0200.0100
StoreLib IR3 Version = 16.14-0
System Overview :
===============
------------------------------------------------------------------------------------
Ctl Model Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth
------------------------------------------------------------------------------------
0 AVAGOMegaRAIDSAS9460-8i 8 2 1 0 1 0 Opt On 1&2 Y 3 Opt
------------------------------------------------------------------------------------
Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=Array NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled Patrol Read|DS=DimmerSwitch|EHS=Emergency Spare Drive
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit/CV
Hlth=Health|Safe=Safe-mode boot|CertProv-Certificate Provision mode
Chrg=Charging | MsngCbl=Cable Failure
Здесь мы увидим модель и состояние нашего контроллера AVAGO MegaRAID SAS 9460-8i. Видим что есть батарейка в состоянии Opt. Видим, что к контроллеру подключены два физических диска.
Получим список виртуальных дисков для контроллера:
storcli64.exe /c0 /vall showНебольшое отступление. Синтаксис команды гибкий, вы можете писать параметры со слешами двумя способами: с отступами и без отступов. При работе в командной строке я предпочитаю ставить отступы, а при написании скриптов пишу без отступов, мне так удобнее.
storcli64.exe /c0 /vall show storcli64.exe /c0/vall show
CLI Version = 007.1907.0000.0000 Sep 13, 2021
Operating system = Windows Server 2016
Controller = 0
Status = Success
Description = None
Virtual Drives :
==============
-----------------------------------------------------------------
DG/VD TYPE State Access Consist Cache Cac sCC Size Name
-----------------------------------------------------------------
0/0 RAID1 Optl RW Yes RWBD - ON 6.985 TB 7Tb_NVMe
-----------------------------------------------------------------
VD=Virtual Drive| DG=Drive Group|Rec=Recovery
Cac=CacheCade|OfLn=OffLine|Pdgd=Partially Degraded|Dgrd=Degraded
Optl=Optimal|dflt=Default|RO=Read Only|RW=Read Write|HD=Hidden|TRANS=TransportReady
B=Blocked|Consist=Consistent|R=Read Ahead Always|NR=No Read Ahead|WB=WriteBack
AWB=Always WriteBack|WT=WriteThrough|C=Cached IO|D=Direct IO|sCC=Scheduled
Check Consistency
Найден один массив RAID1 объёмом 6.985 TB в состоянии Optimal. В операционной системе это Disk 0.
Посмотрим на физические диски:
storcli64.exe /c0 /eall /sall showC:\zabbix\scripts>storcli64.exe /c0 /eall /sall show
CLI Version = 007.1907.0000.0000 Sep 13, 2021
Operating system = Windows Server 2016
Controller = 0
Status = Success
Description = Show Drive Information Succeeded.
Drive Information :
=================
----------------------------------------------------------------------------------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type
----------------------------------------------------------------------------------------------------
74:6 0 Onln 0 6.985 TB NVMe SSD N N 512B Micron_7300_MTFDHBE7T6TDF U -
----------------------------------------------------------------------------------------------------
EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|DG=DriveGroup
DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare
UBad=Unconfigured Bad|Sntze=Sanitize|Onln=Online|Offln=Offline|Intf=Interface
Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info
SeSz=Sector Size|Sp=Spun|U=Up|D=Down|T=Transition|F=Foreign
UGUnsp=UGood Unsupported|UGShld=UGood shielded|HSPShld=Hotspare shielded
CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded
UBUnsp=UBad Unsupported|Rbld=Rebuild
Вижу один NVMe диск в слоте 6 и корпусе 74. Так, а где второй диск? Не знаю как устроена структура этого контроллера, но второй диск я-таки нашёл:
storcli64.exe /c0 /sall showC:\zabbix\scripts>storcli64.exe /c0 /sall show
CLI Version = 007.1907.0000.0000 Sep 13, 2021
Operating system = Windows Server 2016
Controller = 0
Status = Success
Description = Show Drive Information Succeeded.
Drive Information :
=================
----------------------------------------------------------------------------------------------------
EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type
----------------------------------------------------------------------------------------------------
:6 1 Onln 0 6.985 TB NVMe SSD N N 512B Micron_7300_MTFDHBE7T6TDF U -
----------------------------------------------------------------------------------------------------
EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|DG=DriveGroup
DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare
UBad=Unconfigured Bad|Sntze=Sanitize|Onln=Online|Offln=Offline|Intf=Interface
Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info
SeSz=Sector Size|Sp=Spun|U=Up|D=Down|T=Transition|F=Foreign
UGUnsp=UGood Unsupported|UGShld=UGood shielded|HSPShld=Hotspare shielded
CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded
UBUnsp=UBad Unsupported|Rbld=Rebuild
Вижу второй NVMe диск тоже в слоте 6 и без корпуса. Оказывается, параметр /eall отображает все диски во каждом Enclosure, а бывают диски, которые не привязаны к корпусам, это было для меня новостью…
Есть способ отобразить все диски, нужно обратиться к дисковым группам:
storcli64.exe /c0 /dall showCLI Version = 007.1907.0000.0000 Sep 13, 2021
Operating system = Windows Server 2016
Controller = 0
Status = Success
Description = Show Drive Group Succeeded
TOPOLOGY :
========
---------------------------------------------------------------------------
DG Arr Row EID:Slot DID Type State BT Size PDC PI SED DS3 FSpace TR
---------------------------------------------------------------------------
0 - - - - RAID1 Optl N 6.985 TB dflt N N none N N
0 0 - - - RAID1 Optl N 6.985 TB dflt N N none N N
0 0 0 :6 1 DRIVE Onln N 6.985 TB dflt N N none - N
0 0 1 74:6 0 DRIVE Onln N 6.985 TB dflt N N none - N
---------------------------------------------------------------------------
DG=Disk Group Index|Arr=Array Index|Row=Row Index|EID=Enclosure Device ID
DID=Device ID|Type=Drive Type|Onln=Online|Rbld=Rebuild|Optl=Optimal|Dgrd=Degraded
Pdgd=Partially degraded|Offln=Offline|BT=Background Task Active
PDC=PD Cache|PI=Protection Info|SED=Self Encrypting Drive|Frgn=Foreign
DS3=Dimmer Switch 3|dflt=Default|Msng=Missing|FSpace=Free Space Present
TR=Transport Ready
Результат
Мы выяснили, что на сервере есть RAID1 массив из двух NVMe дисков.
Реализация нумерации корпусов и слотом странная. Кстати, в BIOS отображается с такими же EID:Slot. Утилита LSA для Windows тоже видит диски именно так. Установка последней прошивки контроллера ситуацию не изменила. Этот массив я не собирал, а получил готовую сборку вместе с сервером, так что прокомментировать этот момент не могу. Вероятно, это такая фича для NVMe дисков.
Ещё для меня стало новостью, что диски в контроллере могут быть не привязаны к Enclosure. Это привело к тому, что пришлось переписать шаблон для мониторинга LSI контроллеров в Zabbix, добавив автообнаружение именно таких дисков.
Ссылки
Управление RAID контроллером LSI (Broadcom, Avago) с помощью StorCLI в Oracle Linux
Avago MegaRAID 9460-8i — 12Gb/s SAS/SATA/NVMe контроллер
There are a few different ways that you can check the RAID configuration on a Dell server. One way is to use the OpenManage Server Administrator tool. This tool will allow you to see all of the RAID information for your server.
Another way is to use the Dell PowerEdge Expandable RAID Controller utility. This utility will also allow you to see all of the RAID information for your server. Finally, you can also check the RAID configuration by looking at the BIOS settings for your server.
- Log into the server as an administrator
- Open the System Configuration Utility (SCU)
- Select the Controller tab, and then select the RAID controller you want to check information on from the drop-down menu
- Select Properties from the Controller tasks list
- The information for that specific RAID controller will be displayed in the window, which will include information such as the controller model, BIOS version, cache size, and more
How to Check Raid Configuration in Windows Server 2019
If you manage a Windows Server 2019, at some point you’ll need to check the RAID configuration. This can be done in several ways, but the easiest is to use the Command Prompt.
First, open the Command Prompt by typing “cmd” into the search bar.
Right-click on the Command Prompt icon and select “Run as administrator.”
Next, type “diskpart” and press Enter. This will open the DiskPart utility.
Now, type “list disk” and press Enter. This will show all of the disks connected to your server. Make note of which disk is your boot disk (it will likely be Disk 0).
Type “select disk 0” and press Enter. This will select your boot disk.
Finally, type “detail disk” and press Enter.
This will provide information about your selected disk, including its RAID configuration.
How to Check Raid Configuration in Command Prompt
When it comes to configuring and checking your RAID array in Windows, the command prompt is still the best tool for the job. Although there are now some graphical tools that can be used for managing RAID arrays, they don’t provide as much information or control as the command prompt. In this article, we’ll show you how to check your RAID configuration in Windows using the command prompt.
The first thing you need to do is open the command prompt. You can do this by typing “cmd” into the search box on the Start menu and pressing Enter. Once the command prompt window opens, you need to type the following commands:
diskpart
list disk
These two commands will list all of the disks attached to your computer and their basic information.
The next step is to find out which disk is part of your RAID array. To do this, you need to look at the “Status” column for each disk. If a disk says “Online” and has a size that’s larger than 0 bytes, then it’s probably part of your RAID array.
Once you’ve identified which disks are part of your RAID array, you need to select one of them by typing its number into the command prompt followed by these two commands:
select disk 1 (or whichever number corresponds to your selected disk)
detail disk
These two commands will give you detailed information about your selected disk, including its partition style (which should say “RAW” if it’s part of a RAID array), capacity, and whether it’s healthy or not. If everything looks good so far, then congratulations! Your RAID array is properly configured and working correctly!
Most computers that come with a RAID controller also have an onboard BIOS RAID configuration utility. This is a great way to check your raid configuration without having to install any extra software. Here’s how to do it:
1. Enter the BIOS setup utility by pressing the appropriate key during boot (usually F2 or DEL).
2. Navigate to the “Boot” or “Security” tab and look for an option that says something like “RAID Configuration” or “Configure SATA as.”
3. Select the RAID mode you want to use (typically RAID 0, 1, 5, or 10) and then save your changes and exit the BIOS utility.
How to Check Raid Configuration in Dell Server Linux
Dell servers running Linux can use the “dmraid” utility to check the configuration of their RAID arrays. This can be useful if you’re troubleshooting an issue with your RAID, or if you simply want to know more about how it’s configured.
To use dmraid, first install it on your Dell server if it’s not already present.
Then, open a terminal and run the following command:
sudo dmraid -rE
This will show you information about all of the RAID arrays on your system, including the type of array, the devices that are included in each array, and the status of each array.
If you want to see detailed information about a specific array, you can use the -s option followed by the name of the array. For example, this command will show detailed information about an array called “myarray”:
How to Check Raid Configuration in Windows Server 2012 R2
In Windows Server 2012 R2, there are two ways to check your RAID configuration. The first way is to use the Disk Management tool. To do this, open the Disk Management console by going to Start > Administrative Tools > Computer Management.
Once the console opens, select “Disk Management” from the left-hand menu.
This will bring up a list of all the disks attached to your server. If you see a disk that has “RAID” in its description, then it is part of a RAID array.
You can click on any of these disks to see more information about them, including which RAID level they are using.
The second way to check your RAID configuration is to use the PowerShell Get-StorageSubSystem cmdlet. This cmdlet will give you detailed information about all storage subsystems on your server, including any RAID arrays that are configured.
To use this cmdlet, open a PowerShell window and type:
Credit: www.youtube.com
How Do You Check If the System is Configured With Raid Dell?
How do you check if the system is configured with RAID Dell?
There are a few ways that you can check to see if your Dell system is configured for RAID. One way is to look in the BIOS settings.
To do this, restart your computer and press F2 to enter the BIOS setup menu. Once in the BIOS menu, look for a section called “Drive Configuration” or something similar. This section will list all of the drives installed in your system and whether or not they are configured for RAID.
Another way to check is to use the Dell OpenManage Server Administrator tool. This tool is installed on most Dell servers and can be accessed via the web interface or through a Windows application. Once logged in, click on “Storage” and then “Logical Drive Information”.
This will show you all of the logical drives that have been created on your server, as well as their associated RAID level.
How Do I Check My Server Raid Status?
RAID, or redundant array of independent disks, is a data storage virtualization technology that combines multiple physical disk drive components into one or more logical units for the purposes of data redundancy, performance improvement, or both.
There are several different types of RAID configurations, but the most common is RAID 0, 1, 5 and 6. To check your server RAID status, you will need to use a tool called ‘mdadm’.
This tool is included in most Linux distributions and can be used to view information about all existing RAID arrays on your system.
To use mdadm to check your server RAID status:
1) Run the command ‘mdadm –detail /dev/md0’ (assuming that your RAID array is located at /dev/md0).
This will display detailed information about the array, including the devices that make up the array, their status and other important details.
2) If you want to check the status of a specific device within the array, you can use the ‘–examine’ option with mdadm. For example, running ‘mdadm –examine /dev/sda1’ will give you detailed information about that particular device within the array.
How to Check Raid Configuration in Dell Server R740?
There are a few ways that you can check the RAID configuration on your Dell Server r740. The first way is to use the OMSA (OpenManage Server Administrator) tool. This is a web-based application that you can use to manage and monitor your server.
To access OMSA, you will need to open a web browser and type in the IP address of your server. Once you have logged in, you will be able to see information about all of the components on your server, including the RAID controller.
Another way to check the RAID configuration on your Dell Server r740 is through the BIOS.
To access the BIOS, you will need to restart your server and press F2 when prompted during boot up. Once in the BIOS, look for an option called “System Configuration” or something similar. In this section, there should be a sub-section for “RAID”.
Here you will be able to see information about the RAID controller and any disks that are configured in a RAID array.
The last way to check the RAID configuration on your Dell Server r740 is by using the command line tools provided by Dell. These tools are available for download from Dell’s website.
Once downloaded and installed, these tools can be used to display information about all of the components on your server, including the RAID controller.
How Do I Access Raid Configuration?
Assuming you would like to know how to access the RAID configuration for the purposes of making changes, there are a few different ways this can be done. Many motherboards these days have what is called an on-board RAID controller. This means that there is a chip on the motherboard dedicated to handling RAID tasks.
In order to access the configuration for this type of controller, you need to enter the BIOS setup program for your computer. This is typically done by pressing a key during bootup, such as F2 or DEL. Once in the BIOS, look for an option related to RAID configuration or storage controllers.
The specific steps will vary depending on your motherboard and BIOS version, but once you find the right area, you should be able to make any desired changes to the RAID configuration.
If your motherboard does not have an on-board RAID controller, then you will need a separate hardware component in order to configure a RAID array. In this case, you will need to refer to the documentation that came with your RAID controller in order to determine how to access and change its settings.
RAID Configuration Dell Physical Server | Tech Arkit
Conclusion
This blog post provides a detailed guide on how to check the RAID configuration on a Dell server. It is a useful resource for anyone who needs to troubleshoot an issue with their server or make sure that their server is configured correctly.
RAID-массивы – это способ объединения нескольких жестких дисков в одну логическую систему для обеспечения большей производительности и отказоустойчивости. Проверка статуса RAID-массива на сервере является важным шагом для обнаружения проблем и повышения надежности хранения данных. В этой статье мы рассмотрим несколько способов проверки статуса RAID-массива.
1. Использование утилиты mdadm
Одним из способов проверки статуса RAID-массива на сервере является использование утилиты mdadm. Для этого выполните следующую команду в терминале:
sudo mdadm --detail /dev/md0
Эта команда покажет подробную информацию о RAID-массиве, такую как уровень RAID, состояние дисков и синхронизацию.
2. Использование утилиты smartmontools
Другим способом проверки статуса RAID-массива на сервере является использование утилиты smartmontools. Эта утилита позволяет проверить состояние жестких дисков, входящих в RAID-массив. Для этого выполните следующую команду:
sudo smartctl -a /dev/sda
Эта команда покажет информацию о состоянии жесткого диска, его SMART-данные и ошибки, если они есть.
3. Использование веб-интерфейса контроллера RAID
Если ваш сервер оснащен аппаратным контроллером RAID, то проверка статуса RAID-массива может быть произведена через веб-интерфейс контроллера. Для этого подключитесь к интерфейсу и просмотрите текущее состояние массива и дисков.
Важно регулярно проверять статус RAID-массива на сервере, чтобы своевременно выявлять и устранять проблемы. Это поможет избежать потери данных и обеспечить надежную работу сервера.
Надеемся, что эта статья была полезной для вас. Поддерживайте свой RAID-массив в хорошем состоянии!