USB CD-ROM fails to mount during install

Bug #14980 reported by Joe Harrington
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
High
Fabio Massimo Di Nitto

Bug Description

I just tried to install the hoary RC dated 2005-03-30 02:49. My config:
AMD64, 1 HDD as PATA secondary master, no other PATA devices, USB CD (Sony
DRX-500ULX), USB keyboard and mouse, no ATAPI CD, no floppy, SATA onboard but no
drives connected. Same behavior whether or not SATA is disabled in BIOS.

It fails to load ide-{mod,probe-mod,detect,floppy}. It does load usb-storage.
I understand this is normal.

The install goes through language and keyboard selection fine, but can't mount
the CD it just booted from. There is a device file that gets created and
destroyed when I plug/unplug the USB cable to the CD. Ditto for my thumb drive.

When I go to VC2 and type:

mkdir /tmp/foo
mount -r /dev/cdroms/cdrom0 /tmp/foo
It says:
mount: Mounting /dev/cdroms/cdrom0 on /tmp/foo failed: Invalid argument

There's nothing new on VC4 when I do that. It also won't mount my thumb drive,
same error. Both drives mount under FC3, so I know they're fine.

When I tell the installer screen on VC1 to try mounting it again, the error on
VC4 is:
Apr 4 19:40:52 cdrom-detect: CDROM-mount failed (error=1):
device=/dev/cdroms/cdrom0
It does that twice, with the usual messages about retrying, unmounting, and
giving up.

I tried mounting the device file that the cdrom0 link points to directly, same
"Invalid argument" error. Ditto for the thumb drive.

--jh--

Revision history for this message
Matt Zimmerman (mdz) wrote :

Please attach the output from 'dmesg' after reproducing the problem

Revision history for this message
Joe Harrington (joeharr) wrote :

I just got the same result with the 2005-04-04 daily install CD.

(Which, if you followed the conversation that started at the end of bug 8196, I
have now managed to download correctly.)

When I try to mount the cd-rom without -r, it tells me the device is
write-protected and that it is mounting read-only, 3 times. Then it gives the
invalid argument error. Likewise, for the thumb drive, the light on the thumb
drive flashes when I issue the mount command. So, both drives are being talked
to, and at least some of the data from the CD are being interpreted correctly.
Adding -t iso9660 to the CD mount command doesn't help.

Because of the above, I have no way of transferring the output of dmesg off of
the affected machine. Here's what's new in dmesg when I

mkdir /mnt
mount /dev/cdroms/cdrom0 /mnt

VFS: Can't find an ext2 filesystem on dev sr0.
cramfs: wrong magic
attempt to access beyond end of device
sr0: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, blk=16

If you can tell me how to start the network and get a server or client
program to talk to the net, I can transfer the whole dmesg output off.
Likewise, if you can tell me how to partition the hard disk that's
there, it might mount. I couldn't find fdisk on the boot image (no surprise).

--jh--

Revision history for this message
Matt Zimmerman (mdz) wrote :

The kernel believes that the disc only contains 4 blocks of data. This could be
due to a problem with the CD-R media. If you remove the CD-R and insert a
pressed CD (such as an official Ubuntu 4.10 disc), are you able to mount and
read that, or do you see the same problem?

Revision history for this message
Joe Harrington (joeharr) wrote :

Well, that's embarrassing. It mounts all the other disks I have tried,
including some dvds, some pressed disks, and some other cds from the same batch.
 Sadly, it's not the media, it turns out to be the cd burner in my laptop.
Another disk from the same batch of cds worked fine when burned in another
burner, and three cds from that batch all failed in the same way when burned on
the laptop's burner.

Sorry to have bothered everyone with my error.

--jh--

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.