Re: upgrade failed debian 8.7

2017-02-08 Thread Henrique de Moraes Holschuh 
On Sat, Feb 4, 2017, at 17:52, Sven Hartge wrote:
> Henrique de Moraes Holschuh  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

Re: upgrade failed debian 8.7

2017-02-07 Thread Mike Nunn 
On 5 February 2017 at 17:08, Sven Hartge  wrote:
> Knowing Hetzner, I doubt they will be helpful.

They suggested changing the nvme disks though I thought this should
only be a last resort.

I tried your earlier suggestion and upgraded to 4.9 kernel from
backports all seems well with sync!

Thanks again for your help.

Regards

Mike

Re: upgrade failed debian 8.7

2017-02-05 Thread Sven Hartge 
Mike Nunn  wrote:

> It's Hetzners standard build on their hardware so will follow up with
> them, as you say something seriously wrong.

Knowing Hetzner, I doubt they will be helpful.

S°

-- 
Sigmentation fault. Core dumped.

Re: upgrade failed debian 8.7

2017-02-05 Thread Mike Nunn 
On 5 February 2017 at 15:31, Sven Hartge  wrote:
> You can unfuzz your package system by temporarily commenting the call to
> "sync" in update-initramfs to get it to complete, but you really should
> try to find out the real problem.

Package system unfuzzed, thanks!

It's Hetzners standard build on their hardware so will follow up with
them, as you say
something seriously wrong.

Thanks very much for you help!

Mike

Re: upgrade failed debian 8.7

2017-02-05 Thread Sven Hartge 
Mike Nunn  wrote:
> On 5 February 2017 at 14:47, Sven Hartge  wrote:

>> Please test if just calling "strace sync" as root hangs as well.

> Yes it does

