Re: Issues with Recovery and Documentation

[Gerald B. Cox]

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 going on for years.

I gave up and just re-installed; which I venture to guess is what everyone
else does.
Sad that you can't rely on Fedora recovery tools... maybe that is why they
don't even bother to put it on the Workstation live ISO.

In any event, I opened up a bugzilla.


On Sat, Jul 8, 2017 at 2:41 PM, stan  wrote:

> 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:
> >
> > chroot: failed to run command
> > "bin/bash"open("/usr/share/locale/en_US.UTF-8/LC_
> MESSAGES/libc.mo",O_RDONLY)
> > WTF  These files weren't on my system when it was running... why
> > does it need them now???  This is bizarre...
>
> I have no further insight to offer.  Like you, I haven't used this for
> a long time, and the last time I did, it worked without issues.  Did
> strace give an actual error when you ran the command? Did you find a
> workaround?  Is there anything more relevant in the logs?
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Issues with Recovery and Documentation

[stan]

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:
> 
> chroot: failed to run command
> "bin/bash"open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo",O_RDONLY)
> WTF  These files weren't on my system when it was running... why
> does it need them now???  This is bizarre...

I have no further insight to offer.  Like you, I haven't used this for
a long time, and the last time I did, it worked without issues.  Did
strace give an actual error when you ran the command? Did you find a
workaround?  Is there anything more relevant in the logs?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Issues with Recovery and Documentation

[Gerald B. Cox]

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/en_US.UTF-8/LC_MESSAGES/libc.mo",O_RDONLY)
WTF  These files weren't on my system when it was running... why does
it need them now???  This is bizarre...



On Fri, Jul 7, 2017 at 1:47 PM, stan  wrote:

> 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:
> > chroot:  failed to run command '/bin/bash':  Input/output error
> >
> > I checked and it is there.  What's going on?
>
> Don't know, but some research that might help.
>
> I found people with problems chrooting if they used a rescue disk that
> was a different architecture than their system (32 bit vs 64 bit).
>
> Someone said if they explicitly listed /bin/bash after the chroot
> command, it worked, others said it made no difference.
>
> The only solution I found for this on the web was that the file
> /usr/lib/locale/locale-archive caused a floating point exception.
> It isn't clear to me which system it was on.  It looks like it is the
> rescue system from the result below.
>
> https://bbs.archlinux.org/viewtopic.php?id=132271
>
> ...
> Result of strace -e trace=open chroot . /bin/bash:
>
> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
> open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
> open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
> open("/usr/lib/locale/en_US.UTF-8/LC_IDENTIFICATION",
> O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/lib/locale/en_US.utf8/LC_IDENTIFICATION",
> O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
> open("/usr/lib/locale/en_US/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) =
> -1 ENOENT (No such file or directory)
> open("/usr/lib/locale/en.UTF-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC)
> = -1 ENOENT (No such file or directory)
> open("/usr/lib/locale/en.utf8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) =
> -1 ENOENT (No such file or directory)
> open("/usr/lib/locale/en/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1
> ENOENT (No such file or directory) open("/etc/ld.so.cache",
> O_RDONLY|O_CLOEXEC) = 3 open("/lib/libreadline.so.6",
> O_RDONLY|O_CLOEXEC) = 3 open("/lib/libncursesw.so.5",
> O_RDONLY|O_CLOEXEC) = 3 open("/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
> open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/dev/tty",
> O_RDWR|O_NONBLOCK) = 3 open("/usr/lib/locale/locale-archive",
> O_RDONLY|O_CLOEXEC) = 3 --- {si_signo=SIGFPE, si_code=FPE_INTDIV,
> si_addr=0x7f6d662c1712} (Floating point exception) --- +++ killed by
> SIGFPE +++ Floating point exception
>
> deleting ./usr/lib/locale/locale-archive allows me to chroot.
> ...
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Issues with Recovery and Documentation

[stan]

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:
> chroot:  failed to run command '/bin/bash':  Input/output error
> 
> I checked and it is there.  What's going on?

Don't know, but some research that might help.

I found people with problems chrooting if they used a rescue disk that
was a different architecture than their system (32 bit vs 64 bit).

Someone said if they explicitly listed /bin/bash after the chroot
command, it worked, others said it made no difference.

The only solution I found for this on the web was that the file
/usr/lib/locale/locale-archive caused a floating point exception.
It isn't clear to me which system it was on.  It looks like it is the
rescue system from the result below.

https://bbs.archlinux.org/viewtopic.php?id=132271

...
Result of strace -e trace=open chroot . /bin/bash:

open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/locale/en_US.UTF-8/LC_IDENTIFICATION",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en_US.utf8/LC_IDENTIFICATION",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en_US/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
open("/usr/lib/locale/en.UTF-8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC)
= -1 ENOENT (No such file or directory)
open("/usr/lib/locale/en.utf8/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
open("/usr/lib/locale/en/LC_IDENTIFICATION", O_RDONLY|O_CLOEXEC) = -1
ENOENT (No such file or directory) open("/etc/ld.so.cache",
O_RDONLY|O_CLOEXEC) = 3 open("/lib/libreadline.so.6",
O_RDONLY|O_CLOEXEC) = 3 open("/lib/libncursesw.so.5",
O_RDONLY|O_CLOEXEC) = 3 open("/lib/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 open("/dev/tty",
O_RDWR|O_NONBLOCK) = 3 open("/usr/lib/locale/locale-archive",
O_RDONLY|O_CLOEXEC) = 3 --- {si_signo=SIGFPE, si_code=FPE_INTDIV,
si_addr=0x7f6d662c1712} (Floating point exception) --- +++ killed by
SIGFPE +++ Floating point exception

deleting ./usr/lib/locale/locale-archive allows me to chroot.
...
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Issues with Recovery and Documentation

[Hedayat Vatankhah]

/*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:  failed to run command '/bin/bash':  Input/output error

I checked and it is there.  What's going on?


Using a 32-bit CD with a 64-bit system or the other way around; I guess.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Issues with Recovery and Documentation

[Gerald B. Cox]

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 get
to the troubleshooting tools, apparently, they aren't on the workstation.
It might be helpful to point that out.  When looking through the online
docs I couldn't find it... maybe I just missed it - but it doesn't seem to
be in an obvious place.

Then when I finally was able to get into boot the server livecd and go into
troubleshooting, and rescue a Fedora System...

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:  failed to run command '/bin/bash':  Input/output error

I checked and it is there.  What's going on?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org