Visit Our UNIX and Linux User 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  
Old 03-22-2011
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

Previous Thread | Next Thread
Test Your Knowledge in Computers #748
Difficulty: Medium
The ZX81 was a home computer that was produced by Sinclair Research and manufactured in Dundee, Scotland.
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
vparboot(1M)															      vparboot(1M)

NAME
vparboot - boot a virtual partition SYNOPSIS
kernel_path] boot_opts] boot_addr] PA-RISC platforms only Itanium(R)-based platforms only name]| server_ip client_ip optional_data]]] DESCRIPTION
The command causes the virtual partition monitor to boot the specified virtual partition. The monitor must be running. The virtual parti- tion must exist in the monitor configuration and be in the state. For this reason, it is not possible to boot the local partition using this command. The partition in which the command is executing is called the local partition. On hard-partitionable systems, such as Superdome, if there is a pending reboot for reconfiguration the specified virtual partition will not be booted until all the virtual partitions on that hard partition (nPartition) are shut down and the virtual partition monitor is rebooted. Refer to "Performing a Reboot for Reconfig for an nPartition" in the for more information. Options recognizes the following command line options and arguments: Specifies the unique name of the virtual partition that is to be booted. The virtual partition must exist in the monitor's database, must be in the state, and must have a configured boot device. Required. Specifies the absolute path to a bootable kernel for the virtual partition. For example, if a non-partitioned system start string at the ISL prompt is: the kernel-path is the portion of this string. If this option is omitted, the value is taken from any specified during virtual partition creation or its most recent modification, or if has never been specified. Specifies the command-line options to be applied when the virtual partition is booted. For example, if a non-partitioned system start string at the ISL prompt is: the boot_opts string in this case will be Note that if there is a space included in the string, the string must be quoted. Refer to the virtual partitions administration guide and the chapter titled "Monitor and Shell Commands" for a full list of supported boot option strings. If the option is omitted, the value is taken from any specified during virtual partition creation or its most recent modification, or the empty string if has never been specified. Specifies the device from which the virtual partition kernel image is read. It must be one of the following three forms: bo[ot] | pri[mary] (case-insensitive). This is the default if the option is omitted. attempts to boot vp_name from the device previously configured with the attribute. It is an error if no device has been so configured. (case-insensitive). attempts to boot vp_name from the device previously configured with the attribute. It is an error if no device has been so configured. (case-insensitive). On PA-RISC platforms attempts to boot from a device previously configured with the attribute. It is an error if no device has been so configured. On Itanium(R)-based platforms, lists all the tape devices assigned to the partition. The user will then be prompted to select the tape device from which to boot the partition. This will restore the contents archived using from All the contents on the target disk will be lost. Boot From Hardware Path: Any other string is assumed to be the hardware path to the desired boot device (for example, 10/6.0). does not check any part of such a specification. If it is not a proper path, the path does not exist, the virtual parti- tion does not own the device at that path, or there is no bootable device at that path, the command either fails with an error, or the boot attempt fails with no error indication. Boot actions: If the boot from primary path fails, then the combination of and attributes decides the boot action to be taken. Refer to the vparcreate(1M) or vparmodify(1M) manpage for details. (PA-RISC platforms only) Specifies a path to a cold-install kernel such as This form of the command is used to cold-install an instance of HP-UX on a virtual partition. Most often, this is done on a newly-created virtual partition, one that has a completely unwritten disk. However, it can be used to cold- install HP-UX over an existing instance. ignite_kernel can reside either on the local virtual partition (the one on which is run) or on any other networked sys- tem or virtual partition accessible from that partition. The syntax for ignite_kernel is: If cold-install_kernel begins with a slash, "/", you are specifying an absolute path and looks for it at that location. With Ignite-UX revisions prior to C.6.0, if cold-install_kernel does not begin with "/", the default path is prepended to cold-install_kernel. With Ignite-UX revision C.6.0 or later, there is no cold-install_kernel at the default path Hence it is required to specify an absolute path, such as If the Server name or IP address, is not specified, loads the cold-install kernel from the file space of the local vir- tual partition. Otherwise the command loads it from the file space of the specified server. The comma is a required part of the server name syntax. (Itanium-based platforms only) Arguments are optional. Once the command exits, you must enter in a console window until you reach the virtual console for vp_name. There you are presented with one or more MAC addresses of I/O controllers assigned to vp_name. Select the appropriate address to load the cold-install kernel. If no MAC address can be identified, or if the selected MAC address fails to load the cold-install kernel, you must identify the source of the problem, then retry the command. Specifies the DB-Profile name from which user specified Direct boot settings are read from the database Specifies the static IP address for the boot server Specifies the static IP address for the client. If client IP information is missing in the DB-Profile, DHCP will be used by default. Specifies the static IP address for the gateway Specifies the subnet mask for the local network Specifies the absolute path to a bootable file on the boot server. If empty then it will be assumed that the server controls the boot File for the client. Specifies the optional command line arguments to pass to the boot file SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser. When virtual partition flexible administrative capability is enabled, a virtual partition can only be booted from within a Designated-Admin vPar. RETURN VALUE
The command exits with one of the following values: Successful completion. One or more error conditions occurred. EXAMPLES
Boot the virtual partition called Boot the virtual partition specifying an alternate kernel: Cold-install the virtual partition from a file on a remote PA server: Cold-install the virtual partition using DB-Profile settings on a remote Itanium server: Profile Name: profile1 Network Type: IPv4 Server IP address: 15.1.165.152 Client IP address: 15.1.163.92 Gateway IP address: 15.1.165.240 Subnet Mask: 255.255.248.0 Boot File: /opt/ignite/boot/nbp.efi Optional Data: IINSTALL Cold-install the virtual partition passing network information on a remote Itanium server: ERRORS
displays error messages on standard error for any of the following conditions: o vp_name does not exist in the monitor. o vp_name is in some state other than and so cannot be booted. Use the command instead. o An error occurs while trying to access an Ignite server or cold-install file. You have specified the or device, but the corresponding device has not been configured in vp_name. NOTE: If the boot device has not been configured properly, the command will complete without error, but the virtual partition will not boot. Possible reasons for this could be: -- The or attribute was assigned to a device other than a disc or DVD. -- The attribute was assigned to a device other than tape. -- The file at the default or configured kernel path does not exist or is not a bootable image. o The command and the virtual partition monitor are at different revision levels. This message is only a warning. The command continues. o When the virtual partition flexible administrative capability is enabled and the local virtual partition is not a Designated-Admin vPar. AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
vparadmin(1M), vparcreate(1M), vparconfig(1M), vpardump(1M), vparefiutil(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), vpardbprofile(1M), vparresources(5), vpartition(5), vpmon(5). vparboot(1M)

Featured Tech Videos