现有一台ubuntu18版本的电脑，

原网络拓扑是出口两台防火墙主备部署，下各接一台交换机，口字型的网络，防火墙上两个网口聚合

通过lsblk或者fdisk -l发现硬盘还有部分空间未分配使用，现需将未分配的空间加到/根分区上。

在windows 2012中安装client5.1会出现这样的报错，内部错误 28173、2146498298：

这是因为windows 2012中默认没有安装

通常情况下可以使用fdisk、df等命令查看硬盘的分区情况以及当前已使用空间大小、剩余空间大小等信息。但是如果要查看硬盘的硬件信息如 硬盘型号、序列号、已运行时间等信息该用什么工具查看呢？

在Linux下可以使用hdparm工具查看硬盘的相关信息或对硬盘进行测速、优化、修改硬盘相关参数设定。我主要常用这个工具来测试硬盘速度。

hdparm(hard disk parameters)
功能说明：显示与设定硬盘的参数。

该命令用来获取或设置SATA/IDE设备的参数。注意了，既可以获取也可以设置，所以使用这个命令的时候务必要小心。当然我们只是为了获取查看硬盘信息，故不会对硬盘及系统造成什么危害。通常会配合 -i 或 -I（大写的i） 选项来取得硬盘的硬件信息。用法如下：

