Hp Dv6 Boot From Usb

0 views

Skip to first unread message

Colby DuLin

unread,

Aug 3, 2024, 5:53:02 PM8/3/24

to agputtiemul

Why should I care about auto snapshot, if even manual snapshot is not working? It does not matter, how many times I do snapshot to alternate slice, I end up with switch booting from backup partition... What do I do to solve it?

Alright ?
Lets try another way to solve this problem .
Lets try installing a new image using the CLI or J-Web. The newly installed image will become the primary image, and the device will boot from it on the next reboot.

And to ensure that the resilient dual-root partitions feature operates correctly, execute the following command to copy the new Junos OS image into the alternate root partition:

user@switch> request system snapshot slice alternate

_US/junos16.1/topics/task/installation/ex-series-software-installing-single-routing-engine-cli.html

Please update me if that help !

I've recently installed ubuntu 1404 server on this machine to an SSD in the optical drive bay. All work correctly until I start adding SATA drives in the main body of the server -> then the server seems to try and boot from these SATA discs instead.

I don't know if you already solved your problem but here is what I found. It says here that you could install GRUB on a flash drive during Ubuntu installation and this should solve the problem. Unfortunately for an unknown reason this did not work for me (at this point I have a guess). So I tried this but the install command resulted in an error about embedding or something like that.

Did some research and it turned out the flash drive needs to be MBR (I guess this was the reason it failed during install). I tried formatting the USB in Ubuntu using these instructions but I failed and I assume it was my own fault. I ended up doing it with elevated command prompt in Windows using DISKPART and Windows 7 install disk.

Hi,
My solution for booting from ODD bay in AHCI mode:
1) Install any microSD card. Actually I used old SanDisk 2Gb
2) Install SSD using SATA cable to ODD and power converter.
3) Install Ubuntu LTS server with / and swap mounted on SSD, /boot and GRUB on SD.
Please note if you will add some drives later probably swap will not mount because ODD drive change it dev path.

to run SSD is actually simple: on system boot press F10, get to system configuration options for RAID, create an array and include only new SSD drive into it, make it bootable. After that - create another array and add your HDDs.

For anyone that runs into this issue. It does always boot from USB. Directly on the motherboard there is an additional USB port. I stuck a usb key in there. Added the SSD drive on the optical drive SATA connector. And installed Ubuntu with the /boot on the USB stick. Been running it like this for years now. Never had an issue.

In the end - it looks like for me it was the ISO software. I tried four different utilities. Finally, when I used WinISO v6.4 - ISO booted immediately with no problem. Secure Boot can be enabled since an MS install DVD is acceptable to it.

What worked for me was to change the Rufus partition after selecting the .iso. The .iso defaulted the partition setting to BIOS or UEFI. I changed it to MBR UEFI. Then when booting, F11, One-time settings. Both the RAID and USB partitions were no available. I selected USB and drilled down as to select the bootx64.efi file.

I am installing Leap onto my Dell Laptop on to a separate Hard Drive so that I can use either Windows or Leap without dual booting from one hard drive. I have downloaded and made a bootable USB Drive using Rufus. My issue is that my Dell XPS laptop uses UEFI Bios and does not allow me to select the USB Drive itself. Instead it is asking for a specific file from the USB Stick. Can somebody please let me know which file I need to select to be able to boot and install Leap from? If you need any more infomation or if i am missing something please let me know and I will try to fill in.
Regards
Charles

I have no idea what Rufus does to your USB and you probably should be addressing your question to Rufus community. The standard way to create bootable openSUSE USB is to dd the image onto the full drive (not partition).

Hi there, many thanks for the reply. I will try to expand a bit more. I was hoping that the option to select the USB drive would be there however its not. When i enter Bios to select the bootable media, it asks you add a bootable device. When you go to add a bootable device it brings up the usb drive, but is asking for a specific file within the .opensuse iso file itself. I have tried to select different files with.efi file name but to no success.

I tried creating a virtual machine ti run this from in windows 11, however i need it to connect to be able to plug an ethernet cable in, but it would not regconise it even after creating virtual switches and selecting different options.

