Comment 4 for bug 1657938

Hi,
in the log I've seen:
2017-01-15T18:31:03.674750Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-15T18:31:28.754081Z 0 [Warning] InnoDB: 1048576 bytes should have been written. Only 12288 bytes written. Retrying for the remaining bytes.
2017-01-15T18:31:28.754329Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
2017-01-15T18:31:28.754417Z 0 [ERROR] InnoDB: Write to file ./ib_logfile1failed at offset 11534336, 1048576 bytes should have been written, only 12288 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2017-01-15T18:31:28.754601Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
2017-01-15T18:31:28.755145Z 0 [ERROR] InnoDB: Cannot set log file ./ib_logfile1 to size 48 MB
2017-01-15T18:31:28.755214Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
2017-01-15T18:31:29.055637Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-15T18:31:29.055792Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-15T18:31:29.055829Z 0 [ERROR] Failed to initialize plugins.
2017-01-15T18:31:29.055850Z 0 [ERROR] Aborting

That looks like an I/O error either due to failing Hardware or due to out-of-space on the disk backing the Database.

I/O Errors should be in dmesg but I haven't seen any, could you check your system for out-of-space constraints and also let us know if the issue is persistent and reproducible (e.g. when trying to upgrade again).