[systemd-devel] systemd .device units timing out

[Avi Kivity]

On 06/14/2011 06:17 PM, Lennart Poettering wrote:
> On Mon, 06.06.11 16:01, Avi Kivity (avi at redhat.com) wrote:
>
> >  I have a system which was upgraded to F15 and thus systemd.  During
> >  the boot process it times out starting various .device units, like
> >  sda1.device.  If I let it alone it will boot in about a week or so,
> >  but meanwhile it is unusable.  I am able to start it up using
> >  emergency.target and various hacks, but it won't boot cleanly.
> >
> >  Any hints?
>
> Hmm, systemd only sees devices properly marked in udev with the systemd
> tag. It would be interesting to find out if the block devices are
> properly marked in the udev db.
>
> Can you paste the output of "udevadm info -qall -p
> /sys/class/block/sda1" after this happened? This should tell us what
> data might be missing in the db.
>

It's hard to reproduce, since I can't stop device units:

$ sudo systemctl status dev-sda2.device
dev-sda2.device - WDC_WD3200KS-00PFB0
       Follow: unit currently follows state of 
sys-devices-pci0000:00-0000:00:1f.2-host0-target0:0:0-0:0:0:0-block-sda-sda2.device
       Loaded: loaded
       Active: active (plugged)
       Device: 
/sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2

$ sudo systemctl stop dev-sda2.device
Job timed out.

$ udevadm info -qall -p /sys/class/block/sda2
P: /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2
N: sda2
S: disk/by-id/ata-WDC_WD3200KS-00PFB0_WD-WCAPD3610786-part2
S: disk/by-id/scsi-SATA_WDC_WD3200KS-00_WD-WCAPD3610786-part2
S: disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part2
S: disk/by-uuid/2951a22e-5f31-4178-be18-dcd1ba35c4e4
S: disk/by-label/\x2fboot_alt
E: UDEV_LOG=3
E: 
DEVPATH=/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda2
E: MAJOR=8
E: MINOR=2
E: DEVNAME=/dev/sda2
E: DEVTYPE=partition
E: SUBSYSTEM=block
E: ID_ATA=1
E: ID_TYPE=disk
E: ID_BUS=ata
E: ID_MODEL=WDC_WD3200KS-00PFB0
E: 
ID_MODEL_ENC=WDC\x20WD3200KS-00PFB0\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=21.00M12
E: ID_SERIAL=WDC_WD3200KS-00PFB0_WD-WCAPD3610786
E: ID_SERIAL_SHORT=WD-WCAPD3610786
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=0
E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_FEATURE_SET_AAM=1
E: ID_ATA_FEATURE_SET_AAM_ENABLED=1
E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=128
E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=254
E: ID_ATA_FEATURE_SET_PUIS=1
E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_SCSI_COMPAT=SATA_WDC_WD3200KS-00_WD-WCAPD3610786
E: ID_PATH=pci-0000:00:1f.2-scsi-0:0:0:0
E: ID_PART_TABLE_TYPE=dos
E: ID_FS_LABEL=/boot_alt
E: ID_FS_LABEL_ENC=\x2fboot_alt
E: ID_FS_UUID=2951a22e-5f31-4178-be18-dcd1ba35c4e4
E: ID_FS_UUID_ENC=2951a22e-5f31-4178-be18-dcd1ba35c4e4
E: ID_FS_SEC_TYPE=ext2
E: ID_FS_VERSION=1.0
E: ID_FS_TYPE=ext3
E: ID_FS_USAGE=filesystem
E: ID_PART_ENTRY_SCHEME=dos
E: ID_PART_ENTRY_TYPE=0x83
E: ID_PART_ENTRY_NUMBER=2
E: UDISKS_PRESENTATION_NOPOLICY=0
E: UDISKS_PARTITION=1
E: UDISKS_PARTITION_SCHEME=mbr
E: UDISKS_PARTITION_NUMBER=2
E: UDISKS_PARTITION_TYPE=0x83
E: UDISKS_PARTITION_SIZE=314572800
E: 
UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
E: UDISKS_PARTITION_OFFSET=314572800
E: UDISKS_PARTITION_ALIGNMENT_OFFSET=0
E: 
DEVLINKS=/dev/disk/by-id/ata-WDC_WD3200KS-00PFB0_WD-WCAPD3610786-part2 
/dev/disk/by-id/scsi-SATA_WDC_WD3200KS-00_WD-WCAPD3610786-part2 
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part2 
/dev/disk/by-uuid/2951a22e-5f31-4178-be18-dcd1ba35c4e4 
/dev/disk/by-label/\x2fboot_alt
E: TAGS=:systemd:

(I have the same experience with sda1, I'm playing with sda2 since it 
won't kill my machine if I screw it up)

I'm guessing something is wrong with hotplug/hotunplug; but I have no 
idea how systemd talks to them.


-- 
error compiling committee.c: too many arguments to function