How to add a second disk to Proliant MicroServer

[mxc]

Hi mxc,
This is the output from the fdisk -l:

Disk /dev/mapper/35000c5001620695a-part1: 1000.2 GB, 1000203091968 bytes
26 heads, 24 sectors/track, 3130643 cylinders, total 1953521664 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x86768889

Device Boot Start End Blocks Id System
/dev/mapper/35000c5001620695a-part1p1 2048 1953521663 976759808 83 Linux

Disk /dev/mapper/35000c5004b426b2f-part2p1: 2011 MB, 2011168768 bytes
255 heads, 63 sectors/track, 244 cylinders, total 3928064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/35000c5001620695a-part1p1: 1000.2 GB, 1000202043392 bytes
255 heads, 63 sectors/track, 121600 cylinders, total 1953519616 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

I notice though that somehow the file didn't capture the message "Disk /dev/mapper/35000c5001620695a-part1p1 doesn't contain a valid partition table".

The output of fdisk should also list the physical partitions e.g /dev/sda, /dev/sdb. /dev/mapper is used for the multi-disk type abstraction disk systems such as logical volume management, mdadm (software raid) etc. But there should be the physical disks listed as well. Is this the entire output? It might have scrolled passed your terminal. From the above it looks like you got 1 disk with 2 partitions. A 1000.2GB partition and another partition of 2011MB about 2G.

You probably using lvm (logical volume management), but your new disk should still show up with fdisk. You can run pvdisplay and see what partitions have been allocated to the logical volume.
What is the output of "mount"?

As with the others I am a bit confused as to whether you setup raid/lvm or not because in the beginning you say you not using raid and then later you say you are using raid? Also if the 1TB was formatted in an enclosure and then placed in the microserver where is the operating system sitting? If the microsver is booting and you are trying to add a new disk the information provided does not add up.

