Odd CHROOT Error
by enorbet from LinuxQuestions.org on (#5R94T)
I borked a Legacy (CSM) booting old system by resizing the partition. I've run e2fsck on it (no errors) and I can see everything on the partition. No data was apparently harmed. I know the MBR is still OK because I still get the full LILO menu. It's just that nothing will boot from it with a kernel panic - no init system found.
Maybe I'm just over-tired but I figured I may need to re-run LILO so I tried to chroot in as I've done many times on many systems.
In this case I mounted dev/sda9 (it is a single partition system) on "/mnt/LOOP" and did the whole "mount -o bind dev, sys, proc" thing (on proper separate lines of course) but when I issued
Code: chroot /mnt/LOOP/ bin/bashI got an error saying it couldn't find /bin/bash !
This is particularly odd since an "ls /mnt/LOOP/bin" or even "ls /mnt/LOOP/bin | grep bash" reveals it is there. In fact, altering the chroot command with
Code: chroot /mnt/LOOP /mnt/LOOP/bin/bashstill gives the same fail.
Anybody have ideas as to what's causing the error?
Maybe I'm just over-tired but I figured I may need to re-run LILO so I tried to chroot in as I've done many times on many systems.
In this case I mounted dev/sda9 (it is a single partition system) on "/mnt/LOOP" and did the whole "mount -o bind dev, sys, proc" thing (on proper separate lines of course) but when I issued
Code: chroot /mnt/LOOP/ bin/bashI got an error saying it couldn't find /bin/bash !
This is particularly odd since an "ls /mnt/LOOP/bin" or even "ls /mnt/LOOP/bin | grep bash" reveals it is there. In fact, altering the chroot command with
Code: chroot /mnt/LOOP /mnt/LOOP/bin/bashstill gives the same fail.
Anybody have ideas as to what's causing the error?