Visit The New, Modern Unix Linux Community

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Thread Tools Search this Thread
Special Forums Hardware Boot Loaders Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key
# 1  
Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key


I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error

" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "

I have tried CD and USB in which the bootable Windows 7 exists but the same error occurs. It is also worth to note that CD or USB can be seen as a removable media when kubuntu session is opened.

Could anyone tell me the solution ?


Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #193
Difficulty: Easy
Python was selected the Programming Language of the Year in 2007, 2010, and 2018.
True or False?

10 More Discussions You Might Find Interesting

1. Ubuntu

Cannot access or boot encrypted drive (gave up waiting for root device...)

I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before. When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies

2. Solaris

Can't open boot device..

Hello Forum, I'm really in a fix now, I'm getting this error message now, seems like the boot block is damaged? When I do probe-all the system freezes... Can any one guide me as what to do next? System is Solaris 8 running Open Boot PROM 4 System also does not have a cd/dvd rom drive... ... (17 Replies)
Discussion started by: br1an
17 Replies

3. Solaris

Can't open boot device

I installed a new hard drive completely blank. sun blade 150 openboot 4.10.6 message: Boot device: disk:a File and args: Bad magic number in disk label Can't open label package Evaluating: Can't open boot device (15 Replies)
Discussion started by: janiper
15 Replies

4. Solaris

How to know what is the boot device?

Hello, I am wondering which commend /file to check to find out what is the boot device? regards Ahmed Egypt (1 Reply)
Discussion started by: ahmedamer12
1 Replies

5. Solaris

question about opb boot device

hi all: I have a sun blade-1000 for labs only, with 73G hd loaded, which boot block installed on slice 0. I'm confused by setting "boot-device" value in obp, which my question as follow: in ok mode, I got device alias like this: disk0: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@2,0 as I know the... (4 Replies)
Discussion started by: netshu
4 Replies

6. Solaris

Can't open boot device

I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
Discussion started by: mayewil
2 Replies

7. Solaris

ERROR: Can't open boot-device

Hi i need help pls ... Server type sun fire 3800 I need to install solaris 9 . When i boot the system i recieve the following : System Controller 'sunfire3800': Type 0 for Platform Shell Type 1 for domain A console Type 2 for domain B console Type 3 for... (5 Replies)
Discussion started by: tt155
5 Replies

8. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

9. UNIX for Dummies Questions & Answers

Setting a boot device alias on Sun hardware

I watched this done a long time ago, but cannot find it anywhere. I need to alias the boot device "disk" to /sbus@7,0/QLGC,isp@0,10000/sd@c,0 I think I need to set "use-nvramrc?" to true, and then create an alias within the nvramrc to point disk to the boot disk, but this is the step I cannot... (3 Replies)
Discussion started by: 98_1LE
3 Replies

10. UNIX for Dummies Questions & Answers

Changing boot device on a Sun box

I need to change the boot slice on a Sun box, more specifically the alias of "disk". When I do a printenv from the ok prompt, it lists "boot-device disk net", but when it boots, it is looking at the wrong slice on "disk" (3 Replies)
Discussion started by: 98_1LE
3 Replies
BOOT.CFG(5)						      BSD File Formats Manual						       BOOT.CFG(5)

