in suse linux enterprise desktop 10 ,whan i do online updates , knowingly or unknowingly i checked the kernel version.
after rebooting the message displayed is error 15: file not found .{and also in the recovery mode }
then i go to use another OS ubuntu 8.04kerrnel 2.6.24-16.In this, when we updates online or using package manager or add or remove program it shows depackage error and we maually correct the problem .then we rebooting the computer it shows four versions of ubuntu os ubuntu 8.04.1 kernel 2.6.24-22 , 2.6.24-.21 , 2.6.24-19 , 2.6.24-16, and suse linux 10 .OS not seen .
how can i use the suse linux os without reinstallation.?(and in ubuntu after updating online updates now the ubuntu is ubuntu 8.04.3 LTS kernel 2.6.24-24.)
If you are habitually booting from Ubuntu’s bootloader and you do an online update in Suse, the pointer to Suse in Ubu’s menu.lst becomes obsolete and you get “file not found”. You can inoculate the menu.lst for Grub in Ubuntu by using a generic pointer that is not dependent on the kernel version that exists in Suse. For more on that see this tutorial: HowTo Boot / Multiboot openSUSE from the Grub Bootloader in Ubuntu
On the other hand, if you prefer to boot habitually from Suse’s bootloader, and not have it fail whenever you have a kernel upgrade in Ubuntu, you can do much the same thing (slight variations) and inoculate Suse’s menu.lst against changes to Ubu’s kernel. There’s a tutorial for that here: HowTo Boot / Multiboot Ubuntu from the Grub Bootloader in openSUSE
This all applies equally to openSUSE as to SLED/SLES 10.0
If you are using Ubuntu’s loader, Ubuntu will appear at the top of the list.
If you are using SLED’s loader, SLED will appear at the top of the list.
Edit these lines into the menu.lst that lives in Ubuntu:
# Swerdna's entry to boot the SLED installation on /dev/sdaX by symlinks
title SLED 10 (on /dev/sdaX) by symlinks
root (hd0,Y)
kernel /boot/vmlinuz root=/dev/sdaX
initrd /boot/initrd
savedefault
boot
You can open the file for editing in Ubuntu by running this command:
gksu gedit /boot/grub/menu.lst
Replace X by your partition number for the root partition of SLED as seen from Ubuntu. You can deduce X by running this command in Ubuntu:
sudo fdisk -l
Replace Y by the number you get when you subtract one from X.
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0006fbd2
Device Boot Start End Blocks Id System
/dev/sda1 1 13055 104864256 83 Linux
/dev/sda2 13056 26110 104864287+ 83 Linux
/dev/sda3 * 26111 26241 1052257+ 83 Linux
/dev/sda4 26242 38913 101787840 f W95 Ext’d (LBA)
/dev/sda5 26242 26764 4200966 82 Linux swap / Solaris
/dev/sda6 26765 31985 41937651 c W95 FAT32 (LBA)
/dev/sda7 31986 35632 29294496 83 Linux
/dev/sda8 35633 38913 26354601 83 Linux
elcot@elcot-laptop:~$
I think that the boot loader is present in the sda3.Shall I proceed?
Then in which place, Should I edit “Swerdna Entries And those lines” in the Menu lst of Ubuntu?
use the gksu gedit command to open it. Right under this line:
### END DEBIAN AUTOMAGIC KERNELS LIST
put one space/empty line then these lines:
# Swerdna's entry to boot the SLED installation on /dev/sda3 by symlinks
title SLED 10 (on /dev/sda3) by symlinks
root (hd0,2)
kernel /boot/vmlinuz root=/dev/sda3
initrd /boot/initrd
savedefault
boot
yes. we done what you said above. Then booting into **SLED 10 (on /dev/sda3) by symlinks **, it goes many lines up and finally shows the following
loading reiserfs
waiting for device /dev/sda3 to appear: OK
rootfs:major=8 minor=3 devn=2051
fsck 1.38 (30 june 2005)
(here there are 3 lines seen we did not take down notes)
file syestem is clean
replaying journal : done
reiserfs journal '/dev/sda 3’in blocks [18…8211]: o transactions replayed
checking internal tree … finished
fsck succeeded . mounting root device read- write.
mounting root /dev/sda3
RieserFS:sda3:found reiserfs farmat “3.6” with standard journal
RieserFS:sda3:using ordered data mode
reiserfs:sda3:using jlush barriers
RieserFS:sda3:journal params:device sda3,size 8192,journal first block 18,max trans len 1024,max batch 900,max commit age 30,max trans age 30.
RieserFS:sda3:checking transaction log (sda3)
RieserFS:sda3:using r5hash to sort names
No init found.try passing init=option to the kernel
umount: /dev/ device is busy
umount: /dev/ device is busy
kernel panic - not syncing: Attempted to kill init!
(here we press and hold down the computer power button to shutdown the computer)
then what is the problem?
then what we will do?
The boot succeeded in that Grub found then /boot/symlinks – but there is an additional problem, perhaps with the reiserfs partition as illustrtaed by the fsck dialogue. So two things to do now:
No 1: can you explain more of this statement:
in suse linux enterprise desktop 10 ,whan i do online updates , knowingly or unknowingly i checked the kernel version.
No 2: boot into Ubuntu. Make a directory sda3 in /mnt and then mount sda3 into the directory /mnt/sda3. And then run these commands:
cat /mnt/sda3/etc/SuSE-release
ls -l /mnt/sda3/boot | egrep “initrd|vmlinuz”
And post the results back.
Post Script: this is very telling but I don’t know how to interpret it – maybe someone else does:
No init found.try passing init=option to the kernel
umount: /dev/ device is busy
umount: /dev/ device is busy
swerdna adjusted his/her AFDB on Friday 24 Jul 2009 07:36 to write:
>
> The boot succeeded in that Grub found then /boot/symlinks – but there
> is an additional problem, perhaps with the reiserfs partition as
> illustrtaed by the fsck dialogue.
swerdna, maybe the fsck is because he is having to physically having to
power of as the system is halted and not a filesystem error as it seems to
pass the check ?
Sorry for sticking my nose in but was trying to work out what might be wrong
myself, I wonder if the OP start in “init 1” he can get the system at least
to a prompt?
will butt out now
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
when we click on the update icon in suse linux, we saw the update window with many updates with check boxes.some check boxes are checked and some are unchecked.we checked the one with kernel version.(we did not know what it is exactly)and then click on install updates.it requires to restart.boot into the suse linux and shows error 15:file not found.press any key to continue.
2)sorry .you ask me to make a directory sda3.how to do it?( i am new to linux and studying linux and work with some commands.the problem makes me to do some with linux) .
hai swerdna ,
i want to say one more thing:
the kernel version of suse linux 10 before updating was 2.6.16.54-0.28-smp . After updating ,the kernel version is 2.6.16.60-0.33
To make the directory sda3, enter this command in Gnome terminal window:
sudo mkdir /mnt/sda3
To mount the partition sda3, enter this command:
sudo mount /dev/sda3 /mnt/sda3
then these as discussed to finish the job:
cat /mnt/sda3/etc/SuSE-release
ls -l /mnt/sda3/boot | egrep “initrd|vmlinuz”
*]sudo cat /mnt/sda3/boot/grub/menu.lst
regarding #1
You typed this: ls -/ /mnt/sda3/boot | egrep “initrd|vmlinuz”
instead of this: ls -l /mnt/sda3/boot | egrep “initrd|vmlinuz”
regarding #2
Don’t worry about the egrep thing, you probably did a typo, but the info I wanted came through from item number 3 as well so we don’t need #2
A question for you: You said earlier that you have kernel 2.6.16.60-0.33. How did you know that to be true?
from #3
If you indeed succeeded in installing 2.6.16.60-0.33, then the openSUSE bootloader updated properly and should be working. It remains to be seen (from item #1) whether the symlinks are pointing OK, so run that please. If they are OK then that’s not the problem and you’ll have to activate the auto-magic repair facility on the install DVD.
I’m groping here and hoping for advice from someone who can interpret the kernel panic message data directly, instead of this round about way.
swerdna adjusted his/her AFDB on Friday 24 Jul 2009 10:26 to write:
>
> Good idea – don’t butt out. I only subscribed for booting and am lost
> now.
>
> So how would vijay2009 boot Suse to runlevel 1?
>
>
just tag init 1 on the end of the kernel line in grub.
Probably best if he selects the failsafe and then just enters init 1 it will
echo on the kernel param line, this should be the rescue console and skips a
load of stuff during boot.
also there is IIRC init -b which is an even more of an emergency login that
skips nearly everything during boot to at least get you to a prompt.
At least it would prove that the system is actually there and bootable, he
will be presented with a prompt to login to the rescue system with the root
pass, or maybe with no password at all.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
@vijay2009, the advice of baskitcaise looks good to me. So let’s try it.
I tried on my Ubuntu machine, dual booting with Suse, the following a version of the SLED bootloader entry which gives a “failsafe” boot of Suse from the Ubuntu loader. I took this extract from your SLED loader:
and combined it with the Suse code to get this variant:
# Swerdna's entry to boot the SLED installation on /dev/sda3 by symlinks to the Failsafe state
title SLED 10 (on /dev/sda3) by symlinks
root (hd0,2)
kernel /boot/vmlinuz root=/dev/sda3 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd
savedefault
boot
The red is all one line.
So edit that into the Ubu loader as before, leaving your new entry for SLED alone and adding this “failsafe” entry below it. Then try the boot again and report if you get to the prompt and can login or what?
