Initrd should check scd0

[John McCabe-Dansted]

Binary package hint: casper

Linux sometimes puts the cdrom device at /dev/scd0, but according to /casper.log the initrd for the 7.10 LiveCD has only checked for a cdrom at sr0. I hit this when attempting to boot a custom livecd built according to the instructions at
http://www.atworkonline.it/~bibe/ubuntu/custom-livecd.htm

This appears to be related to Bug #143958.

ProblemType: Bug
Architecture: i386
Date: Wed Feb 27 18:40:40 2008
Dependencies:

DistroRelease: Ubuntu 7.10
NonfreeKernelModules: cdrom
Package: casper None [modified: /var/lib/dpkg/info/casper.list]
PackageArchitecture: i386
SourcePackage: casper
Uname: Linux ubuntu-xp 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

[Colin Watson (cjwatson)]

Bug 143958 is unrelated.

Could you please post casper.log? sr* isn't actually hardcoded, so I wonder what it's thinking.

[Colin Watson (cjwatson)]

I wonder if we need /etc/udev/rules.d/30-cdrom_id.rules in casper's initrd?

[Scott James Remnant (Canonical) (canonical-scott)]

That only makes the type of the CD drive available in the uevent environment and udevdb, the only use in the default rules is assigning the cdrom group -- not relevant in the initrd (or the real system initramfs)

For various reasons (mostly because devices.txt tells us to), we rename all SCSI CD-ROM devices from sr[0-9]* to scd%n (ie. sr0 becomes scd0, sr1 becomes scd1) -- so it should not be possible for any sr[0-9]* devices to exist in the LiveCD initrd; casper shouldn't check for them?

(Note if it's checking under sysfs that's ok, the kernel node name is still sr0, but it has to remember to translate that to scd0)

In the full system, we add sr0 compatibility symlinks (60-symlinks.rules) -- adding this to the casper initrd might help? (or just fixing casper <g>)

[welgin (wayne-elgin)]

I just discovered this problem yesterday while trying out Heron's LTS Client (8.04). I wasn't knowledgeable enough to dump info from BusyBox, but I saw a number of sr0 errors pop up, when I turned off the splash and quiet options. I might be able to post some info later tonight, if I can get the syntax correct. I see also that this has been happening in one form or another since at least Feb 2007.

Is there something I can try to get the install to happen?

[Brian Murray (brian-murray)]

A casper.log file was never provided for this issue so I am setting it to incomplete.

[Launchpad Janitor (janitor)]

[Expired for casper (Ubuntu) because there has been no activity for 60 days.]