FAILURE - READ_BIG

[Jerry McAllister]

On Fri, Mar 06, 2009 at 08:55:18AM +0200, Andrei Kolu wrote:

> Carl Chave wrote:
> >Have you tried re-burning with a different (higher quality) cd blank and 
> >see
> >if that makes a difference?
> >
> >Alternatively you could get the network boot ISO and forgo using the CD
> >altogether.
> >

Well, I don't seem to have any difficulty reading the CD.  
It is while doing the boot from CD - after reading it, that the
error shows up.

////jerry


> >
> >  
> I'd suggest to use CD/DVD-RW media- usually those tend to be a much 
> better quality then plain CD/DVD-R disks. I presume that FreeBSD is more 
> vocal about usual hardware error messages than Linux or Windows- they 
> just don't show you anything unpleasant- that can make false presumption 
> that those operating systems are more hardware compatible.
> 
> Yes, you can ignore this message. Read more here: 
> http://en.wikipedia.org/wiki/Reed-Solomon_error_correction
> >On 3/5/09, Jerry <jerrymc at msu.edu> wrote:
> >  
> >>Hello,
> >>
> >>I don't know if it is appropriate to post this here, but I am wondering
> >>if any pr has been done on this.  I tried to do some searching, but
> >>only found some stuff in questions indicating a number of people
> >>seeing the same thing, but only one person suggesting anything and
> >>that didn't produce any different response.  The error message
> >>still came up.
> >>
> >>Several posters sseem to report hangs while reading the CD during
> >>an install when the error appears.
> >>
> >>I burned a 7.1 i386 ISO and booted it to do an install, intending to
> >>wipe previous stuff and do a clean install.    During the boot, I get
> >>
> >>acd0 FAILURE - READ_BIG MEDIUM ERROR  asc=0x11 ascq=0x05
> >>
> >>The message is repeated a couple of lines later with different
> >>numbers on the asc= and ascq=
> >>
> >>Someone suggested ignoring it.
> >>
> >>One responder suggested doing:
> >>
> >>'enter the bootloader prompt (6) & type
> >>
> >>set hw.ata.atapi_dma=0
> >>boot
> >>
> >>I have tried this, but gotten the same error messages.
> >>
> >>I am reluctant to wipe stuff and start trying to write new stuff if
> >>things are going to fail in the middle even though I have backups.
> >>I depend on this system for a lot of communication.
> >>
> >>Has this been reported - and I just haven't been effective on my search?
> >>Is there some resolution or work around that works?
> >>
> >>Thank you for any help you can give,
> >>
> >>////jerry
> >>
> >>_______________________________________________
> >>freebsd-bugs at freebsd.org mailing list
> >>http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
> >>To unsubscribe, send any mail to "freebsd-bugs-unsubscribe at freebsd.org"
> >>
> >>    
> >_______________________________________________
> >freebsd-bugs at freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
> >To unsubscribe, send any mail to "freebsd-bugs-unsubscribe at freebsd.org"
> >  
> 
> _______________________________________________
> freebsd-bugs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
> To unsubscribe, send any mail to "freebsd-bugs-unsubscribe at freebsd.org"