2.常用指令
a.安全擦除
hdparm –user-master u –security-set-pass PASSWORD /dev/sda 设置密码
hdparm –user-master u –security-erase PASSWORD /dev/sda 安全擦除
类似安全擦除：
hdparm –yes-i-know-what-i-am-doing –sanitize-crypto-scramle /dev/sdx
hdparm –yes-i-know-what-i-am-doing –sanitize-status /dev/sdx
b.设置硬盘容量(硬盘必须直连服务器，通过raid卡无法执行此项指令）
yum install sg3_utils.x86_64
sg_readcap /dev/sdb
hdparm -N VP –yes-i-know-what-i-am-doing /dev/sdb （VP： certain LBA blocks）
c.解锁
hdparm –user-master u –security-set-pass PASSWORD /dev/sda
hdparm –user-master u –security-unlock PASSWORD /dev/sda
hdparm –user-master u –security-disable PASSWORD /dev/sda
d.升级固件版本
hdparm –fwdownload /root/Desktop/xxx.bin –yes-i-know-what-i-am-doing –please-destroy-my-drive /dev/sdc
————————————————

hdparm -I /dev/sda

语法：hdparm [-CfghiIqtTvyYZ][-a <快取分区>][-A <0或1>][-c ][-d <0或1>][-k <0或1>][-K <0或1>][-m <分区数>][-n <0或1>][-p ][-P <分区数>][-r <0或1>][-S <时间>][-u <0或1>][-W <0或1>][-X <传输模式>][设备]

参数说明：

-a<快取分区> 设定读取文件时，预先存入块区的分区数，若不加上<快取分区>选项，则显示目前的设定。
-A<0或1> 启动或关闭读取文件时的快取功能。
-c 设定IDE32位I/O模式。
-C 检测IDE硬盘的电源管理模式。
-d<0或1> 设定磁盘的DMA模式。
-f 将内存缓冲区的数据写入硬盘，并清楚缓冲区。
-g 显示硬盘的磁轨，磁头，磁区等参数。
-h 显示帮助。
-i 显示硬盘的硬件规格信息，这些信息是在开机时由硬盘本身所提供。
-I 直接读取硬盘所提供的硬件规格信息。
-k<0或1> 重设硬盘时，保留-dmu参数的设定。
-K<0或1> 重设硬盘时，保留-APSWXZ参数的设定。
-m<磁区数> 设定硬盘多重分区存取的分区数。
-n<0或1> 忽略硬盘写入时所发生的错误。
-p 设定硬盘的PIO模式。
-P<磁区数> 设定硬盘内部快取的分区数。
-q 在执行后续的参数时，不在屏幕上显示任何信息。
-r<0或1> 设定硬盘的读写模式。
-S<时间> 设定硬盘进入省电模式前的等待时间。
-t 评估硬盘的读取效率。
-T 平谷硬盘快取的读取效率。
-u<0或1> 在硬盘存取时，允许其他中断要求同时执行。
-v 显示硬盘的相关设定。
-W<0或1> 设定硬盘的写入快取。
-X<传输模式> 设定硬盘的传输模式。
-y 使IDE硬盘进入省电模式。
-Y 使IDE硬盘进入睡眠模式。
-Z 关闭某些Seagate硬盘的自动省电功能。

hdparm常用参数使用举例：

1、显示硬盘的相关设置：
[root@oracle ~]# hdparm /dev/sda
/dev/sda:
IO_support = 0 (default 16-bit)
readonly = 0 (off)
readahead = 256 (on)
geometry = 19929［柱面数］/255［磁头数］/63［扇区数］, sectors = 320173056［总扇区数］, start = 0［起始扇区数］

2、显示硬盘的柱面、磁头、扇区数：
[root@oracle ~]# hdparm -g /dev/sda
/dev/sda:
geometry = 19929［柱面数］/255［磁头数］/63［扇区数］, sectors = 320173056［总扇区数］, start = 0［起始扇区数］

3、测试硬盘的读取速度：

[root@oracle ~]# hdparm -t /dev/xvda

/dev/xvda:
Timing buffered disk reads: 422 MB in 3.01 seconds = 140.20 MB/sec
[root@oracle ~]# hdparm -t /dev/xvda

/dev/xvda:
Timing buffered disk reads: 408 MB in 3.01 seconds = 135.59 MB/sec
[root@oracle ~]# hdparm -t /dev/xvda

/dev/xvda:
Timing buffered disk reads: 416 MB in 3.01 seconds = 138.24 MB/sec

4、测试硬盘缓存的读取速度：

[root@oracle ~]# hdparm -T /dev/xvda

/dev/xvda:
Timing cached reads: 11154 MB in 1.98 seconds = 5633.44 MB/sec
[root@oracle ~]# hdparm -T /dev/xvda

/dev/xvda:
Timing cached reads: 10064 MB in 1.98 seconds = 5077.92 MB/sec
[root@oracle ~]# hdparm -T /dev/xvda

/dev/xvda:
Timing cached reads: 10600 MB in 1.98 seconds = 5351.73 MB/sec


5、检测硬盘的电源管理模式：
[root@oracle ~]# hdparm -C /dev/sda
/dev/sda:
drive state is: standby [省电模式]

6、查询并设置硬盘多重扇区存取的扇区数，以增进硬盘的存取效率：
[root@oracle ~]# hdparm -m /dev/sda
[root@oracle ~]# hdparm -m 参数值为整数值如8 /dev/sda 附：硬盘坏道修复方法
检查：smartctl -l selftest /dev/sda
卸载：umount /dev/sda*
修复：badblocks /dev/sda

On an HPE Gen8-series or HPE ProLiant Gen9-series servers with HPE Integrated Lights-Out 4 (iLO 4), the NAND flash device may not initialize or mount properly, which may cause a variety of symptoms, which are listed below:

AHS Errors

• AHS Logs display a blank date when performing the following:
  “Select a range of the Active Health log in days From: _______ To:_________”
  AHS file system mount may fail with (I/O Error) or (No Such Device).
• The HP Active Health System (AHS) Logs are unable to be downloaded. AHS Data is not available due to a filesystem error.
• The iLO Diagnostic tab will display the following error message: “Embedded media manager failed initialization” or “The AHS file system mount failed with (No such device) or “The AHS file system mount failed with (I/O error)” or “Controller firmware revision 2.09.00 Could not partition embedded media device.”
• Unable to download AHS log and “bb_dl_disabled” is displayed.

Embedded Media Errors

• Controller Firmware Version 2.09.00 may fail to restart.
• Unable to partition Embedded media device.
• Embedded media manager may fail initialization.

Intelligent Provisioning Errors

• Intelligent Provisioning will not execute when selecting F10.

OneView Errors

• Remote Insight/Integrated Lights-Out Self-Test Error 8192.
• Unable to register this HP OneView instance with iLO: There was a problem with posting a command to the iLO.
• Unable to register this HP OneView instance with iLO: The iLO initialization was unable to complete.
• Unable to determine if this server hardware is being managed by another management system. Received an error from iLO <ip address of iLO> with Error: Blob Store is not yet initialized. and Status: 126

SCOPE

Any HPE ProLiant Gen8-series or HPE ProLiant Gen9-series server running iLO 4.

RESOLUTION

The resolution for this issue may take several steps that need to be completed in the order specified below.

OVERVIEW

Step 1) Upgrade the iLO 4 firmware to version 2.61
Step 2) Perform a NAND format
Step 3) Check the iLO status If the iLO status is normal, then skip to Step 6 If the iLO status is still degraded, continue to Step 4
Step 4) Schedule downtime; AC power-cycle and repeat the NAND format
Step 5) Check the iLO status If the iLO status is normal, continue to
Step 6 If the iLO status is still degraded, then skip to Step 7
Step 6) Perform these final steps if the system board does not need to be replaced: Reboot the server; reinstall IP; and refresh the server in OneView (if server is managed by OneView)
Step 7) If steps 1-4 did not resolve the degraded iLO, replace the system board.

