intended behavior of mediacheck on FAIL

[Andre Robatino]

What is the intended behavior of mediacheck on FAIL (either on Install or Live
images)? In doing a test install in a KVM guest using the "check" boot
parameter
on an Install image, the mediacheck FAILed (which happens frequently in KVM,
although not reproducibly) but instead of at least prompting for what to do, it
just continued as if nothing happened. This is bad since would force people to
constantly watch the mediacheck progress to catch a FAIL and even then they
might not see it if it goes by too fast. The original mediacheck showed a screen
with PASS or FAIL and you had to tell it to continue. It's okay to proceed
automatically on PASS but not on FAIL. I tried deliberately corrupting Install
and Live images by replacing a few MiB at the end by zeroes and it always drops
to a dracut prompt, which did not happen with the original KVM install.

[Chris Murphy]

On Apr 28, 2012, at 3:09 PM, Andre Robatino wrote:

>  What is the intended behavior of mediacheck on FAIL (either on
> Install or Live
>  images)? In doing a test install in a KVM guest using the "check" boot
> parameter
>  on an Install image, the mediacheck FAILed (which happens frequently in KVM,
>  although not reproducibly) but instead of at least prompting for what to do, it
>  just continued as if nothing happened. This is bad since would force people to
>  constantly watch the mediacheck progress to catch a FAIL and even then they
>  might not see it if it goes by too fast. The original mediacheck showed a screen
>  with PASS or FAIL and you had to tell it to continue. It's okay to proceed
>  automatically on PASS but not on FAIL. I tried deliberately corrupting Install
>  and Live images by replacing a few MiB at the end by zeroes and it always drops
>  to a dracut prompt, which did not happen with the original KVM install. 
I'm doing EFI booting, so I get the option to Verify and Boot from within GRUB Legacy,
but I'm having the same problem. The result is nasty. See this bug.

https://bugzilla.redhat.com/show_bug.cgi?id=817262

And check out the attached photograph, which goes by so fast I have no chance of seeing
it. I only got suspicious when I thought, hmm, that verify was awfully fast. I had to
remove 'rghb quiet' and also use a 1/50th shutter speed to capture the failure.

[Andre Robatino]

Chris Murphy <lists <at> colorremedies.com> writes:

>  I'm doing EFI booting, so I get the option to Verify and Boot
> from within GRUB 
Legacy, but I'm having the same
>  problem. The result is nasty. See this bug.
>  
>  https://bugzilla.redhat.com/show_bug.cgi?id=817262
>  
>  And check out the attached photograph, which goes by so fast I have no chance 
of
seeing it. I only got
>  suspicious when I thought, hmm, that verify was awfully fast. I had
> to remove 
'rghb quiet' and also use a
>  1/50th shutter speed to capture the failure. 
OK, so that confirms this happens on Lives as well as Installs, so needs to be
fixed on both. What component should I file against?

Also should mention that I already filed
https://bugzilla.redhat.com/show_bug.cgi?id=809663 to expose mediacheck as a
boot menu option on Install images (it's already there on Lives) but this other
problem needs to be fixed to make it useful.

[Chris Murphy]

On Apr 28, 2012, at 3:59 PM, Andre Robatino wrote:
>  OK, so that confirms this happens on Lives as well as Installs, so
> needs to be
>  fixed on both. What component should I file against? 
My problem is explicitly with dd'ing Live-Desktop ISO to a USB stick. The ISO file
passes SHA256 checksum, as does burned media. And burned media pass using the Verify and
Boot option in the GRUB menu.

I think this would be filed against livecd-tools but I don't know so I'm going to
leave my bug alone until I hear from adamw, bcl or mjg.


Chris Murphy

[Andre Robatino]

Filed https://bugzilla.redhat.com/show_bug.cgi?id=817419 .