The output from /etc/fstab totally contradicts the output from "fdisk -l". Are they from the same machine? What is the output of "ls -l /dev/disk/by-uuid" (that's lower case L).

Maybe you just tired from all those sleepless nights and need to let us know the current state of affairs clearly. Is there another disk with the OS? Doesn't look like it from the above output.

So please provide output of:

"mount"
""ls -l /dev/disk/by-uuid"
"fdisk -l" -- full output
"pvdisplay" and "mdadm --detail --scan" - one of these may give an error.

PHP Training

[MyWorld]

You should never change that setting (AHCI vs IDE) once an operating system is installed. It will mess up your installation badly. Just leave it at AHCI.

All the advice in here should give you a hand, I just add another layer of troubleshooting.

After reading everything and considering how thorough you have done everything, I would like to suggest that it may also be a setting in the BIOS, try seeing if there is a RAID setting that is enabled and disable it.

How you can test, unplug /dev/sda, plug the 1TB into that controller, boot a liveCD and see if it picks up the drive correctly.
Also, make sure all your SATA cables are new/undamaged, try another cable, you should have some lying around. SATA cables cannot bend like the old IDE cables, so a sharp bend in the cable can cause headaches.

Now for the technical part:
If it is not the controller, and you have ruled out any hardware problems (different controllers, different cables, unplugging everything and only leaving the drives attatched, etc.), you need to find out why the system does not release or recognise the drive.

sudo su                          # This will give you a permanent superuser session, everything you need to do is going to be as root so this is easier, otherwise you need to type sudo before each command
cffdisk /dev/sdb                 # This is much easier to use than fdisk and the chances that you will make a mistake minimal
                                 # Create new primary partition and set the filetype, write changes to disk
mkfs.ext4 /dev/sdb1              # Format the drive ext4 filesystem. See if any errors are reported


mkdir /opt/data                  # Create the mount path
mount /dev/sdb1 /opt/data        # If it succeeds or fail, does not matter, check you logs

dmesg | tail                     # If something is wrong it should be mentioned here
cat /var/log/errors.log | tail   # Check the timestamp and see if there are any errors
cat /var/log/kernel.log | tail   # Same, see corresponding timestamp and see if there are any kernel errors

If this does not help, how old is the drive? Try and see if you can test another drive to make sure it is not the drive that is causing the errors.

This is a mouthful, hope you get everything sorted!

[cabous]

Hi mxc,
Neep - I definately don't want to set up RAID now. I tried to only paste the information relevant to my 1TB when pasting info from fdisk etc - didn't think the other info would be necessary.

I ran those commands (no output from pvdisplay or mdadm - I ran both using sudo):

MOUNT
/dev/mapper/35000c5004b426b2f-part1 on / type ext4 (rw,errors=remount-ro) #My 250GB disk
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
none on /sys/kernel/config type configfs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

FDISK -L
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e416c

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 484466687 242232320 83 Linux
/dev/sda2 484468734 488396799 1964033 5 Extended
/dev/sda5 484468736 488396799 1964032 82 Linux swap / Solaris

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
81 heads, 63 sectors/track, 382818 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1784df20

Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953525167 976761560 83 Linux

Disk /dev/mapper/35000c5004b426b2f: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e416c

Device Boot Start End Blocks Id System
/dev/mapper/35000c5004b426b2f1 * 2048 484466687 242232320 83 Linux
/dev/mapper/35000c5004b426b2f2 484468734 488396799 1964033 5 Extended
/dev/mapper/35000c5004b426b2f5 484468736 488396799 1964032 82 Linux swap / Solaris

Disk /dev/mapper/35000c5001620695a: 1000.2 GB, 1000204886016 bytes
81 heads, 63 sectors/track, 382818 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1784df20

Device Boot Start End Blocks Id System
/dev/mapper/35000c5001620695a1 2048 1953525167 976761560 83 Linux

Disk /dev/mapper/35000c5001620695a-part1: 1000.2 GB, 1000203837440 bytes
26 heads, 24 sectors/track, 3130646 cylinders, total 1953523120 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x86768889

Device Boot Start End Blocks Id System
/dev/mapper/35000c5001620695a-part1p1 2048 1953521663 976759808 83 Linux

Disk /dev/mapper/35000c5004b426b2f-part1: 248.0 GB, 248045895680 bytes
255 heads, 63 sectors/track, 30156 cylinders, total 484464640 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/35000c5004b426b2f-part2: 2011 MB, 2011169792 bytes
255 heads, 63 sectors/track, 244 cylinders, total 3928066 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/mapper/35000c5004b426b2f-part2p1 2 3928065 1964032 82 Linux swap / Solaris

Disk /dev/mapper/35000c5004b426b2f-part5: 2011 MB, 2011168768 bytes
255 heads, 63 sectors/track, 244 cylinders, total 3928064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Re those 'sleepless nights' - I got my boy doing tummy time next to me right now as I reply He'll have plenty to think about next time he wants to wake up

PS LS -L
total 0
lrwxrwxrwx 1 root root 10 Jul 21 21:32 091c4c3a-6ab6-456d-bcdc-ac245083a770 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Jul 21 21:32 28e36f05-301b-4454-a133-22e96d05a18a -> ../../dm-2
lrwxrwxrwx 1 root root 10 Jul 21 21:32 79d267fc-9619-4bcf-98d6-86eecb1c7621 -> ../../dm-3

[cabous]

MyWorld,
I'll try your live CD option after replacing the bootable disk with the 1TB. If that still fails I'm just going to reinstall Ubuntu - the first time I didn't have my 1TB plugged in - I figured it may give me too much problems - thought that the installation process would maybe force me to go RAID.

PS - I installed the 64 bit version of Ubuntu - that shouldn't be a problem, right?
PPS - I couldn't find a download site for cffdisk.

[mxc]

Hi Cabos,

From the output above you have two physical disk. /dev/sda = 250G and /dev/sdb = 1TB. /dev/sda has 3 partitions while /dev/sdb1 has only 1 partition. It appears that /dev/sda is holding your OS. I assume /dev/sdb is the new drive.

All the devices are used in some multi-disk setup as is evident from the /dev/mapper links. So /dev/sdb1 is being mapped by the deivce /dev/mapper/35000c5001620695a. From the output of mount it appears that this is not currently mounted anywhere. You will need to mount the device /dev/mapper/35000c5001620695a and not /dev/sdb1. It seem that you are using lvm.

There are several steps to get the disk to be available for use under lvm. First you need to find out what logical volumes you have run "lvdisplay","vgdisplay" and "pvdisplay" and post the output. If you know enough about lvm you just need to find out what volume group the partitions is part of and if it has been alloctated to a logical volume. Then you need to mount the logical volume. You cannot mount /dev/sdb1 directly.

PHP Training

[MyWorld]

Sorry, not cffdisk, just cfdisk, it should be installed already.

What mxc said, that is why I suggested seeing in the BIOS is you turned of the RAID options for your controllers. Also, I do not know what you chose when you installed Ubuntu but LVM is also used for ecryptfs (like encrypt my Home directory...)
http://www.howtoforge.com/linux_lvm

[cabous]

Hi Guys,
My install memory stick didn't have a live disk option so I just reinstalled and paid attention to my settings.

- IDE Configuration is now set to AHCI in the BIOS (There weren't other options for RAID / no-RAId in the BIOS)
- I didn't specify LVM (maybe accidently with first install)

... and now my 1TB is mounted properly. Bargain and thanks again!

I'll read up about LVM - it may be useful in my environment in the future.

Blessings