unbootable usb stick “Non-system disk or disk error”












0















All,



I have a USB stick that used to boot fine. I thought I'd reuse it. Reformatted it, copied some files over, and now it won't boot. I've used "lilo -M /dev/sdc mbr" with no luck. Note that the stick itself isn't busted, I can boot to it, but not from it but the computer refuses to like it as a boot device. Any idea what I broke, and how to fix it? As a backup it's usable so long as I boot it from a floppy, but I want it to boot directly like it used to. I erased everything off it in case the ext4 FS was somehow at fault (maybe the partition table or something), but no luck.



However, if I 'dd' an .iso image to the stick, it boots to that just fine. I can then use lilo to write to the stick and have it boot to anything (ignoring the .iso), and all is well, but if I then delete the .iso, it's back to 'Non-system disk'. So it seems the .iso file is somehow involved in/with the MBR. Nothing like this ever happens with HDDs that I'm aware of. My understanding is that the MBR is a world unto itself and if it is 1st stage lilo bootable then it cares nothing about any other file on the disk until the 2nd stage is reached. I use floppies like that all the time (MBR only, no files at all) to control my boot. I can just leave the .iso there of course, and use partitions on the rest of the stick, but that seems very inelegant.



Thoughts?










share|improve this question

























  • Make sure you mark a partition as active/boot as some stupid biosen refuse to load an MBR otherwise.

    – psusi
    Jan 26 '15 at 0:34
















0















All,



I have a USB stick that used to boot fine. I thought I'd reuse it. Reformatted it, copied some files over, and now it won't boot. I've used "lilo -M /dev/sdc mbr" with no luck. Note that the stick itself isn't busted, I can boot to it, but not from it but the computer refuses to like it as a boot device. Any idea what I broke, and how to fix it? As a backup it's usable so long as I boot it from a floppy, but I want it to boot directly like it used to. I erased everything off it in case the ext4 FS was somehow at fault (maybe the partition table or something), but no luck.



However, if I 'dd' an .iso image to the stick, it boots to that just fine. I can then use lilo to write to the stick and have it boot to anything (ignoring the .iso), and all is well, but if I then delete the .iso, it's back to 'Non-system disk'. So it seems the .iso file is somehow involved in/with the MBR. Nothing like this ever happens with HDDs that I'm aware of. My understanding is that the MBR is a world unto itself and if it is 1st stage lilo bootable then it cares nothing about any other file on the disk until the 2nd stage is reached. I use floppies like that all the time (MBR only, no files at all) to control my boot. I can just leave the .iso there of course, and use partitions on the rest of the stick, but that seems very inelegant.



Thoughts?










share|improve this question

























  • Make sure you mark a partition as active/boot as some stupid biosen refuse to load an MBR otherwise.

    – psusi
    Jan 26 '15 at 0:34














0












0








0








All,



I have a USB stick that used to boot fine. I thought I'd reuse it. Reformatted it, copied some files over, and now it won't boot. I've used "lilo -M /dev/sdc mbr" with no luck. Note that the stick itself isn't busted, I can boot to it, but not from it but the computer refuses to like it as a boot device. Any idea what I broke, and how to fix it? As a backup it's usable so long as I boot it from a floppy, but I want it to boot directly like it used to. I erased everything off it in case the ext4 FS was somehow at fault (maybe the partition table or something), but no luck.



However, if I 'dd' an .iso image to the stick, it boots to that just fine. I can then use lilo to write to the stick and have it boot to anything (ignoring the .iso), and all is well, but if I then delete the .iso, it's back to 'Non-system disk'. So it seems the .iso file is somehow involved in/with the MBR. Nothing like this ever happens with HDDs that I'm aware of. My understanding is that the MBR is a world unto itself and if it is 1st stage lilo bootable then it cares nothing about any other file on the disk until the 2nd stage is reached. I use floppies like that all the time (MBR only, no files at all) to control my boot. I can just leave the .iso there of course, and use partitions on the rest of the stick, but that seems very inelegant.



Thoughts?










share|improve this question
















All,



