Hello, I made a bit of mistake that I cannot appear to get out of. I modified my /etc/default/grub file to include the 1920x1200 resolution as I described previously. I have another disk in my computer, and an opensuse USB disk. When I performed my grub2-mkconfig it captured these two system also. Now if I unplug my USB drive, the system gets messed up and will not respond to commands. What commands can give grub2-mkconfig so that it will ignore the USB and other drive? It may think that that the USB is my primary system, though when during boot I f2 and the tell it to boot from the hard drive the same things happen. There must be something short of a system reinstall. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/16/2015 10:27 PM, don fisher wrote:
Hello,
I made a bit of mistake that I cannot appear to get out of. I modified my /etc/default/grub file to include the 1920x1200 resolution as I described previously. I have another disk in my computer, and an opensuse USB disk. When I performed my grub2-mkconfig it captured these two system also. Now if I unplug my USB drive, the system gets messed up and will not respond to commands. What commands can give grub2-mkconfig so that it will ignore the USB and other drive? It may think that that the USB is my primary system, though when during boot I f2 and the tell it to boot from the hard drive the same things happen. There must be something short of a system reinstall.
There is. If you read the man page for initrd you'll see that you can specify, for example, the root (the logical "/"") to use; where to put the resulting initrd (the logical "/boot"); also -B Don't run the update-bootloader(8) script after the initrd(s) have been created. This is useful if you call mkinitrd(8) not for the running system -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Thu, 16 Apr 2015 19:27:25 -0700 don fisher <hdf3@comcast.net> пишет:
Hello,
I made a bit of mistake that I cannot appear to get out of. I modified my /etc/default/grub file to include the 1920x1200 resolution as I described previously. I have another disk in my computer, and an opensuse USB disk. When I performed my grub2-mkconfig it captured these two system also. Now if I unplug my USB drive, the system gets messed up and will not respond to commands.
Please explain what you mean. Bootloader menu does not appear? Bootloader menu appears but does not respond keyboard input? Bootloader cannot boot Linux kernel? Linux kernel is booted and you observe some problems after that?
What commands can give grub2-mkconfig so that it will ignore the USB and other drive? It may think that that the USB is my primary system, though when during boot I f2 and the tell it to boot from the hard drive the same things happen. There must be something short of a system reinstall.
Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/18/2015 11:42 PM, Andrei Borzenkov wrote:
В Thu, 16 Apr 2015 19:27:25 -0700 don fisher <hdf3@comcast.net> пишет:
Hello,
I made a bit of mistake that I cannot appear to get out of. I modified my /etc/default/grub file to include the 1920x1200 resolution as I described previously. I have another disk in my computer, and an opensuse USB disk. When I performed my grub2-mkconfig it captured these two system also. Now if I unplug my USB drive, the system gets messed up and will not respond to commands.
Please explain what you mean. Bootloader menu does not appear? Bootloader menu appears but does not respond keyboard input? Bootloader cannot boot Linux kernel? Linux kernel is booted and you observe some problems after that?
What commands can give grub2-mkconfig so that it will ignore the USB and other drive? It may think that that the USB is my primary system, though when during boot I f2 and the tell it to boot from the hard drive the same things happen. There must be something short of a system reinstall.
Andrei, As by some as a yet undetermined action, the /boot/grub2/grub.conf file from my USB drive got copied to my hard drive. So whenever I booted the hard drive, I was actually booting the USB drive. So when I unplugged the USB drive I was unplugging the running system disk, which is why the system, which was now unplugged, no longer responded to commands. I solved it with a system reinstall. Everything is fine now. I had assumed a dependency had been generated rather than the actual problem. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
Anton Aylward -
don fisher