> strace sync
> .
> open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=2855152, ...}) = 0
> mmap(NULL, 2855152, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc63a03c000
> close(3)= 0
> sync(

> 20 minutes now, exits immediately on my local machine.

This should not take that long. On a normal system, sync times of over 2
seconds are rare and if you have something like a SSD or NVMe as storage
it should be nearly instant.

> Looks like you narrowed it down to an underlying problem.

You can unfuzz your package system by temporarily commenting the call to
"sync" in update-initramfs to get it to complete, but you really should
try to find out the real problem.

Maybe by using the latest kernel from backports.

S°

-- 
Sigmentation fault. Core dumped.

Re: upgrade failed debian 8.7

2017-02-05 Thread Mike Nunn 
On 5 February 2017 at 14:47, Sven Hartge  wrote:

> Can you please check if process 12056 is "/bin/sync"? Search for a line
> above looking like
> 3400  execve("/bin/sync", ["sync"], [/* 23 vars */]) = 0

Yes it is:

12056 execve("/bin/sync", ["sync"], [/* 18 vars */]) = 0

> Please test if just calling "strace sync" as root hangs as well.

Yes it does

strace sync
.
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2855152, ...}) = 0
mmap(NULL, 2855152, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc63a03c000
close(3)= 0
sync(

20 minutes now, exits immediately on my local machine.

Looks like you narrowed it down to an underlying problem.

Thanks very much for your help.

Re: upgrade failed debian 8.7

2017-02-05 Thread Sven Hartge 
Mike Nunn  wrote:
> [-- text/plain, encoding 7bit, charset: UTF-8, 24 lines --]

> I have an strace output for the following:

> strace -f -o foo update-initramfs -u -v

> It stopped at the following line as usual:

> Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs

> The last few lines of the strace output:

> 12056 open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
> 12056 fstat(3, {st_mode=S_IFREG|0644, st_size=2855152, ...}) = 0
> 12056 mmap(NULL, 2855152, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f46dea0e000
> 12056 close(3)  = 0
> 12056 sync(

> I have tried this twice with the same screen output and strace output.

Can you please check if process 12056 is "/bin/sync"? Search for a line
above looking like

3400  execve("/bin/sync", ["sync"], [/* 23 vars */]) = 0

(3400 being the PID of sync in my example here)

If this is the case, then you build stops at line 176 of
/usr/sbin/update-initramfs. Good news is: at that point the initramfs
has already been created successfully and moved into the right place.
The only step left is to run "update-grub".

But when the sync() system call blocks for such a long time, there is
something very wrong with either the kernel or the underlying medium.

Please test if just calling "strace sync" as root hangs as well.

But right now, I don't think this is a bug in update-initramfs but
somewhere else. Maybe inside the NVMe driver in the Linux Kernel.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: upgrade failed debian 8.7

2017-02-05 Thread Mike Nunn 
On 5 February 2017 at 13:33, Lisi Reisz  wrote:

> In addition to Ric's "Please don't top post".


OK will do Thanks, Is it worth starting a new thread as the problem is now
much more specific?

Mike

Re: upgrade failed debian 8.7

2017-02-05 Thread Lisi Reisz 
And please don't break threads.

In addition to Ric's "Please don't top post".

This email above which I am top posting requires a lot of effort on the part 
of any potential helper.  No "history".  Thread broken.  Replied to wrong 
email .

Lisi

On Sunday 05 February 2017 11:24:34 Mike Nunn wrote:
> I have an strace output for the following:
>
> strace -f -o foo update-initramfs -u -v
>
> It stopped at the following line as usual:
>
> Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs
>
> The last few lines of the strace output:
>
> 12056 open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
> 12056 fstat(3, {st_mode=S_IFREG|0644, st_size=2855152, ...}) = 0
> 12056 mmap(NULL, 2855152, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f46dea0e000
> 12056 close(3)  = 0
> 12056 sync(
>
> I have tried this twice with the same screen output and strace output.
>
> I'm not sure what to do next.
>
> Thanks for any help.
>
> Mike

Re: upgrade failed debian 8.7

2017-02-05 Thread Mike Nunn 
I have an strace output for the following:

strace -f -o foo update-initramfs -u -v

It stopped at the following line as usual:

Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs

The last few lines of the strace output:

12056 open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
12056 fstat(3, {st_mode=S_IFREG|0644, st_size=2855152, ...}) = 0
12056 mmap(NULL, 2855152, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f46dea0e000
12056 close(3)  = 0
12056 sync(

I have tried this twice with the same screen output and strace output.

I'm not sure what to do next.

Thanks for any help.

Mike

Re: upgrade failed debian 8.7

2017-02-04 Thread Ric Moore 

On 02/04/2017 03:25 PM, Mike Nunn wrote:

Please don't top post. Thanx, Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: upgrade failed debian 8.7

2017-02-04 Thread Mike Nunn 
update-initramfs pid 1373

sudo lsof -p 1373
COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
update-in 1373 root  cwdDIR9,2 4096 16515073 /root
update-in 1373 root  rtdDIR9,2 40962 /
update-in 1373 root  txtREG9,2   125400 23461891 /bin/dash
update-in 1373 root  memREG9,2  1738176 26869908
/lib/x86_64-linux-gnu/libc-2.19.so
update-in 1373 root  memREG9,2   140928 26869905
/lib/x86_64-linux-gnu/ld-2.19.so
update-in 1373 root0u   CHR  136,4  0t07 /dev/pts/4
update-in 1373 root1u   CHR  136,4  0t07 /dev/pts/4
update-in 1373 root2u   CHR  136,4  0t07 /dev/pts/4
update-in 1373 root   10r   REG9,2 8974 19546736
/usr/sbin/update-initramfs

Re: upgrade failed debian 8.7

2017-02-04 Thread Mike Nunn 
df
Filesystem 1K-blocksUsed Available Use% Mounted on
/dev/md2   458453504 6569528 428572808   2% /
udev   10240   0 10240   0% /dev
tmpfs   13187516  320656  12866860   3% /run
tmpfs   32968784 504  32968280   1% /dev/shm
tmpfs   5120   0  5120   0% /run/lock
tmpfs   32968784   0  32968784   0% /sys/fs/cgroup
/dev/md1  498980   52528420267  12% /boot
tmpfs6593760   0   6593760   0% /run/user/1000
none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/bce41dd5773c817aea6e833cf53e43a1679c29e3d73c20c09ad3040bca57d573

shm65536   0 65536   0%
/var/lib/docker/containers/e9c96303b37e485c0990ac5c0b60e75009c2663b4bba9310867e73ec22c71401/shm

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/bbe023c51a117696a4cf8cf9770ca7bfdb47e79a8b65d7a733afaba6d2b15839

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/a238b58eeb33998d8adbeefa3b82d129d1cc5d9990667cafec8d818399cf6f03

shm65536   0 65536   0%
/var/lib/docker/containers/97a599c4375ce06d3df465529851f20fd6c63dae5da25221abce1e768d25a215/shm

shm65536   0 65536   0%
/var/lib/docker/containers/f839ffd572eb8d2a9e5059012227e06778bf491da83b0058c115be724f857e66/shm

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/d0fe269d720b17579a9939bfa9d64b0d1607f35140f0dfd593cc7f9f20bc7f9e

shm65536   0 65536   0%
/var/lib/docker/containers/13e5125d33b80f5a54dcaeddb078ce093b27f8fa19797359166b32be9b122a7d/shm

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/4e773bf15bc02540a2478aef0fffec0b83879712557d4985c31d0a80c3bbc498

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/91ebefd722e8aab74b1037511bdbc22ce8366b98fd4f081695116cbecd40c992

shm65536   0 65536   0%
/var/lib/docker/containers/e7f8c5eccb175562c2a7941be220790d36240f0e9e38d96311166fd25a91d368/shm

shm65536   0 65536   0%
/var/lib/docker/containers/4fff1f2b2b141846488d39aede964a2629b16f0d97913f7207841cd4ca69/shm

df -i
Filesystem   Inodes  IUsedIFree IUse% Mounted on
/dev/md2   29122560 270014 288525461% /
udev8239770310  82394601% /dev
tmpfs   8242196685  82415111% /run
tmpfs   8242196 22  82421741% /dev/shm
tmpfs   8242196  7  82421891% /run/lock
tmpfs   8242196 13  82421831% /sys/fs/cgroup
/dev/md1 131072329   1307431% /boot
tmpfs   8242196  4  82421921% /run/user/1000
none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/bce41dd5773c817aea6e833cf53e43a1679c29e3d73c20c09ad3040bca57d573

shm 8242196  1  82421951%
/var/lib/docker/containers/e9c96303b37e485c0990ac5c0b60e75009c2663b4bba9310867e73ec22c71401/shm

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/bbe023c51a117696a4cf8cf9770ca7bfdb47e79a8b65d7a733afaba6d2b15839

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/a238b58eeb33998d8adbeefa3b82d129d1cc5d9990667cafec8d818399cf6f03

shm 8242196  1  82421951%
/var/lib/docker/containers/97a599c4375ce06d3df465529851f20fd6c63dae5da25221abce1e768d25a215/shm

shm 8242196  1  82421951%
/var/lib/docker/containers/f839ffd572eb8d2a9e5059012227e06778bf491da83b0058c115be724f857e66/shm

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/d0fe269d720b17579a9939bfa9d64b0d1607f35140f0dfd593cc7f9f20bc7f9e

shm 8242196  1  82421951%
/var/lib/docker/containers/13e5125d33b80f5a54dcaeddb078ce093b27f8fa19797359166b32be9b122a7d/shm

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/4e773bf15bc02540a2478aef0fffec0b83879712557d4985c31d0a80c3bbc498

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/91ebefd722e8aab74b1037511bdbc22ce8366b98fd4f081695116cbecd40c992

shm 8242196  1  82421951%
/var/lib/docker/containers/e7f8c5eccb175562c2a7941be220790d36240f0e9e38d96311166fd25a91d368/shm

shm 8242196  1  82421951%
/var/lib/docker/containers/4fff1f2b2b141846488d39aede964a2629b16f0d97913f7207841cd4ca69/shm

cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,relatime 0 0
udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=8239770,mode=755 0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=13187516k,mode=755 0 0
/dev/md2 / ext4 rw,relatime,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime
0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup

Re: upgrade failed debian 8.7

2017-02-04 Thread Sven Hartge 
Mike Nunn  wrote:

> can't install strace as apt suggests running dpkg --configure -a , prob due
> to the failure of the upgrade

> with update-initramfs -u -v -k 3.16.0-4-amd64 hung there doesn't seem to be
> a cpio process running

Strange.

If it hangs at "Building cpio /boot/initrd.img-3.16.0-4-amd64.new
initramfs" then there should be a cpio process.

Could then please share the full output of "df", "df -i" and "cat
/proc/mounts", each done as user "root"?

Grüße,
S°

-- 
Sigmentation fault. Core dumped.

Re: upgrade failed debian 8.7

2017-02-04 Thread Mike Nunn 
can't install strace as apt suggests running dpkg --configure -a , prob due
to the failure of the upgrade

with update-initramfs -u -v -k 3.16.0-4-amd64 hung there doesn't seem to be
a cpio process running

On 4 February 2017 at 19:02, Sven Hartge  wrote:

> Mike Nunn  wrote:
> > Sven Hartge  wrote:
>
> >> Hmm. How long did you wait for it to complete? Is "/boot" full?
> >> Or is the disk /boot is on just abysmally slow?
>
> > It's still stuck, been over an hour now. Everything else seems fast,
> > no obvious slowdown.
>
> > Filesystem Size  Used Avail Use% Mounted on
> > /dev/md1   488M   52M  411M  12% /boot
>
> > Disks are NVMe Gen3 x4 SSD (Software-RAID 1)
>
> Please do
>
> a) lsof -p `pidof cpio`
> b) strace -f -p `pidof cpio`
>
> (If those tools are not installed, please install them.)
>
> Grüße,
> Sven.
>
> --
> Sigmentation fault. Core dumped.
>
>

Re: upgrade failed debian 8.7

2017-02-04 Thread Sven Hartge 
Henrique de Moraes Holschuh  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.

Re: upgrade failed debian 8.7

2017-02-04 Thread Henrique de Moraes Holschuh 
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

Re: upgrade failed debian 8.7

2017-02-04 Thread Sven Hartge 
Mike Nunn  wrote:
> Sven Hartge  wrote:

>> Hmm. How long did you wait for it to complete? Is "/boot" full?
>> Or is the disk /boot is on just abysmally slow?

> It's still stuck, been over an hour now. Everything else seems fast,
> no obvious slowdown.

> Filesystem Size  Used Avail Use% Mounted on
> /dev/md1   488M   52M  411M  12% /boot

> Disks are NVMe Gen3 x4 SSD (Software-RAID 1)

Please do

a) lsof -p `pidof cpio`
b) strace -f -p `pidof cpio`

(If those tools are not installed, please install them.)

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

upgrade failed debian 8.7

2017-02-04 Thread Mike Nunn 
Sven Hartge  wrote:

> Hmm. How long did you wait for it to complete? Is "/boot" full?
> Or is the disk /boot is on just abysmally slow?

It's still stuck, been over an hour now. Everything else seems fast,
no obvious slowdown.

Filesystem Size  Used Avail Use% Mounted on
/dev/md1   488M   52M  411M  12% /boot

Disks are NVMe Gen3 x4 SSD (Software-RAID 1)

Thanks

Mike

Re: upgrade failed debian 8.7

2017-02-04 Thread Sven Hartge 
Mike Nunn  wrote:

> It seems to stop after the last line shown below.

>  Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs

Hmm. How long did you wait for it to complete? Is "/boot" full? Or is
the disk /boot is on just abysmally slow?

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

upgrade failed debian 8.7

2017-02-04 Thread Mike Nunn 
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

upgrade failed debian 8.7

2017-02-04 Thread Mike Nunn 
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

Re: upgrade failed debian 8.7

2017-02-04 Thread Sven Hartge 
Mike Nunn  wrote:

> uname -a 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64
> GNU/Linux

> I ran sudo apt update followed by upgrade

> it hangs at the following point:

> Setting up linux-image-3.16.0-4-amd64 (3.16.39-1) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64

> Progress: [  0%]

> Any advice very gratefully received.

Please interrupt the currently running process (STRG+C) and do it in two
steps: 

a) sudo -i 
   to get a genuine root shell

b) apt upgrade

With this I want to check if there is anything funny happening with the
terminal when using just "sudo apt upgrade".

If this does not change anything, interrupt the process again and just
issue "update-initramfs -u -v -k 3.16.0-4-amd64" to see if anything
strange happens during the generation of the initramfs.

S°

-- 
Sigmentation fault. Core dumped.

upgrade failed debian 8.7

2017-02-04 Thread Mike Nunn 
uname -a 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64
GNU/Linux

I ran sudo apt update followed by upgrade

it hangs at the following point:

Setting up linux-image-3.16.0-4-amd64 (3.16.39-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64

Progress: [  0%]

Any advice very gratefully received.

Thanks

Mike