Custom ISO not booting on Flash Drive

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












I've developed a custom minimal ubuntu distribution (there is a specific reason for this) which I've been able to successfully boot inside of a VM and burn to a CD. However, when I try to use unetbootin (or rufus, or dd, or most anything else) it fails miserably. I get two specific errors



stdin: not a typewriter

/init: line3: can't open /dev/sr0: No medium found


This ISO was built using casper and squashfs if that helps in anyway.
I've tried setting the live-media-path=/casper/ but that doesn't seem to help that much. I've tried using isohybrid but that doesn't make a difference either.



Does anyone have a pointer or idea that can help? Is there any additional information that I can provide?



Thanks,
Chris










share|improve this question



















  • 1




    Did you create the custom iso file inside an VM? In that case, maybe it is relying on some virtual driver, that belongs to that particular virtual machine (and the software creating it).
    – sudodus
    Mar 22 at 7:58










  • The ISO was created on a bare metal host. However, I may have built the kernel and initrd inside of a chroot container. I'll double check that as that may be causing problems. I'll update after I run some tests. Thanks for the idea.
    – Chris Rapier
    Mar 22 at 10:20






  • 1




    Sudodus, I have to say that you are a steely eyed missile man. This ended up being the problem. Building the kernel and initrd in the chroot was mucking everything. When I replaced them with kernels built outside of chroot it worked fine. Thank yo so much for the insight.
    – Chris Rapier
    Mar 22 at 10:50










  • I am glad that I could help you find a solution. Thanks for sharing your solution :-)
    – sudodus
    Mar 22 at 12:31














up vote
2
down vote

favorite












I've developed a custom minimal ubuntu distribution (there is a specific reason for this) which I've been able to successfully boot inside of a VM and burn to a CD. However, when I try to use unetbootin (or rufus, or dd, or most anything else) it fails miserably. I get two specific errors



stdin: not a typewriter

/init: line3: can't open /dev/sr0: No medium found


This ISO was built using casper and squashfs if that helps in anyway.
I've tried setting the live-media-path=/casper/ but that doesn't seem to help that much. I've tried using isohybrid but that doesn't make a difference either.



Does anyone have a pointer or idea that can help? Is there any additional information that I can provide?



Thanks,
Chris










share|improve this question



















  • 1




    Did you create the custom iso file inside an VM? In that case, maybe it is relying on some virtual driver, that belongs to that particular virtual machine (and the software creating it).
    – sudodus
    Mar 22 at 7:58










  • The ISO was created on a bare metal host. However, I may have built the kernel and initrd inside of a chroot container. I'll double check that as that may be causing problems. I'll update after I run some tests. Thanks for the idea.
    – Chris Rapier
    Mar 22 at 10:20






  • 1




    Sudodus, I have to say that you are a steely eyed missile man. This ended up being the problem. Building the kernel and initrd in the chroot was mucking everything. When I replaced them with kernels built outside of chroot it worked fine. Thank yo so much for the insight.
    – Chris Rapier
    Mar 22 at 10:50










  • I am glad that I could help you find a solution. Thanks for sharing your solution :-)
    – sudodus
    Mar 22 at 12:31












up vote
2
down vote

favorite









up vote
2
down vote

favorite











I've developed a custom minimal ubuntu distribution (there is a specific reason for this) which I've been able to successfully boot inside of a VM and burn to a CD. However, when I try to use unetbootin (or rufus, or dd, or most anything else) it fails miserably. I get two specific errors



stdin: not a typewriter

/init: line3: can't open /dev/sr0: No medium found


This ISO was built using casper and squashfs if that helps in anyway.
I've tried setting the live-media-path=/casper/ but that doesn't seem to help that much. I've tried using isohybrid but that doesn't make a difference either.



Does anyone have a pointer or idea that can help? Is there any additional information that I can provide?



Thanks,
Chris










share|improve this question















I've developed a custom minimal ubuntu distribution (there is a specific reason for this) which I've been able to successfully boot inside of a VM and burn to a CD. However, when I try to use unetbootin (or rufus, or dd, or most anything else) it fails miserably. I get two specific errors



