Yakkety crash during install setting NTP

Bug #1589122 reported by Arlen B Taylor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have attempted to install Yakkety on an existing computer(which had Ubuntu on previously) with new drives and other hardware. I am using UNETBootin with a downloaded latest daily version of Ubuntu. The download occurred yesterday and about 1700 Zulu UTC-7. This is the third attempt that has failed.

The Motherboard is an MSI Z170A Gaming M9 with 64GB DDR4 RAM. The processor is an Intel I7. The machine is being used normally as an AD FileServer with 6 hard drives, 2 CD drives and 2 hot connectors connected through SATA III connections.

No error messages occur other than the install has crashed. Data was collected and I assume transmitted.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
CurrentDesktop: KDE
Date: Sat Jun 4 11:05:00 2016
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160603)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Arlen B Taylor (abtaylr) wrote :
Revision history for this message
Arlen B Taylor (abtaylr) wrote :

In my most recent attempt to install I did a fresh download of Kubuntu 16.10 live to another Pen Drive
and got an error message 'ubi-console-setup' failed with return code of 1. I tried to re-select the keyboard, if that is what it is referring to, choosing the Danish keyboard instead of US. It still came up with the same failure of the install.

I am currently doing a fresh download onto yet another pen drive and will try again.

Revision history for this message
Arlen B Taylor (abtaylr) wrote :

The stalling event seems to occur at setting the time zone. The keyboard thing might just be a red herring.

Revision history for this message
Arlen B Taylor (abtaylr) wrote :

It continues to crash at configuring time zone. I have tried setting the time and time zone using the trial version kubuntu, which works fine, of course, it doesn´t transfer anything over to setup.

Revision history for this message
Arlen B Taylor (abtaylr) wrote :

It appears that there is a timeout happening when the install program tries to sync with the time server. I have been looking, unsuccessfully, for a way to get past that problem. The machine is logged onto the router, so it has access to the internet. I am working from the machine now with the trial version running after the latest installer crash.

Arlen B Taylor (abtaylr)
summary: - Yakkety crash during install 3/4 way through
+ Yakkety crash during install setting NTP
description: updated
Revision history for this message
Arlen B Taylor (abtaylr) wrote :

I have continued to attempt install each time with the same result. I am installing onto a SAMSUNG 500MB SSD. The BIOS of the computer is setup for UEFI + Legacy. For what itś worth I have pinged from the Virtual Console ntp.ubuntu.com successfully.

During the install I checked automatic updating and 3rd party drivers. For a keyboard I select English(US) alternate international since I use a 105-key model.

This what shows in the latest syslog:

'Kubuntu 16.10 _Yakkety Yak_ - Alpha amd64 (20160604)'
log-output -t ubiquity setxkbmap -model pc105 -layout us -variant alt-intl -option
kubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Plugin timezone failed with code 2
kubuntu systemd-timesyncd[1417]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
kubuntu systemd-timesyncd[1417]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
kubuntu systemd-timesyncd[1417]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).

Revision history for this message
Arlen B Taylor (abtaylr) wrote :

I have continued to re-install using many different USB MemorySticks. I have switched from using UEFI USBKey to instead using legacy USBKey. I have noticed that an additional error appears now that the copy function has failed, etc., etc. My computer mostly has USB 3.1, but there are a couple of USB 3.0. With those I get the same errors, just a little longer to get there.

With the change to not using UEFI, I now have the menu that appears in the install routine. I have run the checkdisk routine and it always comes up stating that 1 file is in error without identifying which one it is. I have used GParted on another computer and re-formatted my USB drives before using UNETBootin to get the latest version of Kubuntu Daily Live-64bit. Despite this extra effort the check disk routine still always comes up with the same error.

Next I am going to use a USB 2.1 hub to put the USB Memory Stick for my next attempt.

Revision history for this message
Arlen B Taylor (abtaylr) wrote :

I am discontinuing attempts to install Kubuntu 16.10. I have tried using UEFI and Legacy with both USB Stick and DVD all with the same result. The USB always shows 1 file in error on checkdisk. I have updated each day to have the latest daily version. I have wiped the USB's and re-formatted in GParted to insure that there are no remnants from a previous use of the USB drive.

I will now move to Kubuntu 16.04.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1587602, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.