Thanks for taking the time to respond. Yes, I got the same type of errors
you received, in addition to the:
> "bin/bash"open("/usr/share/locale/en_US.UTF-8/LC_
MESSAGES/libc.mo",O_RDONLY)
I listed previously.
It appears there is something quirky going on with locale, and apparently
this has been
On Fri, 7 Jul 2017 14:45:38 -0700
"Gerald B. Cox" wrote:
> Your onto something...I tried renaming the file on both the rescue
> image and then on the target system, and it didn't help..
> I did find when running the strace it returned with a bunch of no
> such file or directory as above and also:
Your onto something...I tried renaming the file on both the rescue image
and then on the target system, and it didn't help..
I did find when running the strace it returned with a bunch of no such file
or directory as above and also:
chroot: failed to run command
"bin/bash"open("/usr/share/locale/e
On Fri, 7 Jul 2017 12:04:23 -0700
"Gerald B. Cox" wrote:
> the process was able to find my installation and mount it under
> /mnt/sysimage
>
> Then it says: If you would like to make your system the root
> environment, run the command:
>
> chroot /mnt/sysimage
>
> I then get the response:
> c
/*Gerald B. Cox*/ wrote on Fri, 7 Jul 2017 12:04:23 -0700:
<...>
the process was able to find my installation and mount it under
/mnt/sysimage
Then it says: If you would like to make your system the root
environment, run the command:
chroot /mnt/sysimage
I then get the response:
chroot:
I've been fortunate that I haven't had to use the rescue functions for
years, but today unfortunately I slugging through it and hopefully someone
can assist. I'd rather not have to reinstall just because I can't use
chroot.
I was able to figure out that you have to install the server livecd to ge