TrevorH wrote: ↑2019/11/13 17:37:49
So to be absolutely sure, I copied the iso to a USB stick and then attached that to a vbox VM and booted it, did a default Server with GUI install which installed over 1300 packages successfully. So whatever packages there are that "have the incorrect checksum" they're either not presnt on my USB stick or I'm not reading them with that install type.
In addition, prior to the release of CentOS 8 there were probably hundreds if not thousands of automated installs and CI runs against it. I am pretty sure that if there was a general problem with it, we'd already know.
Thank you for this ^
OK this is ALL great info but no one has mentioned how they are copying their ISOs to their usb's? I have Windows 10. What are you using to do it? I am unable to use the "dd" method on Windows 10, natively..
Historically, I had been using RUFUS but as mentioned, it has had problems before. Then I found Fedora and tested their OS and found their tool. Their tool works perfectly for CentOS 7 and Fedora so I had since been using that. Here I am now
I googled and found this page
https://wiki.centos.org/HowTos/InstallFromUSBkey
It's for Centos7 and above so hope it's correct. It echoes what you guys are stating around the "device" compared to the partition. It has four programs listed as "known working" to copy the ISO to usb from Windows.
The first one looks like malware:
https://www.virustotal.com/gui/file/4ed ... /detection
I tried the "DD for Windows" which is in no way user-friendly and definitely not noob friendly. There is a possibility to erase your Windows hard disk using this
But anyway, I used it and then plugged the usb back into Centos to validate the SHA. I have a single partition on the usb. The `/dev/` devices are showing as /dev/sdb and /dev/sdb1
Sha256 =
Code: Select all
root@CV000142 Desktop]# sha256sum /dev/sdb && sha256sum /dev/sdb1
f37d37024022100eaeaba928a2672c8dd734569e3a162cbafd060f18647bf5db /dev/sdb
7ff7642c6ed881100db0006f4523298a31999d1dc0f57c0dcdcf16cd6ece837e /dev/sdb1
[root@CV000142 Desktop]#
The release notes have ea17ef71e0df3f6bf1d4bf1fc25bec1a76d1f211c115d39618fe688be34503e8 . Neither the above match. Plus, I had trouble finding the device as per the docs:
Code: Select all
> .\dd.exe --list rawwrite dd for windows version 0.6beta3.
Written by John Newbigin <jn@it.swin.edu.au>
This program is covered by terms of the GPL Version 2.
Win32 Available Volume Information
\\.\Volume{c37effbf-39fd-47de-a908-7134c243e2f1}\
link to \\?\Device\HarddiskVolume1
fixed media
Not mounted
\\.\Volume{364ffe4c-d4e2-4c52-8bb2-176fcd8b4372}\
link to \\?\Device\HarddiskVolume4
fixed media
Mounted on \\.\c:
\\.\Volume{e2fd272c-9ed1-11e9-a2d9-d6fe72dc694d}\
link to \\?\Device\HarddiskVolume43
removeable media
Mounted on \\.\d:
\\.\Volume{4664ffed-3bb7-44da-bb61-49daac15dc62}\
link to \\?\Device\HarddiskVolume2
fixed media
Not mounted
\\.\Volume{bf418c5f-a7ab-11e9-a2e6-3cf01139a390}\
link to \\?\Device\HarddiskVolume39
removeable media
Mounted on \\.\e:
\\.\Volume{bf418c60-a7ab-11e9-a2e6-3cf01139a390}\
link to \\?\Device\HarddiskVolume40
removeable media
Mounted on \\.\f:
Next - win32 disk imager. This was straight forward to use. You just select the ISO and the device letter, in my case D:. Write was successful. So I put back into the centos laptop I have and it again has /dev/sdb , /dev/sdb1 and /dev/sdb2
Calculating the SHAs gives:
Code: Select all
# sha256sum /dev/sdb && sha256sum /dev/sdb1 && sha256sum /dev/sdb2
6cb697600cccfabbf3a506082ab4f8579a0a585a1618ee8fe0a6aac9cabd1872 /dev/sdb
ea17ef71e0df3f6bf1d4bf1fc25bec1a76d1f211c115d39618fe688be34503e8 /dev/sdb1
5bfdaa324a0115b384c31b2f3cc97d5a4cba26a8df2b493bf9ca2075fecad36d /dev/sdb2
[root@CV000142 Desktop]#
So looks like that tool does the same as Fedora Media Writer...
So what's the right way to do this from Windows 10?
So anyway, just in case it's impossible from Windows 10, I copied the ISO to centos and ran:
The result was I had /dev/sdb , /dev/sdb1 and /dev/sdb2
I didn't bother checking the sha. I put the usb back into windows and opened the terminal and run:
Code: Select all
diskpart
list disk
select disk (the ID number given to the usb drive shown in the previous command)
clean
Now when doing the dd copy in centos, the result is the same sdb & sdb1 & sdb2
Checking the sha against this gives:
Code: Select all
# sha256sum /dev/sdb && sha256sum /dev/sdb1 && sha256sum /dev/sdb2
190ac61ab767e08670fe6a1626c8b05420cc2931970732da07cd60d815bf9ba2 /dev/sdb
ea17ef71e0df3f6bf1d4bf1fc25bec1a76d1f211c115d39618fe688be34503e8 /dev/sdb1
5bfdaa324a0115b384c31b2f3cc97d5a4cba26a8df2b493bf9ca2075fecad36d /dev/sdb2
[root@CV000142 Desktop]#
So the result is the same!
@TrevorH can you clarify what you see on your side?