Gparted Ubuntu Server
Maybell Hughs
I'm super new to Ubuntu and have basic understanding of how to use it. I'm trying to set up a Minecraft server and want to have it backed up onto a second HDD. I've installed the server distro of Ubuntu but can't figure out how to format the second drive. When I tried to use parted it said it couldn't write to certain sectors because they were in use. A little Google use later and I figured I would try gparted. When I try to run gparted though I get a display error: Gym Warning cannot open DISPLAY.
The command line version of gparted (g stands for graphical) is parted. Making mistakes with parted is easy to do... make a backup of your personal files even it is not on the disk you expect to alter.
"2.The proper paths must be set via the set prefix command.
Many GRUB 2 commands will not work until the correct path is set.
If the path to the grub folder (normally /boot/grub) is not correct, an unknown command or file not found message is likely. "
So I next tried to follow the guide's trouble-shooting procedure, step by step. As soon as I got to 'insmod normal' after settiat
ng preifx and root, grub2 declared "file not found". It didn't help even when I entered 'insmod (hd0,5)/boot/grub/normal.mod'.
Since I must pass this essential step first, there was not much I could do next. However, I was able to define initrd and kernel as follows in the meantime after I discovered that they both reside in the root directory of the /dev/sda5 partition.
I've just searched through my entire broken Ubuntu computer and found omly one file in /boot/grub and it's named grubenv, using an Ubuntu rescue livcd. However, my MacBook-based Ubuntu system does show the normal.mod file in /boot/grub directory and another directory. The grub_rescue guide is really helpful and thorough.
I've now discovered some bad news from 'sodo fdisk -l'. It indicated that all my 4 partitions sda2, sda6, sda7, and sda5 'don't end on cylinder boundary'. Does it mean that the partition table is hopelessly broken?
"Partitions Don't End on Cylinder Boundary" is a message that you usually can safely ignore.
In past times when disks were a fixed number of real sectors of real cylinders read with a number of heads, it was recommended to start and end partitions on cylinder boundaries. Nowadays most disks only simulate that they have a fixed number of heads, cylinders and sectors, and the cylinder boundary start/end is no more required.
Thanks again. Using the Ubuntu 32-bit Boot Repair Disk, I was able to restored the missing normal.mod file to my broken Linux computer's /boot/grub directory for the /dev/sda5 partition. However, it failed to appeared in grub_rescue's /dev/sda5's /boot/grub directory. I wasn't able to run 'sudo update-grub' while using the repair disk.
I've just burned an Ubuntu-12.04.5-server-i386.iso disk. Can I use it live without installing it on my system? As you know, my aim is to troubleshoot my Ubuntu 12.04 Desktop partition table. Please let me know. Thanks.
I was able to use Ubuntu Server Disk tonight and found that its prvided the same information as Grub Rescue. I didn't find any
directory named discs in /dev as indicated in the following two commands I saw in an article named " Boot Ubuntu Linux into Rescue Mode to fixsystem.html".
I've just run 32-Bit Boot-Repair Disk on my broken system. The URL of the Repair-Info file is htp://paste.ubuntu.com/8328191.
I've looked at it and it's a very long file. Can you two kindly look it over and advise me what to do next?
After taking another look at the repair-info file, I'm inclined to think that it would be better for me to try to salvage my personal files from this broken computer than to revive the /dev/sda5 partition. My orinignal Ubutu 12.04 OS seems to have gone for good.
If you then want to raid-0 those, it can be done on the hardware level or the software level. Hardware is dependant on the controller but you just make another virtual drive and add those 2 drives to it. But if you want Ubuntu to handle the raid-0, it would be software controlled. That is doable but not intuitive at install time.
Or from the ubuntu server cd, you can also setup the partitions. Basically same steps, manually mark disks as raid members. Apply and save. Then go back to the partitioning menu and it should have option near the top to setup raid sets. Once those are setup, back at the main partitioning menu, you should see the new raid-0 set in the partition list. Pick that and setup you boot, root, home partitions. Or at a minimum setup root and let it do the rest. Be sure to mark root or boot as boot-able.
@WNYmathGuy - You are correct on the raid set virtual drives, I didnt understand there where 2 controllers. But why 2 controllers? Get a SAS expander, adding 16,24,48 or more ports to the one controller. Then can setup all kinds of raid sets. That is if that one controller supports expanders. Most main line ones do.
When I deploy new servers through VMWare ESX, I usually copy an existing base that I have already setup. I keep the base image VMDK size small so it is quick to copy. When I have copied the image and am setting up a new server, I adjust the size of the VMDK in VMWare and then use gparted to fill up the space that is added to the end of the virtual disk.
We now need to delete the sda2 partition and re-add it. When we re-add it, we can change the number of cylinders to fill the partition up with all the remaining space. Press p to print the current partitions.
Now we will re-create the partition. Set the partition number to 2, for the starting cylinder, set to whatever was the starting cylinder before. The default should be set as this anyway. For the end cylinder, leave the default as this will have the value of the last available cylinder.
You will now need to reboot. After the reboot we use the pvresize command to fill out the extra space. As fair as I can tell, this resizes the amount of space that a LVM volume group can use on a partition and needs to be run if you resize its partition.
c80f0f1006