Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 75747

Summary: Absolute Newbie installing Gentoo Linux: i reached upto "tar -xvjpf /mnt/cdrom/stages/stage3-x86-2004.3.tar.bz2" following the installation handbook, command executes and then after a while, error message comes up (described in detail below)
Product: Gentoo Release Media Reporter: ajay <ajay_pm>
Component: EverythingAssignee: Gentoo LiveCD Package Maintainers <livecd>
Status: RESOLVED INVALID    
Severity: normal CC: stian, vapier
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description ajay 2004-12-26 20:23:16 UTC
I checked the md5 sum for the downloaded .iso file (install-x86-universal-2004.3-r1.iso) and it comes out OK.
I tried burning the same .iso file to 2 different cd-rw disks, still the same error came up.


Reproducible: Always
Steps to Reproduce:
1. I boot into gentoo kernel with the help of universal gentoo Live-CD (install-x86-universal-2004.3-r1.iso)

2. setup a user called "ajay" as part of "users" group and setup password for "ajay"

3. check for nic config and find that it is configured correctly automatically with the help of dhcp (by router).

4. use fdisk to partition disk (hda) as 
/dev/hda1 Linux, Bootable, Id:83
/dev/hda2 Linux Swap, Id:82
/dev/hda3 Linux, Id:83

exit from fdisk by pressing 'w'

5. mke2fs -j /dev/hda1
   mke2fs -j /dev/hda2
   mke2fs -j /dev/hda3

6. mkswap /dev/hda2
&  swapon /dev/hda2

7. # mount /dev/hda3 /mnt/gentoo
   # mkdir /mnt/gentoo/boot
   # mount /dev/hda1 /mnt/gentoo/boot

8. check date, which is correct except that i can't change TimeZone to EST instead of GMT

9. # cd /mnt/gentoo

10. # tar -xvjpf /mnt/cdrom/stages/stage3-x86-2004.3.tar.bz2


Actual Results:  
The "tar" command starts to execute , after a while the following message 
comes up repeatedly with different values for 'logical block' and 'sector' 
fields......

message which repeats is:
Buffer I/O Error on device hdc, logical block xxxxxxxx
hdc: media error (bad sector): status=0x51 {DriveReady SeekComplete Error)
hdc: media error (bad sector): error=0x30
ide: failed opcode was 100
end_request: I/O error, dev hdc, sector xxxxxxxxx

finally i got these few lines:

bzip2: I/O or other error, bailing out. Possible reason follows
bzip2: input/output error
       input file = (stdin), output file = (stdout)
tar: Read 1416 bytes from /mnt/cdrom/stages/stage3-x86-2004.3.tar.bz2
tar: unexpected EOF in archive
tar: unexpected EOF in archive
tar: Error is not recoverable, exiting now.

Expected Results:  
the tar process should have completed sucessfully , so that i could proceed 
with the installation process (which is installing Portage) and further on.

Unless my cd-writer drive(installed on a another machine, where i downloaded 
the .iso file, off the internet) is bad or there is something wrong/corrupt 
being written to my cd-rw disks i dont know why the error message comes up 
during gentoo linux installation. Or could it be that the cd-rom drive 
installed on the target system(the one on which i am trying to install gentoo 
linux) is bad ? its seems unlikely though.

the target system is a Celeron 533 Mhz, 152 MB RAM, SIS audio and video, D-
link DFE 530+ TX nic, serial (com1) port mouse, standard keyboard, 36X cd-rom 
drive, 1.44MB floppy drive system.
Comment 1 Stian Skjelstad 2004-12-26 20:29:16 UTC
Buffer I/O Error on device hdc, logical block xxxxxxxx
hdc: media error (bad sector): status=0x51 {DriveReady SeekComplete Error)
hdc: media error (bad sector): error=0x30
ide: failed opcode was 100
end_request: I/O error, dev hdc, sector xxxxxxxxx


You have a failty IDE disk og CDROM. Either way, the problem is defect hardware/media. If /dev/hdc is your cdrom-drive, try to burn a new cd, if it is your hard-drive, you should get a new one (The kernel will automatically disable DMA if there is communication errors, and not media errors).

I suggest to close this bug as invalid.
Comment 2 SpanKY gentoo-dev 2004-12-26 22:22:22 UTC
yep, the hardware is broken (probably bad burn)