(SOLVED)Help, Tried to install 2nd copy of Linux and now I cant boot 1st copy
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unless I'm mistaken the core.img entry with grub legacy won't work unless grub legacy is fixed with a patch to boot ext4,
That could be the problem. I remember reading that booting ext4 partitions with Grub Legacy was a problem. Running PCLinuxOS here, it still uses Grub Legacy and booting with the core.img entry works fine so that may be the OP's problem.
I agree with the above post. Delete sda3 and sda4. You can then either create a data partition with the remaining space on sda2 which now only contains swap or you can delete the Extended partition which contains the swap, create a new swap partition in the Extended and resize your Mint partition to include the rest of the drive. I'd go with the first option, much easier since your Mint partition is already 250GB.
Your previous post indicate Mint is on sda1. Since you can now boot Mint, when you do open a terminal and run this command: df
This should show output similar to below:
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 39G 14G 24G 36% /
If while booted into Mint you see '/dev/sda1' under the 'Filesystem' column and the root symbol (/ forward slash) under 'Mounted on', then you know Mint is on sda1. Running sudo fdisk -l will show you that sda2 is an Extended partition and sda5 is your swap. So deleting sda3 and sda4 should just delete your CentOS boot partition and the LVM partition. Just pay attention to what you are doing.
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000c356b
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 485378047 242688000 83 Linux
/dev/sda2 972599294 976771071 2085889 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda3 485378048 486402047 512000 83 Linux
/dev/sda4 486402048 972597247 243097600 8e Linux LVM
/dev/sda5 972599296 976771071 2085888 82 Linux swap / Solaris
Partition table entries are not in disk order
Disk /dev/mapper/VolGroup-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_root doesn't contain a valid partition table
Disk /dev/mapper/VolGroup-lv_home: 191.0 GB, 191012798464 bytes
255 heads, 63 sectors/track, 23222 cylinders, total 373071872 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_home doesn't contain a valid partition table
Disk /dev/mapper/VolGroup-lv_swap: 4227 MB, 4227858432 bytes
255 heads, 63 sectors/track, 514 cylinders, total 8257536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap doesn't contain a valid partition table
Ok that worked too....Thanks! I had to deactivate sda4 to delete it.
sda2 is empty do you know what its doing and do I need it? Its 1.99g with 100% free.
What does this mean---> Partition 2 does not start on physical sector boundary.
Why does sda5 say "solaris"
user@laptop ~ $ sudo fdisk -l
[sudo] password for user:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000c356b
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 972597247 486297600 83 Linux
/dev/sda2 972599294 976771071 2085889 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 972599296 976771071 2085888 82 Linux swap / Solaris
user@laptop ~ $
/dev/sda2 shows to be the extended partition in your output of fdisk. It should be safe to get rid of it, but it looks like /dev/sda5 is your swap and may lie within the extended partition, judging by the sector counts. Both the extended and swap partitions end at 976771071. Not sure why it is seen as Solaris. If you want, you could use your install disk or a live CD to remove all partitions except for /dev/sda1 and then create a new swap, which should then be a new /dev/sda2
The "does not start on physical sector boundry" appears to be caused by a problem with sector size. From your fdisk:
From what I have read, it looks like the Centos partitioner may have had problems when it re-sized your original Mint partition and created the extended partition and LVM, due to the structure of the existing setup and sector size.
There is information at other places concerning the error. You can Google it if you want to know more. People seem to think that it is a minor error.
[QUOTE]Why does sda5 say "solaris"/QUOTE] This is normal. If it was me I would leave things as they are. Gparted will most likely show sda1 (/) as a primary partition, sda2 as a extended partition and sda5 (swap/solaris} located within sda2, and free space following sda2. If you decide to try another distro don't select the lvm option during partitioning, and look for an option to install grub to the partition of the distro that you are installing if your not replacing mint.
Last edited by colorpurple21859; 02-19-2014 at 05:33 AM.
Cent0s was a HUGE disappointment anyway. Nothing worked! All the fixes to fix the not working thing failed. It took 7 steps to fix one thing and all 7 steps usually didnt work. What a mess!!! If Mint was anything like C6 I would be back using winXP.
Your Extended partition (sda2) is almost the exact size of your swap partition (sda5) so you seem to have it the way your originally did with Mint on one large partition and your swap in the Extended. I'd leave it the way it is.
Thanks you VERY much everyone who helped me fix my computer. In the process of doing this I also accidentally erased my usb backup of all passwords and bookmarks when I installed tails (to test and try). So I really wanted to get this back up and running.
Not having your exact computer is like sleeping on a hotel pillow, its just not the same as "YOUR" pillow.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Is there any site that has beginner 101 Linux FAQ?
I dont even know where Linux stores installed programs and stuff like that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.