-2

Trying to deploy a 2xSSD server (with mdraid level 1), errors on the 1st line:

clearpart --all --initlabel --drives=sda,sdb

with the message "sda not found".

As the SSD is SATA3, shouldn't it be called via the standard sdX names?

The machine is physical (Tyan AFAIR), and I'm trying to deploy latest CentOS 5.x via TheForeman, which includes DHCP/TFTP and Puppet.

The disks are SanDisk Industrial/ Embedded SSD (32 GB), mounted via 2.5 to 3.5 adapter to server disk brackets and connected directly to the motherboard SATA ports

SyRenity
  • 3,179
  • 11
  • 57
  • 79
  • Is this a physical machine or virtualized somehow? – EEAA Mar 23 '14 at 21:36
  • Are they connected to a SAS controller? maybe the device names are different? Have a look at the dmesg output as suggested by EEAA. – hookenz Mar 23 '14 at 21:50
  • 4
    Which **operating system** are you attempting this with? Which version of the OS? What type of server hardware? What specific SSDs are you using? What are they connected to? What installation media are you using? This is *so* little information to go on, it's nearly impossible to give proper answers. – ewwhite Mar 23 '14 at 22:29
  • Sorry, posted it quite in a hurry, updated above. That said I'm trying with another machine (Tyan shut down on me several times, probably due to overheating), will ask to close if it works. – SyRenity Mar 25 '14 at 13:59
  • Works fine (old machine was the culprit), asked to close. – SyRenity Mar 25 '14 at 15:27

2 Answers2

2

While /dev/sdX is the most common, I've also seen /dev/xvdX, especially with some configurations of the Xen hypervisor.

Regardless, just look through the output of dmesg after boot, and you'll find the device names listed as the kernel enumerates them.

EEAA
  • 109,363
  • 18
  • 175
  • 245
1

In the absence of better information (e.g. OS version, hardware involved, SSD brand, installation method/media), let's assume you're installing CentOS or a Redhat derivative from USB (or USB-attached CD/DVD) or IPMI virtual media. That could impact your SCSI device naming.

You can run a manual installation and scan for the devices that show up. Or you could break out of the installer at the point of the error (go to another virtual terminal) and see which devices were detected. Even an fdisk -l at that point would give you an idea of what the installer found.

ewwhite
  • 197,159
  • 92
  • 443
  • 809