I am using the installation file Fedora-7-KDE-Live-i686.iso. This file
was downloaded and verified using Bit Torrent. To make double sure it
was an uncorrupted download I verified the SHA1 signature of this
download using HashCalc.

In the startup screen of this disk I am able to boot when I select "Run
from Image."

I cannot boot when I select "Verify and Run from Image." The
verification fails when it has reached about 35%. I have burned two
disks and both do the same. Even after using the Memorex "CD Repair and
Cleaner" kit.

What I see on screen:
--------
Uncompressing Linux... Ok, Booting the kernal.
Usb 3-1: device not accepting address 2, error -71
Buffer I/O error on device SR0, Logical Block 175747
Buffer I/O error on device SR0, Logical Block 175747
Buffer I/O error on device SR0, Logical Block 175747
Buffer I/O error on device SR0, Logical Block 175747
Buffer I/O error on device SR0, Logical Block 175747
Buffer I/O error on device SR0, Logical Block 175747
Buffer I/O error on device SR0, Logical Block 175747
Buffer I/O error on device SR0, Logical Block 175747

Verifying ISO image...
dev/root: <long signature>
Fragment Sums: <long signature>
Fragment Count: 20
Percent complete 34.9Buffer I/O error on device SR0, Logical Block 61400
Buffer I/O error on device SR0, Logical Block 61401
Buffer I/O error on device SR0, Logical Block 61402
Buffer I/O error on device SR0, Logical Block 61403
Buffer I/O error on device SR0, Logical Block 61404
Buffer I/O error on device SR0, Logical Block 61405
Buffer I/O error on device SR0, Logical Block 61406
Buffer I/O error on device SR0, Logical Block 61407
Buffer I/O error on device SR0, Logical Block 61408
Buffer I/O error on device SR0, Logical Block 61409

034.9
The media check is complete, the result is FAIL.

It is not recommended you use this media.
Bug in initramfs /init detected. Dropping to shell. Good Luck!
---------

The Usb 3-1 error 71 line does not always appear.

The Buffer I/O errors and media fail happens on a computer with a
CDR/DVD drive and another computer that has a CD Rom with no recording
capability.

I have no idea what do to about these errors. I do not know if this disk
can be trusted to boot without verification to install a dual boot or
not. Any information about this is much appreciated.

I would also like to know where to look up error 71.

*****
Remove the "sj." from the domain name part of my email address if you
desire to respond directly. It is a spam jammer.

On Thu, 20 Sep 2007 12:22:47 -0700, Artist wrote:

> I am using the installation file Fedora-7-KDE-Live-i686.iso. This file
> was downloaded and verified using Bit Torrent. To make double sure it
> was an uncorrupted download I verified the SHA1 signature of this
> download using HashCalc.
>
> In the startup screen of this disk I am able to boot when I select "Run
> from Image."
>
> I cannot boot when I select "Verify and Run from Image." The
> verification fails when it has reached about 35%. I have burned two
> disks and both do the same. Even after using the Memorex "CD Repair and
> Cleaner" kit.
>
> What I see on screen:
> --------
> Uncompressing Linux... Ok, Booting the kernal.
> Usb 3-1: device not accepting address 2, error -71
> Buffer I/O error on device SR0, Logical Block 175747
> Buffer I/O error on device SR0, Logical Block 175747
> Buffer I/O error on device SR0, Logical Block 175747
> Buffer I/O error on device SR0, Logical Block 175747
> Buffer I/O error on device SR0, Logical Block 175747
> Buffer I/O error on device SR0, Logical Block 175747
> Buffer I/O error on device SR0, Logical Block 175747
> Buffer I/O error on device SR0, Logical Block 175747
>
> Verifying ISO image...
> dev/root: <long signature>
> Fragment Sums: <long signature>
> Fragment Count: 20
> Percent complete 34.9Buffer I/O error on device SR0, Logical Block 61400
> Buffer I/O error on device SR0, Logical Block 61401
> Buffer I/O error on device SR0, Logical Block 61402
> Buffer I/O error on device SR0, Logical Block 61403
> Buffer I/O error on device SR0, Logical Block 61404
> Buffer I/O error on device SR0, Logical Block 61405
> Buffer I/O error on device SR0, Logical Block 61406
> Buffer I/O error on device SR0, Logical Block 61407
> Buffer I/O error on device SR0, Logical Block 61408
> Buffer I/O error on device SR0, Logical Block 61409
>
> 034.9
> The media check is complete, the result is FAIL.
>
> It is not recommended you use this media.
> Bug in initramfs /init detected. Dropping to shell. Good Luck!
> ---------
>
> The Usb 3-1 error 71 line does not always appear.
>
> The Buffer I/O errors and media fail happens on a computer with a
> CDR/DVD drive and another computer that has a CD Rom with no recording
> capability.
>
> I have no idea what do to about these errors. I do not know if this disk
> can be trusted to boot without verification to install a dual boot or
> not. Any information about this is much appreciated.
>
> I would also like to know where to look up error 71.
>
> *****
> Remove the "sj." from the domain name part of my email address if you
> desire to respond directly. It is a spam jammer.
Burn it at a slower rate ...... usually 4x does rather well.

