F5 No Valid Boot Device Found

0 views

Skip to first unread message

Robert

unread,

Aug 4, 2024, 10:30:04 PM8/4/24

to exfreevsumpsigh

ihave upgraded IOS for CISCO ISR 4431. after i copied new IOS and removed previous Image from flash, when i reload it initially gives error that no Valid Boot image found. and then it boots from same image. please help.

licensed under the GNU General Public License ("GPL") Version 2.0. The

software code licensed under GPL Version 2.0 is free software that comes

with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such

GPL code under the terms of GPL Version 2.0. For more details, see the

documentation or "License Notice" file accompanying the IOS-XE software,

or the applicable URL provided on the flyer accompanying the IOS-XE

software.

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.

But if you want to clean up, check the configuration of the router and there should be a boot variable string pointing to the wrong/deleted IOS file. Remove that line and this error message should go away.

When I install Windows 7 (64bit) Enterprise over WDS, it successfully goes through the installation but then when it actually tries to boot from the hard drive where it installed windows, it doesn't recognize it as a valid boot device....

I use the console command (hyperterminal) and it looks to be "locked". I press Ctrl-B or any other and nothing happen. Also I have the Tape unit connected with a backup of the system and nothing happen....

Thank you so much for your quick reply. I am going to do it and I will post agan tomorrow morning. The main problem is that when I start server autpomatically try to start from tape and it remain there (i cannot write anything). When I press Ctrl-B I go to the main menu and I can select only the commands:

Finally, following your indications and extra verifications, I have found more hardware problems. I identified that hard disk was damaged, so I used other HD and swapped the motherboard (hard disk motherboard). Now server rp3440 identify HD and it can be acceded. The problem now looks to software. After to try to boot up from P1 device I have these messages:

BOot [PRIALT] Boot from specified path

DIsplay Redisplay the current menu

HElp [] Display help for specified command

RESET Restart the system

MAin Return to Main Menu

----

Information Menu: Enter command > bo pri

Interact with IPL (Y, N, or Cancel)?> n

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.

While trying to answer this question on askubuntu: How do I Uninstall GRUB I read the Wikipedia article on MBR and also the perfect answer on a somewhat related question here on Superuser, however, one thing is still not clear to me:

My understanding is that the only thing BIOS normally checks on an MBR is its signature at the very end of the 512-byte sector, and then it just transfers control to the initial bootloader situated in the first 446 bytes of the boot sector.

The BIOS decides if a drive is bootable based on the 16-byte partition record, present after the MBR code area (held in a table starting at the 446th byte). The first byte in each partition record represents the drive's bootable status (and is set to 0x80 if bootable, or 0x00 if not). Some BIOSes may check other parts of the MBR as well (e.g. partition types, checksums), but the basic requirement is the bootable flag.

This is implementation dependent, and is why you need to properly select a boot order. In most cases, the BIOS will look through each storage medium in the order you set, and determine whether it can boot from that device (via the MBR data). If it can, it does - if not, it continues looping through the other devices (again, in the order you selected).

Once a valid boot device is found (i.e. the bootable flag is set, and other additional checks pass), the BIOS copies the MBR sector into RAM. The BIOS then relocates the instruction pointer to the beginning of this location (using a JUMP instruction), where the MBR code segment is located, and the computer then starts.

If the BIOS supports the BIOS Boot Specification, MBR code can return control to BIOS with a certain instruction, signaling it of boot failure and prompting it to try the next device. Older BIOSes just print an error message though. A good tell if your BIOS supports it is whether you can boot from USB.

No, but the drive must have a valid MBR or GUID partition table - otherwise, it won't be detected by the computer. While the code part of the MBR can indeed be empty, the first sector of the drive must have a well-formed MBR/GPT.

I have read the accepted answer by @Breakthrough but I think it's wrong. Or at least for the hardware I have here it does not apply (Mainboard MSI MS-6340).In the answer by @Breakthrough he says booting is by partition.So you can have one disk with many bootable partitions.But in the BIOS of my mainboard I can only select disks. Not partitions.

Also note if you format a disk (for example an USB pen drive) with FAT32 then it will have a MBR! Although it is not bootable! Don't ask me what the MBR bootstrap code of this disk will do. It probably simply aborts and goes to the next boot option.

On the resource center here under Additional Resources there is the SD card OOB QSPI Demo that should be helpful with how the device tree and u-boot files should look. For the SD card OOB QSI Demo copy the files found in this compressed file to a microSD card and boot the ZYBO from it to restore the Quad SPI flash with the factory default. It will take several minutes to complete.

I moved this thread to a sub section where more experienced embedded linux engineers look. I would suggest using the supported Petalinux projects available at the Petalinux Support for Digilent Boards page which includes the Zybo.

I will reach out to more embedded linux engineers to see if they have any input for you. I did find some web pages that look like they would be helpful here and here .The Xilinx's u-boot might be helpful as well.

Hi,

I wanted to fresh install F37, by downloading my favourite spin KDE Plasma Desktop via Fedora Media Writer on a USB pen to run live.

Everything went smoothly, I chose the traditional (not LVM) partitioning way on a superfast M.2 SSD. First I deleted former F36 partitions already on it, then I created the following mount points (in Btrfs):

Thus, chances are that I messed out with new partitions.

I also assume, that if the right command is executed, the GPT PMBR will be fixed, as it is written there. Am I right, or am I just making things much more simple than they are?

Otherwise, which is that command (write, as such, is something different, I know)? And above all, which is the right syntax?

More helpful suggestion?

The efi partition should only be about 200MB and the boot partition should be about 500 - 750MB. A swap partition is not needed on most fedora installations since the default swap is done using zram in memory. (Swap will be needed if intending to do hibernation or if RAM is extremely small)

I'm trying to do a clean install of F31 from a live image on USB, using manual partitioning so I can preserve my /home partition, but I always get this error. No valid boot loader target device found. See below for details. For a UEFI...

The grub config has been created automatically via "sudo grub-mkconfig -o /boot/grub/grub.cfg" and having "os-prober" installed.

I found a workaround to start Windows by using the grub command line and entering "exit" which leads to an exit of the grub boot selection and a booting of Windows.

Is there any way I can achieve this via the grub selection menu directly or what am I doing wrong ending up with the error above?

I recently made a dual boot installation of Windows 10 and Linux following this advice. I did as most recommended, installed Windows 10 first. When installing I set the first (EFI/boot) partition size to 1 gigabytes, as told here. I'm not sure if needed, but also set MSR partition size to 128Mb same way (automatic install suggested only 16Mb for MSR partition). Forget the recovery partition part, it you use the latest (or very fresh) install package from Microsoft, created by Windows Media Creation Tool, the Windows 10 install will create it automatically after the main Windows partition. Just remember to leave enough empty space to hard drive, do not use all empty space for Windows main partition.

I am not using grub and don't have two efi system partitions, so I can only imagine, that this configuration needs some additional configuration steps (boot files for windows are on second system EFI partition, which is not mounted?).

Though I agree this would likely be fixable by installing GRUB to the Windows EFI, this doesn't explain why this happens with the GRUB config as present. I do suspect it is possible that your firmware does not allow GRUB to see the second drive in this scope, but that would be hard to test for. Maybe - without having tested it - what output do you get for