Mammoth have a range of server solutions suitable for all types of web applications, large and small.
Mammoth Cloud servers can be upgraded or downgraded at any time, providing almost unlimited growth potential.
Whether you are running a small Wordpress blog, or a large Magento e-commerce platform, Mammoth has a solution suitable for your business - now, and in the future.
Choose from Windows 2012 R2 or Windows 2008 R2 and connect via Remote Desktop (RDP) after deployment.
Deploy your VPS in 60 seconds. Choose from CentOS, Debian, or Ubuntu and connect via SSH after deployment.
Our cPanel cloud servers come pre-installed, just connect to the WHM web interface after deployment.
The Finnix Recovery CD can be used to perform a number of tasks
that are otherwise difficult or impossible to do on your Linux VPS.
Common uses include:
This guide will walk you through booting into the Recovery CD
along with how to perform some basic tasks.
1. After logging into mPanel, click the "Manage" button next to
the VPS you wish to work on.
2. The bottom right corner of the screen shows the active Kernel
and lets you select a new one. Take note of the kernel you are
3. Change the kernel to Finnix Recovery CD and
4. A prompt will ask you to confirm that a VPS restart is needed
- click OK.
5. Mammoth VPS will begin shutting down your VPS before
restarting it with the Recovery CD.
6. From the "Access" menu click "Rescue Console" - the Recovery
CD will boot without networking, so you must access it through the
7. Once the Finnix Recovery CD has booted, the Rescue Console
screen will look like this:
Unlike when using your VPS normally, while using the Recovery CD
your Mammoth VPS hard drive (either /dev/xvda2 or
/dev/xvda) is not mounted as the root partition.
In fact, its initially not mounted at all - which is a
requirement if you ever need to repair your filesystem with
the fsck command:
If you need to reset your root password, you can mount the hard
drive and then use the passwd command in combination with chroot
("change root partition") command:
If you want to use SSH while Finnix is running:
Change Filesystem Types
With Finnix, its possible to reformat your hard disk with a
different filesystem type. However, this will delete all your files
(and mPanel's reinstall function would convert you back to ext3) so
on its own its not that useful.
In combination with mPanel's "attach backup" feature it is
possible to take a backup, and then immediately drop into Finnix to
reformat the disk and then copy everything from your ext3 backup
into the new filesystem:
2. Click on the "Backups" menu item.
3. Create a fresh backup. Any changes made after this backup is
taken but before the filesystem is converted will be lost, so it is
a good idea to shut down your web server, database, and anything
else that will modify files. Of course if you have already booted
into Recovery CD, then none of those things are running anyway.
4. Return to the "Backups" menu item, select the radio box next
to your backup, and click Attach Selected.
5. Click "OK" when prompted to reboot your VPS and attach the
6. Run through the "Enter Recovery" steps from earlier in this
guide to start the Finnix Recovery CD and access the rescue
7. The backup is attached as a new device (either
/dev/xvdb1 or /dev/xvdk) - confirm you can see it
by mounting it and looking at the files. Be sure to unmount it once
8. Having verified your backup, reformat your main disk (either
/dev/xvda2 or /dev/xvda) - in this example, we
use XFS. The -f flag is required to force overwriting the existing
9. Now mount both the backup and your normal hard disk
simultaneously and copy the files from backup to the normal disk.
The -a switch (archive mode) does a recursive copy and
preserves the file modes, owners, timestamps, symbolic links, and
10. Edit the hard-disk's /etc/fstab and change the filesystem
type from ext3 to xfs:
11. Return to the Backups area, and de-attach the backup.
12. Follow the "Leaving Recovery" steps to boot your VPS back up
Once you have finished with your management tasks, you need to
simply change back to the kernel you were previously using: