Speaking to your two broad possibilities: (a) incomplete write to the USB and (b) incompatibility between hardware and test environment.
ISO to USB write process
My laptop is running RHEL 7. I downloaded the ISO to that laptop, and ran the suggested dd command to write the ISO to the USB drive. The dd command seemed to finish successfully.
(I thought I had saved my dd output somewhere, but having trouble finding it now.)
As I mentioned in the previous comment, the checksum of the file on my laptop matches. This seems a pretty rock-solid copy process. Note that I did *NOT* pre-format the USB or anything: I just assumed the DD process would destroy whatever was there and write from the beginning.
I'll check with a different USB. I'll also try writing it from the desktop using a different method (other than dd).
Incompatible hardware / exam environment
Bluntly, this seems impossible. The laptop is already running RHEL7! It should be pretty much guaranteed to be compatible.
For the desktop: this is info that I didn't have when I first commented last night). On the desktop where I worked-around the boot issue using grub commands:
(My actual performance on the exam is another story...)
The success of the exam compatibility test, AND the exam itself, raises doubt about whether the ISO-to-USB copy was bad. How bad could it have been, if everything other than booting worked perfectly? That's a very specific and restrained write failure.
Switching between exam modalities
Switching between modalities can be difficult in the current Covid climate. I live in Maryland; the local testing center has been closed for several months. Reopening date unknown. Travel between states to a different testing facility raises other potential issues.
For some of us, remote testing is by far the most practical method, for the near future. (Which is why you guys rolled it out in the first place!) Not so easy to switch modalities.
And I don't really believe there is an incompatibility issue here. Something else is going on. Does the Sandisk Cruzer protect a partition or some sectors at its beginning? Do the dd did not start where it was supposed to?
Or is there something wrong with the ISO? Doesn't work properly with UEFI systems, or something?
I don't know where you saw some information about the iso size that led you to expect a size of 4GB. All I know is that the iso sometimes updated, and the size change a bit (well not from 1GB to 4GB). Possible the 4GB size was very early version for a pilot phase.
Checking the file integrity and ensuring the file is not corrupted, complete and the correct one is something that can be solved by checking the checksum and proper versionning. My colleague @shefeeqyr is looking into the topic.
At the moment, I tested early August, the working file was:
1267597312 (1.2G) rhrexboot.iso
The sha512 checksum was:
(you need to type: sha512sum rhrexboot.iso).
Since I tested that one, and I verified its integrity, if the file has not been updated since then, that should be the same checksum, and it should prove it's not a corrupted file).
The correct URL to download the latest version of the Remote Exam iso is here:
Anyway, what USB key are you using? I suspect the issue might be somewhere else?
My checksum matches! Thanks.
Really, this checksum info should have been provided on the download page for the ISO, as is standard practice with distribution of installers.
On reading the first reply, I realize that I had misunderstood something. I had inferred that the ISO itself was 4Gb. I guess what is actually happening is that the ISO is smaller, and it loads the ~4Gb OS onto the USB. That makes more sense. My expectation was wrong.
But it still should boot! My USB is a brand-new SanDisk Cruzer 32Gb, fresh out of the box. I'll try loading it on another USB. But I'd be surprised if the flash drive itself is the issue, esp since I was able to finish booting after performing the grub workaround.
Hi @JimHardy ,
I agree for the checksum (and even the versionning should be added). A @shefeeqyr said, it's work in progress.
I agree it should boot, if flashing the image was properly done, if the hardware is compatible and if there are no restrictions, as it could be on some corporate laptops... A lot of possible root cause!
It booted properly for many candidates, the key would be to identify why that did not work in your case.
Indeed the USB key seems decent enough, sufficient space, and probably fast enough read/write speed...
I tried to boot into the redhat remote exam environment via my usb.
I was sent to the grub> prompt.
I typed "exit".
I proceeded to enter the environment to run my compatibility test.
I hope this helps someone.
My download speed in the compatibility test says it is too slow. I have a 2.8Mbps download connection speed (as measured by speedtest.net) and I know from looking at my router IP traffic that I am the only one using my home network and registering at 2.8Mbps during the network test. Why is it still saying the download speed is too slow ?
2.8 Mbps from Speedtest.net sounds a bit unpredictable to me. Usually, speedtest picks a nearest server to test bandwidth and hence realtime results can be quite different. The download/upload test of our compatibility test looks at the speed to access Red Hat servers and hence it will be different based on distance, time of testing etc.
You can try conducting a few more iterations of this test at different times of the day to see if the failure is consistent.
Is the remote exam environment the same as the lab environment in the online course? In essenece do I open a workstation window and then get a terminal? What exactly is being download during the exam. Are they big files (like in the Gigabytes) ?
The Remote Exam image (ISO) is not the same as your lab environment. You will be downloading an ISO that has to be written to a USB drive and that will make your USB drive a bootable device hosting an operating system. This operating system will be a highly secured, restricted spin off based on Fedora Workstation 32. The size of the ISO file will change with each revision and hence be sure to download the latest version posted in the document attached to this resource in RHLC. As of now, the size is about 1.2 GB.
You would boot to that operating system (Live USB) and login to the exam proctoring portal. You will have access to one full screen window from your laptop/desktop and the exam environment will be cloud-based.
Hope this clarifies.
Can we take exam just with external webcam ? I have laptop which has IR camera + normal integrated camera and when i attach external webcam than proctor was not able to see me via webcam. He can see only 2 camera's out of 3.
I had raise ticket but i did not got the clear response whether issue is been resolved or not. Is there a way to check and confirm that issue has been resolved.