Bug#932855: e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133

2019-07-24 Thread jim_p
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855

Thank you so much! I can finally access my data :)



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages e2fsprogs depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcom-err2  1.44.5-1
ii  libext2fs2   1.44.5-1
ii  libss2   1.44.5-1
ii  libuuid1 2.33.1-0.1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
ii  parted 3.2-25+b1

-- no debconf information



Bug#932855: e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133

2019-07-24 Thread Carsten Andrich
I just stumbled over this issue myself. I got my system to boot by adding
the "fastboot" option to the kernel command line from GRUB, which skips fsck
(among other things) and therefore ignores the missing logsave.

--
M.Sc. Carsten Andrich

Ilmenau University of Technology
Electronic Measurement and Signal Processing Group

Ilmenau University of Technology   +49 3677 694269
Helmholtzplatz 2   carsten.andr...@tu-ilmenau.de
98693 Ilmenau, Germany



Bug#932855: e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133

2019-07-24 Thread Uwe Kleine-König
On Wed, Jul 24, 2019 at 10:06:08AM +0300, jim_p wrote:
> Package: e2fsprogs
> Version: 1.44.5-1
> Followup-For: Bug #932855
> 
> Proof that I did install logsave 1 as I said above
> 
> # cat var/log/apt/history.log | tail -5
> Start-Date: 2019-07-24  09:10:05
> Commandline: apt-get install logsave
> Requested-By: vaggos (1000)
> Install: logsave:i386 (1.45.3-1)
> End-Date: 2019-07-24  09:10:07
> 
> Do I have to do anything else, e.g something related to initramfs?

update-initramfs -u -k all

should do the trick.

Best regards
Uwe


signature.asc
Description: PGP signature


Bug#932855: e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133

2019-07-24 Thread jim_p
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855

Proof that I did install logsave 1 as I said above

# cat var/log/apt/history.log | tail -5
Start-Date: 2019-07-24  09:10:05
Commandline: apt-get install logsave
Requested-By: vaggos (1000)
Install: logsave:i386 (1.45.3-1)
End-Date: 2019-07-24  09:10:07

Do I have to do anything else, e.g something related to initramfs?



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages e2fsprogs depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcom-err2  1.44.5-1
ii  libext2fs2   1.44.5-1
ii  libss2   1.44.5-1
ii  libuuid1 2.33.1-0.1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
ii  parted 3.2-25+b1

-- no debconf information



Bug#932855: e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133

2019-07-24 Thread jim_p
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855

I know it will sound like a support question, but please help me.
I have 2 pcs, one with debian unstable i386 and one with debian testing amd64.
Obviously, the first one was hit by that bug earlier today.

Because I have no optical drive on my systems so as to load a live cd, I
removed the drive with the i386 installation, installed it on the amd64 one and
chrooted from there. As suggested here, I installed logsave, exited the chroot
and put the drive back in place. However, the problem still persists. Any ideas
why?



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages e2fsprogs depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcom-err2  1.44.5-1
ii  libext2fs2   1.44.5-1
ii  libss2   1.44.5-1
ii  libuuid1 2.33.1-0.1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
ii  parted 3.2-25+b1

-- no debconf information



Bug#932855: e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133

2019-07-23 Thread Colin Booth
Package: e2fsprogs
Version: 1.45.3-1

The split of logsave(8) from e2fsprogs into its own package breaks all
initramfs images built using the scripts/functions file shipped with
initramfs-tools-core due to a missing dependency in the broken package.

Expected: correctly fsck'ed and booting system.

Observed: initramfs panic with "The X filesystem on Y requires a manual
fsck".

Installing logsave fixes the problem as update-initramfs is able to
locate and pack the file correctly.

-- 
Colin Booth