installed new hard drive - now can't find it

[Dana Holland]

When I do a fdisk /dev/sda I get:

# fdisk /dev/sda

The number of cylinders for this disk is set to 6637.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
    (e.g., DOS FDISK, OS/2 FDISK)

But if I issue the command on anything above that:

]# fdisk /dev/sdb

Unable to open /dev/sdb

My confusion is that I already have partitions (devices?) that start 
with sda...


# fdisk -l

Disk /dev/sda: 255 heads, 63 sectors, 6637 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/sda1   *         1        13    104391   83  Linux
/dev/sda2            14      1288  10241437+  83  Linux
/dev/sda3          1289      1798   4096575   83  Linux
/dev/sda4          1799      6637  38869267+   f  Win95 Ext'd (LBA)
/dev/sda5          1799      1862    514048+  83  Linux
/dev/sda6          1863      1989   1020096   83  Linux
/dev/sda7          1990      2626   5116671   83  Linux
/dev/sda8          2627      3391   6144831   83  Linux
/dev/sda9          3392      4156   6144831   83  Linux
/dev/sda10         4157      4160     32098+  82  Linux swap
/dev/sda11         4161      4798   5124703+  83  Linux

We're nervous about this because it's a live system - the data changes 
constantly.

Could it have anything to do with the Array Configuration Utility?  Is 
there something in there that we should do?  This is a Raid-5 box.


Mark Knecht wrote:

  > I would guess you'd step thought looking at:
> 
> fdisk /dev/sda
> fdisk /dev/sdb
> 
> etc. until you find it. For me 'finding' a drive amounts to fdisk not 
> complaining that the devide doesn't exist.
> 
> At that point you should be able to partition it with fdisk and bring it 
> up.