Unable to boot 2.6.24.14 or newer kernels with SCSI cd changer attached
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unable to boot 2.6.24.14 or newer kernels with SCSI cd changer attached
I have a 200-disc SCSI-attached CD changer that I'd like to make use of, and I'm currently running Ubuntu 8.10 (Intrepid Ibex). However, ever since upgrading from kernel 2.6.22.14-generic to kernel 2.6.24.14-generic (and all subsequent kernels) the boot process hangs and drops out to initramfs/busybox while the CD changer initializes itself (i.e. it checks all 200 element slots for discs).
After around 7 minutes, I get a message that ch0 has finished and that a SCSI disk is attached. However, I'm stuck in initramfs.
I increased the root timeout value to 10 minutes and the system will boot, but what then happens is I get numerous error messages from within Gnome that I can't mount the audio disc (which is is in the changer for testing).
I'm at a loss as to how best to diagnose and resolve the situation. Any help or suggestions would be very much appreciated!
The error I get is:
Code:
Begin: Waiting for root file system... ...
Done.
Check root= bootarg cat /proc/cmdline
or missing modules, devices: cat /proc/modules ls /dv
ALERT! /dev/disk/by-uuid/5767f0bf-9340-4c3a-9e2b-7afe3b1114e5 does not exist. Dropping to a shell.
The (truncated) dmesg output from the running 2.6.22-14-generic boot is:
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
Suggest : Go back to the kernel, that worked.
Changing the kernel is not always an upgrade, just a change.
A newer kernel often has new features ( some, you don't need ),
while other functions can be broken until a later version.
Bare in mind that just released versions of "Linux Enterprise"
are using e.g. kernel-2.6.18 to use the safest around.
.....
Changing the kernel is not always an upgrade, just a change.
A newer kernel often has new features ( some, you don't need ),
while other functions can be broken until a later version.
Bare in mind that just released versions of "Linux Enterprise"
are using e.g. kernel-2.6.18 to use the safest around.
.....
Knudfl: Thank you very much for your advice, and I'm thinking that may be the only option. However, I'm also thinking it may be a bit selfish on my part: if there's a chance to squash a bug that possibly affects others, I should dig into it to report back to the maintainers. Also, it might be a great chance to learn more about my system and Linux in general! I just wish I had a better idea as to how to approach debugging the problem.
"Probe all LUNs on each SCSI device"
If you have a SCSI device that supports more than one LUN (Logical Unit Number), e.g. a CD jukebox, and only one LUN is detected, you can say Y here to force the SCSI driver to probe for multiple LUNs. The vast majority of SCSI devices only have one LUN, and so most people can say N here. The max_luns boot/module parameter allows to override this setting.
May or may not be it. I suggest looking into that parameter, seeing if you can find the configs for the old and new kernel and compare them to see the differences which may have triggered your problem, and trying to configure your own kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.