VBox fdisk does not display the added hard disk Solution

VBox fdisk does not display the added hard disk solution. You cannot use the fdisk command to view the disk we added: [root @ rac1 ~] # Fdisk-l Disk/dev/sda: 32.2 GB, 32212254720 bytes255 heads, 63 sectors/track, 3916 cylindersUnits = cylinders of 16065*512 = 8225280 bytesSector size (logical/physical ): 512 bytes/512 bytesI/O size (minimum/optimal): 512 bytes/512 bytesDisk identifier: 0x00085ca1 Device Boot Start End Blocks Id System/dev/sda1 * 1 26 204800 83 LinuxPartition 1 does not end on cylinderboundary. /dev/sda2 26 281 2048000 82 Linux swap/SolarisPartition 2 does not end on cylinder boundary./dev/sda3 281 3917 29203456 83 Linux [root @ rac1 ~] # -- But view/proc/partitions, which can be displayed as: [root @ rac1 ~] # Cat/proc/partitionsmajor minor # blocks name 8 0 31457280 sda 8 1 204800 sda1 8 2 2048000 sda2 8 3 29203456 sda3 8 16 8388608 sdb 8 32 8388608 sdc 8 48 8388608 sdd 8 64 8388608 sde 8 80 1048576 sdf 8 96 1048576 sdg 8 112 1048576 sdh [root @ rac1 ~] # Run start_udev manually and run the fdisk command to view the disk. It is estimated that there is a problem during udev startup. View the udev service status: [root @ rac1 ~] # Service udev-post status [root @ rac1 ~] # Chkconfig udev-post -- listudev-post 0: off 1: on 2: on 3: on 4: on 5: on 6: off [root @ rac1 ~] # Service udev-post startRetrigger failed udev events [OK] Note: I am from Oracle linux, so the udev service is udev-post. If it is redhat, the corresponding service is: udev does not study this issue in depth. Add start_udev to the startup Item to ensure normal use. [Root @ rac2 ~] # Vim/etc/rc. d/rc. local #! /Bin/sh # This script will be executed * after * allthe other init scripts. # You can put your own initialization stuffin here if you don't # want to do the full Sys V style initstuff. touch/var/lock/subsys/local/sbin/start_udev.