[opensuse-factory] Rescue program on dvd
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I know the rescue option in the dvd had to be dropped. Too problematic, and no maintainer. Could some of it be "rescued"? The thing that fails most is grub. Just a repair grub, perhaps a repair missing kernel/initrd? Once the system boots, the user should be able to repair the rest (hope). :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkyodsMACgkQtTMYHG2NR9W3mACeL4xQWJevZF3nzSzbYWKtz3dP yQMAnjtrUrfJRGrGfoyEouiJN6Q2XH37 =T2Uo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Søndag den 3. oktober 2010 14:27:46 skrev Carlos E. R.:
I know the rescue option in the dvd had to be dropped. Too problematic, and no maintainer.
Could some of it be "rescued"?
The thing that fails most is grub. Just a repair grub, perhaps a repair missing kernel/initrd?
Once the system boots, the user should be able to repair the rest (hope).
I've been wondering if this functionality isn't still "available" (almost), by simply booting the cd/dvd media, select "Boot from harddisk", once the installed system is booted, run yast bootloader to install grub properly again. But I'm unsure how much you can break your bootloader installation and still be able to use the "boot from harddisk" option. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2010-10-03 at 14:35 +0200, Martin Schlander wrote:
Søndag den 3. oktober 2010 14:27:46 skrev Carlos E. R.:
Could some of it be "rescued"?
The thing that fails most is grub. Just a repair grub, perhaps a repair missing kernel/initrd?
I've been wondering if this functionality isn't still "available" (almost), by simply booting the cd/dvd media, select "Boot from harddisk", once the installed system is booted, run yast bootloader to install grub properly again.
But I'm unsure how much you can break your bootloader installation and still be able to use the "boot from harddisk" option.
No, you can't. Not with the current option, that is. Time ago, but not long ago, there were two similar options. One, is to simply load the hard disk MBR and boot it, as if the DVD was not inserted. This is currently the default option of the DVD, by the way. It is obvious that if the HD boot sequence is broken, it will not work. This is what we currently have. The other option, which was removed, booted the HD system (after asking which partition had it), but using the kernel in the DVD entirely. If the HD had no kernel at all, this option would still boot (with an older kernel, of course). This second option did allow for a kernel reinstall, download, grub repair, etc. The lot. Very usefull - and removed. :-( - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkyoe7UACgkQtTMYHG2NR9UeeACfeDDSrwcNHXMNK+uw9wfmvbr/ pFEAni9qwFSdQ6xRXnXEWbqTPZkTKYod =NxCW -----END PGP SIGNATURE-----
On Sunday 03 October 2010 07:48:52 Carlos E. R. wrote:
On Sunday, 2010-10-03 at 14:35 +0200, Martin Schlander wrote: ...
But I'm unsure how much you can break your bootloader installation and still be able to use the "boot from harddisk" option. ... The other option, which was removed, booted the HD system (after asking which partition had it), but using the kernel in the DVD entirely. If the HD had no kernel at all, this option would still boot (with an older kernel, of course).
Yes, that was lost in attempt to create complete rescue system that will take care of any possible problem that is now abandoned altogether.
This second option did allow for a kernel reinstall, download, grub repair, etc. The lot. Very usefull - and removed. :-(
It shouldn't be so big deal to have some script that will: - attempt to mount partitions, - check for kernel and initrd presence, - if multiple kernels and initrds are present, collect info to list it as boot option - try to identify openSUSE partitions looking at /etc/SuSE-release - use information from SuSE-release to label partitions in the list - present list to the user and ask what to boot Above will solve boot loader problem. Problem with single kernel left after update that doesn't boot should be solved with multiple kernels available, not with rescue system. That will solve problem with broken or non existing initrd too. All that is asked is:"Don't burn all bridges, before you are sure that new one will stand." (but that is the problem with distro direction that is discussed in opensuse- project ML) -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le 03/10/2010 17:32, Rajko M. a écrit :
It shouldn't be so big deal to have some script that will: - attempt to mount partitions, - check for kernel and initrd presence, - if multiple kernels and initrds are present, collect info to list it as boot option - try to identify openSUSE partitions looking at /etc/SuSE-release - use information from SuSE-release to label partitions in the list - present list to the user and ask what to boot
Above will solve boot loader problem.
not so easy because of a rarely said fact: openSUSE is the only distribution really RAID and LVM friendly, but this allows a variety of boot systems very difficult to debug
Problem with single kernel left after update that doesn't boot should be solved with multiple kernels available, not with rescue system. That will solve problem with broken or non existing initrd too.
All that is asked is:"Don't burn all bridges, before you are sure that new one will stand."
there is an option for this in zypper. It have some drawbacks that could easily be overcome with some twitting (limiting to 2/3 kernels,making the boot option title fancier) jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 10/03/2010 11:42 AM, jdd wrote:
Le 03/10/2010 17:32, Rajko M. a écrit :
It shouldn't be so big deal to have some script that will: - attempt to mount partitions, - check for kernel and initrd presence, - if multiple kernels and initrds are present, collect info to list it as boot option - try to identify openSUSE partitions looking at /etc/SuSE-release - use information from SuSE-release to label partitions in the list - present list to the user and ask what to boot
Above will solve boot loader problem. not so easy because of a rarely said fact: openSUSE is the only distribution really RAID and LVM friendly, but this allows a variety of boot systems very difficult to debug
Problem with single kernel left after update that doesn't boot should be solved with multiple kernels available, not with rescue system. That will solve problem with broken or non existing initrd too.
All that is asked is:"Don't burn all bridges, before you are sure that new one will stand." there is an option for this in zypper. It have some drawbacks that could easily be overcome with some twitting (limiting to 2/3 kernels,making the boot option title fancier)
jdd
A graphical representation for " Reinstall Grub Bootloader " from the boot menu of the Live CD/DVD would help immensely especially for openSUSE newcomers. Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2010-10-03 at 10:32 -0500, Rajko M. wrote:
On Sunday 03 October 2010 07:48:52 Carlos E. R. wrote:
On Sunday, 2010-10-03 at 14:35 +0200, Martin Schlander wrote:
...
The other option, which was removed, booted the HD system (after asking which partition had it), but using the kernel in the DVD entirely. If the HD had no kernel at all, this option would still boot (with an older kernel, of course).
Yes, that was lost in attempt to create complete rescue system that will take care of any possible problem that is now abandoned altogether.
No, that was dropped two releases earlier. It was an option independent of the rescue system. You had to boot the installation system, and at the point of choosing install or upgrade, or thereabouts, there was another option to boot an installed system.
Above will solve boot loader problem.
Problem with single kernel left after update that doesn't boot should be solved with multiple kernels available, not with rescue system. That will solve problem with broken or non existing initrd too.
No; that's prevention, not solving.
All that is asked is:"Don't burn all bridges, before you are sure that new one will stand." (but that is the problem with distro direction that is discussed in opensuse- project ML)
You should have a look "down on the forums". Almost every day there is someone with an unbootable system. These newcomers ask in the forum, not in the mail lists. And if devs don't look "down there" they miss a big part of the picture. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkyot3wACgkQtTMYHG2NR9VwVgCdGF413hzabn0mc6yyF9cnQW1p JMQAn0rNZ5DM37f0jn3vWOx+hjqMfK9N =N1mw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 10/03/2010 01:03 PM, Carlos E. R. wrote:
On Sunday, 2010-10-03 at 10:32 -0500, Rajko M. wrote:
On Sunday 03 October 2010 07:48:52 Carlos E. R. wrote:
On Sunday, 2010-10-03 at 14:35 +0200, Martin Schlander wrote:
...
The other option, which was removed, booted the HD system (after asking which partition had it), but using the kernel in the DVD entirely. If the HD had no kernel at all, this option would still boot (with an older kernel, of course).
Yes, that was lost in attempt to create complete rescue system that will take care of any possible problem that is now abandoned altogether.
No, that was dropped two releases earlier. It was an option independent of the rescue system. You had to boot the installation system, and at the point of choosing install or upgrade, or thereabouts, there was another option to boot an installed system.
Above will solve boot loader problem.
Problem with single kernel left after update that doesn't boot should be solved with multiple kernels available, not with rescue system. That will solve problem with broken or non existing initrd too.
No; that's prevention, not solving.
All that is asked is:"Don't burn all bridges, before you are sure that new one will stand." (but that is the problem with distro direction that is discussed in opensuse- project ML)
You should have a look "down on the forums". Almost every day there is someone with an unbootable system. These newcomers ask in the forum, not in the mail lists. And if devs don't look "down there" they miss a big part of the picture.
-- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar)
Yes this is true about it being dropped. I actually found it useful. But, instead of replacing it with nothing should we not include something better - more effective? I've also been helping out on the forums. It can get quite intense and consuming. If some one is working on an idea, I would be happy to help. I can't code. However, I can help out on the testing. Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 03 October 2010 11:46:59 Roman Bysh wrote:
On 10/03/2010 11:42 AM, jdd wrote: ...
not so easy because of a rarely said fact: openSUSE is the only distribution really RAID and LVM friendly, but this allows a variety of boot systems very difficult to debug
The fact is that attempt to help RAID and LVM that are not so often present on computers will make simple solution complicated and no one with enough coding abilities will step up and make such script. To go from: 1) single hard disk, multiple partitions setup, which is on 99% of desktop computers (Linux), and on 99.999% when you look on first time users that are the most endangered specie in case of boot problems, to: 2) help to RAID and LVM users too, there is huge difference in amount of work to create solution. For SUSE insider that worked on boot process first should be only few hours of work. Second was actually never solved. Do we really want to abandon 99% to favor lesser then 1% ? ...
All that is asked is:"Don't burn all bridges, before you are sure that new one will stand."
there is an option for this in zypper. It have some drawbacks that could easily be overcome with some twitting (limiting to 2/3 kernels,making the boot option title fancier)
Problem is that such option is not default and it is not because it is half way done. You can have multiple kernels, but they will stay in /boot and will show in boot menu forever until they are removed manually. Each kernel update will just add new kernel entry and its failsafe option. Manual removal is possible, but it requires from user to learn what can be removed and how to do that, even from users that installed Linux to do something else with it, which, like artwork, we are missing big time. There is also another problem. User has great chance to hit Debian based information, over some Ubuntu advice, and apply wrong solution.
jdd
A graphical representation for " Reinstall Grub Bootloader " from the boot menu of the Live CD/DVD would help immensely especially for openSUSE newcomers.
Ability to boot the system will give you ability to run YaST with all perks it offers, so developing GUI that is not as simple as script that will use text mode, is not urgent need. You probably never used old YaST1 module that allowed to boot from any partition that contained kernel. The only problem with that module it was buried in text mode that shows up when installation fails or it is canceled. It was not user friendliness champion, but it will let you boot system and continue from there.
Roman
-- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le 03/10/2010 22:26, Rajko M. a écrit :
Do we really want to abandon 99% to favor lesser then 1% ?
I have nothing to do with this decision;but it seems that this is what was done, and after the dev asked for help here and nobody answered!
there is an option for this in zypper. It have some drawbacks that could easily be overcome with some twitting (limiting to 2/3 kernels,making the boot option title fancier)
Problem is that such option is not default and it is not because it is half way done.
it's not default, but could be. That said it's only a partial solution, because the problem is often when grub install fails *the first time* and there is no kernel atm.
Ability to boot the system will give you ability to run YaST with all perks it offers, so developing GUI that is not as simple as script that will use text mode, is not urgent need.
You probably never used old YaST1 module that allowed to boot from any partition that contained kernel. The only problem with that module it was buried in text mode that shows up when installation fails or it is canceled. It was not user friendliness champion, but it will let you boot system and continue from there.
of course, I did! there are two things pretty easy to do, patching the *rescue* option: * add some script to take care of the mount -bind (dev, sys, proc), really impossible to manage by a newbie; * just add a script with the necessary steps to go root on the distro: same "mounts -bind", then chroot, the script have just to guess what is the necessary partition or prompt for one (or try any). Mandriva have (had?) a rescue menu: "log rescue" or "log actual install" jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-10-04 at 07:51 +0200, jdd wrote:
Le 03/10/2010 22:26, Rajko M. a écrit :
it's not default, but could be. That said it's only a partial solution, because the problem is often when grub install fails *the first time* and there is no kernel atm.
Many newcomers go to the forums asking for help. After installation of Linux, their computer will not boot, not windows, not Linux. Those that ask have some other computer, or go to a friends or something. Others reformat with windows only. Almost every week there is a problem like this. It gets tiring, because you have to extract information from them about the partitioning, then tell them to repair grub using command line... not easy. And every week the same problem, many don't read previous solutions or don't know how to apply them, need hand holding. I don't think devs here are aware of the problem.
there are two things pretty easy to do, patching the *rescue* option:
* add some script to take care of the mount -bind (dev, sys, proc), really impossible to manage by a newbie;
Quite so. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkypov0ACgkQtTMYHG2NR9WwOgCfQJVUG8zZv7d+GhVL95/p1AYj 3eAAn1Ybk4T01c+H4fdr1EKjKfCffy5w =mtzi -----END PGP SIGNATURE-----
Le dimanche 03 octobre 2010, à 14:27 +0200, Carlos E. R. a écrit :
Hi,
I know the rescue option in the dvd had to be dropped. Too problematic, and no maintainer.
Could some of it be "rescued"?
I guess the answer is yes, if somebody steps up to do so. Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 10/03/2010 02:35 PM, Martin Schlander wrote:
Søndag den 3. oktober 2010 14:27:46 skrev Carlos E. R.:
I know the rescue option in the dvd had to be dropped. Too problematic, and no maintainer.
Could some of it be "rescued"?
The thing that fails most is grub. Just a repair grub, perhaps a repair missing kernel/initrd?
Once the system boots, the user should be able to repair the rest (hope).
I've been wondering if this functionality isn't still "available" (almost), by simply booting the cd/dvd media, select "Boot from harddisk", once the installed system is booted, run yast bootloader to install grub properly again.
But I'm unsure how much you can break your bootloader installation and still be able to use the "boot from harddisk" option.
I proposed a kexec boot option for the dvd a long time ago see : https://bugzilla.novell.com/show_bug.cgi?id=432929 which after using the rescue system (is this what is no longer on the dvd?) and kexec to boot a couple of times seemed a better option than the "boot installed system" option. It has the advantage of booting the system with it's own kernel. Scripting is not a strong point with me and my openSUSE time is taken up by multimedia and a few other things I maintain, blender-2.54 beta is waiting for my attention and it's not an easy update, so I can't help. All the script would have to do is - mount the installed system - locate the correct kernel in /boot - then kexec boot it. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le 05/10/2010 15:47, Dave Plater a écrit :
the installed system - locate the correct kernel in /boot - then kexec boot it.
don't works if the problem is the kernel, as was recently, but nice for grub problems thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-10-05 at 16:15 +0200, jdd wrote:
the installed system - locate the correct kernel in /boot - then kexec boot it.
don't works if the problem is the kernel, as was recently, but nice for grub problems
Correct. Different problems, different solutions. It would be nice if someone could create a rescue cd specially taylored for opensuse systems. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkysX1YACgkQtTMYHG2NR9VVegCdFHzewPHr6eFbBa2QCz61/dxj f/oAniY+FPM50aKyBDWZJAV7xV201ii4 =CBa/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le 06/10/2010 13:36, Carlos E. R. a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2010-10-05 at 16:15 +0200, jdd wrote:
the installed system - locate the correct kernel in /boot - then kexec boot it.
don't works if the problem is the kernel, as was recently, but nice for grub problems
Correct. Different problems, different solutions.
It would be nice if someone could create a rescue cd specially taylored for opensuse systems.
I will try something on studio :-) jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 10/05/2010 04:15 PM, jdd wrote:
Le 05/10/2010 15:47, Dave Plater a écrit :
the installed system - locate the correct kernel in /boot - then kexec boot it.
don't works if the problem is the kernel, as was recently, but nice for grub problems
thanks jdd
Then the kernel from the dvd or cd can be used. Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 10/06/2010 08:02 AM, jdd wrote:
Le 06/10/2010 13:36, Carlos E. R. a écrit :
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2010-10-05 at 16:15 +0200, jdd wrote:
the installed system - locate the correct kernel in /boot - then kexec boot it. don't works if the problem is the kernel, as was recently, but nice for grub problems Correct. Different problems, different solutions.
It would be nice if someone could create a rescue cd specially taylored for opensuse systems. I will try something on studio :-)
jdd
I would recommend using lxde as the DE. Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Wednesday 06 October 2010 schrieb Dave Plater:
On 10/05/2010 04:15 PM, jdd wrote:
Le 05/10/2010 15:47, Dave Plater a écrit :
the installed system - locate the correct kernel in /boot - then kexec boot it.
don't works if the problem is the kernel, as was recently, but nice for grub problems
thanks jdd
Then the kernel from the dvd or cd can be used. Just booting with that kernel is not enough because it might need to load modules that aren't available on the harddisk. You have to redirect /lib/modules/<kernel-version> to the rescue CD to get a fully working system. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le 06/10/2010 14:02, jdd a écrit :
I will try something on studio :-)
jdd
this is the very first draft http://susestudio.com/appliance/edit/265519 right now, with nearly nothing more than a standard minimal X install, starting on init 3 (startx needed to have graphical) what is needed: *script to mount a given partition with bounded system folders. Do you know how a script can understand what are the good partitions? or simply mount all available partitions? * how to add kexec options? please don't make copies (new appliances) from this one before it's a bit better, give advices here of course feel free to dl it and try it (it's only an usb applicance for now) jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2010-10-06 at 18:07 +0200, Markus Koßmann wrote:
Am Wednesday 06 October 2010 schrieb Dave Plater:
On 10/05/2010 04:15 PM, jdd wrote:
Then the kernel from the dvd or cd can be used.
Just booting with that kernel is not enough because it might need to load modules that aren't available on the harddisk. You have to redirect /lib/modules/<kernel-version> to the rescue CD to get a fully working system.
So a rescue system needs several options in order to boot the installed system. One, is booting kernel and modules from the CD, but switch to init on HD. This is needed if the kernel was damaged on the HD. Another, is booting the kernel on the HD entirely. This one can be used if only grub is damaged/missing. Another one? :-? - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkytsoIACgkQtTMYHG2NR9W+swCaAjxsZ70BRsBSojBrHmj1v6il 7goAn2Kzh7zRBOhc0Z4+v5meDuaeXRzY =LGqP -----END PGP SIGNATURE-----
I can't make kexec work. Is the openSUSE kernel compiled with the relevant option (CONFIG_KEXEC=y)? what I did: in place of trying from a live cd, simply trying from the openSUSE installed as vmware (11.3, xfce) - should work! so boot the openSUSE, open a root terminal and type kexec -l /boot/vmlinuz --append=(result of cat /proc/cmdline - copy/paste) --initrd=/boot/initrd return with an error "reading_legacy sectors_per_track failed" then kexec -e fails (freeze the virtual machine) wjat can I do? I have the same error when trying from a live cd thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 01/18/2011 08:08 AM, jdd wrote:
I can't make kexec work. Is the openSUSE kernel compiled with the relevant option (CONFIG_KEXEC=y)?
As always all your booted kernel config is here zcat /proc/config.gz | grep "KEXEC" CONFIG_KEXEC=y
what I did:
in place of trying from a live cd, simply trying from the openSUSE installed as vmware (11.3, xfce) - should work!
so boot the openSUSE, open a root terminal and type
kexec -l /boot/vmlinuz --append=(result of cat /proc/cmdline - copy/paste) --initrd=/boot/initrd
return with an error "reading_legacy sectors_per_track failed"
then kexec -e fails (freeze the virtual machine)
wjat can I do? I have the same error when trying from a live cd
What you foget is to mount where the /boot is :-) it's written in your previous message.
Before kexec you have to mount /boot from the installed system.
Hope this help
thanks jdd
-- Bruno Friedmann (irc:tigerfoot) Ioda-Net Sàrl www.ioda-net.ch openSUSE Member User www.ioda.net/r/osu Blog www.ioda.net/r/blog fsfe fellowship www.fsfe.org GPG KEY : D5C9B751C4653227 vcard : http://it.ioda-net.ch/ioda-net.vcf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le 18/01/2011 08:17, Bruno Friedmann a écrit :
CONFIG_KEXEC=y
ok
What you foget is to mount where the /boot is :-)
no, I only try to boot the present run. it's faster for tests to boot openSUSE and right then try to reboot with kexec. anyway I tested the two options (direct reboot or from a live cd) with the exact same result the only problem I see is the error message (reading_legacy sectors_per_track failed" that is issued after the kernel load (first kexec) and don't crash the system, so I can in,vestigate more, but how? thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, 18 Jan 2011 09:45:34 +0100
jdd
the only problem I see is the error message (reading_legacy sectors_per_track failed" that is issued after the kernel load (first
I guess you forgot to quote the "--command-line" parameters. Just try it with kexec --initrd=/boot/initrd --reuse-cmdline -l /boot/vmlinux kexec -e I use this all the time in production systems to save the few minutes the BIOS needs to initialize everything and it works well (on SLES11SP1 though). It did not work for me in KVM, but I *guess* that KVM just crashed on the kexec operation, similar as it does when trying to suspend to disk. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Last notice... the kexec works when (re)booting an openSUSE running system (boot normally, open a root xterm and key in the kexec basic -l and --initrd), but I can't make it work from a live cd (built from studio). Of course, I mount the root partition and give the correct location for the kernel. In fact boot begins, I have the messages on screen (I can see usb messages) then the screen is blurred. sometime there is no more signal coming to the monitor, sometime the machine is simply freezed tests are done on a perfectly working install... jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (11)
-
Bruno Friedmann -
Carlos E. R. -
Carlos E. R. -
Dave Plater -
jdd -
Markus Koßmann -
Martin Schlander -
Rajko M. -
Roman Bysh -
Stefan Seyfried -
Vincent Untz