nunya wrote:
> On Thu, 20 Sep 2007 12:22:47 -0700, Artist wrote:
>
>> I am using the installation file Fedora-7-KDE-Live-i686.iso. This file
>> was downloaded and verified using Bit Torrent. To make double sure it
>> was an uncorrupted download I verified the SHA1 signature of this
>> download using HashCalc.
>>
>> In the startup screen of this disk I am able to boot when I select "Run
>> from Image."
>>
>> I cannot boot when I select "Verify and Run from Image." The
>> verification fails when it has reached about 35%. I have burned two
>> disks and both do the same. Even after using the Memorex "CD Repair and
>> Cleaner" kit.
>>
>> What I see on screen:
>> --------
>> Uncompressing Linux... Ok, Booting the kernal.
>> Usb 3-1: device not accepting address 2, error -71
>> Buffer I/O error on device SR0, Logical Block 175747
>> Buffer I/O error on device SR0, Logical Block 175747
>> Buffer I/O error on device SR0, Logical Block 175747
>> Buffer I/O error on device SR0, Logical Block 175747
>> Buffer I/O error on device SR0, Logical Block 175747
>> Buffer I/O error on device SR0, Logical Block 175747
>> Buffer I/O error on device SR0, Logical Block 175747
>> Buffer I/O error on device SR0, Logical Block 175747
>>
>> Verifying ISO image...
>> dev/root: <long signature>
>> Fragment Sums: <long signature>
>> Fragment Count: 20
>> Percent complete 34.9Buffer I/O error on device SR0, Logical Block 61400
>> Buffer I/O error on device SR0, Logical Block 61401
>> Buffer I/O error on device SR0, Logical Block 61402
>> Buffer I/O error on device SR0, Logical Block 61403
>> Buffer I/O error on device SR0, Logical Block 61404
>> Buffer I/O error on device SR0, Logical Block 61405
>> Buffer I/O error on device SR0, Logical Block 61406
>> Buffer I/O error on device SR0, Logical Block 61407
>> Buffer I/O error on device SR0, Logical Block 61408
>> Buffer I/O error on device SR0, Logical Block 61409
>>
>> 034.9
>> The media check is complete, the result is FAIL.
>>
>> It is not recommended you use this media.
>> Bug in initramfs /init detected. Dropping to shell. Good Luck!
>> ---------
>>
>> The Usb 3-1 error 71 line does not always appear.
>>
>> The Buffer I/O errors and media fail happens on a computer with a
>> CDR/DVD drive and another computer that has a CD Rom with no recording
>> capability.
>>
>> I have no idea what do to about these errors. I do not know if this disk
>> can be trusted to boot without verification to install a dual boot or
>> not. Any information about this is much appreciated.
>>
>> I would also like to know where to look up error 71.
>>
>> *****
>> Remove the "sj." from the domain name part of my email address if you
>> desire to respond directly. It is a spam jammer.
> Burn it at a slower rate ...... usually 4x does rather well.

The maximum burn speed for the burner is 48x. This is the burn speed I
created the first two disks with. I followed your advice on the third
disk and burned it at 4x. The result was the same except this time
instead of failing at 35% it failed near the end of the last fragment at
100%. All the other error messages showed when booting with this third
disk also. I burned a fourth disk at 2x and got the same result as the
third.

*****
> Remove the "sj." from the domain name part of my email address if you
> desire to respond directly. It is a spam jammer.

On Thu, 20 Sep 2007 15:54:56 -0700, Artist wrote:

