Re: Windows 8 Auf Usb Stick Installieren
Denna Repaci
I want to try Ubuntu as after upgrading to windows 10, my laptop runs slow. I have created bootable USB several times but can't make my laptop to boot. I saw tutorials and already setup bios to boot from USB first and also turnoff fast boot from power option. I can however use other USB for windows 10 that i have and that works but not from Ubuntu USB
It gets a hangup at boot, it displays "press Esc to see startup option" and nothing happens. If I press Esc then it displays "press Esc to pause" and if press Esc nothing happens. Basically I have to turn off the laptop by pressing the power button.
The Ubuntu live USB that you made with the 1.5GB Ubuntu iso is not loading successfully, so try booting your laptop with the Ubuntu Minimal CD. The Ubuntu Minimal CD is less than 60MB in size, and loads the rest of the packages required to install Ubuntu during the installation process.
It is possible to make an Ubuntu Minimal USB on either Ubuntu or Windows Subsystem for Linux 2 in Windows 10 using dd. While the minimal iso image is handy, it isn't useful for installing on UEFI-based systems that you want to run in UEFI mode. The mini iso lacks the proper files for booting the computer in UEFI mode. Thus the computer will boot in BIOS compatibility mode, and the installation will be in BIOS mode.
Download the file called mini.iso to your Downloads folder. You can download the mini.iso file to wherever on your computer that you want, but download it to your Downloads folder so that you can easily run the commands in the following steps without changing anything.
If you are using Windows Subsystem for Linux download the Microsoft File Checksum Integrity Verifier tool from the official Microsoft Download Center. The Microsoft File Checksum Integrity Verifier tool is a command line utility that computes MD5 or SHA1 cryptographic hashes for files.
Check in the Disks disk utility to find out the device name of your USB flash drive. This is very important because if you use the wrong device name in step 6, you will overwrite your whole operating system instead of writing to the USB flash drive. So check the USB flash drive device name twice. It should be something like /dev/sd* where instead of the * character there is a lower case letter like a, b, c, etc. In the following step I am assuming that the device name is /dev/sdc, but the device name of your USB drive could be something else like /dev/sda or /dev/sdb so check the device name of your USB drive twice and make sure that you get it right in step 6!
The dd if='mini.iso' of=/dev/sdc bs=4096 command should take only a few seconds to complete on most computers because the mini.iso is a small file, less than 60MB. The result of running this command will be a bootable Ubuntu mini USB.
If you select the Install option (the complete install, not the cli install) from the menu screen in Step 7, then you can select other options during the Ubuntu installation process to download all the packages that you need to perform a complete Ubuntu installation. Select the Ubuntu desktop package collection from the list of predefined collections of software in the Software selection screen in the Ubuntu mini CD installer. When you restart the system at the end of the installation, you will have a working Ubuntu desktop with the default desktop environment.
I remember having this problem on an older laptop a year or two ago. It probably has something to do with how the computer is trying to start. Sometimes UEFI won't launch a Legacy USB and vice versa. Make sure you're iso file is for UEFI booting or disable that and use Legacy, but then you need to make sure that your iso file is the one that boots with Legacy.
Try to put your bootable media in USB 3.0 ports instead of 2.0 It seems that 2.0 ports are totally frozen in my case. Ubuntu does not recognize any input in the test mode of bootable usb media and also after I managed to inatall the entire OS including keyboard or mouse.
So I reinstalled the key from Windows using Rufus (look like it make a not UEFI one) and I used the "Bypass boot order" or "Boot override" section provided by the ASUS BIOS. The section list all the connected USB devices, you select the one you want to boot in directly and it worked !
I have been struggling for ten years with the problem that an older computer (32 Bit Acer Aspire One) BIOS does recognize my USB .iso file. I just today found the answer from a wiser person than I and I want to share this with all of you.
Here is how to do it properly:If your computer has only LEGACY boot mode, the USB stick has to have a MBR (Master Boot Record) partition table before making a .iso installation (boot) file. And the USB should have a single FAT32 partition.
After multiple attempts and hours of research, I did find a writing that said that another USB device connected to port near USB stick may cause the computer not to recognize the USB iso-stick.!!!
I first installed HA on a windows machine through Virtual Box. But i found constant connectivity issues. I had some old Intel Compute Stick STK1AW32SC lying around so i thought I give it a try. The compute stick was first pretty descent to use for simple tasks when i bought it, but after all the windows updates it became totally useless. This is how I installed HA:
Before you insert the Ubuntu USB into the Intel Stick, you must enter BIOS and switch it over to Windows 64 bit mode. Even though you only have Windows 32 bit installed, your Intel Stick starts in 64 bit mode.
Follows are the instructions I used to accomplish this. Note that Windows Server 2019 is the last Server OS from Microsoft that will run on this hardware - Microsoft recompiled Server 2022 with CPU-specific opcodes and it won't run on older hardware. (or so they say)
Ingredients: HP DL 380 g6, 800GB worth of 15k rpm drives on a SmartArray, 32GB ram, a 32GB PNY usb stick, the Server 2019 ISO downloaded from Microsoft Volume License Service Center, some knowledge and experience and trial and error. You should have a scratch OS on the system. I recommend Server 2012R2 You will also need a copy of Rufus and a windows 10 system and you may need a Server 2008R2 ISO installer as well. (available from volume license)
This should also work for the DL180 g6 as well with one exception - the 180's do not come with ILO circuitry. However the stub interface still exists on the motherboard and will produce an "unknown device IPMI" in Device Manager. HP has a Null Driver inf file for Server 2008 that will make this go away if it bothers you, search for it.
Create the BIOS update USB stick on the win10 system. You must use diskpart to "clean" the USB stick then use diskpart to apply an MBR loader on it. Then use Rufus to format the USB stick NTFS. Then run the BIOS update and let it extract then run the HP USB key generation program as administrator. It probably will error out saying the USB stick is write protected - if you get the error, click OK on it then the SECOND the dialog box disappears immediately rerun the USB key generation program - the second time it will work and generate the USB key if you restart it fast enough
copy the P410i firmware update to the server and update the RAID card. Also update the hard disk firmwares (apparently the disk firmware updater will not run on Server 2019) Allow the server to reboot and tap the spacebar when the Show Options message comes up on the screen. When the screen is in character mode printing out the boot notifications press F8 to get into the array utility. Delete all logical drives and recreate the array how you like. You MUST set the array as bootable otherwise it will not appear.
Using Rufus on the win10 system again, create the bootable Windows Server 2019 USB stick. You MUST select "MBR" format in Rufus and you MUST also click the Advanced section of Rufus and select the option to "make the stick bootable on old BIOSes"
Boot the server with the Windows Server 2019 USB stick and install a fresh server. Let it reboot a few times and at the desktop put in the local admin password and then go to the desktop as administrator.
In Device Manager select the Base Driver errored device, right click and select update then select to search the local computer and search the driver directory in downloads. It will install the ILO 2 regular driver
In Device Manager select the IMPI errored device, right click and select update then select to search the local computer and select the controller directory in downloads. It will install the ILO 2 controller driver
I did the same as you, using the older drivers when possible. The only issue is that the ILO driver simply doesn't work in 2022, which breaks the ability of the system management homepage to query hardware, so you're basically blind to any hardware issues that come up. You'd have to use the ILO webpage itself to look at those details.
Maybe there' s some trick to getting that ILO driver working... gives an error code 10 in device manager, and if I was really concerned about it, I'd dig deeper, but it's one of those things I can find a way to do without SMH since apparently I have to.
Follow up... I decided to look closer at the DL360 G7 I updated to Server 2022 yesterday. Turns out I just had to uninstall the "HP Baseboard Management Controller IPMI Device" driver that was failing to start. Didn't need it.
For SMH, initially it wasn't showing me any data and couldn't contact the management controller (ILO). I ended up uninstalling SMH and the HP WBEM driver, and then reinstalling (WBEM first, then SMH). There's a trick to it though...
I left my "C:\HP\hpsmh" folder intact after uninstalling SMH. Then I installed HP WBEM, but if you just run the cpxxxx.exe installer, it fails because it does a check and will only work on Server 2016 or older. The key is to just use 7z or something to extract the contents of that and you'll see an MSI file in there. Just install that MSI and you're good to go.
Another tip... The DL360 G7 driver download page does have the WBEM installer, but if you cruise over to the DL360 Gen9 page instead, they have a newer version of it. Version 11.1.0.0 (instead of 10.75.0.0 I think). Version 10.75 might actually still let you install on Server 2019/2022, since the version 11 release notes say something about fixing an issue that let you install on unsupported products.
d3342ee215