Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #177409 > unrolled thread

upgrade failed debian 8.7

Back to article view | Back to linux.debian.user

Contents

  upgrade failed debian 8.7 Mike Nunn <bonnie650@gmail.com> - 2017-02-04 19:20 +0100
    Re: upgrade failed debian 8.7 Henrique de Moraes Holschuh <hmh@debian.org> - 2017-02-04 20:40 +0100
      Re: upgrade failed debian 8.7 Sven Hartge <sven@svenhartge.de> - 2017-02-04 21:00 +0100
        Re: upgrade failed debian 8.7 Henrique de Moraes Holschuh <hmh@debian.org> - 2017-02-08 11:40 +0100
          Issues with power management solitone <solitone@mail.com> - 2017-02-08 12:00 +0100
            Re: Issues with power management Lisi Reisz <lisi.reisz@gmail.com> - 2017-02-15 18:30 +0100
              Re: Issues with power management Darac Marjal <mailinglist@darac.org.uk> - 2017-02-15 18:40 +0100
                Re: Issues with power management solitone <solitone@mail.com> - 2017-02-15 18:50 +0100

#177409 — upgrade failed debian 8.7

[Multipart message — attachments visible in raw view] — view raw

Thanks for the reply,

It seems to stop after the last line shown below.

update-initramfs -u -v -k 3.16.0-4-amd64
Keeping /boot/initrd.img-3.16.0-4-amd64.dpkg-bak
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
Copying module directory kernel/drivers/hid

********
Calling hook zz-busybox
Adding binary /bin/busybox
Calling hook dmsetup
/usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not
executable
/usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not
executable
/usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs

Thanks

Mike

[toc] | [next] | [standalone]

#177417

On Sat, 04 Feb 2017, Mike Nunn wrote:
> /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable

Is /tmp mounted "noexec"?  Just Don't Do It[tm].  The system will break
in hideously crazy, suprising ways.  BTW, this is also valid for the
filesystem hosting whatever directory $TMPDIR (and $TEMP, $TMP...)
points to.

Mounting /tmp "noexec" is not really supported, regardless of whether it
used to work in the past or not.


If that's the case, here's a rough idea on how to fix the breakage:

1. fix the /tmp definiton on /etc/fstab, it must not be "noexec".

2. assuming you actually managed to boot, run as root:

   mount /tmp -o remount,exec
   update-initramfs -u

   that should create a working initramfs for the next boot.

-- 
  Henrique Holschuh

[toc] | [prev] | [next] | [standalone]

#177418

Henrique de Moraes Holschuh <hmh@debian.org> wrote:
> On Sat, 04 Feb 2017, Mike Nunn wrote:

>> /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable

> Is /tmp mounted "noexec"?  Just Don't Do It[tm].  The system will break
> in hideously crazy, suprising ways.  BTW, this is also valid for the
> filesystem hosting whatever directory $TMPDIR (and $TEMP, $TMP...)
> points to.

The above output seems to be normal, I get the same on my system.
Besides, the files mentioned ...

,----
| /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable
`----

... don't even exist on those directories:

,----
| # ls -l /usr/share/initramfs-tools/scripts/*
| -rw-r--r-- 1 root root 9394 Dec 15 22:34 /usr/share/initramfs-tools/scripts/functions
| -rw-r--r-- 1 root root 4457 Apr 17  2016 /usr/share/initramfs-tools/scripts/local
| -rw-r--r-- 1 root root 3050 Feb 20  2016 /usr/share/initramfs-tools/scripts/nfs
|
| /usr/share/initramfs-tools/scripts/init-bottom:
| total 8
| -rwxr-xr-x 1 root root 147 Dec 18 11:50 plymouth
| -rwxr-xr-x 1 root root 572 Feb  1 22:45 udev
|
| /usr/share/initramfs-tools/scripts/init-premount:
| total 4
| -rwxr-xr-x 1 root root 464 Dec 18 11:50 plymouth
|
| /usr/share/initramfs-tools/scripts/init-top:
| total 16
| -rwxr-xr-x 1 root root 351 Dec  9  2015 all_generic_ide
| -rwxr-xr-x 1 root root 295 Dec  9  2015 blacklist
| -rwxr-xr-x 1 root root 358 Dec  9  2015 keymap
| -rwxr-xr-x 1 root root 501 Feb  1 22:45 udev
|
| /usr/share/initramfs-tools/scripts/local-block:
| total 8
| -rwxr-xr-x 1 root root  689 Dec 16 12:56 lvm2
| -rwxr-xr-x 1 root root 1206 Jul 28  2016 mdadm
|
| /usr/share/initramfs-tools/scripts/local-bottom:
| total 4
| -rwxr-xr-x 1 root root 46 Jul 28  2016 mdadm
|
| /usr/share/initramfs-tools/scripts/local-premount:
| total 8
| -rwxr-xr-x 1 root root  270 Sep 22 15:48 btrfs
| -rwxr-xr-x 1 root root 1041 Dec  9  2015 resume
|
| /usr/share/initramfs-tools/scripts/local-top:
| total 4
| -rwxr-xr-x 1 root root 970 Dec 16 12:56 lvm2
|
| /usr/share/initramfs-tools/scripts/panic:
| total 4
| -rwxr-xr-x 1 root root 151 Dec 18 11:50 plymouth
`----

