Bug 1493902 - unable to install f27 using usb stick
Summary: unable to install f27 using usb stick
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F27BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2017-09-21 07:10 UTC by lnie
Modified: 2017-09-22 07:57 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 08:43:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (42.34 KB, image/png)
2017-09-21 07:10 UTC, lnie
no flags Details
screenshot (38.89 KB, image/png)
2017-09-21 14:41 UTC, lnie
no flags Details

Description lnie 2017-09-21 07:10:03 UTC
Created attachment 1328801 [details]
screenshot

Description of problem:
create an installer using 
"dd if=Fedora-Workstation-Live-x86_64-27-20170920.n.0.iso of=/dev/sdb" with usb stick,then boot the installer,the installation failed,as shown in the attached 
screenshot.
f26 mediawriter dosen't works well(#bz1493899),so I choose to create the installer using dd  

Version-Release number of selected component (if applicable):
20170920.workstation

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2017-09-21 07:45:43 UTC
It seems that this only affects workstation-live not server.iso,though 
you are unlikely to create the server.iso installer using mediawriter.

Comment 2 Fedora Blocker Bugs Application 2017-09-21 07:46:23 UTC
Proposed as a Blocker for 27-beta by Fedora user lnie using the blocker tracking app because:

 This affects the Beta_Release_Criteria:
  Release-blocking live and dedicated installer images must boot when written to a USB stick with any of the officially supported methods.

Comment 3 Kamil Páral 2017-09-21 08:43:02 UTC
It's working fine for me:
$ sudo dd if=Fedora-Workstation-Live-x86_64-27-20170920.n.0.iso of=/dev/sdb bs=16M status=progress oflag=direct

$ sudo cmp Fedora-Workstation-Live-x86_64-27-20170920.n.0.iso /dev/sdb
cmp: EOF on Fedora-Workstation-Live-x86_64-27-20170920.n.0.iso

$ sudo checkisomd5 /dev/sdb
Press [Esc] to abort check.
The media check is complete, the result is: PASS.
It is OK to use this media.

I booted it and verified checksum over both bios and uefi, all ok.

When using dd, you must be very careful to not use in over a mounted partition. Also, if you mount the partition after writing, it might also change filesystem metadata, which in turn fails the mediacheck. It's a very common mistake, I attribute your problem to it. If you can't make it work, ping me and we'll look at it.

Comment 4 lnie 2017-09-21 14:40:36 UTC
Have you tried to use the created installer?
I have created the installer using dd carefully,the media check passes,
but it's still unable to do installation with usb stick.please see the attached screenshot.server.iso works fine,but workstation dosen't

Comment 5 lnie 2017-09-21 14:41:16 UTC
Created attachment 1329029 [details]
screenshot

Comment 6 Kamil Páral 2017-09-21 15:29:23 UTC
Yes, it works fine here. Not sure what went wrong there. One thing confuses me - you're talking about creating USB sticks, and then you're attaching VM screenshots. So which one is it? USB sticks should be tested with bare metal. VMs can be booted from the image directly, just mount it as DVD.

Comment 7 lnie 2017-09-22 04:39:26 UTC
My fault,I have used a tiny tricks here :
I insert the usb stick to the host machine,then add it to the virtual machine using virt-manager's add-hardware option,and add it to the boot menu.
It works well all the time,not sure what went wrong this time.

Comment 8 Kamil Páral 2017-09-22 07:57:27 UTC
Sure, that should work, but it's very easy to get the stick automounted and therefore have checksum changed, or something else can go wrong. If you have troubles with it, always also try a proper way of booting to check whether it's a real problem or just something in your particular process.


Note You need to log in before you can comment on or make changes to this bug.