Note: The 2.61 iLO 4 firmware is a critical update. As such, HPE requires users to update to this version immediately. Install this update to take advantage of significant improvements to the write algorithm for the embedded 4 GB non-volatile flash memory (also known as the NAND). These improvements increase the NAND lifespan.

Additional considerations before performing a NAND format

A NAND format can be performed while the server is online in most cases.

Exception: For ESXi hosts booting from the Embedded SD Card – it isstrongly recommended to perform the NAND format with the ESXi OSshutdown.This recommendation also applies when updating the iLO 4firmware or resetting the iLO for ESXi hosts booting from the Embedded SDCard

A server AC power removal may be required (prior to the NAND format) in order for the NAND format to be successful. This can be accomplished for ML or DL servers by shutting down the server and disconnecting the power cables for a few seconds. For blade servers, an E-fuse can be accomplished by logging into the OA CLI and typing “reset server #” where “#” is the bay number of the blade.

An AuxPwrCycle feature was added in iLO 4 firmware version 2.55 so that the equivalent of an AC power removal can be performed remotely on a server.
Refer to Customer Notice “HPE Integrated Lights Out (iLO) 4 – RESTful Command to Allow an Auxiliary Power-Cycle Is Available in Firmware Version 2.55 (and Later)” located at the following URL:

Required steps to perform after a successful NAND format

• If the server is powered on when performing the NAND format, a server reboot is required after a successful NAND format. This reboot repopulates the RIS and RESTful data on the server during the next server POST with iLO 4 firmware version 2.53 or newer installed. If iLO 4 firmware version 2.50 or older is installed, connect to the iLO CLI (using putty) and use the following command “oemHP_clearRESTapistate” before rebooting the server to repopulate the RIS and RESTful data on the server.
• Reinstall Intelligent Provisioning (IP) to ensure that it is working properly and reported as installed in the iLO 4 GUI “System Information – Firmware Information” page.
• If using OneView: After the server is rebooted (to repopulate the RIS and RESTful data on the server), perform a server refresh in OneView; any existing errors in OneView will need to be marked as cleared after the refresh.

Detailed steps

Step 1. Upgrade the iLO 4 firmware to version 2.61. To download the firmware. The latest version of the iLO 4 firmware is available as follows:

Note: For ESXi hosts booting from the Embedded SD Card (Gen8/Gen9)- it is strongly recommended to perform this step with the ESXi OS shutdown.

1. Click the following link:
   https://support.hpe.com/hpesc/public/home
2. Enter a product name (e.g., “DL380 Gen9”) in the text search field and wait for a list of products to populate. From the products displayed, identify the desired product and click on the Drivers & software icon to the right of the product.
3. From the Drivers & software dropdown menus on the left side of the page:
   • Select the Software Type – (e.g. Firmware)
   • Select the Software Sub Type – (e.g. Network)
   • For further filtering if needed – Select the specific Operating System from the Operating Environment.
