Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On 10/15/2014 02:45 PM, Jape Person wrote:
On 10/15/2014 01:38 PM, Don Armstrong wrote:
On Wed, 15 Oct 2014, Sven Joachim wrote:
I don't think there is actually an I/O error here, looking at the code
systemd-gpt-auto-generator makes this error up:
,
| errno = 0;
| r = blkid_probe_lookup_value(b, PTTYPE, pttype, NULL);
| if (r != 0) {
| if (errno == 0)
| errno = EIO;
| log_error(Failed to determine partition table type of %s:
%m, node);
| return -errno;
`
Somebody who is familiar with libblkid (i.e. not me) might explain why
blkid_probe_lookup_value() apparently failed but did not set errno.
Great catch. Yeah, blkid_probe_lookup_value apparently just returns -1
on all errors, regardless of what the error was.
This is probably a bug in systemd-gpt-auto-generator, but upstream (and
the maintainer) would know much more than I.
Thank you, both!
I'll see if I can file a cogent bug report.
Please let me know if you have particular suggestions about that.
Just wanted to note that I did file a bug report
(765...@bugs.debian.org). It was even almost cogent, except for the part
where I pasted the contents of /etc/fstab into the template area after I
had already given bugreport permission to gather that information
itself! Der!
Again, thanks to Sven and Don for your interest.
Jape
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/543fc202.90...@comcast.net
Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On 10/15/2014 02:45 PM, Jape Person wrote:
On 10/15/2014 01:38 PM, Don Armstrong wrote:
On Wed, 15 Oct 2014, Sven Joachim wrote:
I don't think there is actually an I/O error here, looking at the code
systemd-gpt-auto-generator makes this error up:
,
| errno = 0;
| r = blkid_probe_lookup_value(b, PTTYPE, pttype, NULL);
| if (r != 0) {
| if (errno == 0)
| errno = EIO;
| log_error(Failed to determine partition table type of %s:
%m, node);
| return -errno;
`
Somebody who is familiar with libblkid (i.e. not me) might explain why
blkid_probe_lookup_value() apparently failed but did not set errno.
Great catch. Yeah, blkid_probe_lookup_value apparently just returns -1
on all errors, regardless of what the error was.
This is probably a bug in systemd-gpt-auto-generator, but upstream (and
the maintainer) would know much more than I.
Thank you, both!
I'll see if I can file a cogent bug report.
Please let me know if you have particular suggestions about that.
I filed a bug report -- 765...@bugs.danubian.org -- a few minutes ago.
I'm sorry if this is a duplicate notification. I accidentally sent the
original from the wrong e-mail account and wanted to be sure you knew
that Jape (nickname) and Jim were the same person.
Again, thank you Sven and Don, for your help.
Jape
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/543fc52e.5010...@comcast.net
Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
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. 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 ? Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8738apuz1g@turtle.gmx.de
Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On Wed, 15 Oct 2014, Jape Person wrote: 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 part of systemd; it generates rules to mount partitions from GPT partition tables without needing to express them in /etc/fstab. [See man systemd-gpt-auto-generator for details.] The drive came originally from Lenovo (T520i) with and MSDOS parititon table. I just used the standard partition scheme provided by the netinst d-i (testing), so there are only /dev/sda1 and the swap partition present. I used ext4 as the file system. I'm also having the drive checked by smartmontools at boot time and have received no warnings. You're basically not supposed to get I/O errors on drives like that. I'd try running smartctl -a /dev/sda; or similar just to see whether any errors have occured on the drive. It's possible that there's a bad sector early on which is only exposed when something tries to find a gpt partition table, or it could be a bug in systemd-gpt-auto-generator which your particular setup is triggering. You might be able to trigger it with gdisk -l /dev/sda; or similar, too. If that doesn't turn up anything useful, file a bug against systemd, and ask the maintainers what additional debugging information you can provide. [It's probably severity minor, since this particularly failure isn't going to hurt anything.] I thought I ought to check to see if anyone thinks this is likely to indicate that I'm about to get bit in the butt. I'd make sure that I had my backups in order, but that's really just out an abundance of caution. -- Don Armstrong http://www.donarmstrong.com I stared at the mountain rising over me. Empty. It was a pointless thing to have done -- climb up it, across it, and down it. Stupid! It looked perfect; so clean and untouched, and we had changed nothing. [...] I had been on it too long, and it had taken everything. -- Joe Simpson Touching the Void p117 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015155348.gi4...@teltox.donarmstrong.com
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 noneswapsw 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 976771071165355535 Extended /dev/sda5 943699968 97677107116535552 82 Linux swap / Solaris Cheers, Sven Thank you for taking an interest! Jape -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/543e9a91.3000...@comcast.net
Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On 10/15/2014 11:53 AM, Don Armstrong wrote: On Wed, 15 Oct 2014, Jape Person wrote: 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 part of systemd; it generates rules to mount partitions from GPT partition tables without needing to express them in /etc/fstab. [See man systemd-gpt-auto-generator for details.] Now that's weird, or maybe it's just me. I tried to look for manpages for systemd-gpt-auto-generator, and I'd swear I was told No manual entry for... Sven Joachim told me to check the manpages, and I looked at man systemd, which gave me an online reference for Generators Specifications which wasn't helpful at all. But I'm now seeing documentation when I type man systemd-gpt-auto-generator, so I'm guessing I made a typo earlier on and didn't even notice in the output from the man request. The drive came originally from Lenovo (T520i) with and MSDOS parititon table. I just used the standard partition scheme provided by the netinst d-i (testing), so there are only /dev/sda1 and the swap partition present. I used ext4 as the file system. I'm also having the drive checked by smartmontools at boot time and have received no warnings. You're basically not supposed to get I/O errors on drives like that. I'd try running smartctl -a /dev/sda; or similar just to see whether any errors have occured on the drive. It's possible that there's a bad sector early on which is only exposed when something tries to find a gpt partition table, or it could be a bug in systemd-gpt-auto-generator which your particular setup is triggering. You might be able to trigger it with gdisk -l /dev/sda; or similar, too. I checked with smartctl and was told the test completed without error. There were no errors in the log at all. However, the output from the gdisk command was: GPT fdisk (gdisk) version 0.8.10 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. *** Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 43493272-B516-4A14-95E5-BF0E895243CB Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 2048-sector boundaries Total free space is 6125 sectors (3.0 MiB) Number Start (sector)End (sector) Size Code Name 12048 943697919 450.0 GiB 8300 Linux filesystem 5 943699968 976771071 15.8 GiB8200 Linux swap I can see the words invalid GPT and valid MBR in that report, but -- save for the sizes and locations pertinent to the different disks -- this is exactly the same output that command gives me on my other systems. Do you see anything significant? If not, I'll try my hand at filing a severity minor bug against systemd to see if the maintainers think anything of it. If that doesn't turn up anything useful, file a bug against systemd, and ask the maintainers what additional debugging information you can provide. [It's probably severity minor, since this particularly failure isn't going to hurt anything.] I thought I ought to check to see if anyone thinks this is likely to indicate that I'm about to get bit in the butt. I'd make sure that I had my backups in order, but that's really just out an abundance of caution. Yup. I'm meticulous about backup strategy and practice. I'm retired, so I have plenty of time to implement it. I never allow myself any excuses. Thank you for your suggestions. Jape -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/543ea384.6090...@comcast.net
Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On 2014-10-15 17:53 +0200, Don Armstrong wrote:
On Wed, 15 Oct 2014, Jape Person wrote:
I'm also having the drive checked by smartmontools at boot time and
have received no warnings.
You're basically not supposed to get I/O errors on drives like that. I'd
try running smartctl -a /dev/sda; or similar just to see whether any
errors have occured on the drive. It's possible that there's a bad
sector early on which is only exposed when something tries to find a gpt
partition table, or it could be a bug in systemd-gpt-auto-generator
which your particular setup is triggering.
I don't think there is actually an I/O error here, looking at the code
systemd-gpt-auto-generator makes this error up:
,
| errno = 0;
| r = blkid_probe_lookup_value(b, PTTYPE, pttype, NULL);
| if (r != 0) {
| if (errno == 0)
| errno = EIO;
| log_error(Failed to determine partition table type of %s:
%m, node);
| return -errno;
`
Somebody who is familiar with libblkid (i.e. not me) might explain why
blkid_probe_lookup_value() apparently failed but did not set errno.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87tx35th1w@turtle.gmx.de
Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On Wed, 15 Oct 2014, Sven Joachim wrote:
I don't think there is actually an I/O error here, looking at the code
systemd-gpt-auto-generator makes this error up:
,
| errno = 0;
| r = blkid_probe_lookup_value(b, PTTYPE, pttype, NULL);
| if (r != 0) {
| if (errno == 0)
| errno = EIO;
| log_error(Failed to determine partition table type of %s:
%m, node);
| return -errno;
`
Somebody who is familiar with libblkid (i.e. not me) might explain why
blkid_probe_lookup_value() apparently failed but did not set errno.
Great catch. Yeah, blkid_probe_lookup_value apparently just returns -1
on all errors, regardless of what the error was.
This is probably a bug in systemd-gpt-auto-generator, but upstream (and
the maintainer) would know much more than I.
--
Don Armstrong http://www.donarmstrong.com
We want 6. 6 is the 1.
-- The Prisoner (2009 Miniseries) _Checkmate_
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141015173819.gj4...@teltox.donarmstrong.com
Re: Who is systemd-gpt-auto-generator, and why does s/he not like my partition table?
On 10/15/2014 01:38 PM, Don Armstrong wrote:
On Wed, 15 Oct 2014, Sven Joachim wrote:
I don't think there is actually an I/O error here, looking at the code
systemd-gpt-auto-generator makes this error up:
,
| errno = 0;
| r = blkid_probe_lookup_value(b, PTTYPE, pttype, NULL);
| if (r != 0) {
| if (errno == 0)
| errno = EIO;
| log_error(Failed to determine partition table type of %s:
%m, node);
| return -errno;
`
Somebody who is familiar with libblkid (i.e. not me) might explain why
blkid_probe_lookup_value() apparently failed but did not set errno.
Great catch. Yeah, blkid_probe_lookup_value apparently just returns -1
on all errors, regardless of what the error was.
This is probably a bug in systemd-gpt-auto-generator, but upstream (and
the maintainer) would know much more than I.
Thank you, both!
I'll see if I can file a cogent bug report.
Please let me know if you have particular suggestions about that.
Jape
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/543ec0d2.8030...@comcast.net
