My host just added 2 SSD to my server. It seems that the 2 SSD has been partitioned and formated. However just to make sure I repartitioned again. I noticed that SDB1 and SDC1 is bootable. I deleted both partition from SDB and create a new one.
Command (m for help): v
Remaining 14804 unallocated 512-byte sectors
Command (m for help): p
Disk sdb: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb4852a81
Device Boot Start End Blocks Id System
sdb1 1 31130 250051693+ 8e Linux LVM
Command (m for help): w
The partition table has been altered!
That's it. It's been like this for hours. This is an SSD. The guy that provided the SSD actually did the partitioning but I thought I'll just delete their partition and create one my self. I am not sure I am doing it correctly. Why fdisk doesn't return to command prompt?
What is strange is fdisk -l doesn't show sda at all:
root@host [~]# fdisk -l
Disk /dev/sdb: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb4852a81
Device Boot Start End Blocks Id System
/dev/sdb1 1 31130 250051693+ 8e Linux LVM
Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00037518
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdc2 64 182402 1464625152 8e Linux LVM
Disk /dev/mapper/VolGroup-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap: 33.8 GB, 33839644672 bytes
255 heads, 63 sectors/track, 4114 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_home: 1412.2 GB, 1412247322624 bytes
255 heads, 63 sectors/track, 171695 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
root@host [~]#
also typing df yield root@host [~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
50G 8.4G 39G 18% /
tmpfs 32G 0 32G 0% /dev/shm
/dev/sdc1 485M 62M 398M 14% /boot
/dev/mapper/VolGroup-lv_home
1.3T 196G 1.1T 16% /home
/usr/tmpDSK 485M 11M 449M 3% /tmp
why the hell /dev/sdc1, which is a partition in a new drive is mounted to /boot?
How do we check the mounting system anyway? Does that mean that now my server will boot to sdc1?
