clone causes 'missing operating system', is there a quick mbr fix
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
clone causes 'missing operating system', is there a quick mbr fix
Here's the deal. We have a simple image created by the system-restore-cd linux app. The device has NO cd, so it's on a usb stick. But in the past, I would boot off a DSL (damn small linux) distro on a usb stick, do the install (30 mins), then reboot off the system-restore cd and re-image.
Took a little but worked. Well someone re-used the dsl usb stick, so I booted off the system-restore. Fdisked the local drive, made it bootable and restored the image. That is all fine, I can mount, look around, etc, but on boot I just get "missing operating system".
Not sure why if I install the whole OS first, then wipe it and restore an image it works. I can only assume it's the master boot record? If so, is there a simple mbr command you can issue, or does someone else have .02 to throw out.
That's what I would have figured, maybe the partimage app doesn't do something it should, as I have seen it first hand. In the past, I would have to run the whole install from the damn small linux, just to reboot and re-do the image, so there is something, and w/o that other stick I am stuck.
As for the bootloader, I mounted the flash drive, and there is a /boot/grub folder. So I am guessing there using grub. The menu.1st file shows; (removing a lot of the comments)
default 0
timeout 1
# Enter the entry for DSL here. Something like this.
I did look and all things seem fine (there is a /boot/linux24 kernel), it really seems to be something with the partition or boot.
Any suggestions or thoughts are appreciated. I tried a simple grub-install /dev/sda1 and got;
Could not find device for /boot: Not found or not a block device.
Yea, that makes sense. I did make the partition first, (empty) so the restore copied everything it was supposed to. But it just didn't copy whatever hidden or however you want to word it 'things' to make it boot. In windows the old sys: command, or looking around and playing in the past, in windows you could syslinux -ma and that would work, not sure on a linux sustem how to say, make this bootable, but thanks for the link.
My new method is using clonezilla and it works great, but this device, I don't have any working one's to make a copy of, so I need this one to work to then image with clonezilla.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.