I have a USB stick that used to boot fine. I thought I'd reuse it. Reformatted it, copied some files over, and now it won't boot. I've used "lilo -M /dev/sdc mbr" with no luck. Note that the stick itself isn't busted, I can boot to it, but not from it but the computer refuses to like it as a boot device. Any idea what I broke, and how to fix it? As a backup it's usable so long as I boot it from a floppy, but I want it to boot directly like it used to. I erased everything off it in case the ext4 FS was somehow at fault (maybe the partition table or something), but no luck.



However, if I 'dd' an .iso image to the stick, it boots to that just fine. I can then use lilo to write to the stick and have it boot to anything (ignoring the .iso), and all is well, but if I then delete the .iso, it's back to 'Non-system disk'. So it seems the .iso file is somehow involved in/with the MBR. Nothing like this ever happens with HDDs that I'm aware of. My understanding is that the MBR is a world unto itself and if it is 1st stage lilo bootable then it cares nothing about any other file on the disk until the 2nd stage is reached. I use floppies like that all the time (MBR only, no files at all) to control my boot. I can just leave the .iso there of course, and use partitions on the rest of the stick, but that seems very inelegant.



Thoughts?







usb mbr lilo






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 25 '15 at 16:54







Ray Andrews

















asked Jan 25 '15 at 1:27









Ray AndrewsRay Andrews

7603826




7603826













  • Make sure you mark a partition as active/boot as some stupid biosen refuse to load an MBR otherwise.

    – psusi
    Jan 26 '15 at 0:34



















  • Make sure you mark a partition as active/boot as some stupid biosen refuse to load an MBR otherwise.

    – psusi
    Jan 26 '15 at 0:34

















Make sure you mark a partition as active/boot as some stupid biosen refuse to load an MBR otherwise.

– psusi
Jan 26 '15 at 0:34





Make sure you mark a partition as active/boot as some stupid biosen refuse to load an MBR otherwise.

– psusi
Jan 26 '15 at 0:34










1 Answer
1






active

oldest

votes


















1














Victory!



Thanks to psusi I now know that the boot flag must be set on the USB stick even though on a HDD this was never necessary (when using lilo). This is true even when only the MBR on the stick is being used (as with a floppy), and the map file is on another drive.






