Kernel boot options removed by fault, no boot options Post: 302530020

Sponsored Content

Operating Systems Linux Ubuntu Kernel boot options removed by fault, no boot options Post 302530020 by cdt on Sunday 12th of June 2011 08:23:35 AM

06-12-2011

Registered User

[SOLVED] Kernel boot options removed by fault, no boot options

Hello Everyone,

First of all, I highly appreciate all Linux forum members and whole Linux community.

. I wish you the best for all of you !

I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went good so far (Vbox, developing, Unix scripting, etc); I am not a very beginner in UNIX, having some skills in PHP/MYSQL/APACHE/BASH/LINUX - WIN/BATCH as well (several years, let's say).

But what is happening now,

is putting me into a trouble: yesterday I have performed some wifi kernel modules installation with Synaptic and some new kernel were added to boot menu, some of them with --recovery option, some of them new ones. Uninstalling these last wifi modules (and probably another ones), all kernel modules (including the current (and good) one were uninstalled, of course, they disappeared from the boot menu as well).

I agree that was totally my fault because I have installed wifi modules which have required kernel recompiling, but I dd not know then the full image of this disaster.

In the last open session (just before reboot), I have seen that all kernel images/module disapperared from /root folder, /vmlinuz file disappeared too; of course using GUI boot loader, I have observed only 2 Memory test options and the M$Win OS (the second OS installed).

My issue now is: I would like to repair the previous Mint 10 installation, no to reinstall because it is taking some time to reparameter all settings .. if it is possible.

CURRENT STATUS:
> I have a Linux Mint 10 burned disk (this one where I typing these lines);
> wired/wireless network on;
> all partitions are not changed
> Linux Mint boot menu has only 2 Mem test option + 1 M$Win OS boot option
> Old Linux kernel definitions is missing from boot menu as well as from:
/root folder
in the / [root] there is no any vmlinuz binaries (I don't remember the correct name for the vmlinuz ..)
> I am able to burn any CD/DVD's, download any binaries/apps from the internet and so on.
> I am online now, ready to give you all details you need about my steps performed yesterday (as much as I remember ;(( -- poor of me ...)

QUESTIONS FOR YOU:
> I would like to avoid the full reinstallation in order to keep the old and full Linux Mint 10 destop;
> I would like to repair the linux kernel, putting it in the right place (/root, /) and create again the records in boot menu, in order to boot again LM10 as it was until yesterday evening.
> Hoping that this problem could have a solution, would you be kind to advise me a good procedure to peform (to install) as this kernel changes to do not happen again in the future.

Hoping that someone of you has encountered this before, I am here to follow your instructions. If the name of this topic could be redefined (in order to reflect this issue better), please do so or suggest me to do, I have not used so much the discussion forums until now, but I will do from now on

...

All the best for you.

Cristian

Last edited by cdt; 09-09-2011 at 01:33 AM..

cdt

View Public Profile for cdt

Find all posts by cdt

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

menu.lst, boot options?

Hi all, I would like to have some details on menu.lst!! the reason is ,if i am trying to add my own boot option where do i need to add it? is it in menu.lst only or elsewere(am referring to unix os) because i tried adding a unique boot option and it was not reflected when the system booted?...

2. HP-UX

Boot Options on HP PA-RISC and Itanium Servers

I've never really explored the options available in the boot firmware on our servers. Outside of needing to change boot device paths a few times for various reasons, I'm wondering what the implications are of turning off FASTBOOT. According to the man page for 'setboot', it seems that when...

3. Solaris

Boot options - DVD drive read error

I was wondering if there was a way to boot from openboot from the dvd drive. I was thinking about imaging the dvd to a blank drive and going about it that way. I just need to do a flash install.

4. Solaris

Loading Kernel module at boot

Is there any link/tutorial on loading Solaris kernel modules at boot time??

5. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and...

6. UNIX for Dummies Questions & Answers

New kernel won't boot

I compiled new kernel in linux 10.04 called linux-2.6.26.8-xenomai, it runs alongside the other kernel, but when I want to boot it I get an error message saying: Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sda5 does not exist. After making the modules and headers I made the...

7. Slackware

/boot: how do I change the current kernel?

Slackware 14.0 Hi: I once changed the smp kernel running in my system by another one in /boot. What I did was to relink /boot/System.map, /boot/vmlinuz and /boot/config. But I don't remember if I did something else. Would that alone be OK.

8. Linux

Unload kernel module at boot time (Debian Wheezy 7.2, 3.2.0-4-686-pae kernel)

Hi everyone, I am trying to prevent the ehci_hcd kernel module to load at boot time. Here's what I've tried so far: 1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here): 2) Blacklisted the module by adding the following string to 3) Tried to blacklist the module...

LEARN ABOUT FREEBSD

nextboot

NEXTBOOT(8)						    BSD System Manager's Manual 					       NEXTBOOT(8)

NAME

     nextboot -- specify an alternate kernel and boot flags for the next reboot

SYNOPSIS

     nextboot [-e variable=value] [-f] [-k kernel] [-o options]
     nextboot -D

DESCRIPTION

     The nextboot utility allows specifying some combination of an alternate kernel, boot flags and kernel environment for the next time the
     machine is booted.  Once the loader(8) loads in the new kernel information, it is deleted so in case the new kernel hangs the machine, once
     it is rebooted, the machine will automatically revert to its previous configuration.

     The options are as follows:

     -D 	 Invoking nextboot with this option removes an existing nextboot configuration.

     -e variable=value
		 This option adds the provided variable and value to the kernel environment.  The value is quoted when written to the nextboot
		 configuration.

     -f 	 This option disables the sanity checking which checks if the kernel really exists before writing the nextboot configuration.

     -k kernel	 This option specifies a kernel directory relative to /boot to load the kernel and any modules from.

     -o options  This option allows the passing of kernel flags for the next boot.

FILES

     /boot/nextboot.conf  The configuration file that the nextboot configuration is written into.

EXAMPLES

     To boot the GENERIC kernel with the nextboot command:

	   nextboot -k GENERIC

     To enable into single user mode with the normal kernel:

	   nextboot -o "-s" -k kernel

     To remove an existing nextboot configuration:

	   nextboot -D

SEE ALSO

     boot(8), loader(8)

HISTORY

     The original nextboot manual page first appeared in FreeBSD 2.2.  It used a very different interface to achieve similar results.

     The current incarnation of nextboot appeared in FreeBSD 5.0.

AUTHORS

     This manual page was written by Gordon Tetlow <gordon@FreeBSD.org>.

BUGS

     The nextboot code is implemented in the loader(8).  It is not the most thoroughly tested code.  It is also my first attempt to write in
     Forth.

     Finally, it does some evil things like writing to the file system before it has been checked.  If it scrambles your file system, do not blame
     me.

BSD
								 January 31, 2012							       BSD