Morning,
Burned network version of media to CD to install because didn’t have a DVD available at the time. After successful install it will not boot without it. How do I fix this to boot on its own from the HD?
Thanks!..
What’s the output from:
/usr/sbin/efibootmgr -v
This is mostly a crude way of determining whether you are booting with UEFI or with traditional BIOS booting.
EFI variables are not supported on this system.
Okay. So you are using traditional BIOS booting.
What is the output from:
grep LOADER_TYPE /etc/sysconfig/bootloader
cat /etc/default/grub_installdevice
This will give information about how booting was setup on your system.
grep LOADER_TYPE /etc/sysconfig/bootloader
LOADER_TYPE=“grub2”
cat /etc/default/grub_installdevice
/dev/disk/by-id/ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M5YDJ0C0
activate
Does that disk exist?
Check with:
ls -l /dev/disk/by-id/ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M5YDJ0C0
It will probably be a link to “…/…/sdb”.
I think I have been missing the obvious. Check your BIOS settings. Your BIOS is probably configured to boot from “/dev/sda” (the first hard drive), but you need it to boot from “/dev/sdb” (the second hard drive).
I think I confused things in my last reply.
I am also helping another user with boot issues, and I think I got confused between the two. It’s the other user who has two drives. I don’'t know whether you have only one or more hard drives.
Apologies for any confusion.
I have 3 drives:
C) Leap, 1.8 TB
2nd) backup files, 400+ GB
3rd) Windows Image back
And you know, I did a test to see if this problem would occur if I Diskpart C: and restore Windows 10 Pro doing a clean and reformat the HD, and strangely its doing the same thing. I ran the Window CD to try to fix the startup and it reported to have fixed it, but the issue persist. Then I installed Leap on another Computer and everything went fine.
What go’s on?
I’m not at all sure.
There’s something that is confusing your BIOS. But when you boot the CD, the boot code on the CD is able to boot your hard drive.
There are weird requirements that some BIOS follow. I’m not good at guessing.
Is the hard drive with openSUSE using traditional DOS partitioning or GPT partitioning? If you are not sure, then the output from either of
fdisk -l
parted -l
should tell you.
Maybe post either of those outputs.
With MBR boot windows may have changed the boot flag and will have replace MBR code with generic. . If you used grump in MBR and not also on a the partition that contains /boot directory. You will have to reinstall grub. if you used generic boot code in MBR you may only need to change the boot flag.
**The Good Leap Install:
Using **fdisk -l
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10SPZX-11Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A223D2F7-8935-43FA-822E-0A7DF23F068B
Device ** Start** ** End** ** Sectors** ** Size** Type
/dev/sda1 2048 18431 16384 8M BIOS boot
/dev/sda2 18432 1949329407 1949310976 929.5G Linux filesystem
/dev/sda3 1949329408 1953525134 4195727 2G Linux swap
Disk /dev/sdb: 931.49 GiB, 1000170586112 bytes, 1953458176 sectors
Disk model: My Passport 083A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf6d36cf4
Device Boot Start ** End** ** Sectors** ** Size** Id Type
/dev/sdb1 2048 1953458175 1953456128 931.5G 7 HPFS/NTFS/exFAT
Disk /dev/loop0: 44.18 MiB, 46325760 bytes, 90480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 174.75 MiB, 183222272 bytes, 357856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 156.4 MiB, 163614720 bytes, 319560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 215.19 MiB, 225640448 bytes, 440704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 42.86 MiB, 44916736 bytes, 87728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 89.1 MiB, 93429760 bytes, 182480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop6: 156.7 MiB, 164290560 bytes, 320880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop7: 42.85 MiB, 44912640 bytes, 87720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop8: 73.10 MiB, 77565952 bytes, 151496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop9: 85.78 MiB, 89927680 bytes, 175640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop10: 54.52 MiB, 57151488 bytes, 111624 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop11: 260.73 MiB, 273375232 bytes, 533936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop12: 3.94 MiB, 4108288 bytes, 8024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop13: 409.42 MiB, 429297664 bytes, 838472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop14: 117.81 MiB, 123510784 bytes, 241232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop15: 91.26 MiB, 95682560 bytes, 186880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop16: 132 KiB, 135168 bytes, 264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop17: 172.92 MiB, 181297152 bytes, 354096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop18: 22.43 MiB, 23511040 bytes, 45920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop19: 95.78 MiB, 100417536 bytes, 196128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop20: 136.89 MiB, 143515648 bytes, 280304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop21: 10.47 MiB, 10964992 bytes, 21416 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop22: 153.48 MiB, 160923648 bytes, 314304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Thanks for that “fdisk” output.
Some BIOS are known to be fussy about the “pmbr_boot” flag when using GPT partitioning. You might try toggling that flag to see if it helps. You can google “pmbr_boot” for information about how to do that.
Okay, I will do my homework on this,
Thanks for your help!..
Check out what I found as to why I was having this weird behavior. Before endeavoring into installing Lead,
- backup Windows to my 3rd HD
- changed my boot sequence from CD, Hd1, Hd2, Hd3, Iomega Zip, USB to CD, USB, Iomega Zip, Hd1, Hd2, Hd3,
So I decided to change it back and now everything is working properly. Can you explain why that change would effect my boot of the primary HD?
I don’t know enough about your system. However: with traditional BIOS booting, the boot code makes a call to the BIOS whenever it wants to read from a disk. It identifies the disk by number (0, 1, …). When you change the boot order, that also changes the disk numbering used by the BIOS.