share|improve this answer


























  • Are you quite sure that you had a partition flagged as bootable before? If you install lilo to the MBR after, then extlinux is unused.

    – psusi
    Jan 26 '15 at 1:16











  • I would have thought so, but the computer throws 'Non-system disk' at me if extlinux isn't there, yet, as you say, lilo boots exactly as it would from a HDD, which is to say that it seems to ignore extlinux. I've done it several times: lilo alone: nope. install extlinux: lilo works. reinstall extlinux: lilo unchanged. Mind ... lilo never cared about the bootable flag itself ...

    – Ray Andrews
    Jan 26 '15 at 2:58











  • Right... LILO doesn't care about the boot flag.. but some bioses do... so if you didn't have it set prior to installing extlinux, and installing extlinux did set it, then that is what fixed it.

    – psusi
    Jan 26 '15 at 3:02











  • Tricky tho. I don't have the boot flag set on any of my HHDs and everything boots. extlinux w.o. boot flag didn't boot, (it didn't set it automaticaly), but when set, if the two extlinux files are not there, then no luck. I wonder if those files are needed by the BIOS itself somehow/

    – Ray Andrews
    Jan 26 '15 at 5:27











  • ... maybe the BIOS uses the boot flag to find those two files. Seems that way.

    – Ray Andrews
    Jan 26 '15 at 5:28











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f180917%2funbootable-usb-stick-non-system-disk-or-disk-error%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Victory!



Thanks to psusi I now know that the boot flag must be set on the USB stick even though on a HDD this was never necessary (when using lilo). This is true even when only the MBR on the stick is being used (as with a floppy), and the map file is on another drive.






share|improve this answer


























  • Are you quite sure that you had a partition flagged as bootable before? If you install lilo to the MBR after, then extlinux is unused.

    – psusi
    Jan 26 '15 at 1:16











  • I would have thought so, but the computer throws 'Non-system disk' at me if extlinux isn't there, yet, as you say, lilo boots exactly as it would from a HDD, which is to say that it seems to ignore extlinux. I've done it several times: lilo alone: nope. install extlinux: lilo works. reinstall extlinux: lilo unchanged. Mind ... lilo never cared about the bootable flag itself ...

    – Ray Andrews
    Jan 26 '15 at 2:58











  • Right... LILO doesn't care about the boot flag.. but some bioses do... so if you didn't have it set prior to installing extlinux, and installing extlinux did set it, then that is what fixed it.

    – psusi
    Jan 26 '15 at 3:02











  • Tricky tho. I don't have the boot flag set on any of my HHDs and everything boots. extlinux w.o. boot flag didn't boot, (it didn't set it automaticaly), but when set, if the two extlinux files are not there, then no luck. I wonder if those files are needed by the BIOS itself somehow/

    – Ray Andrews
    Jan 26 '15 at 5:27











  • ... maybe the BIOS uses the boot flag to find those two files. Seems that way.

    – Ray Andrews
    Jan 26 '15 at 5:28
















1














Victory!



Thanks to psusi I now know that the boot flag must be set on the USB stick even though on a HDD this was never necessary (when using lilo). This is true even when only the MBR on the stick is being used (as with a floppy), and the map file is on another drive.






share|improve this answer


























  • Are you quite sure that you had a partition flagged as bootable before? If you install lilo to the MBR after, then extlinux is unused.

    – psusi
    Jan 26 '15 at 1:16











  • I would have thought so, but the computer throws 'Non-system disk' at me if extlinux isn't there, yet, as you say, lilo boots exactly as it would from a HDD, which is to say that it seems to ignore extlinux. I've done it several times: lilo alone: nope. install extlinux: lilo works. reinstall extlinux: lilo unchanged. Mind ... lilo never cared about the bootable flag itself ...

    – Ray Andrews
    Jan 26 '15 at 2:58











  • Right... LILO doesn't care about the boot flag.. but some bioses do... so if you didn't have it set prior to installing extlinux, and installing extlinux did set it, then that is what fixed it.

    – psusi
    Jan 26 '15 at 3:02











  • Tricky tho. I don't have the boot flag set on any of my HHDs and everything boots. extlinux w.o. boot flag didn't boot, (it didn't set it automaticaly), but when set, if the two extlinux files are not there, then no luck. I wonder if those files are needed by the BIOS itself somehow/

    – Ray Andrews
    Jan 26 '15 at 5:27











  • ... maybe the BIOS uses the boot flag to find those two files. Seems that way.

    – Ray Andrews
    Jan 26 '15 at 5:28














1












1








1







Victory!



Thanks to psusi I now know that the boot flag must be set on the USB stick even though on a HDD this was never necessary (when using lilo). This is true even when only the MBR on the stick is being used (as with a floppy), and the map file is on another drive.






share|improve this answer















Victory!



Thanks to psusi I now know that the boot flag must be set on the USB stick even though on a HDD this was never necessary (when using lilo). This is true even when only the MBR on the stick is being used (as with a floppy), and the map file is on another drive.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 26 '15 at 16:22

























answered Jan 26 '15 at 0:47









Ray AndrewsRay Andrews

7603826




7603826













  • Are you quite sure that you had a partition flagged as bootable before? If you install lilo to the MBR after, then extlinux is unused.

    – psusi
    Jan 26 '15 at 1:16











  • I would have thought so, but the computer throws 'Non-system disk' at me if extlinux isn't there, yet, as you say, lilo boots exactly as it would from a HDD, which is to say that it seems to ignore extlinux. I've done it several times: lilo alone: nope. install extlinux: lilo works. reinstall extlinux: lilo unchanged. Mind ... lilo never cared about the bootable flag itself ...

    – Ray Andrews
    Jan 26 '15 at 2:58











  • Right... LILO doesn't care about the boot flag.. but some bioses do... so if you didn't have it set prior to installing extlinux, and installing extlinux did set it, then that is what fixed it.

    – psusi
    Jan 26 '15 at 3:02











  • Tricky tho. I don't have the boot flag set on any of my HHDs and everything boots. extlinux w.o. boot flag didn't boot, (it didn't set it automaticaly), but when set, if the two extlinux files are not there, then no luck. I wonder if those files are needed by the BIOS itself somehow/

    – Ray Andrews
    Jan 26 '15 at 5:27











  • ... maybe the BIOS uses the boot flag to find those two files. Seems that way.

    – Ray Andrews
    Jan 26 '15 at 5:28



















  • Are you quite sure that you had a partition flagged as bootable before? If you install lilo to the MBR after, then extlinux is unused.

    – psusi
    Jan 26 '15 at 1:16











  • I would have thought so, but the computer throws 'Non-system disk' at me if extlinux isn't there, yet, as you say, lilo boots exactly as it would from a HDD, which is to say that it seems to ignore extlinux. I've done it several times: lilo alone: nope. install extlinux: lilo works. reinstall extlinux: lilo unchanged. Mind ... lilo never cared about the bootable flag itself ...

    – Ray Andrews
    Jan 26 '15 at 2:58











  • Right... LILO doesn't care about the boot flag.. but some bioses do... so if you didn't have it set prior to installing extlinux, and installing extlinux did set it, then that is what fixed it.

    – psusi
    Jan 26 '15 at 3:02











  • Tricky tho. I don't have the boot flag set on any of my HHDs and everything boots. extlinux w.o. boot flag didn't boot, (it didn't set it automaticaly), but when set, if the two extlinux files are not there, then no luck. I wonder if those files are needed by the BIOS itself somehow/

    – Ray Andrews
    Jan 26 '15 at 5:27











  • ... maybe the BIOS uses the boot flag to find those two files. Seems that way.

    – Ray Andrews
    Jan 26 '15 at 5:28

















Are you quite sure that you had a partition flagged as bootable before? If you install lilo to the MBR after, then extlinux is unused.

– psusi
Jan 26 '15 at 1:16





Are you quite sure that you had a partition flagged as bootable before? If you install lilo to the MBR after, then extlinux is unused.

– psusi
Jan 26 '15 at 1:16













I would have thought so, but the computer throws 'Non-system disk' at me if extlinux isn't there, yet, as you say, lilo boots exactly as it would from a HDD, which is to say that it seems to ignore extlinux. I've done it several times: lilo alone: nope. install extlinux: lilo works. reinstall extlinux: lilo unchanged. Mind ... lilo never cared about the bootable flag itself ...

– Ray Andrews
Jan 26 '15 at 2:58





I would have thought so, but the computer throws 'Non-system disk' at me if extlinux isn't there, yet, as you say, lilo boots exactly as it would from a HDD, which is to say that it seems to ignore extlinux. I've done it several times: lilo alone: nope. install extlinux: lilo works. reinstall extlinux: lilo unchanged. Mind ... lilo never cared about the bootable flag itself ...

– Ray Andrews
Jan 26 '15 at 2:58













Right... LILO doesn't care about the boot flag.. but some bioses do... so if you didn't have it set prior to installing extlinux, and installing extlinux did set it, then that is what fixed it.

– psusi
Jan 26 '15 at 3:02





Right... LILO doesn't care about the boot flag.. but some bioses do... so if you didn't have it set prior to installing extlinux, and installing extlinux did set it, then that is what fixed it.

– psusi
Jan 26 '15 at 3:02













Tricky tho. I don't have the boot flag set on any of my HHDs and everything boots. extlinux w.o. boot flag didn't boot, (it didn't set it automaticaly), but when set, if the two extlinux files are not there, then no luck. I wonder if those files are needed by the BIOS itself somehow/

– Ray Andrews
Jan 26 '15 at 5:27





Tricky tho. I don't have the boot flag set on any of my HHDs and everything boots. extlinux w.o. boot flag didn't boot, (it didn't set it automaticaly), but when set, if the two extlinux files are not there, then no luck. I wonder if those files are needed by the BIOS itself somehow/

– Ray Andrews
Jan 26 '15 at 5:27













... maybe the BIOS uses the boot flag to find those two files. Seems that way.

– Ray Andrews
Jan 26 '15 at 5:28





... maybe the BIOS uses the boot flag to find those two files. Seems that way.

– Ray Andrews
Jan 26 '15 at 5:28


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f180917%2funbootable-usb-stick-non-system-disk-or-disk-error%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

Is this a new Fibonacci Identity?

19世紀