4. Select the latest release of Firmware – Lights-Out Management iLO 4 firmware version 2.61 (or later). Note: To ensure the latest version will be downloaded, click on the Revision History tab to check if a new version of the firmware/driver is available.
5. Click Download.

Step 2. Perform NAND format using one of the methods detailed in the customer advisory: using one of the methods detailed in the customer advisory: HPE Integrated Lights-Out 4 (iLO 4) – How to Format the NAND Used to Store AHS logs, OneView Profiles, and Intelligent Provisioning
Find the document at:

Note: iLO 4 firmware version 2.44 (or later) is required to format the NAND using the following steps.

Step 3. Check the iLO status using the options available in the customer advisory: HPE Integrated Lights-Out 4 (iLO 4) – How to Format the NAND Used to Store AHS logs, OneView Profiles, and Intelligent Provisioning (find the document at the link in Step 2).

If the iLO status is normal based on the above criteria, then skip to Step 6 If the iLO status is still degraded, continue to Step 4

Step 4. If the iLO status is still degraded, perform the following steps:

a) Schedule a maintenance window
b) Shut down the server
c) Perform an E-fuse (server blade) or AC Power Pull (DL / ML series servers) d) Perform the NAND format again (refer to the instructions in Step 2 above)

Step 5. Check the iLO status (refer to the instructions in Step 3 above)
If the iLO status is normal, continue to Step 6
If the iLO status is still degraded, then skip to Step 7

Step 6. Perform these final steps after the NAND format is successful:
a) Reboot the server
b) Reinstall Intelligent Provisioning (see additional details below)
c) If the server is managed by HPE OneView, perform a server refresh to bring the server back under management.

Note: Any existing errors in OneView will need to be marked as cleared after the refresh.

Step 7. If steps 1-4 did not resolve the degraded iLO, contact HPE support to arrange a system board replacement. Follow these steps to complete the remediation:

a) Open an HPE support case to arrange for a replacement system board / arrange a maintenance window
b) During the maintenance window, shutdown the server
c) Unassign the OneView profile (if the server is under OneView management)
d) Replace the system board
e) Enter Server Model and Serial Number via RBSU
f) Update to iLO 4 firmware 2.61 (or later)
g) Check iLO status (refer to Step 3 above)
h) Reassign the OneView profile (if the server is under OneView management)

Note: Any existing errors in OneView will need to be marked as cleared after the OneView profile is applied.

If additional assistance is needed, contact HPE support and reference Advisory a00019495en_us as follows:

Click on the following URL to locate the HPE Customer Support phone number in your country:

https://h20195.www2.hpe.com/v2/Getdocument.aspx?docname=A00039121ENW .

OneView Considerations

OneView relies on the NAND to be accessible to perform many operations such as adding a new server or applying a profile. Because of this there are several things that need to be understood when dealing with this issue in an OneView environment.

1. OneView interaction with the NAND – OneView uses a portion of the NAND called the iLO blob store. If the blob store is not accessible, adding a server to OneView or assigning a profile to the server cannot be completed.
2. Impact of an inaccessible NAND when managed by OneView – If the NAND becomes inaccessible after the server was added in OneView, there are several things that can cause an outage:
   1. E-fuse – If an E-fuse reset is performed, the server will not be able to be brought back under management until the NAND issue is remediated and this will cause an unexpected outage.
   2. Server is removed and reinserted – This would essentially be the same as performing an E-fuse, so the same information in the E-fuse section applies here.
   3. Un-assign a server profile – If a server profile is unassigned, the server profile will not be able to be reassigned until the NAND issue is remediated.
3. Migration from Virtual Connect to OneView – If an enclosure is migrated from Virtual Connect and a server has an inaccessible NAND, that server will not be able to be added properly until the NAND issue is remediated. If an in-service migration is attempted on a server with an inaccessible NAND, an unexpected outage will occur. Reference advisoryhttps://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c05384185for more detail.
4. Formatting of the NAND – The NAND format wipes the iLO blob store that is used by OneView. It is important to issue a server refresh after a successful NAND format to recover the blob that OneView uses.

