Re: [Xen-users] Target filesystem doesn't have requested /sbin/init.

[Stephan Seitz <s.seitz@xxxxxxxxxxx>]

Hi,

whatever you've done to your domU filesystem, but I assume you crashed it.
As seen in your previous post it didn't only had no execution bit, it also was
owned by uid 1000. maybe only a mount issue, but who knows?

I also don't think that a chmod -R +x could count as a solution, as it will leaf
your system with a lot more unforseeable file rights.

A "permission denied" could also occur if the binary has been compiled for
another platform.

Anyway, I'ld try to add your disk in question to another, similar domU to have
at least your tools running.

e.g. by using

xm block-attach / xl block-attach

cheers,

Stephan



Am Dienstag, den 24.07.2012, 13:01 +0900 schrieb jaeyong yoo:

I've encountered another problem  

>     It says  "run-init: /sbin/init: Permission denied" 
>     
>     
>     Here is the log.
>     
>     
>     Begin: Loading essential drivers ... done.
>     Begin: Running /scripts/init-premount ... done.
>     Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
>     Begin: Running /scripts/local-premount ... done.
>     [    0.524394] kjournald starting.  Commit interval 5 seconds
>     [    0.524412] EXT3-fs: mounted filesystem with ordered data mode.
>     Begin: Running /scripts/local-bottom ... done.
>     done.
>     Begin: Running /scripts/init-bottom ... done.
>     run-init: /sbin/init: Permission denied
>     [    0.568553] Kernel panic - not syncing: Attempted to kill init!
>     [    0.568565] Pid: 1, comm: run-init Not tainted 2.6.32-5-xen-amd64 #1
>     [    0.568572] Call Trace:
>     [    0.568585]  [<ffffffff8130c037>] ? panic+0x86/0x143
>     [    0.568596]  [<ffffffff8100e635>] ? xen_force_evtchn_callback+0x9/0xa
>     [    0.568605]  [<ffffffff8100ecf2>] ? check_events+0x12/0x20
>     [    0.568614]  [<ffffffff8100e635>] ? xen_force_evtchn_callback+0x9/0xa
>     [    0.568622]  [<ffffffff8100ecf2>] ? check_events+0x12/0x20
>     [    0.568631]  [<ffffffff8130de12>] ? _spin_lock_irq+0x7/0x22
>     [    0.568640]  [<ffffffff8130de94>] ? _write_lock_irq+0x7/0x16
>     [    0.568649]  [<ffffffff81058276>] ? exit_ptrace+0xa7/0x126
>     [    0.568658]  [<ffffffff8100ecdf>] ? xen_restore_fl_direct_end+0x0/0x1
>     [    0.568667]  [<ffffffff8105222d>] ? do_exit+0x72/0x6c6
>     [    0.568675]  [<ffffffff81052946>] ? complete_and_exit+0x0/0x16
>     [    0.568683]  [<ffffffff81011b63>] ? sysret_check+0x17/0x5a
>     [    0.568690]  [<ffffffff81011b42>] ? system_call_fastpath+0x16/0x1b
>     
>     
>     
>     
>     But, i don't think it is indeed permission problem because after I tried several settings to give +rx to files I did
>     /$chmod +rx * -R at root directory.
>     
>     
>     Do you have any idea?
>     
>     
>     Best
>     - Jaeyong
>     
>     On Tue, Jul 24, 2012 at 12:29 PM, jaeyong yoo <y.jaeyong@xxxxxxxxx> wrote:
> >         Ah! that's it!!! Now the problem solved.
> >     
> >         I feel so stupid.
> >     
> >         
> >         
> >     
> >         Thanks a lot all of you :)
> >     
> >         
> >         
> >     
> >         Jaeyong
> >     
> >         
> >         
> >     
> >         On Tue, Jul 24, 2012 at 12:22 PM, Jeff Sturm <jeff.sturm@xxxxxxxxxx> wrote:
> > >             > From: xen-users-bounces@xxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of jaeyong yoo
> > >             > Sent: Monday, July 23, 2012 10:29 PM
> > >         
> >     
> > >             >
> > >             > Also, there is /sbin/init. So, it is not about the file missing.
> > >             >
> > >             > (initramfs) ls /root/sbin/init  -l
> > >             > -rw-------    1 1000     1000         36992 Jan  1  2011 /root/sbin/init
> > >             
> > >             
> > >         
> >     
> > >             No execute permission?
> > >             
> > >             -Jeff
> > >             
> > >             
> > >         
> >     
> >         
> >         
> >     
>     
>     
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users