no device while mounting /dev/sr0 on cdrom

[sylviette]

Hello,

after having built a new iso with 4.2 version, starting (virtual or physical) machine I get mounting /dev/sr0 on /cdrom failed: no such device mounting /dev/sr1 on /cdrom failed: no such device errors and boot doesn't go on.

here's what I've done: loaded on customizer an "hand-tailored" iso (built on shell starting from downloaded standard 18.04 iso - budgie flavour - then mounting it, extracting it, "unsquashfs-ing" it, chrooting, ...) apt dist-upgraded it changed host and username in casper.conf update-initramfs -k all -u apt clean rebuilt iso

result: mounting /dev/sr0 on /cdrom failed: no such device at boot

Thinking it was due to my "hand-tailored" distro, I've tried with a brand new ubuntu-budgie 18.04 and redone every passage shown above.

result: mounting /dev/sr0 on /cdrom failed: no such device at boot

Thanks, Sil

UPDATE: thinking it could be ubuntu-budgie fault, I tried again with "standard" ubuntu and got the same issue.

[kamilion]

uhhh, I'm sorry, but customizer has nothing to do with the SCSI Reader 0 / 1 devices not responding.

Your information is insufficient for me to diagnose the problem with your initramfs failing to discover devices to mount.

Check the casper liveboot script settings for your initramfs build.

Feel free to stop by #kamikazi on the freenode IRC server network and ping me (Kamilion) to get some real-time help.

(Also, I'm totally unfamiliar with ubuntu-budgie -- what is it?)

[ghost]

(Also, I'm totally unfamiliar with ubuntu-budgie -- what is it?)

I think It's budgie desktop flavour of ubuntu https://ubuntubudgie.org/

[sylviette]

uhhh, I'm sorry, but customizer has nothing to do with the SCSI Reader 0 / 1 devices not responding.

Your information is insufficient for me to diagnose the problem with your initramfs failing to discover devices to mount.

Check the casper liveboot script settings for your initramfs build.

Feel free to stop by #kamikazi on the freenode IRC server network and ping me (Kamilion) to get some real-time help.

(Also, I'm totally unfamiliar with ubuntu-budgie -- what is it?)

Hello,

I think I have found the reason of above description behaviour (found, notice, not understood).

As I've told in UPDATE section of my first post, the issue happens with "standard" ubuntu too (btw, budgie is a "flavour" of ubuntu). I've tried to remaster the cd entirely by hand, i.e. by mounting, rsyncing, extracting, expanding quashfs, chrooting, customizing and back until cd remastering. I've got a little problem, due to my poor memory ;-) : after remastering, even if I' had changed /etc/casper.conf and given update-initramfs command, username and hostname remained unchanged, ubuntu/ubuntu (or ubuntu-budgie/ubuntu-budgie). Last week, starting with a fresh downloaded image, I've "noticed" (probably I woke up, finally ;-) ) that initrd dimensions and date were different in (chroot directory)/boot and in (ISO directory)/casper, so I got the decision to copy (chroot directory)/boot initrd into (ISO directory)/casper, replacing the old one ... Miracle! At boot username and hostname were thje ones I've written on /etc/casper.

Now we arrive to "mounting /dev/sr0 on /cdrom failed: no such device at boot" problem. Having given my distro a basic customization, I've mounted it, ..., chrooted, heavily customized, ... , remastered cd having care to copy again new (chroot directory)/boot initrd in place of old one in (ISO directory)/casper. Remastered and booted the image, "mounting /dev/sr0 on /cdrom failed: no such device at boot" issue again. So I've deleted everything, remounted ... etc etc the basically customized image, heavily customized it but this tima I had care NOT to copy new initrd in place of old one; once remastered the iso, the system went up w/o problems.

Hoping this sort of analysis help.

Sil

[hsd-dev]

I faced the same issue as well.

Ubuntu 18.04.2
kernel linux-image-4.18.0-15-generic

I tried this "fix" during boot and it worked! This link made me realize that the initrd's extension has changed since 16.04.5. So I removed the .lz extension here. Now I am able to boot fine. Hope that helps.

[johnfidel98]

I faced the same issue as well.

Ubuntu 18.04.2
kernel linux-image-4.18.0-15-generic

I tried this "fix" during boot and it worked! This link made me realize that the initrd's extension has changed since 16.04.5. So I removed the .lz extension here. Now I am able to boot fine. Hope that helps.

Fix worked tested with virtualbox

[tawfiknasser]

I faced the same issue as well.

Ubuntu 18.04.2
kernel linux-image-4.18.0-15-generic

I tried this "fix" during boot and it worked! This link made me realize that the initrd's extension has changed since 16.04.5. So I removed the .lz extension here. Now I am able to boot fine. Hope that helps.

I added .lz in boot option initrd=/casper/initrd and booted successfully. Thank you