Ceph

I have yet to get anything to start without major intervention since upgrading from infernalis to jewel 10.2.0

systemctl start ceph does nothing

to start the mon I must run systemctl start ceph-mon@elara

to start an osd I must repeat the following for every disk:
mount -t xfs /dev/disk/by-partlabel/Ceph_OSD.0.XFSdata /srv/ceph/osd/osd.0 -o noatime,nodiratime,logbsize=256k,logbufs=8,allocsize=4M
systemctl start ceph-osd@0

then finally I have to run this to start the MDS:
systemctl start ceph-mds@fs1

I have a feeling the ceph-disk is misbehaving and causing the whole startup process to fail.

I don't know exactly where to start, please let me know what logs you need and I'll get them promptly.

on previous versions of ceph (firefly-infernalis) I've been using the same config and never had this problem. The info shown below is from a system that began life with infernalis on debian jewell. Except for a new problem creating pidfiles because of my config+running ceph as non-root (which has been resolved), infernalis worked perfectly on this particular config.

@root@elara:/etc/ceph# systemctl status ceph-osd@0
● ceph-osd@0.service - Ceph object storage daemon
Loaded: loaded (/lib/systemd/system/ceph-osd.service; disabled)
Active: failed (Result: start-limit) since Sat 2016-04-23 19:10:00 MDT; 44min ago
Process: 4141 ExecStart=/usr/bin/ceph-osd -f --cluster ${CLUSTER} --id %i --setuser ceph --setgroup ceph (code=exited, status=1/FAILURE)
Process: 4089 ExecStartPre=/usr/lib/ceph/ceph-osd-prestart.sh --cluster ${CLUSTER} --id %i --setuser ceph --setgroup ceph (code=exited, status=0/SUCCESS)
Main PID: 4141 (code=exited, status=1/FAILURE)

Apr 23 19:10:00 elara systemd1: Unit ceph-osd@0.service entered failed state.
Apr 23 19:10:00 elara systemd1: ceph-osd@0.service start request repeated too quickly, refusing to start.
Apr 23 19:10:00 elara systemd1: Failed to start Ceph object storage daemon.
Apr 23 19:10:00 elara systemd1: Unit ceph-osd@0.service entered failed state.
Apr 23 19:25:07 elara systemd1: ceph-osd@0.service start request repeated too quickly, refusing to start.
Apr 23 19:25:07 elara systemd1: Failed to start Ceph object storage daemon.
root@elara:/etc/ceph# systemctl status ceph-disk@0
● ceph-disk@0.service - Ceph disk activation: /0
Loaded: loaded (/lib/systemd/system/ceph-disk@.service; static)
Active: inactive (dead)
root@elara:/etc/ceph# systemctl start ceph-disk@0
Job for ceph-disk@0.service failed. See 'systemctl status ceph-disk@0.service' and 'journalctl -xn' for details.
root@elara:/etc/ceph# systemctl status ceph-disk@0
● ceph-disk@0.service - Ceph disk activation: /0
Loaded: loaded (/lib/systemd/system/ceph-disk@.service; static)
Active: failed (Result: exit-code) since Sat 2016-04-23 19:55:08 MDT; 4s ago
Process: 10705 ExecStart=/bin/sh -c flock /var/lock/ceph-disk /usr/sbin/ceph-disk --verbose --log-stdout trigger --sync %f (code=exited, status=1/FAILURE)
Main PID: 10705 (code=exited, status=1/FAILURE)

Apr 23 19:55:08 elara sh10705: File "/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 4964, in run
Apr 23 19:55:08 elara sh10705: main(sys.argv[1:])
Apr 23 19:55:08 elara sh10705: File "/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 4915, in main
Apr 23 19:55:08 elara sh10705: args.func(args)
Apr 23 19:55:08 elara sh10705: File "/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 4347, in main_trigger
Apr 23 19:55:08 elara sh10705: raise Error('unrecognized partition type %s' % parttype)
Apr 23 19:55:08 elara sh10705: ceph_disk.main.Error: Error: unrecognized partition type None
Apr 23 19:55:08 elara systemd1: ceph-disk@0.service: main process exited, code=exited, status=1/FAILURE
Apr 23 19:55:08 elara systemd1: Failed to start Ceph disk activation: /0.
Apr 23 19:55:08 elara systemd1: Unit ceph-disk@0.service entered failed state.
root@elara:/etc/ceph#
@

I could not find anyone else reporting this, but I can't be the only one experiencing this problem as a jewel early adopter.

Thanks a bunch for your help guys!