Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On 10/15/2014 11:34 AM, Sven Joachim wrote:
On 2014-10-15 16:14 +0200, Jape Person wrote:
I am seeing this during the boot sequence on a Debian testing
installation. Sometimes it is actually left showing on TTY1 after the
DM (lightdm in this case) comes up, and sometimes not.
From TTY1
...
systemd-gpt-auto-generator[152]: Failed to determine partition table
type of /dev/sda: Input/output error
...
So, I checked dmesg:
From dmesg
...[ 4.853751] systemd-gpt-auto-generator[154]: Failed to determine
partition table type of /dev/sda: Input/output error
[ 4.854298] systemd[151]:
/lib/systemd/system-generators/systemd-gpt-auto-generator failed with
error code 1.
... and later on ...
[12650.204616] systemd-gpt-auto-generator[7555]: Failed to determine
partition table type of /dev/sda: Input/output error
...
I looked in the BTS and couldn't even find a package named
systemd-gpt-auto-generator, much less a bug that had been filed for
it. I guess it's a routine or function name?
It's a program that is part of the systemd package. See the manpage for
what it does.
Ah, thanks for that! Looking in the systemd manpage hadn't occurred to
me. Duh!
It would also be nice to know why I'm seeing this only on this
particular system and not on any of the other three systems with very
similar Debian testing installations on them.
Can you please show your /etc/fstab file and the output of
"fdisk -l /dev/sda" ?
/etc/fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=7ffec658-3f62-4b7c-b944-bb60bc257b83 / ext4
errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=e44c4b27-a764-4fcc-b4f8-a1d1d7542fd7 none swap sw
0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
Hmm. I haven't edited this file on this system. I have usually removed
references to optical drives in the past. Maybe that entry (/dev/sr0) is
why I've been hearing the optical drive get activated once-in-a-while on
this system.
output of "# fdisk -l /dev/sda":
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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 identifier: 0xe553ae0a
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 943697919 471847936 83 Linux
/dev/sda2 943699966 976771071 16535553 5 Extended
/dev/sda5 943699968 976771071 16535552 82 Linux swap / Solaris
Cheers,
Sven
Thank you for taking an interest!
Jape
Reply to: