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

相关文章

windows和Linux使用命令行计算文件的MD5值

《windows和Linux使用命令行计算文件的MD5值》在Windows和Linux系统中,您可以使用命令行(终端或命令提示符)来计算文件的MD5值,文章介绍了在Windows和Linux/macO... 目录在Windows上:在linux或MACOS上:总结在Windows上:可以使用certuti

解决IDEA报错:编码GBK的不可映射字符问题

《解决IDEA报错:编码GBK的不可映射字符问题》:本文主要介绍解决IDEA报错:编码GBK的不可映射字符问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录IDEA报错:编码GBK的不可映射字符终端软件问题描述原因分析解决方案方法1:将命令改为方法2:右下jav

Linux之systemV共享内存方式

《Linux之systemV共享内存方式》:本文主要介绍Linux之systemV共享内存方式,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一、工作原理二、系统调用接口1、申请共享内存(一)key的获取(二)共享内存的申请2、将共享内存段连接到进程地址空间3、将

MyBatis模糊查询报错:ParserException: not supported.pos 问题解决

《MyBatis模糊查询报错:ParserException:notsupported.pos问题解决》本文主要介绍了MyBatis模糊查询报错:ParserException:notsuppo... 目录问题描述问题根源错误SQL解析逻辑深层原因分析三种解决方案方案一:使用CONCAT函数(推荐)方案二:

Win安装MySQL8全过程

《Win安装MySQL8全过程》:本文主要介绍Win安装MySQL8全过程,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录Win安装mysql81、下载MySQL2、解压文件3、新建文件夹data,用于保存数据库数据文件4、在mysql根目录下新建文件my.ini

Redis 热 key 和大 key 问题小结

《Redis热key和大key问题小结》:本文主要介绍Redis热key和大key问题小结,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录一、什么是 Redis 热 key?热 key(Hot Key)定义: 热 key 常见表现:热 key 的风险:二、

IntelliJ IDEA 中配置 Spring MVC 环境的详细步骤及问题解决

《IntelliJIDEA中配置SpringMVC环境的详细步骤及问题解决》:本文主要介绍IntelliJIDEA中配置SpringMVC环境的详细步骤及问题解决,本文分步骤结合实例给大... 目录步骤 1:创建 Maven Web 项目步骤 2:添加 Spring MVC 依赖1、保存后执行2、将新的依赖

快速修复一个Panic的Linux内核的技巧

《快速修复一个Panic的Linux内核的技巧》Linux系统中运行了不当的mkinitcpio操作导致内核文件不能正常工作,重启的时候,内核启动中止于Panic状态,该怎么解决这个问题呢?下面我们就... 感谢China编程(www.chinasem.cn)网友 鸢一雨音 的投稿写这篇文章是有原因的。为了配置完

Spring 中的循环引用问题解决方法

《Spring中的循环引用问题解决方法》:本文主要介绍Spring中的循环引用问题解决方法,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录什么是循环引用?循环依赖三级缓存解决循环依赖二级缓存三级缓存本章来聊聊Spring 中的循环引用问题该如何解决。这里聊

Spring Boot中JSON数值溢出问题从报错到优雅解决办法

《SpringBoot中JSON数值溢出问题从报错到优雅解决办法》:本文主要介绍SpringBoot中JSON数值溢出问题从报错到优雅的解决办法,通过修改字段类型为Long、添加全局异常处理和... 目录一、问题背景:为什么我的接口突然报错了?二、为什么会发生这个错误?1. Java 数据类型的“容量”限制