It was almost ironical that less than 24 hours after I posted my previous post (which, now, no longer exists for reasons that I will explain below) celebrating 30-days of uptime with 96MB.com (or the 96MB RAM VPS box it is sitting on), 96MB.com received such a huge visiting volume that the box could no longer hold it through and surrendered with a DB Connection Error screen. Out of panic, I tried to reboot the box, the shutdown was fine, however after I tried to boot it up again, here is the error message that I have got: Filesystem unmounted: sudo /bin/umount /home/xen/vps2433.vm/mnt VPS config file written: /home/xen/vps2433.vm/vps2433.vm.cfg Filesystem Created: sudo /sbin/mkswap /dev/VolGroup00/vps2433.vm_vmswap Filesystem labelled: sudo /sbin/e2label /dev/VolGroup00/vps2433.vm_rootimg domU_disk_root Filesystem mounted: sudo /bin/mount /dev/VolGroup00/vps2433.vm_rootimg /home/xen/vps2433.vm/mnt VPS hostname file written: /usr/local/openitc/tmp/vps2433.vm_etc_hostname Files chowned: sudo /bin/chown root:root /usr/local/openitc/tmp/vps2433.vm_etc_* File moved: sudo /bin/mv /usr/local/openitc/tmp/vps2433.vm_etc_hostname /home/xen/vps2433.vm/mnt/etc/hostname VPS hosts file written: /usr/local/openitc/tmp/vps2433.vm_etc_hosts Files chowned: sudo Read More
