Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upInstaller media check consistently fails at 4.8% #2246
Comments
andrewdavidwong
added
bug
C: installer
labels
Aug 13, 2016
andrewdavidwong
added this to the Release 3.1 milestone
Aug 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 15, 2016
Member
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
closed this
Aug 15, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ThomasWaldmann
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.
ThomasWaldmann
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
eduncan911
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.
eduncan911
commented
May 11, 2017
•
|
I ran into this as well.
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:
And now it passes. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
May 13, 2017
Member
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.
|
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
eduncan911
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.
eduncan911
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 14, 2017
Member
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
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 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Ah, you're right. That was so long ago that I forgot. |
andrewdavidwong
added
the
duplicate
label
May 14, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
zylstra
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. ...
zylstra
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. ... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
scalablecory
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.
scalablecory
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 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Dec 6, 2017
Member
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.
|
Since this issue is closed as a duplicate of #2051, I suggest instead commenting on #2051, which is open.
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.
As is common among free and open-source software projects, support is primarily given by knowledgeable members of the community through our mailing lists. |
andrewdavidwong commentedAug 13, 2016
Qubes OS version (e.g.,
R3.1):R3.1Problem description:
Gabriele Bini wrote:
Original message
Related issues:
Possibly related to #2051.