Hi Steve, this issue can be easily reproduced through either of the following scenario on Ubuntu 12.04.
Assuming Ubuntu 12.04 is located as /sda2, and I have two HDD connected as sda, sdb. sdb4 is formatted as ext4
1. Adding one entry in /etc/fstab which will try to mount a non-existing disk device node. Simulate as failure partition
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sdc4 /test ext2 defaults 0 0
2. Intentionally corrupt a working partition through DD command to simulate a disk/partition error
dd if=/dev/zero of=/dev/sdb4 bs=1M count=100
Then add an entry to found the failure partition
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sdb4 /disk1 ext2 defaults 0 0
In either case, we saw system got stuck during mount procedure without any message indicating which partition or disk is having problem and never reach the login prompt.
Hi Steve, this issue can be easily reproduced through either of the following scenario on Ubuntu 12.04.
Assuming Ubuntu 12.04 is located as /sda2, and I have two HDD connected as sda, sdb. sdb4 is formatted as ext4
1. Adding one entry in /etc/fstab which will try to mount a non-existing disk device node. Simulate as failure partition
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sdc4 /test ext2 defaults 0 0
2. Intentionally corrupt a working partition through DD command to simulate a disk/partition error
dd if=/dev/zero of=/dev/sdb4 bs=1M count=100
Then add an entry to found the failure partition
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sdb4 /disk1 ext2 defaults 0 0
In either case, we saw system got stuck during mount procedure without any message indicating which partition or disk is having problem and never reach the login prompt.