Mandriva install hangs midway. Not sure if cd-r is bad or the drive. How to make out?

saivin · 11-24-2009, 11:02 PM

Hi,
I'm trying to install Mandriva One (GNOME) on my laptop (Dell Vostro 1400, standard configuration). The live installer is hanging at around middle of the progress bar. If we try to open another program/terminal etc the progress bar goes and a blank installer window stays on for ever.

I looked at dmesg and all I could makeout that it is complaining some i/o error, media error etc. Not sure if it is my cd (Sony CD-R) which is faulty or it is my cd-rom which is faulty. Pease note, I tried installing Fedora earlier but even it hangs mid-way. However it pops an error message saying Media error.

If the whole cd-rom bundle I bought is faulty its somewhat ok, but if my cd-rom drive itself has gone bad don't know what to do. Is there a way I can find out? Any command line tools etc.

Thanks in advance.

Code:

Linux version 2.6.31.5-desktop586-1mnb (herton@n2.mandriva.com) (gcc version 4.4.1 (GCC) ) #1 SMP Fri Oct 23 00:21:26 EDT 2009
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  NSC Geode by NSC
  Cyrix CyrixInstead
  Centaur CentaurHauls
  Transmeta GenuineTMx86
  Transmeta TransmetaCPU
  UMC UMC UMC UMC
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
 BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
 BIOS-e820: 0000000000100000 - 000000007f66d800 (usable)
 BIOS-e820: 000000007f66d800 - 0000000080000000 (reserved)
 BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
 BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
 BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
 BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
DMI 2.4 present.
last_pfn = 0x7f66d max_arch_pfn = 0x100000
MTRR default type: uncachable
.
.
.
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
SQUASHFS error: sb_bread failed reading block 0x7a920
SQUASHFS error: Unable to read fragment cache block [1e95021d]
SQUASHFS error: Unable to read page, block 1e95021d, size f81c5
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] ASC=0x10 <<vendor>> ASCQ=0x90
end_request: I/O error, dev sr0, sector 1026444
Buffer I/O error on device sr0, logical block 256611
Buffer I/O error on device sr0, logical block 256612

camorri · 11-25-2009, 08:46 AM

Did you do a md5sum check on the .iso file you downloaded?

How did you burn the CD, nice and slow with nothing else going on on the system at the time?

Is this known good media?

Most often these types of problems are bad burns, or bad downloads.

Can you try to boot another machine with the CD and see what happens? If it boots right up, then start to look at hardware.

If you need help with burning or md5sum checking, look here --> http://www.linuxquestions.org/linux/answers/LQ_ISO for help. Everything is explained.

alam · 11-25-2009, 09:21 AM

I had this happened several times (last time with mandriva 2010 in last week). All the time, I found either the DVD was old and corrupted or md5sum was wrong. This information is obvious, but I thought this might be useful.

I check the md5sum and then use the command:
cdrecord -v nameofdvd.iso
instead of using k3b or other software. I found some times the cd-writer probably caused a problem.

saivin · 11-25-2009, 10:21 AM

Thanks for the reply camorri and alam,
I make it a point to check for md5sum/sha(xxx)sum every time I have to burn an iso. So, that was ruled out(checked again anyway).

Could be a case of bad burning. I had kept everything on auto in k3b. But this time put speed at 16x and checked the 'verify data after burning' option. Now, Mandriva is installed. Guess same thing happened with my F12 iso too. (alam, even i like burning in commandline, but thought let me not get too geeky until the issue is isolated

)

I said 'could be' because, the same cd installed mandriva fine on my old desktop!

Anyway, I could install Mandriva and am enjoying it right now. What a solid release!

camorri · 11-25-2009, 12:04 PM

Glad you have had success.

ernie · 11-27-2009, 12:27 PM

As an after thought for others who may see this thread: It has been my experience that burning a disk at the rated capability of the disk will often result in a bad burn (I know not why). I never suffer from this problem because I listened to a more experienced Linux user early on, and set my burner software to burn the disk at a speed about one half the rated capability of the slower of either the burner or the disk. As an example, if I use a CD burner that supports 16x, and the disk is rated at 12x, I choose 6x (about 1/2 the slower of the two). Since I started using a DVD burner, I use only DVD media, so this is no longer an issue (my DVD burner supports only one burn speed). For tasks such as burning an install image, I use a DVD ∓ RW so the disk can be re-burned for the next new release (which happens two times a year). Rewritable disks are more expensive, but much easier on the local land fill than write-once disks.

HTH,