Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #62939
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs |
| Date | 2019-01-02 20:40 +0100 |
| Message-ID | <xbUwV-2ii-5@gated-at.bofh.it> (permalink) |
| References | <x5UzD-36H-1@gated-at.bofh.it> <x5UzD-36H-1@gated-at.bofh.it> <xbF4S-1bI-1@gated-at.bofh.it> <x5UzD-36H-1@gated-at.bofh.it> <xbF4S-1bI-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[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
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web