Bug 1499479 - systemd-gpt-auto-generator[17455]: Failed to dissect: Input/output error
Summary: systemd-gpt-auto-generator[17455]: Failed to dissect: Input/output error
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-07 19:27 UTC by Vedran Miletić
Modified: 2018-05-29 11:55 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:55:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vedran Miletić 2017-10-07 19:27:46 UTC
Description of problem:
When installing the new kernel, the error

systemd-gpt-auto-generator[17455]: Failed to dissect: Input/output error

appears in dmesg.

Version-Release number of selected component (if applicable):
systemd-233-6

How reproducible:
Didn't try.

Additional info:
$ sudo fdisk -l
Disk /dev/mmcblk0: 29,1 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B2B79BD2-5749-4601-AC25-AD8E76FE2F6C

Device            Start      End  Sectors  Size Type
/dev/mmcblk0p1     2048   411647   409600  200M EFI System
/dev/mmcblk0p2   411648  1435647  1024000  500M Linux filesystem
/dev/mmcblk0p3  1435648 54962175 53526528 25,5G Linux filesystem
/dev/mmcblk0p4 54962176 61069311  6107136  2,9G Linux swap




Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Comment 1 Michal Schmidt 2017-10-09 13:32:06 UTC
Do you get the error if you run the generator directly?:
/lib/systemd/system-generators/systemd-gpt-auto-generator

If yes, try running it with more verbose logging (export SYSTEMD_LOG_LEVEL=debug) and/or under strace and attach the output here.

Comment 2 Vedran Miletić 2017-10-10 19:53:37 UTC
No. Any combination of arguments I can try?

Comment 3 Fedora End Of Life 2018-05-03 08:33:21 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2018-05-29 11:55:28 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.