Same issue still persists after using the "root=UUID=" syntax with
grub (which is the default).
Kernel line in grub command line:
linux /boot/vmlinuz-3.16-2-amd64
root=UUID=11bb4d9d-8451-4632-9985-1bd9b155dba8 ro quiet
Booting ends up with the following screen (with input disabled):
Decom
On Mon, 27 Oct 2014 00:54:54 +
Ben Hutchings wrote:
> > Processing triggers for initramfs-tools (0.116) ...
> > update-initramfs: Generating /boot/initrd.img-3.16-3-amd64
> > /803: No such file or directory
> > [update continues]
> >
> > After a reboot, the system is unbootable due to a miss
On Mon, 27 Oct 2014 00:54:54 +
Ben Hutchings wrote:
> > After a reboot, the system is unbootable due to a missing rootfs.
> [...]
>
> We support hexadecimal device numbers in the 'root=' kernel parameter
> when booting, but do not expect to see them at build time in the mount
> table.
>
> P
Control: severity -1 serious
Control: tag -1 moreinfo
On Sun, 2014-10-26 at 21:41 +0100, Richard Lucassen wrote:
> Package: initramfs-tools
> Version: 0.116
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> During an update, this is what I see:
>
> [..]
> Pr
Package: initramfs-tools
Version: 0.116
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
During an update, this is what I see:
[..]
Processing triggers for initramfs-tools (0.116) ...
update-initramfs: Generating /boot/initrd.img-3.16-3-amd64
/803: No such file or direc
5 matches
Mail list logo
