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