boot.cfg -- configuration file for /boot DESCRIPTION
The file /boot.cfg is used to alter the behaviour of the standard boot loader described in boot(8). Configuration changes include setting the timeout, choosing a console device, altering the banner text and displaying a menu allowing boot commands to be easily chosen. If a boot.cfg file is not present, the system will boot as normal. FILE FORMAT The format of the file is a series of lines containing keyword/value pairs separated by an equals sign ('='). There should be no whitespace surrounding the equals sign. Lines beginning with a hash ('#') are comments and will be ignored. Some keywords can be present multiple times in the file to define additional items. Such keywords are noted below. banner (may be present multiple times) The text from banner lines is displayed instead of the standard welcome text by the boot loader. Up to 10 lines can be defined. No special character sequences are recognised, so to specify a blank line, a banner line with no value should be given. clear If nonzero, clear the screen before printing the banner. If zero, do not clear the screen (the default). consdev Changes the console device to that specified in the value. Valid values are any of those that could be specified at the normal boot prompt with the consdev command. default Used to specify the default menu item which will be chosen in the case of Return being pressed or the timeout timer reaching zero. The value is the number of the menu item as displayed. As described above, the menu items are counted from 1 in the order listed in boot.cfg. If not specified, the default value will be option 1, i.e. the first item. format Changes how the menu options are displayed. Should be set to one of 'a' for automatic, 'l' for letters and 'n' for numbers. If set to automatic (the default), menu options will be displayed numerically unless there are more than 9 options and the timeout is greater than zero. If there are more than 9 options with a timeout greater than zero and the format is set to number, only the first 9 options will be available. load Used to load kernel modules, which will be passed on to the kernel for initialization during early boot. The argument is either the complete path and file name of the module to be loaded, or a symbolic module name. When the argument is not an absolute path, the boot loader will first attempt to load /stand/<machine>/<kernel_version>/modules/<name>/<name>.kmod. If that file does not exist, it will then attempt to load /<name>. May be used as many times as needed. menu (may be present multiple times) Used to define a menu item to be displayed to the end-user at boot time which allows a series of boot commands to be run without further typing. The value consists of the required menu text, followed by a colon (':') and then the desired command(s). Multiple commands can be specified separated by a semi-colon. If the specified menu text is empty (the colon appears immediately after the equals sign), then the displayed menu text is the same as the command. For example: menu=Boot normally:boot menu=Boot single-user:boot -s menu=Boot with module foo:load /foo.kmod;boot menu=Boot with serial console:consdev com0;boot menu=:boot hd1a:netbsd -as Each menu item will be prefixed by an ascending number when displayed, i.e. the order in the boot.cfg file is important. Each command is executed just as though the user had typed it in and so can be any valid command that would be accepted at the nor- mal boot prompt. In addition, ``prompt'' can be used to drop to the normal boot prompt. timeout If the value is greater than zero, this specifies the time in seconds that the boot loader will wait for the end-user to choose a menu item. During the countdown period, they may press Return to choose the default option or press a number key corresponding to a menu option. If any other key is pressed, the countdown will stop and the user will be prompted to choose a menu option with no further time limit. If the timeout value is set to zero, the default option will be booted immediately. If the timeout value is negative or is not a number, there will be no time limit for the user to choose an option. userconf Passes a userconf(4) command to the kernel at boot time . rndseed Takes the path to a random-seed file as written by the -S flag to rndctl(8) as an argument. This file is used to seed the kernel entropy pool rnd(9) very early in kernel startup, so that high quality randomness is available to all kernel modules. This argument should be supplied before any ``load'' commands that may load executable modules. EXAMPLES
Here is an example boot.cfg file: banner=Welcome to NetBSD banner================== banner= banner=Please choose an option from the following menu: menu=Boot normally:boot menu=Boot single-user:boot -s menu=Boot from second disk:boot hd1a: menu=Boot with module foo:load /foo.kmod;boot menu=Boot with modules foo and bar:load /foo.kmod;load /bar.kmod;boot menu=Boot Xen with 256MB for dom0:load /netbsd-XEN3_DOM0 console=pc;multiboot /usr/pkg/xen3-kernel/xen.gz dom0_mem=256M menu=Boot Xen with 256MB for dom0 (serial):load /netbsd-XEN3_DOM0 console=com0;multiboot /usr/pkg/xen3-kernel/xen.gz dom0_mem=256M console=com1 com1=115200,8n1 menu=Boot Xen with dom0 in single-user mode:load /netbsd-XEN3_DOM0 -s;multiboot /usr/pkg/xen3-kernel/xen.gz dom0_mem=256M menu=Go to command line (advanced users only):prompt clear=1 timeout=-1 default=1 userconf disable ehci* # Always load ramdisk module load=/miniroot.kmod N.B. Xen counts serial ports from com1 upwards, but NetBSD counts from com0, so the appropriate device name must be used. Please see the Xen with serial console example above. This will clear the screen and display: Welcome to NetBSD ================= Please choose an option from the following menu: 1. Boot normally 2. Boot single-user 3. Boot from second disk 4. Boot with module foo 5. Boot with modules foo and bar 6. Boot Xen with 256 MB for dom0 7. Boot Xen with 256 MB for dom0 (serial) 8. Boot Xen with dom0 in single-user mode 9. Go to command line (advanced users only) Option [1]: It will then wait for the user to type 1, 2, 3, 4, 5, 6, 7, 8 or 9 followed by Return. Pressing Return by itself will run option 1. There will be no timeout. SEE ALSO
boot(8), boothowto(9) HISTORY
The boot.cfg file appeared in NetBSD 5.0. AUTHORS
The boot.cfg extensions to boot(8) were written by Stephen Borrill <>. BUGS
Support for boot.cfg is currently for NetBSD/i386 and NetBSD/amd64 only. It is hoped that its use will be extended to other appropriate ports that use the boot(8) interface. BSD
November 28, 2011 BSD

Featured Tech Videos