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


Groups > linux.debian.kernel > #62919 > unrolled thread

Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs

Started bypavel piankov <pavel.piankov@patentica.biz>
First post2019-01-02 04:10 +0100
Last post2019-01-02 20:40 +0100
Articles 3 — 3 participants

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs pavel piankov <pavel.piankov@patentica.biz> - 2019-01-02 04:10 +0100
    Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs Ben Hutchings <ben@decadent.org.uk> - 2019-01-02 20:40 +0100
      Processed: Re: Bug#916670: cryptsetup: ERROR: Couldn't resolve  device rootfs "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-01-02 20:40 +0100

#62919 — Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs

Frompavel piankov <pavel.piankov@patentica.biz>
Date2019-01-02 04:10 +0100
SubjectBug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs
Message-ID<xbF4S-1bI-1@gated-at.bofh.it>

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

> update-initramfs: Generating /boot/initrd.img-4.18.0-3-amd64
> cryptsetup: ERROR: Couldn't resolve device rootfs
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

this is due 
rootfs / rootfs rw 0 0
line in /etc/mtab
remove it and the problem no more.

[toc] | [next] | [standalone]


#62939

FromBen Hutchings <ben@decadent.org.uk>
Date2019-01-02 20:40 +0100
Message-ID<xbUwV-2ii-5@gated-at.bofh.it>
In reply to#62919

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

Control: tag -1 unreproducible

On Wed, 2019-01-02 at 05:41 +0300, pavel piankov wrote:
> > update-initramfs: Generating /boot/initrd.img-4.18.0-3-amd64
> > cryptsetup: ERROR: Couldn't resolve device rootfs
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> this is due 
> rootfs / rootfs rw 0 0
> line in /etc/mtab
> remove it and the problem no more.

/etc/mtab is supposed to be a symlink to /proc/self/mounts.  I don't
know why it isn't on your system, but that's not a kernel bug.

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer


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


#62940 — Processed: Re: Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2019-01-02 20:40 +0100
SubjectProcessed: Re: Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs
Message-ID<xbUwW-2ii-19@gated-at.bofh.it>
In reply to#62939
Processing control commands:

> tag -1 unreproducible
Bug #916670 [src:linux] cryptsetup: ERROR: Couldn't resolve device rootfs
Added tag(s) unreproducible.

-- 
916670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916670
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


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


csiph-web