Reinstalling Intelligent Provisioning Considerations

There are online and offline options for reinstalling Intelligent Provisioning

• Intelligent Provisioning can be reinstalled online if the server is running Windows (HPE ProLiant Gen8-series servers/HPE ProLiant Gen9-series servers only) or Linux (HPE ProLiant Gen8-series servers/HPE ProLiant Gen9-series servers). The available online Windows packages are older versions of Intelligent Provisioning.
• Intelligent Provisioning must be reinstalled offline if the server is running VMware (HPE ProLiant Gen8-series servers/HPE ProLiant Gen9-series servers).
• The Intelligent Provisioning software download links are provided below. Intelligent Provisioning versions
• HPE ProLiant Gen8-series servers are only supported with Intelligent Provisioning 1.x
• ” HPE ProLiant Gen9-series servers are only supported with Intelligent Provisioning 2.x

Note: Intelligent Provisioning version 3.x is for HPE ProLiant Gen10-series servers only.

Offline method considerations:

• Run the Intelligent Provisioning Restore Media to restore the Intelligent Provisioning data. Instructions to restore Intelligent Provisioning are as follows:
• Instructions to create a bootable DVD with the IP image are provided on the HPE Intelligent Provisioning recovery media download site under the Installation Instructions tab.

Reference:
https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_170e0ac3cb6e4439bf313f137a#tab3

Note: The DVD can be used multiple times.

Please note the Intelligent Provisioning Recovery Media DVD may be remotely mounted using HPE Integrated Lights-Out 4 (iLO 4) Virtual Media functionality, in order to reinstall Intelligent Provisioning. Additional information is available in the HPE iLO 4 User Guide at the following URL regarding how to mount an ISO image (federated or un-federated) and perform basic virtual media operations. Reference Pages 189 and 223-237:

HPE iLO 4 User Guide:
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03334051-16

In addition, it is possible to write a script that utilizes HPE Integrated Lights-Out 4 (iLO 4) to reinstall Intelligent Provisioning on multiple servers. HPE Lights-Out management processors support an advanced scripting interface for group configuration and server actions. Scripts would need to be customized for the specific environment and task. Sample scripts are available for customers to reference at the following URL: HPE Lights-Out XML Scripting Sample for Windows: https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_459b8adc29c04317ad1d6a6752

Intelligent Provisioning software download links

HPE ProLiant Gen8-series servers are only supported with Intelligent Provisioning 1.x
HPE ProLiant Gen9-series servers are only supported with Intelligent Provisioning 2.x

a.) Linux RPM located at the following URLs: For HPE Gen8-series servers: http://downloads.linux.hpe.com/SDR/repo/ip/rhel/current/x86_64/gen8/

For HPE Gen9-series servers: http://downloads.linux.hpe.com/SDR/repo/ip/rhel/current/x86_64/gen9/firmware-intelligentprovisioning-ip-2.71-1.1.x86_64.rpm

b.) The Windows files are located at the following URLs:

For HPE ProLiant Gen8-series servers: Intelligent Provisioning for Microsoft Windows 64-bit Operating Systems 1.64.0.0 (2 Mar 2017) cp031302.exe https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_01b900175afc4ae68be6c87b39
For HPE ProLiant Gen9-series servers: Intelligent Provisioning for Windows x64 2.50.0.0(6 Jan 2017) cp031091.exe https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_b031497eafd94b9ea2156cdef6

c) ISO images (e.g. for VMware) on Hewlett Packard Enterprise Support Center located at the following: https://support.hpe.com/hpesc/public/home/driverHome?sp4ts.oid=1008862660

For HPE ProLiant Gen8-series servers: Intelligent Provisioning Recovery Media, version 1.70(9 Oct 2017)
For HPE ProLiant Gen9-series servers: Intelligent Provisioning for Gen9 Servers, version 2.70(b)(28 Feb 2018)