** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Heinrich Schuchardt (xypron)

** Summary changed:

- systemd-boot does not find ESP on MBR partitioned drive
+ systemd-boot: missing MBR partition table support

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2035018

Title:
  systemd-boot: missing MBR partition table support

Status in systemd package in Ubuntu:
  New

Bug description:
  I have an arm64 system running Ubuntu Jammy with the MBR partitioned
  drive having the following partitions:

  Device         Boot  Start       End   Sectors  Size Id Type
  /dev/mmcblk0p1      215040 125042654 124827615 59.5G 83 Linux
  /dev/mmcblk0p2      206848    215039      8192    4M 83 Linux
  /dev/mmcblk0p4        2048    206847    204800  100M ef EFI (FAT-12/16/32)

  /dev/mmcblk0p4 is mounted as /boot/efi.

  Though the ESP is identifiable via the partition type I get:

  # bootctl install
  Couldn't find EFI system partition. It is recommended to mount it to /boot or 
/efi.
  Alternatively, use --esp-path= to specify path to mount point.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.10
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  Uname: Linux 5.15.0-83-generic aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Sun Sep 10 08:04:02 2023
  Lspci:
   
  Lspci-vt: -[0000:00]-
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
  MachineType: Unknown Unknown Product
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=66e1e626-5803-40c5-b0be-b1cce4ef5871 ro earlycon console=ttyS0,115200
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  dmi.bios.date: 10/01/2023
  dmi.bios.release: 23.10
  dmi.bios.vendor: U-Boot
  dmi.bios.version: 2023.10-rc3-00049-g0fe0395922-dirty
  dmi.board.name: Unknown Product
  dmi.board.vendor: Unknown
  dmi.chassis.type: 3
  dmi.chassis.vendor: Unknown
  dmi.modalias: 
dmi:bvnU-Boot:bvr2023.10-rc3-00049-g0fe0395922-dirty:bd10/01/2023:br23.10:svnUnknown:pnUnknownProduct:pvr:rvnUnknown:rnUnknownProduct:rvr:cvnUnknown:ct3:cvr:sku:
  dmi.product.name: Unknown Product
  dmi.sys.vendor: Unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035018/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to