I think the error message is misleading in this case.

> Mounting /tmp "noexec" is not really supported, regardless of whether it
> used to work in the past or not.

Looking at "lsof -p `pidof cpio` it looks like the initramfs is build
inside /var/tmp and not /tmp.

Grüße,
S°

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#177547

On Sat, Feb 4, 2017, at 17:52, Sven Hartge wrote:
> Henrique de Moraes Holschuh <hmh@debian.org> wrote:
> > On Sat, 04 Feb 2017, Mike Nunn wrote:
> 
> >> /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
> 
> > Is /tmp mounted "noexec"?  Just Don't Do It[tm].  The system will break
> > in hideously crazy, suprising ways.  BTW, this is also valid for the
> > filesystem hosting whatever directory $TMPDIR (and $TEMP, $TMP...)
> > points to.
> 
> The above output seems to be normal, I get the same on my system.

Argh.  Indeed, a boot hang could/would happen should you get exec
failures on the ORDER files that are *inside* the initramfs, i.e. if the
file reported as not being executable was something like this:

/var/tmp/mkinitramfs_########/scripts/local-block/ORDER

(and yes, it is /var/tmp and not /tmp as I said...  My recollection of
this very obscure issue was slightly corrupted by time :-( )

I failed to notice the path on the ORDER files it was reporting as not
being able to execute, I apologize for that.

-- 
  Henrique de Moraes Holschuh <hmh@debian.org>

[toc] | [prev] | [next] | [standalone]

#177548 — Issues with power management

Hi,

as I told in thread "Monitor switched off after resume from hibernation", my 
MacBookPro 12,1 had problems with hibernation in stretch. If hibernation 
happened after the monitor had been switched off, the system would not turn 
the monitor on again after resume. Therefore I disabled hibernation.

With time, though, I noticed that even suspension doesn't work very well. 
Sometimes the laptop does not suspend, neither if I wait for the set 5 
minutes, nor if I close the lid. It basically remains active, cunsuming 
battery.

So today I tried to re-enable hibernation, and discovered that now it does not 
work at all. Perhaps it was a recent stretch update, but now hibernation can't 
be used at all. Previously it worked at least when the monitor was on. Now 
even when the monitor is on and I hibernate, when the system resumes I don't 
get a usable session. I just get an emtpy black screen with the white cursor 
on it, but nothing happens. I can't even switch to a virtual console with crtl
+alt+F<n>. 

What do you suggest to do to investigate this issue? A functional power 
management is a must on a portable computer.

Thanks!

[toc] | [prev] | [next] | [standalone]

#177816 — Re: Issues with power management

On Wednesday 08 February 2017 10:50:52 solitone wrote:
> What do you suggest to do to investigate this issue?

Not hijack another thread.

Lisi

[toc] | [prev] | [next] | [standalone]

#177818 — Re: Issues with power management

On Wed, Feb 15, 2017 at 05:22:12PM +0000, Lisi Reisz wrote:
>On Wednesday 08 February 2017 10:50:52 solitone wrote:
>> What do you suggest to do to investigate this issue?
>
>Not hijack another thread.

I'm not sure that I see how hijacking a thread prevents a laptop from 
suspending, but - certainly - avoiding it is SOMETHING to try.

The OP could also try the information in, for example:

https://wiki.ubuntu.com/DebuggingKernelSuspend
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
https://wiki.archlinux.org/index.php/Power_management/Suspend_and_hibernate#Troubleshooting

>

>Lisi
>

-- 
For more information, please reread.

[toc] | [prev] | [next] | [standalone]

#177820 — Re: Issues with power management

Sorry for the hijacking, I mistakenly replied to a message in this thread, it 
wasn't deliberate :^)

In the meanwhile I did open another thread, and if you will we can discuss 
there. For now, thanks for the links.

Cheers,
  Davide

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web