stdin: not a typewriter

/init: line3: can't open /dev/sr0: No medium found


This ISO was built using casper and squashfs if that helps in anyway.
I've tried setting the live-media-path=/casper/ but that doesn't seem to help that much. I've tried using isohybrid but that doesn't make a difference either.



Does anyone have a pointer or idea that can help? Is there any additional information that I can provide?



Thanks,
Chris







live-usb iso






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 22 at 7:54









stumblebee

2,3083922




2,3083922










asked Mar 21 at 21:55









Chris Rapier

1111




1111







  • 1




    Did you create the custom iso file inside an VM? In that case, maybe it is relying on some virtual driver, that belongs to that particular virtual machine (and the software creating it).
    – sudodus
    Mar 22 at 7:58










  • The ISO was created on a bare metal host. However, I may have built the kernel and initrd inside of a chroot container. I'll double check that as that may be causing problems. I'll update after I run some tests. Thanks for the idea.
    – Chris Rapier
    Mar 22 at 10:20






  • 1




    Sudodus, I have to say that you are a steely eyed missile man. This ended up being the problem. Building the kernel and initrd in the chroot was mucking everything. When I replaced them with kernels built outside of chroot it worked fine. Thank yo so much for the insight.
    – Chris Rapier
    Mar 22 at 10:50










  • I am glad that I could help you find a solution. Thanks for sharing your solution :-)
    – sudodus
    Mar 22 at 12:31












  • 1




    Did you create the custom iso file inside an VM? In that case, maybe it is relying on some virtual driver, that belongs to that particular virtual machine (and the software creating it).
    – sudodus
    Mar 22 at 7:58










  • The ISO was created on a bare metal host. However, I may have built the kernel and initrd inside of a chroot container. I'll double check that as that may be causing problems. I'll update after I run some tests. Thanks for the idea.
    – Chris Rapier
    Mar 22 at 10:20






  • 1




    Sudodus, I have to say that you are a steely eyed missile man. This ended up being the problem. Building the kernel and initrd in the chroot was mucking everything. When I replaced them with kernels built outside of chroot it worked fine. Thank yo so much for the insight.
    – Chris Rapier
    Mar 22 at 10:50










  • I am glad that I could help you find a solution. Thanks for sharing your solution :-)
    – sudodus
    Mar 22 at 12:31







1




1




Did you create the custom iso file inside an VM? In that case, maybe it is relying on some virtual driver, that belongs to that particular virtual machine (and the software creating it).
– sudodus
Mar 22 at 7:58




Did you create the custom iso file inside an VM? In that case, maybe it is relying on some virtual driver, that belongs to that particular virtual machine (and the software creating it).
– sudodus
Mar 22 at 7:58












The ISO was created on a bare metal host. However, I may have built the kernel and initrd inside of a chroot container. I'll double check that as that may be causing problems. I'll update after I run some tests. Thanks for the idea.
– Chris Rapier
Mar 22 at 10:20




The ISO was created on a bare metal host. However, I may have built the kernel and initrd inside of a chroot container. I'll double check that as that may be causing problems. I'll update after I run some tests. Thanks for the idea.
– Chris Rapier
Mar 22 at 10:20




1




1




Sudodus, I have to say that you are a steely eyed missile man. This ended up being the problem. Building the kernel and initrd in the chroot was mucking everything. When I replaced them with kernels built outside of chroot it worked fine. Thank yo so much for the insight.
– Chris Rapier
Mar 22 at 10:50




Sudodus, I have to say that you are a steely eyed missile man. This ended up being the problem. Building the kernel and initrd in the chroot was mucking everything. When I replaced them with kernels built outside of chroot it worked fine. Thank yo so much for the insight.
– Chris Rapier
Mar 22 at 10:50












I am glad that I could help you find a solution. Thanks for sharing your solution :-)
– sudodus
Mar 22 at 12:31




I am glad that I could help you find a solution. Thanks for sharing your solution :-)
– sudodus
Mar 22 at 12:31















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1018075%2fcustom-iso-not-booting-on-flash-drive%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1018075%2fcustom-iso-not-booting-on-flash-drive%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491