Public bug reported:
I installed ubuntu 22.04.2 in a raids structure.
The grub.cfg files seem fine.
Content of EFI grub.cfg is
search.fs_uuid b9c1881f-a0b5-4fe3-b5ea-eb3d4567cfec root
mduuid/d9442342aaf72e055793a60e5ed333e4
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
The boot crashes.
But a can do this command
mdadm --examine --scan
The response is
mdadm no device listed in /etc/mdadm/mdadm.conf
I suspect that the EFI part does not know how to correctly assemble the RAID
because during the
I don't know how to transmit the crash at this precise moment.
The workaround found is to make a standard EXT4 partition dedicated to
booting. However, that seems abnormal to me then the EFI part proposes
to boot directly on the RAID if it is not possible.
Thank you for doing what is necessary to have something coherent.
Good day.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.3-0ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 28 14:58:24 2023
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: evince (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/2013082
Title:
EFI boot does not detect RAID.
Status in evince package in Ubuntu:
New
Bug description:
I installed ubuntu 22.04.2 in a raids structure.
The grub.cfg files seem fine.
Content of EFI grub.cfg is
search.fs_uuid b9c1881f-a0b5-4fe3-b5ea-eb3d4567cfec root
mduuid/d9442342aaf72e055793a60e5ed333e4
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
The boot crashes.
But a can do this command
mdadm --examine --scan
The response is
mdadm no device listed in /etc/mdadm/mdadm.conf
I suspect that the EFI part does not know how to correctly assemble the RAID
because during the
I don't know how to transmit the crash at this precise moment.
The workaround found is to make a standard EXT4 partition dedicated to
booting. However, that seems abnormal to me then the EFI part proposes
to boot directly on the RAID if it is not possible.
Thank you for doing what is necessary to have something coherent.
Good day.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.3-0ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 28 14:58:24 2023
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2013082/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
