hp dl388 install linux 无法识别raid,HP Proliant DL580 G5安装centos7 x64无法识别阵列卡问题...

本文主要是介绍hp dl388 install linux 无法识别raid,HP Proliant DL580 G5安装centos7 x64无法识别阵列卡问题...,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

1、进入安装光盘,用上下键选择安装centos——Install Centos7(注意不可按Enter键),如图:

b76cc125408810cec21dc1d61bade787.png

2、按Tab键,对安装进行额外配置,在屏幕最下方会显示如下字样:

03d192a3e611e31e401aebefcca06414.png

3、在额外配置的命令行上添加配置: hpsa.hpsa_simple_mode=1 hpsa.hpsa_allow_any=1,如图所示:

56d04fcbb4d4ca019831bacd26f9e158.png

4、按回车继续安装

经过以上几步,安装程序即可识别出HP服务器的硬盘。

参考:

http://serverfault.com/questions/611182/centos-7-x64-and-hp-proliant-dl360-g5-scsi-controller-compatibility

https://www.centos.org/forums/viewtopic.php?f=49&t=47011

So the HP RAID controller driver from around 2001 to ~2009 was the CCISS driver. There was a transition to the HPSA driver at some point, moving the Smart Array controller support back into the regular SCSI subsystem versus the dedicated block driver...

HP servers from the G1 to G5 era used the CCISS driver. On newer operating systems (EL6 and forward), HP ProLiant G6 and newer systems made use of the HPSA driver.

It turns out that RHEL7 removes the old CCISS module. Your fix in this case, since the Smart Array P400 controller in your G5 server isn't recognized, is to force the HPSA driver to load your older controller. Do this with:

hpsa.hpsa_allow_any=1

As a module parameter...

From the man page.

hpsa_allow_any=1: This option allows the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not explicitly known to the driver. This allows newer hardware to work with older drivers. Typically this is used to allow installation of operating systems from media that predates the RAID controller, though it may also be used to enable hpsa to drive older controllers that would normally be handled by the cciss(4) driver. These older boards have not been tested and are not supported with hpsa, and cciss(4) should still be used for these.

EDIT

This is a much more involved process than expected. You need to add that string to the module load parameters.

The official word is that the older controllers are just no longer supported. While you can get it running, it's less-than-ideal. So I'd probably stay away from EL7 for now. There will likely be a workaround, since there's an existing install base of these servers...

⁠kernel component, BZ#1061210 When the hpsa_allow_any option is used, the hpsa driver allows the use of PCI IDs that are not listed in the driver's pci-id table. Thus, cards detected when this option is used, are not supported in Red Hat Enterprise Linux 7.

⁠kernel component, BZ#975791

The following cciss controllers are no longer supported:

◦ Smart Array 5300

◦ Smart Array 5i

◦ Smart Array 532

◦ Smart Array 5312

◦ Smart Array 641

◦ Smart Array 642

◦ Smart Array 6400

◦ Smart Array 6400 EM

◦ Smart Array 6i

◦ Smart Array P600

◦ Smart Array P800

◦ Smart Array P400

◦ Smart Array P400i

◦ Smart Array E200i

◦ Smart Array E200

◦ Smart Array E500

◦ Smart Array P700M

hpsa(4) - Linux man page

Name

hpsa - HP Smart Array SCSI driver

Synopsismodprobe hpsa [ hpsa_allow_any=1 ]

Description

hpsa is a SCSI driver for HP Smart Array RAID controllers.

Optionshpsa_allow_any=1: This option allows the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not explicitly known to the driver. This allows newer hardware to work with older drivers. Typically this is used to allow installation of operating systems from media that predates the RAID controller, though it may also be used to enable

hpsa to drive older controllers that would normally be handled by the

hpsa, and

Supported hardware

The

hpsa driver supports the following Smart Array boards:

Smart Array P700M

Smart Array P212

Smart Array P410

Smart Array P410i

Smart Array P411

Smart Array P812

Smart Array P712m

Smart Array P711m

StorageWorks P1210m

Configuration details

To configure HP Smart Array controllers, use the HP Array Configuration Utility (either

hpacuxe(8) or

hpacucli(8)) or the Offline ROM-based Configuration Utility (ORCA) run from the Smart Array's option ROM at boot time.

