Skip to main content

Posts

Dell Vostro 1520 Boot problem, Recovering & restore Grub from a live Ubuntu cd.

In Vostro 1520 Dell Laptop series, when Ubuntu installed with windows (Dual Boot), due to a problem in bios the MBR will get corrupted and after that you will be unable to see the Grub loader at the startup and you want be able to load either windows or Ubuntu. This happens only because of the corruption at MBR record or partition table.  So by reinstalling grub to the partition u can resolve this problem. The steps of resolving are given below. First you have to boot from the Ubuntu Live CD Then you have to find the sd number of the partition that grub is installed in. ( If you have a separate /boot partition it should be the boot partition sd number otherwise it should be the Ubuntu file system sd number. ). And here I assume that sd number is x . Open the Terminal and execute following codes sudo mkdir /mnt/root -- Setup a folder before change root. Using th...

Linux Mint updates bug found

Bug Description : Failed to fetch http://packages.linuxmint.com/dists/isadora/Release (malformed Release file?) Unable to find expected entry multiverse/binary-i386/Packages in Meta-index file Some index files failed to download, they have been ignored, or old ones used instead. Reasoning and Solution : There is no multiverse section in the Mint repository... please edit your /etc/apt/sources.list and remove the "multiverse" keyword from the lines referring to the Mint repositories.   How to Fix it: This command will open the sources list. ~$ sudo gedit /etc/apt/sources.list This is my file before editing and after editing Before :- deb http://packages.linuxmint.com/ isadora main upstream import multiverse import deb http://archive.ubuntu.com/ubuntu/ lucid main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ lucid-updates main restricted universe multiverse deb http://security.ubuntu.com...

How to fix grub loader when its not loading at the boot

When you installed or restore a Microsoft Windows after the Linux installation you won't see the grub loader is loading at the boot. This is not a error of grub or Linux. But you couldn't load Linux at this situation. There are few ways of fixing this issue. One way is using super grub disk. Here I will tell you an another way of fixing this issue. You just have to boot using any type of Linux CD/DVD Now Open the terminal and type sudo grub and type the password to enter the kernel mode. Now you have to find out few things. First find the hd number of the hard disk. This is normally zero since we are using one hard disk only. But if we are using more of them we have to find out the hd number of the hard disk. Then find the sd number of the partition which contains grub. If you are not partitioned a separate /boot partition at the Linux installation this is same as the ...

Customize your grub loader by just editing a file

You can find a file called menu.lst in the path /boot/grub. By editing this file you can customize your Grub loader easily. First we can set the time out amount of the grub. Go to Section ## timeout sec and set timeout value to an amount of seconds as you like. Then you can Customize the view by changing the colors. It is under # Pretty colors. Then comes the most important thing of the Grub menu list. Find out the kernel list in the File. Normally it is in the bottom. Sample section for one kernel is given below. title        Linux Mint 7 Gloria, kernel 2.6.28-16-generic root       faaab6f9-539b-4f1a-82fc-b5a18887d28d kernel    /vmlinuz-2.6.28-16-generic root=UUID=6a2a464d-bf70-4b4a-8c8e-8dad3ccafe2c ro quiet splash initrd      /initrd.img-2.6.28-16-generic quiet You can always change the title as you wish. root is the UUID of the boot part...

How to mount a partition permanently some where in the folder structure.

First check this post and come to this section How to edit file /etc/fstab You needed to add the following line to the fstab file. # / was on /dev/sdax during installation UUID=xxxx /media/xxxxxxxxx xxx relatime,errors=remount-ro a b xxxx - UUID of the partition x - number of the partition you needed to mount xxx - file format of the partition xxxxxxxxx - Name of the Partition** a - dump b - pass ** Name of the partition should be the same as the Real name of the partition (The name we can see at the Computer (Simultaneous to My Computer in Microsoft Windows)). An example line for this is # /media/MyDisk was on /dev/sda8 during installation UUID=64839f40-b2f1-412f-ae1a- c5a213ba449a /media/MyDisk ntfs relatime,defaults-ro 0 2 It is recommended to have name without spaces here. Because spaces can cause troubles. 

How to overcome the problem Linux kernel image is not booting properly

First check this post and come to this section How to edit file /etc/fstab This is the part of the fstab file that needed in this matter. # / was on /dev/sda x during installation UUID= xxxx / ext3 relatime,errors=remount-ro a b # swap was on /dev/sda y during installation UUID= yyyy none swap sw c d /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8  0 0 x should be the number of the partition of the ubuntu installed y should be the number of swap xxxx - UUID of Ubuntu partition yyyy - UUID of swap a - dump            (0 is my recommendation) c - dump            (0 is my recommendation)      b - pass             (1 is my recommendation) d - pass        ...