Hi there! This is my first post on this forum, so forgive me if I forget important information. I don’t know what to include, so feel free to ask for [and provide commands to print said] info. :3
I have two “issues” with my install of OpenSUSE Tumbleweed:
0. GRUB shows up for some reason. It’s a simple black screen with a header that states its GNU GRUB, a paragraph in the centre detailing how to use GRUB, and a singular command line for entering commands. I haven’t played around with it much, but I have discovered that using the command exit causes GRUB to “close” and the regular OpenSUSE boot begins. I don’t know why this happened :c
- I would like to have /dev/sdb1/ mounted on startup. uh, how would I go about doing this? I know I can google, and I just did; no matter what question I ask I can’t find the resources to do what I intend to do… somehow :3 [thank you seo!]
thank you in advance for the help ^w^
Hi, welcome to these forums
Re 0.: Run YaST - System - Bootloader, Change the delay to 7 secs, Accept
Re 1: Use YaST’s partition manager and add a mountpoint to it, i.e. mount it f.e. on /data
You have not provided much information, so I can only make a wild guess.
My guess is that you previously had a different system installed. And I am also guessing that this is a UEFI system.
Normally, when you set up a UEFI system, it becomes the boot default. However, some hardware doesn’t follow that, and the BIOS controls the boot order. It looks as if your older system is stuck as first in boot order. When you exit from grub, it then tries the next in boot order.
To change this, you will need to go into BIOS settings and change the boot order.
Please provide the output from:
parted /dev/sdb print
Use the preformatted text option (the “</>” in the editor.
2 Likes
My guess is that you previously had a different system installed. And I am also guessing that this is a UEFI system.
It seems this is exactly the issue! This is actually the third OS installed on the “main” SSD; the first was Tumbleweed, but it had codec issues [the classic that opi fixes]. I thought they were driver issues, installed Mint, realized they weren’t driver issues but rather codec issues, and then re-installed Tumbleweed.
The only issue with fixing this? I’m scared of the UEFI! :3
Because the great and powerful UI designers went “no, why would vertical lists work for boot order? why do we need these dumb words?? we need a horizontal list of literal symbols with zero labels on what they are, with these symbols representing various potential boot drives. There’s no communication on any of their individual attributes - whether they can even be booted into or not - but to hell with it! Those stinky end-users don’t know what’s good for them, they will gain magick powers to know what these random drawings of hard disks and ports mean, and they will love it!!”
So as someone whose had a lifetime of troubles with computers, and lowkey has developed an anxiety disorder with configuring computers in a way that could risk brickage, I’ll have to slowly figure out what is even going on ^w^
But do know that this is certainly the correct solution! At the very least I can avoid the GRUB screen by going into the manual boot menu, and selecting the non-labeled “ubuntu” partition.
Please provide the output from:
Model: ATA WDC WD10EZEX-22M (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 1000GB 1000GB ext4
UEFI is good. There’s no reason to be scared of it.
It is likely that your BIOS interface has a menu item for boot order. And you should be able to change the boot order there. If there is an entry for “opensuse-secureboot” then set that to be first.
For your disk: You can add a line to “/etc/fstab”:
/dev/sdb1 /data ext4 defaults 0 2
Change the “/data” to wherever you want it mounted. And it would be better to change that “/dev/sdb1” to something like:
UUID=1234-5678. You can find the actual UUID to use with
blkid /dev/sdb1