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

相关文章

Python中图片与PDF识别文本(OCR)的全面指南

《Python中图片与PDF识别文本(OCR)的全面指南》在数据爆炸时代,80%的企业数据以非结构化形式存在,其中PDF和图像是最主要的载体,本文将深入探索Python中OCR技术如何将这些数字纸张转... 目录一、OCR技术核心原理二、python图像识别四大工具库1. Pytesseract - 经典O

基于Linux的ffmpeg python的关键帧抽取

《基于Linux的ffmpegpython的关键帧抽取》本文主要介绍了基于Linux的ffmpegpython的关键帧抽取,实现以按帧或时间间隔抽取关键帧,文中通过示例代码介绍的非常详细,对大家的学... 目录1.FFmpeg的环境配置1) 创建一个虚拟环境envjavascript2) ffmpeg-py

gitlab安装及邮箱配置和常用使用方式

《gitlab安装及邮箱配置和常用使用方式》:本文主要介绍gitlab安装及邮箱配置和常用使用方式,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1.安装GitLab2.配置GitLab邮件服务3.GitLab的账号注册邮箱验证及其分组4.gitlab分支和标签的

MySQL MCP 服务器安装配置最佳实践

《MySQLMCP服务器安装配置最佳实践》本文介绍MySQLMCP服务器的安装配置方法,本文结合实例代码给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下... 目录mysql MCP 服务器安装配置指南简介功能特点安装方法数据库配置使用MCP Inspector进行调试开发指

在Windows上使用qemu安装ubuntu24.04服务器的详细指南

《在Windows上使用qemu安装ubuntu24.04服务器的详细指南》本文介绍了在Windows上使用QEMU安装Ubuntu24.04的全流程:安装QEMU、准备ISO镜像、创建虚拟磁盘、配置... 目录1. 安装QEMU环境2. 准备Ubuntu 24.04镜像3. 启动QEMU安装Ubuntu4

Python UV安装、升级、卸载详细步骤记录

《PythonUV安装、升级、卸载详细步骤记录》:本文主要介绍PythonUV安装、升级、卸载的详细步骤,uv是Astral推出的下一代Python包与项目管理器,主打单一可执行文件、极致性能... 目录安装检查升级设置自动补全卸载UV 命令总结 官方文档详见:https://docs.astral.sh/

Linux脚本(shell)的使用方式

《Linux脚本(shell)的使用方式》:本文主要介绍Linux脚本(shell)的使用方式,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录概述语法详解数学运算表达式Shell变量变量分类环境变量Shell内部变量自定义变量:定义、赋值自定义变量:引用、修改、删

Nexus安装和启动的实现教程

《Nexus安装和启动的实现教程》:本文主要介绍Nexus安装和启动的实现教程,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一、Nexus下载二、Nexus安装和启动三、关闭Nexus总结一、Nexus下载官方下载链接:DownloadWindows系统根

MySQL 设置AUTO_INCREMENT 无效的问题解决

《MySQL设置AUTO_INCREMENT无效的问题解决》本文主要介绍了MySQL设置AUTO_INCREMENT无效的问题解决,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参... 目录快速设置mysql的auto_increment参数一、修改 AUTO_INCREMENT 的值。

Python基于微信OCR引擎实现高效图片文字识别

《Python基于微信OCR引擎实现高效图片文字识别》这篇文章主要为大家详细介绍了一款基于微信OCR引擎的图片文字识别桌面应用开发全过程,可以实现从图片拖拽识别到文字提取,感兴趣的小伙伴可以跟随小编一... 目录一、项目概述1.1 开发背景1.2 技术选型1.3 核心优势二、功能详解2.1 核心功能模块2.