这篇关于hp dl388 install linux 无法识别raid,HP Proliant DL580 G5安装centos7 x64无法识别阵列卡问题...的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/520260

相关文章

Linux镜像文件制作方式

《Linux镜像文件制作方式》本文介绍了Linux镜像文件制作的过程,包括确定磁盘空间布局、制作空白镜像文件、分区与格式化、复制引导分区和其他分区... 目录1.确定磁盘空间布局2.制作空白镜像文件3.分区与格式化1) 分区2) 格式化4.复制引导分区5.复制其它分区1) 挂载2) 复制bootfs分区3)

Springboot3统一返回类设计全过程(从问题到实现)

《Springboot3统一返回类设计全过程(从问题到实现)》文章介绍了如何在SpringBoot3中设计一个统一返回类,以实现前后端接口返回格式的一致性,该类包含状态码、描述信息、业务数据和时间戳,... 目录Spring Boot 3 统一返回类设计:从问题到实现一、核心需求:统一返回类要解决什么问题?

Java使用Spire.Barcode for Java实现条形码生成与识别

《Java使用Spire.BarcodeforJava实现条形码生成与识别》在现代商业和技术领域,条形码无处不在,本教程将引导您深入了解如何在您的Java项目中利用Spire.Barcodefor... 目录1. Spire.Barcode for Java 简介与环境配置2. 使用 Spire.Barco

maven异常Invalid bound statement(not found)的问题解决

《maven异常Invalidboundstatement(notfound)的问题解决》本文详细介绍了Maven项目中常见的Invalidboundstatement异常及其解决方案,文中通过... 目录Maven异常:Invalid bound statement (not found) 详解问题描述可

idea粘贴空格时显示NBSP的问题及解决方案

《idea粘贴空格时显示NBSP的问题及解决方案》在IDEA中粘贴代码时出现大量空格占位符NBSP,可以通过取消勾选AdvancedSettings中的相应选项来解决... 目录1、背景介绍2、解决办法3、处理完成总结1、背景介绍python在idehttp://www.chinasem.cna粘贴代码,出

SpringBoot整合Kafka启动失败的常见错误问题总结(推荐)

《SpringBoot整合Kafka启动失败的常见错误问题总结(推荐)》本文总结了SpringBoot项目整合Kafka启动失败的常见错误,包括Kafka服务器连接问题、序列化配置错误、依赖配置问题、... 目录一、Kafka服务器连接问题1. Kafka服务器无法连接2. 开发环境与生产环境网络不通二、序

SpringSecurity中的跨域问题处理方案

《SpringSecurity中的跨域问题处理方案》本文介绍了跨域资源共享(CORS)技术在JavaEE开发中的应用,详细讲解了CORS的工作原理,包括简单请求和非简单请求的处理方式,本文结合实例代码... 目录1.什么是CORS2.简单请求3.非简单请求4.Spring跨域解决方案4.1.@CrossOr

nacos服务无法注册到nacos服务中心问题及解决

《nacos服务无法注册到nacos服务中心问题及解决》本文详细描述了在Linux服务器上使用Tomcat启动Java程序时,服务无法注册到Nacos的排查过程,通过一系列排查步骤,发现问题出在Tom... 目录简介依赖异常情况排查断点调试原因解决NacosRegisterOnWar结果总结简介1、程序在

2025最新版Android Studio安装及组件配置教程(SDK、JDK、Gradle)

《2025最新版AndroidStudio安装及组件配置教程(SDK、JDK、Gradle)》:本文主要介绍2025最新版AndroidStudio安装及组件配置(SDK、JDK、Gradle... 目录原生 android 简介Android Studio必备组件一、Android Studio安装二、A

Linux服务器数据盘移除并重新挂载的全过程

《Linux服务器数据盘移除并重新挂载的全过程》:本文主要介绍在Linux服务器上移除并重新挂载数据盘的整个过程,分为三大步:卸载文件系统、分离磁盘和重新挂载,每一步都有详细的步骤和注意事项,确保... 目录引言第一步:卸载文件系统第二步:分离磁盘第三步:重新挂载引言在 linux 服务器上移除并重新挂p