On 2/6/2018 7:15 AM, john doe wrote:
On 2/6/2018 6:53 AM, Jude DaShiell wrote:I ran the integrity check on the debian install menu. The last question I was asked was if system was set to utc or localtime and I answered that question and the disk went to 61% and ejected.So clearly Debian is not fully installed. You should try rescue mode to repair it and report this as a bug.
Note that before reporting I would strongly suggest you to do the following: https://www.debian.org/CD/verifyIf you downloaded the iso using wifi it is more then likely that the file got corrupted.
Verifying authenticity of downloaded Debian iso file. To checksum a file you will need to use the corresponding checksum utility: md5sum for MD5SUMS sha1sum for SHA1SUMS sha256 for SHA256SUMS sha512sum for SHA512SUMSOn the download page for the desired iso file you have also 'SHA512SUMS' and 'SHA512SUMS.sign'.
You download both files using for instance 'wget'.The first step is to verify the signature in 'SHA512SUMS' using 'gpg --verify *.sign'. When you see 'good signature from ...', you have successfully verified the iso which means that the iso has not been tampered with.
To checksum SHA512SUMS you would do: $ sha512sum -c SHA512SUMS 2>&1 | grep -i okIf you see something ending with ': OK', you have successfully checksummed the iso which means that the isoe is not corrupted.
From: https://www.debian.org/devel/debian-installer/"After using the Debian-Installer, please send us an installation report, even if there weren't any problems."On Tue, 6 Feb 2018, john doe wrote:Date: Tue, 6 Feb 2018 00:49:13 From: john doe <johndoe65534@mail.com> To: debian-accessibility@lists.debian.org Subject: Re: debian-buster-di-alpha2-x86_64 standard system install Resent-Date: Tue, 6 Feb 2018 05:49:28 +0000 (UTC) Resent-From: debian-accessibility@lists.debian.org On 2/5/2018 2:14 PM, Jude DaShiell wrote:The debian boot disk already had ejected at 61% of finishing theinstallation there was no way missing components could have been installed under those circumstances unless I put the boot disk back in and waited.? I have two systems here but have never tried an in-house ping since I am in a wifi required situation and only have one wifi adapter, so that can't be done.? By standard system when software selection came up I chose only option 12 and none of the other defaults which normally would start the system out with only a command lineAfter which step did it stop at 61%? If you use rescue mode can you repair your system?I can't test the installation process using an optical media but it looks to me as if Debian is not properly installed.When you say that you have verified the iso; I'm asuming that the checksum is correct (the output should end with 'OK')?On Mon, 5 Feb 2018, john doe wrote:Date: Mon, 5 Feb 2018 05:49:43 From: john doe <johndoe65534@mail.com> To: debian-accessibility@lists.debian.org Subject: Re: debian-buster-di-alpha2-x86_64 standard system install Resent-Date: Mon,? 5 Feb 2018 10:50:02 +0000 (UTC) Resent-From: debian-accessibility@lists.debian.org On 2/5/2018 9:51 AM, Jude DaShiell wrote:?I checked the dvd integrity and integrity check was successful.? I ?installed on a 3tb disk using espeak and had grub for boot loader.?Finishing the install ejected the dvd at 61% and I hit enter then theIf the installer stopped at 61%; clearly some components are missing. What happened at 61% or what am I missing??system got lost in space so I powered down waited about a minute andtried?booting the system.? No beep from grub and no speech either.? Could itbe?the espeak stuff didn't also have its configuration stuff saved to thenew ?installation but the orca stuff got saved?- Do you know if the system can boot (can you ping it)? - Did you install ssh; if yes can you remotely access that host? - Maybe using Debian rescue? - Can you mount that partition from an other system?
-- John Doe