> nunya wrote:
>> On Thu, 20 Sep 2007 12:22:47 -0700, Artist wrote:
>>
>>> I am using the installation file Fedora-7-KDE-Live-i686.iso. This file
>>> was downloaded and verified using Bit Torrent. To make double sure it
>>> was an uncorrupted download I verified the SHA1 signature of this
>>> download using HashCalc.
>>>
>>> In the startup screen of this disk I am able to boot when I select
>>> "Run from Image."
>>>
>>> I cannot boot when I select "Verify and Run from Image." The
>>> verification fails when it has reached about 35%. I have burned two
>>> disks and both do the same. Even after using the Memorex "CD Repair
>>> and Cleaner" kit.
>>>
>>> What I see on screen:
>>> --------
>>> Uncompressing Linux... Ok, Booting the kernal. Usb 3-1: device not
>>> accepting address 2, error -71 Buffer I/O error on device SR0, Logical
>>> Block 175747 Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747 Buffer I/O error
>>> on device SR0, Logical Block 175747 Buffer I/O error on device SR0,
>>> Logical Block 175747 Buffer I/O error on device SR0, Logical Block
>>> 175747 Buffer I/O error on device SR0, Logical Block 175747 Buffer I/O
>>> error on device SR0, Logical Block 175747
>>>
>>> Verifying ISO image...
>>> dev/root: <long signature>
>>> Fragment Sums: <long signature>
>>> Fragment Count: 20
>>> Percent complete 34.9Buffer I/O error on device SR0, Logical Block
>>> 61400 Buffer I/O error on device SR0, Logical Block 61401 Buffer I/O
>>> error on device SR0, Logical Block 61402 Buffer I/O error on device
>>> SR0, Logical Block 61403 Buffer I/O error on device SR0, Logical Block
>>> 61404 Buffer I/O error on device SR0, Logical Block 61405 Buffer I/O
>>> error on device SR0, Logical Block 61406 Buffer I/O error on device
>>> SR0, Logical Block 61407 Buffer I/O error on device SR0, Logical Block
>>> 61408 Buffer I/O error on device SR0, Logical Block 61409
>>>
>>> 034.9
>>> The media check is complete, the result is FAIL.
>>>
>>> It is not recommended you use this media. Bug in initramfs /init
>>> detected. Dropping to shell. Good Luck! ---------
>>>
>>> The Usb 3-1 error 71 line does not always appear.
>>>
>>> The Buffer I/O errors and media fail happens on a computer with a
>>> CDR/DVD drive and another computer that has a CD Rom with no recording
>>> capability.
>>>
>>> I have no idea what do to about these errors. I do not know if this
>>> disk can be trusted to boot without verification to install a dual
>>> boot or not. Any information about this is much appreciated.
>>>
>>> I would also like to know where to look up error 71.
>>
>> Burn it at a slower rate ...... usually 4x does rather well.
>
> The maximum burn speed for the burner is 48x. This is the burn speed I
> created the first two disks with. I followed your advice on the third
> disk and burned it at 4x. The result was the same except this time
> instead of failing at 35% it failed near the end of the last fragment at
> 100%. All the other error messages showed when booting with this third
> disk also. I burned a fourth disk at 2x and got the same result as the
> third.

You may have a batch of bad media or ...

I used to have a 52x CD burner and burned at 24x. I started getting bad
burns no matter what speed I used. I bought "expensive" media thinking
that the "bargain" media was the problem. The problem persisted no
matter what I did. Turned out I have a flakey burner. Got a new one.
Problem went away.

Also, you verified the SHA1SUM of the downloaded file. FYI: You can
verify the CD after you burned it without using the on-the-cd
verification utility. Since in Linux everything is a file, this is what
I do to verify a burn, if the burner software doesn't have the feature.
With the newly burned CD in the drive, type in a terminal:

