bootlader issue lilo

General talk about packaging procedures and packages.
noob51
Posts: 54
Joined: 22. Oct 2013, 16:56

Re: bootlader issue lilo

Post by noob51 » 14. Dec 2013, 13:31

I have lilosetup installed, i set ubuntu and salix flags and reinstalled lilo with following output:




# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-29-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-1
initrd = /boot/initrd.img-3.2.0-29-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-37-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-2
initrd = /boot/initrd.img-3.2.0-37-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-38-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-3
initrd = /boot/initrd.img-3.2.0-38-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-39-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-4
initrd = /boot/initrd.img-3.2.0-39-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-40-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-5
initrd = /boot/initrd.img-3.2.0-40-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-41-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-6
initrd = /boot/initrd.img-3.2.0-41-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-43-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-7
initrd = /boot/initrd.img-3.2.0-43-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-44-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-8
initrd = /boot/initrd.img-3.2.0-44-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-45-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-9
initrd = /boot/initrd.img-3.2.0-45-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-48-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-10
initrd = /boot/initrd.img-3.2.0-48-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-51-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-11
initrd = /boot/initrd.img-3.2.0-51-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-52-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-12
initrd = /boot/initrd.img-3.2.0-52-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-53-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-13
initrd = /boot/initrd.img-3.2.0-53-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /boot/vmlinuz-3.2.0-54-generic
root = /dev/disk/by-uuid/d4c88296-b03e-4768-8f48-be7eb16416b7
label = Ubuntu-14
initrd = /boot/initrd.img-3.2.0-54-generic
read-only
# Linux bootable partition config ends
#
# Linux bootable partition config begins
image = /tmp/lilosetup/mnt/sda6/boot/vmlinuz-huge-smp-3.2.45-smp
root = /dev/disk/by-uuid/6ef7746f-8a84-4a9e-994a-653e72993a88
label = Salix
read-only
# Linux bootable partition config ends

Ubuntu fails to boot, hard to read error mssgs now.

User avatar
mimosa
Salix Warrior
Posts: 3101
Joined: 25. May 2010, 17:02
Contact:

Re: bootlader issue lilo

Post by mimosa » 14. Dec 2013, 14:30

How did you get all those kernels in your Ubuntu /boot?

You'd need to find out which kernel is actually required by your Ubuntu system, and boot that one.

I don't know about Ubuntu internals, but in Salix, /lib/modules contains a subdirectory with the same name as the kernel. So, mount your Ubuntu partition and try

ls /path/to/Ubuntu/partition/lib/modules

then look for that number in the lilo config file posted above, and try booting the corresponding Ubuntu option.

noob51
Posts: 54
Joined: 22. Oct 2013, 16:56

Re: bootlader issue lilo

Post by noob51 » 14. Dec 2013, 16:06

I was able to boot to a prompt which says : error in locking authority file Xauthority when I try to startx.
Also : the disk drive for / is not yet ready or present.

Mount folder in ubuntu partition is empty.

User avatar
mimosa
Salix Warrior
Posts: 3101
Joined: 25. May 2010, 17:02
Contact:

Re: bootlader issue lilo

Post by mimosa » 14. Dec 2013, 20:44

Please answer about the kernel. How were you able to boot? Which option did you choose?

For people to help you, you need to be as specific as possible in the information you give (what did you do? what happened?), and answer any questions.

noob51
Posts: 54
Joined: 22. Oct 2013, 16:56

Re: bootlader issue lilo

Post by noob51 » 15. Dec 2013, 00:22

I followed instructions and attempted to boot the ubuntu #14, proceeded with manual mount, Root file system check failed, maintenance shell only.

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda6
label = Linux
read-only
# Linux bootable partition config ends

I'm trying to compare to the lilo.conf-example file.

User avatar
mimosa
Salix Warrior
Posts: 3101
Joined: 25. May 2010, 17:02
Contact:

Re: bootlader issue lilo

Post by mimosa » 15. Dec 2013, 01:18

What do you mean, trying to compare? Where does the snippet of lilo configuration in your most recent post come from? I can't see it anywhere in the longer section you posted before.

It looks as though you have several Ubuntu installations, and something very strange is going on with at least one of them (too many kernels in /boot). It might be helpful if you could give some background. Was everything working fine before you installed Salix?

noob51
Posts: 54
Joined: 22. Oct 2013, 16:56

Re: bootlader issue lilo

Post by noob51 » 15. Dec 2013, 21:31

One month ago after an update I could no longer boot into xubuntu gui. Unable to fix it I split the parttion and installed salix. To recover my data I chowned the whole ubuntu partition and moved my documents to salix,but did not chown it back to root. I have been playing with lilo and fsck with non root permissions. I will probably wipe the partition but am afraid to loose the mbr, boot partition.

Any suggestions.

User avatar
gapan
Salix Wizard
Posts: 5532
Joined: 6. Jun 2009, 17:40

Re: bootlader issue lilo

Post by gapan » 15. Dec 2013, 22:35

Wait.

Does salix boot and function correctly with your setup right now? If it does, your ubuntu problems might be completely different that setting up lilo to boot ubuntu. Since you already said that you dropped ubuntu because it stopped working properly, probably it's still broken and using lilo won't change that.

If you are sure about which partition your ubuntu resides in, formatting the partition won't change a thing. The MBR will not be affected and the salix installation won't be affected either. But don't delete the partition. That may result in renumbering the partitions and you don't want that, it may get messy.
Image
Image

noob51
Posts: 54
Joined: 22. Oct 2013, 16:56

Re: bootlader issue lilo

Post by noob51 » 16. Dec 2013, 17:14

Good advice, reformating vs. deleting.


Thanks.

Post Reply