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

Special Forums Hardware Boot Loaders Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

03-22-2011

Registered User

52, 0

Join Date: Jul 2010

Last Activity: 14 January 2018, 12:33 PM EST

Posts: 52

Thanks Given: 47

Thanked 0 Times in 0 Posts

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

Hello,

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 ?

thanks

rpf

View Public Profile for rpf

Find all posts by rpf

Previous Thread | Next Thread

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....

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... ...

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

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

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...

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...

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...

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...

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...

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"

LEARN ABOUT NETBSD

boot

BOOT(8) 						    BSD System Manager's Manual 						   BOOT(8)

NAME

     boot -- system bootstrapping procedures

DESCRIPTION

     This document provides information on using common features in the NetBSD boot loader.  Additional information may be found in architecture-
     specific boot(8) manual pages.

     In the native NetBSD boot protocol, options are passed from the boot loader to the kernel via flag bits in the boothowto variable (see
     boothowto(9)).

   Interactive mode
     In interactive mode, the boot loader will present a prompt, allowing input of these commands:

	 boot [device:] [filename] [-1234abcdmqsvxz]
	       The default device will be set to the disk that the boot loader was loaded from.  To boot from an alternate disk, the full name of
	       the device should be given at the prompt.  device is of the form xd [N[x]] where xd is the device from which to boot, N is the unit
	       number, and x is the partition letter.

	       The following list of supported devices may vary from installation to installation:

	       hd      Hard disks.
	       fd      Floppy drives.

	       The default filename is netbsd; if the boot loader fails to successfully open that image, it then tries netbsd.gz (expected to be a
	       kernel image compressed by gzip), followed by netbsd.old, netbsd.old.gz, onetbsd, and finally onetbsd.gz.  Alternate system images
	       can be loaded by just specifying the name of the image.

	       Options are:

	       -1   Sets the machine-dependent flag RB_MD1 in boothowto.

	       -2   Sets the machine-dependent flag RB_MD2 in boothowto.

	       -3   Sets the machine-dependent flag RB_MD3 in boothowto.

	       -4   Sets the machine-dependent flag RB_MD4 in boothowto.

	       -a   Sets the RB_ASKNAME flag in boothowto.  This causes the kernel to prompt for the root file system device, the system crash
		    dump device, and the path to init(8).

	       -b   Sets the RB_HALT flag in boothowto.  This causes subsequent reboot attempts to halt instead of rebooting.

	       -c   Sets the RB_USERCONF flag in boothowto.  This causes the kernel to enter the userconf(4) device configuration manager as soon
		    as possible during the boot.  userconf(4) allows devices to be enabled or disabled, and allows device locators (such as hard-
		    ware addresses or bus numbers) to be modified before the kernel attempts to attach the devices.

	       -d   Sets the RB_KDB flag in boothowto.	Requests the kernel to enter debug mode, in which it waits for a connection from a kernel
		    debugger; see ddb(4).

	       -m   Sets the RB_MINIROOT flag in boothowto.  Informs the kernel that a mini-root file system is present in memory.

	       -q   Sets the AB_QUIET flag in boothowto.  Boot the system in quiet mode.

	       -s   Sets the RB_SINGLE flag in boothowto.  Boot the system in single-user mode.

	       -v   Sets the AB_VERBOSE flag in boothowto.  Boot the system in verbose mode.

	       -x   Sets the AB_DEBUG flag in boothowto.  Boot the system with debug messages enabled.

	       -z   Sets the AB_SILENT flag in boothowto.  Boot the system in silent mode.

	 consdev dev
	       Immediately switch the console to the specified device dev and reprint the banner.  dev must be one of pc, com0, com1, com2, com3,
	       com0kbd, com1kbd, com2kbd, com3kbd, or auto.  See Console Selection Policy in boot_console(8).

	 dev [device]
	       Set the default drive and partition for subsequent filesystem operations.  Without an argument, print the current setting.  device
	       is of the form specified in boot.

	 help  Print an overview about commands and arguments.

	 ls [path]
	       Print a directory listing of path, containing inode number, filename, and file type.  path can contain a device specification.

	 quit  Reboot the system.

     In an emergency, the bootstrap methods described in the NetBSD installation notes for the specific architecture can be used.

FILES

     /boot		      boot program code loaded by the primary bootstrap
     /netbsd		      system code
     /netbsd.gz 	      gzip-compressed system code
     /usr/mdec/boot	      master copy of the boot program (copy to /boot)
     /usr/mdec/bootxx_fstype  primary bootstrap for filesystem type fstype, copied to the start of the NetBSD partition by installboot(8).

SEE ALSO

     Architecture-specific boot(8) manual pages, ddb(4), userconf(4), halt(8), installboot(8), reboot(8), rescue(8), shutdown(8), boothowto(9)

BUGS

     The kernel file name must be specified before, not after, the boot options.  Any filename specified after the boot options, e.g.:

	   boot -d netbsd.test

     is ignored, and the default kernel is booted.

BSD
								 September 4, 2009							       BSD

Boot Loaders