Today in the installation of CentOS 6.2, when the detection of the hard disk, always pass, error is as follows: Disk SDA contains BIOS RAID metadata, but was not part of the any recognized BIOS RAI D sets. Ignoring disk SDA
This situation has a similar situation in Ubuntu,suse, but the hints are not quite the same.
Sometimes it's SDA, sometimes sdb.
The feeling is that this hard drive was previously raid, and now it is not recognized. What to do.
When you go to the Install selection menu
Pressing the TAB key will enter the command line mode of Linux, then add nodmraid after the start command line (note that preceded by a space) and press ENTER.
The next step into the installation process will find the hard drive found.
The Nodmraid command is to turn off the array
This can be done with the installation of the system, but it needs to be set up each time the system is reinstalled. How to solve the problem completely.
I tried it in emergency mode.
Dmraid-r-e/dev/sdb
But the error.
It looks like you can just put the hard drive on another machine and see what happens.
Work immediately began to deal with the problem. Put the hard drive on a different machine
# DMRAID-RE/DEV/SDB
No RAID disks and with names: "/dev/sdb"
Oh, no. Search online, have friends to give a more simple way, with parted
# parted/dev/sdb--script Mklabel GPT
# Parted/dev/sdb--script--Mkpart primary 0-1
Warning:the resulting partition is not properly aligned for best performance.
# parted/dev/sdb--script Print
Model:ata TOSHIBA mk1002ts (SCSI)
disk/dev/sdb:1000gb
Sector size (logical/physical): 512b/512b
Partition TABLE:GPT
Number Start End Size File system Name Flags
1 17.4kB 1000GB 1000GB primary processing finished, put back the original machine, incredibly there is no problem, successfully installed the system.
If so, in the first aid mode, run parted, also should be no problem.
If not, the last trick is DD.
DD If=/dev/null OF=/DEV/SDA bs=512 count=1
This article from "11393002" blog, declined reprint!
CentOS appears disk SDA contains BIOS RAID metadata workaround