[SOLVED] LILO repair and Chroot problems

argondos · 10-16-2010, 06:15 PM

Hello !
I'm fairly new to linux, and a few days ago, as I was updating my system, I got the "EBDA is big ; kernel setup stack overlaps LILO second stage" error after reboot.
I use a 3- boot, ( Win XP / Debian / Debian) and Windows XP works fine, but I can't launch any of the Debian.

I googled the message, and I found this link :
http://ubuntuforums.org/showthread.php?t=329223

The only problem problem is that when I try to chroot, I got another message, "chroot: failed to run command `/bin/bash': No such file or directory"
I googled this message too, but found no relevant answers.

I am now using a knoppix usb drive to try to repair the lilo, but I ran out of ideas ...

Any iclue, either for the lilo or chroot problem ??
Thanks for the answers !

markush · 10-16-2010, 06:25 PM

Hello argondos and welcome to LQ,

could you please post the command you executed to chroot?
If you're still with a liveCD on the system, please post the output of

Code:

df -h

Markus

argondos · 10-16-2010, 08:09 PM

Hello,

Sorry for answering so late ...
for the chroot, I used

Code:

chroot /mnt /bin/bash

and when I type df -h, I got :

Code:

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1             7.5G  689M  6.8G  10% /mnt-system
tmpfs                 1.0G   18M 1007M   2% /ramdisk
/dev/cloop            1.9G  1.9G     0 100% /KNOPPIX
unionfs               1.0G   18M 1007M   2% /UNIONFS
unionfs               1.0G   18M 1007M   2% /home
tmpfs                  10M   64K   10M   1% /UNIONFS/var/run
tmpfs                  10M     0   10M   0% /UNIONFS/var/lock
tmpfs                 100M   72K  100M   1% /UNIONFS/var/log
tmpfs                 1.0G   12K  1.0G   1% /tmp
udev                   20M  416K   20M   3% /dev
tmpfs                 1.0G  4.0K  1.0G   1% /dev/shm

markush · 10-16-2010, 08:23 PM

Well, before chrooting, you'll have to mount the / partition of your Ubuntu. The chroot-command as you've executed it provides, that / of Ubuntu is mounted to /mnt. Please check this. In your output of "df -h" there is nothing mounted on /mnt. Therefore you get the errormessage about /bin/bash not found.

Markus

argondos · 10-16-2010, 09:13 PM

Ok, I have done what you said, but I still got the problem...
Here is what I did :

Code:

mount -o rw /dev/sda1 /mnt
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /dev /mnt/dev
chroot /mnt /bin/bash

and I still got the same mistake.
When I type, df -h, sda1 now appears :

Code:

Sys. de fichiers    Taille  Uti. Disp. Uti% Monté sur
/dev/sdb1             7,5G  689M  6,8G  10% /mnt-system
tmpfs                 1,0G   19M 1006M   2% /ramdisk
/dev/cloop            1,9G  1,9G     0 100% /KNOPPIX
unionfs               1,0G   19M 1006M   2% /UNIONFS
unionfs               1,0G   19M 1006M   2% /home
tmpfs                  10M   64K   10M   1% /UNIONFS/var/run
tmpfs                  10M     0   10M   0% /UNIONFS/var/lock
tmpfs                 100M   72K  100M   1% /UNIONFS/var/log
tmpfs                 1,0G   12K  1,0G   1% /tmp
udev                   20M  416K   20M   3% /dev
tmpfs                 1,0G  4,0K  1,0G   1% /dev/shm
/dev/sda1              16M  141K   15M   1% /mnt
udev                   20M  416K   20M   3% /mnt/dev

Any clue ??

jtarin · 10-17-2010, 12:19 AM

1.Boot to the LiveCD Desktop . The Live CD must be the same as the system you are fixing - either 32-bit or 64-bit (if not then the chroot will fail).
2.Open a terminal
3.Determine your normal system partition - (the switch is a lowercase "L")
sudo fdisk -l
If you aren't sure, run
df -Th. Look for the correct disk size and ext3 or ext4 format.
4.Mount your normal system partition:
Substitute the correct partition: sda1, sdb5, etc.
sudo mount /dev/sdXX /mnt # Example: sudo mount /dev/sda1 /mnt
5.Only if you have a separate boot partition:
sdYY is the /boot partition designation (for example sdb3)
sudo mount /dev/sdYY /mnt/boot
6.Mount the critical virtual filesystems:
sudo mount --bind /dev /mnt/dev
sudo mount --bind /dev/pts /mnt/dev/pts
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
7.Chroot into your normal system device:
sudo chroot /mnt
8.Do your work
9.Exit chroot: CTRL-D on keyboard
10.Unmount virtual filesystems:
sudo umount /mnt/dev/pts
sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt/sys
If you mounted a separate /boot partition:
sudo umount /mnt/boot
11.Unmount the LiveCD's /usr directory:
sudo umount /mnt/usr
12.Unmount last device:
sudo umount /mnt
13.Reboot.
sudo reboot

argondos · 10-19-2010, 05:23 PM

Ok, this is fixed. I was trying to mount sda1, the boot partition, whereas I should have mounted sda5, the partition where my system was. I made the mistake because my disk has 8 partitions, 1 boot, 2 linux, and 5 others ... I wasn't sure wich to choose

Thanks everyone for the answers anyway !!