Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installer media check consistently fails at 4.8% #2246

Closed
andrewdavidwong opened this Issue Aug 13, 2016 · 10 comments

Comments

Projects
None yet
6 participants
@andrewdavidwong
Copy link
Member

commented Aug 13, 2016

Qubes OS version (e.g., R3.1):

R3.1

Problem description:

Gabriele Bini wrote:

I have exactly the same problem. This is what I did:

  1. I downloaded the Qubes-R3.1-x86_64.iso ISO from the Torrent.
  2. I checked the signature and the hash values in the DIGEST file (I checked just the hash values in a second PC) and everything was fine.
  3. I used dd to copy the ISO in a USB flash drive (Sony 8Gb)
  4. When I booted from the USB I tried the “Verify and Install” option but, exactly at 4,8% (as for Cory Nelson) the check failed. There was a message of this type (copied by hand):
    Failed to start media check on /dev/sdc
    See 'systemctl status checkisomd5@-dev-sdc.service' and 'journal.ctl-xn' for details
  5. I couldn't check anything because the system was halted

Original message


Related issues:

Possibly related to #2051.

@marmarek

This comment has been minimized.

Copy link
Member

commented Aug 15, 2016

I made another test: I copied the same ISO on another USB Flash drive (8Gb Kingstone) from a different computer (Mint 17.1), then I tried again the installation on the previous computer: this time it worked!

@marmarek marmarek closed this Aug 15, 2016

@ThomasWaldmann

This comment has been minimized.

Copy link

commented May 8, 2017

Just had the same thing. GPG sig valid, sig check by qubes invalid at 4.8%.

Potential issue: inserting the stick into a windows 10 machine once after creating, before using at (yeah, bad idea).

I just recreate the stick to check that...

Update: yes, that was it. Freshly created stick passes the sig check by qubes.

So: don't put your sticks into anything that accesses/mounts them, especially not into a windows machine.

@eduncan911

This comment has been minimized.

Copy link

commented May 11, 2017

I ran into this as well.

  • Used Etcher on macOS to create USB.
  • Put into my Windows 10 tablet, and missed the startup process and it booted to Windows.
  • Rebooted to bios, booted up, 4.8% failure every time.

So: don't put your sticks into anything that accesses/mounts them, especially not into a windows machine.

I can confirm this is indeed the issue!

The trick for me, because this tablet requires a boot to Windows before rebooting to F12 selection, is to:

  • boot Windows first
  • reboot into BIOS
  • insert USB
  • reboot back to F12 boot selection screen.

And now it passes.

@andrewdavidwong

This comment has been minimized.

Copy link
Member Author

commented May 13, 2017

So we've learned that if you merely insert your USB drive into a Windows machine and take no further action, Windows will silently modify the contents of your drive? Interesting.

@eduncan911

This comment has been minimized.

Copy link

commented May 13, 2017

Yep. I dont think I even signed in, just booted up to login prompted and restarted to get to the USB stick.

@marmarek

This comment has been minimized.

Copy link
Member

commented May 14, 2017

So we've learned that if you merely insert your USB drive into a Windows machine and take no further action, Windows will silently modify the contents of your drive? Interesting.

Yes, we already know this: #2051 (comment)

There was some attempt to prevent this behavior - basically already included the files Windows adds in the image, but it wasn't enough. It also alter modification time of it (or such)... There are some more ideas how to mitigate this (like reverse known modifications before validation).

Anyway, it's a duplicate of #2051

@andrewdavidwong

This comment has been minimized.

Copy link
Member Author

commented May 14, 2017

Ah, you're right. That was so long ago that I forgot.

@zylstra

This comment has been minimized.

Copy link

commented Dec 5, 2017

So the option of "Test this media & install Qubes [...]" doesn't work with a USB created in Windows? Does the "Install Qubes [...]" option work? Not sure I understand what to do here.

Should the Installation Guide (https://www.qubes-os.org/doc/installation-guide/) mention this? Should I add this information to the Installation Guide myself?

Should the Installation Guide include directions to disable Secure Boot and Enable legacy mode, or CMS as it is also commonly called?

Should the website include a link to support, wherever it may be determined to be given, in the footer? Where is support given by the way? The help link at the bottom of the Installation Guide page just links to documentation again. :/

etc. ...

@scalablecory

This comment has been minimized.

Copy link

commented Dec 5, 2017

@zylstra I was unable to create a bootable USB via Windows. I had to juggle an Ubuntu live USB to run dd from Linux. It would be good to document this in the install notes until it is resolved.

@andrewdavidwong

This comment has been minimized.

Copy link
Member Author

commented Dec 6, 2017

Since this issue is closed as a duplicate of #2051, I suggest instead commenting on #2051, which is open.

Should I add this information to the Installation Guide myself?

A PR adding some information on this might be a good idea. If you haven't already, please take a look at our Documentation Guidelines for information about contributing.

Should the website include a link to support, wherever it may be determined to be given, in the footer? Where is support given by the way? The help link at the bottom of the Installation Guide page just links to documentation again. :/

As is common among free and open-source software projects, support is primarily given by knowledgeable members of the community through our mailing lists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.