sha1sum /dev/cdrom (or whatever you burner's device name is)

This will print out the SHA1SUM. Compare it to the one for the ISO that
was burned. If they match, it's a good burn, no matter what the on-cd
verify says.

This also works for any other of the checksum utilities, too.


Stef

Artist wrote:
> nunya wrote:
>> On Thu, 20 Sep 2007 12:22:47 -0700, Artist wrote:
>>
>>> I am using the installation file Fedora-7-KDE-Live-i686.iso. This
>>> file was downloaded and verified using Bit Torrent. To make double
>>> sure it was an uncorrupted download I verified the SHA1 signature of
>>> this download using HashCalc.
>>>
>>> In the startup screen of this disk I am able to boot when I select
>>> "Run from Image."
>>>
>>> I cannot boot when I select "Verify and Run from Image." The
>>> verification fails when it has reached about 35%. I have burned two
>>> disks and both do the same. Even after using the Memorex "CD Repair
>>> and Cleaner" kit.
>>>
>>> What I see on screen:
>>> --------
>>> Uncompressing Linux... Ok, Booting the kernal.
>>> Usb 3-1: device not accepting address 2, error -71
>>> Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747
>>> Buffer I/O error on device SR0, Logical Block 175747
>>>
>>> Verifying ISO image...
>>> dev/root: <long signature>
>>> Fragment Sums: <long signature>
>>> Fragment Count: 20
>>> Percent complete 34.9Buffer I/O error on device SR0, Logical Block 61400
>>> Buffer I/O error on device SR0, Logical Block 61401
>>> Buffer I/O error on device SR0, Logical Block 61402
>>> Buffer I/O error on device SR0, Logical Block 61403
>>> Buffer I/O error on device SR0, Logical Block 61404
>>> Buffer I/O error on device SR0, Logical Block 61405
>>> Buffer I/O error on device SR0, Logical Block 61406
>>> Buffer I/O error on device SR0, Logical Block 61407
>>> Buffer I/O error on device SR0, Logical Block 61408
>>> Buffer I/O error on device SR0, Logical Block 61409
>>>
>>> 034.9
>>> The media check is complete, the result is FAIL.
>>>
>>> It is not recommended you use this media.
>>> Bug in initramfs /init detected. Dropping to shell. Good Luck!
>>> ---------
>>>
>>> The Usb 3-1 error 71 line does not always appear.
>>>
>>> The Buffer I/O errors and media fail happens on a computer with a
>>> CDR/DVD drive and another computer that has a CD Rom with no
>>> recording capability.
>>>
>>> I have no idea what do to about these errors. I do not know if this
>>> disk can be trusted to boot without verification to install a dual
>>> boot or not. Any information about this is much appreciated.
>>>
>>> I would also like to know where to look up error 71.
>>>
>>> *****
>>> Remove the "sj." from the domain name part of my email address if you
>>> desire to respond directly. It is a spam jammer.
>> Burn it at a slower rate ...... usually 4x does rather well.
>
> The maximum burn speed for the burner is 48x. This is the burn speed I
> created the first two disks with. I followed your advice on the third
> disk and burned it at 4x. The result was the same except this time
> instead of failing at 35% it failed near the end of the last fragment at
> 100%. All the other error messages showed when booting with this third
> disk also. I burned a fourth disk at 2x and got the same result as the
> third.

Which then suggests the iso file itself has errors.

--
Israel can do anything it wants to anyone it wants regardless how heinous or
how criminal because any criticism of Israel is antisemitic.
-- The Iron Webmaster, 3862
nizkor http://www.giwersworld.org/nizkook/nizkook.phtml
antisemitism http://www.giwersworld.org/antisem/ a1

On Fri, 21 Sep 2007 03:06:16 +0000, Stefan Patric wrote:

> FYI: You can
> verify the CD after you burned it without using the on-the-cd
> verification utility. Since in Linux everything is a file, this is what
> I do to verify a burn, if the burner software doesn't have the feature.
> With the newly burned CD in the drive, type in a terminal:
>
> sha1sum /dev/cdrom (or whatever you burner's device name is)

This only works if the disc was burned using DAO mode, not an option for
many modern distros.

Stefan Patric wrote:
....
> You may have a batch of bad media or ...
>
> I used to have a 52x CD burner and burned at 24x. I started getting bad
> burns no matter what speed I used. I bought "expensive" media thinking
> that the "bargain" media was the problem. The problem persisted no
> matter what I did. Turned out I have a flakey burner. Got a new one.
> Problem went away.
>
> Also, you verified the SHA1SUM of the downloaded file. FYI: You can
> verify the CD after you burned it without using the on-the-cd
> verification utility. Since in Linux everything is a file, this is what
> I do to verify a burn, if the burner software doesn't have the feature.
> With the newly burned CD in the drive, type in a terminal:
>
> sha1sum /dev/cdrom (or whatever you burner's device name is)
>
> This will print out the SHA1SUM. Compare it to the one for the ISO that
> was burned. If they match, it's a good burn, no matter what the on-cd
> verify says.
>
> This also works for any other of the checksum utilities, too.

In my experience burn failures are not of the bad byte type but of something
that simply makes it impossible to read a file. Thus simply copying it back to
the HD and watching for disk i/o error is sufficient. And for something like an
installation disk it will report which file(s) had the error(s) and if you are
not installing those files you don't care.

--
For two centuries Catholics in the US have struggled against the slander of
being loyal to the Vatican. Today millions of Americans proudly announce
their loyalty to Israel. Make of it what you will.
-- The Iron Webmaster, 3859
nizkor http://www.giwersworld.org/nizkook/nizkook.phtml
http://www.giwersworld.org