You just repeated what you said before. Again - we do not know what Rufus put on this USB so we cannot tell what file to select. The standard bootable image would be \EFI\Boot\bootx64.efi, but if firmware fails to detect USB as bootable, this file is probably missing.

Thanks man for you support, is that possible to get more simplified version of procedure?Bcoz i really dont get it, particularly the purpose of using eMMC and other terminologies like Secure boot also unclear to me.

The init= flag on the current jetpack 4.6 is not honored. My approach bypasses this by changing the symlink of /etc/init to my script and my script then later executes what was originally being pointed to after pivoting the root.

On the Xavier AGX, unlike the NX or the Nano, the root= flag is not honoured. However, the root is abled to be mounted by the running kernel, again my script that is first executed instead of /etc/init does this mount. This approach again eliminates the next to do some extra flashing steps, reducing complexity. Also reduces the next for flashing, which I like to avoid if necessary.

I started off using the Jetson hacks approach. But I have an additional need and that is to be able to run the system with the OS mounted read-only having any writes to the OS happen to a memory overlay filesystem. To be able to do this I need the init= flag in extlinux.conf to be honored, I found that on Jetpack 4.6 this is not honored correctly.

Second to that, found that on jetpack 4.6 and only for the Xavier AGX platform the flag root= on extlinux.conf is also not honored. This led me to using the approach whereby I pivot the root and mount the SSD from the script for Xavier AGX to get around this. This approach also works for the NX and the Nano, so for consistency I now use this approach for all three platforms.

If you want to achieve the above goals then the Jetson hacks approach is simply not sufficient because you are missing the extra partitions. I have scripts the entire approach as well as creating the extra partitions needed for this extra resilient. I then use this base project as the base for another project. Both of those projects are not yet formally released.

In my experience over the years SD cards on any platform get corrupted very easily by non-clean shutdowns meaning boot from SSD is more than just a speed convience. Also, wanting to interact with the user for the fsck step if any repair is required is a standard unix thing but as I mount the OS read-only during operation this is mostly just extra carefulness that unfrotunately means you need the connected keyboard and monitor which is a major disadvantage.

ehm
are there exact steps from first step to the last step that define in unambigious but redundant/clear way how to flash to nvme without use of sdcard using NX? that could be posted to the forum thread so they could be executed like script until completed? without need to discuss terminology? but just by executing?

@lhoang Reading through the nvsdkmanager_flash script, on the Xavier NX this only seems to flash the QSPI memory. This does not appear to take into account building/flashing the NVMe SSD as described in the full document. Did I miss something?

My old Unraid motherboard / cpu / ram died on me a few weeks ago. I think it was about 11 years old so I didn't bother to troubleshoot much. I knew I needed to upgrade anyway, so I did. I got the following:

Everything seems to work ok. It posts and I can boot to a USB Windows 10 flash drive (to install Windows if I wanted) just fine. All the parity, data drives, and cache drive are recognized in the BIOS. However, the motherboard won't boot to the UNRAID USB Device that I took from my previous server. I did plug the UNRAID USB Flash Drive into another PC and all the files are there (made a backup of them as well). I've looked through the BIOS and nothing is standing out that I need to switch. It is confusing since it boots to the Windows Flash drive just fine, but not to the Unraid flash drive, which I know was working in my previous server. Any thoughts on what I might be missing here? Thanks for any help.

Some recent ASRock (and other brands as well) boards will only boot UEFI and not legacy. On your flash drive, if there is a folder named EFI- that means it wants to boot in legacy mode. To tell it to boot UEFI, rename the folder to EFI (remove the trailing - character).

Thank you @Hoopster! That did it. One last question if you don't mind. Since I made a backup of my USB UNRAID FLASH is there a place I can go to find what my latest drive assignments were? I haven't started the array since the parity drive it has listed isn't what I thought it would be. It might be accurate, but I would feel better knowing that all the drives are where they should be before starting the array. Thanks again.

No, I actually do not see a CONFIG folder at all on my backup. No, I stopped the health reports since I only setup notifications to tell me when something was wrong, but the information passed in those emails does not show all the disk assignments (lesson learned). Is there any other place it might be on the flash?