Feisty LiveCD: Unable to find a medium containing a live file system

[TJ]

Binary package hint: linux-source-2.6.20

I have been attempting to boot Feisty 32-bit LiveCD on Dell PowerEdge 6300/550 with 4 Xeon CPUs and several SCSI controllers including a PERC-II RAID-5 array, and Adaptec controllers for Tape drive and CD-ROM.

Boot from CD fails during initrd and it drops to the BusyBox prompt. There are several messages during the lead-up to this point reporting I/O errors on fd0.

Within BusyBox I checked the devices and found:

/dev/sda1,2,3 = the RAID-5 array with three partitions
/dev/sdb1 = a standard SCSI hard disk
/dev/scd0 = the CD-ROM drive

I could mount the CD-ROM using "mount -t iso9660 /dev/scd0 /cdrom" so I was sure the drive was okay.

Eventually in /casper.log I discovered:

/init: /init: 1: cannot open /dev/fd0: No such device or address
mount: Mounting /dev/sda2 on /cdrom failed: No such device
mount: Mounting /dev/sda3 on /cdrom failed: No such device
mount: Mounting /dev/sdb1 on /cdrom failed: No such device
Unable to find a medium containing a live file system

I tried editing the kernel command line before booting to include "root=/dev/scd0 rootdelay=30" (the delay to get past the fd0 errors) but neither option seems to have any positive effect.

So, on this PowerEdge 6300 Feisty won't boot from the CD.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[TJ (tj)]

Ridiculous response! The report states that it isn't possible to boot Linux in order to have access to the tools required to run those reports!

And, as it is explicitly the 'Feisty 32.bit LiveCD' it's pretty obvious it equates to 2.6.20-15 generic. Xeon CPUs should give a clue as to the architecture - i386.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Sorry, I posted in the wrong bug report, had a few opened and picked the wrong one. I think it was not necessary to react so violently, everybody can make a mistake.

[Mackenzie Morgan (maco.m)]

Did you try the "check CD for defects"?

[TJ (tj)]

Indeed - I spent several hours trying to determine and fix the issue. Not being able to use the Alternate installer, I gave up on it.

The problem seemed to be in the initrd trying to mount the hard drives on the /cdrom mount-point:

mount: Mounting /dev/sda2 on /cdrom failed: No such device
mount: Mounting /dev/sda3 on /cdrom failed: No such device
mount: Mounting /dev/sdb1 on /cdrom failed: No such device

but ignoring /dev/scd0.

[Leann Ogasawara (leannogasawara)]

Hi TJ,

Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, I'm wondering if you can still reproduce this issue on the new release? Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download ? Please report back your results, we'd really appreciate it. Thanks!

[TJ (tj)]

I think the issue was caused by bug #143958 that Colin and I solved earlier in the Gutsy development cycle. A similar issue occurred on a laptop using the Alternate installer. I'll try to test this out on a server over the next few days.

[Leann Ogasawara (leannogasawara)]

Hi TJ,

I'm going to go ahead and mark this "Fix Released" against Gutsy. Obviously, feel free to reopen if this is not the case. I'm also going to close the 2.6.20 task. Thanks.

[Martin Samesch (ubuntu-theraphosidae)]

The problem still exists.

Boot process halts with the message from the subject.

I'm using a Toshiba SD-M1711 (/dev/scd0).

Which information do you need?

Cheers,
Martin

[Martin Samesch (ubuntu-theraphosidae)]

me again..

This bug still exists in Hardy beta (desktop i386) so maybe linux-source-2.6.20 isn't the appropriate place for my report. ;-)

Cheers,
Martin

[Bernhard Ernst (bkernst)]

The bug still exists in Ubuntu Desktop i386 32 bit on 10.04.1. This is on a Pentium 3 processor. Repeatable every time.

[Maxim Mai (maxim-sl-mai)]

I confirm that this bug still exists in Ubuntu Desktop amd64 on 10.10.

I have also tried the following versions:

Ubuntu i386 32bit 10.10
Ubuntu amd64 10.10
Ubuntu amd64 10.04

They all report the "no file system" error.

My hardware specs are

CPU: AMD Phenom II 1090T Six-Core
RAM: 8 GB PC3-10600 DDR3 SDRAM (4 x 2GB)
Video Card: ATI Radeon HD 5770
Storages:
1. 64GB SSD
2. 1TB HDD
3. 2TB HDD

Maxim - <email address hidden>