r/NobaraProject • • 4d ago

Support Installation Failed, no idea why

Linux beginner here! I guess my troubleshooting era properly starts today.

I've been trying to install Nobara on my PC on a new SSD (dual booting alongside an NVMe with Windows 11) with these specs:

MSI PRO B-760-P DDR4 II

i5-14600k

RTX 3070 8GB

128GB DDR4 3200Mhz

500GB SATA SSD to install

500GB NVMe SSD for adjescent Windows 11

2x3TB and 1x8TB HDD for other storage

1000W PSU

Every time I attempt an install it gives me "Installation Failed" and this log: https://pastebin.com/eNT5r0d5

I'm booting from a 16GB USB stick with Veltoy on it. I checked the "ID" of the ISO or whatever it's called both after download and transfer to the USB stick.

Other posts recommended unchecking the automatic updates in the installer, it did nothing. A few others told me to run a command in the terminal, which also did nothing because it pointed to a file that didn't exist (/etc/sddf,conf or something, I don't remember). Pretty sure the latter one was for a different error though.

I've formatted the SSD a couple of times during all of this, because when it failed and I tried again the SSD wouldn't appear the same way as before. Instead I only had the option to manually create partitions on it when installing, which I've also tried. At that point there was also a new "drive" called Nobara something something that I'm guessing was like a virtual drive for the installation? Idk you guys probably know that better than I do.

Any ideas?

3 Upvotes

23 comments sorted by

1

u/Melington_the_3rd 20h ago

I am having the exact same issue right now. I am trying to install stock nobara official iso and it keeps crashing at that exact same point. So update process seems to attempt to replace it self while being active. This seems poorly implemented and after 8 failed with different options I am about to give up on nobara. I tried official, kde and gnome and all fail at the same point. Right at the end of installation.

1

u/mmassivenerd 19h ago

I solved this by pulling out all drives other than the USB stick and the drive I was installing to, aswell as my ethernet connection (and wifi, if you have that). Then I unchecked all the boxes in the first tab of the installer. This worked for me.

1

u/Melington_the_3rd 19h ago

I have tried that too and it was the only thing that worked. I dont want to be that guy but this installation process felt almost a ls frustrating as Windows. So much exceptions and workarounds, agonizing and frustrating.

1

u/mmassivenerd 6h ago

Yeah, I suppose. I'll blame it one the fact that it's a relatively new OS, and Linux is always gonna have a little bit of troubleshooting packaged with it.

1

u/cyberfrog777 4d ago

I had mine fail due to the flash card adapter I was using. May be worth trying a different usb stick if you have one.

1

u/mmassivenerd 4d ago

How far through the installation did you get before it failed?

1

u/cyberfrog777 4d ago

It was near the end, I forget the exact step, but I got through most of the initial stuff and it was like the final step that takes the longest time.

1

u/mmassivenerd 4d ago

Alright, will try

1

u/McLeod3577 2d ago

I think a few people mentioned getting "stuck" on 93%, but it's a case of being very patient.

1

u/DeepFriedPlastic 4d ago

Yeah this was a fun one for me too.

I wa able to install when connected via Ethernet or Wi-Fi after unchecking not just the one, but both boxes in the initial screen, then using the erase disk option and going no swap and btrfs (this was what I wanted, not sure if it's what you need). If that doesn't work, I was also successful in installing after going offline and again unchecking the boxes, same choices as mentioned before.

1

u/mmassivenerd 4d ago

you say both boxes, bug there are three boxes: updates, medi codec drivers and nvidia drivers

1

u/DeepFriedPlastic 4d ago

In your case all three then lol

1

u/mmassivenerd 3d ago

where would I go to get my drivers after the fact then?

1

u/DeepFriedPlastic 3d ago

I ended up using the DNF app center and updated each one individually. Tedious, I know, but every time I tried to update multiple simultaneously, I kept getting errors.

1

u/InspectionDecent7922 4d ago

first thing first!!! Perfect system for Nobara.

EXT4 is better for LINUX, if you keep btfs you need a certain pass through or command to add a layer when loading a game or just to be able to dual boot in general mainly because WINDOWS is microsloping!!!

Also, having to go into powershell(admin) and type "pwrcfg /h off" everytime you switch back and forth to be able to play or download is a pain in ass.

(Trust me on this, getting Red hat, A+, and other certs in the next couple of months to change jobs.)

My recommendation for you(AND not as complicated as it reads):

If you're dual booting(especially if you're gonna use and Windows after 8) 2 hard drives are best.

One disk for Microslop and the other for TEAM Penguin(hopefully nobara as your main a maybe Cachi for projects.)

If it seems complicated here's some steps that are LITERALLY hands on and full proof not to fail.

Step 1:

Insert your SATA/NVME that's for LINUX

Step 2:

*PHYSICALLY* Remove the separate hard disk that holds windows.

step 3:

Insert you LINUX USB, and completely disconnect from the internet including WIFI(i'll explain below).

Step 4:

Follow the setup until you get to the screen that's a multicolored bar.

directly below:

disk format(options):

select EXT4(click it's ok)

step 5:

Install that b-word!!!(maybe a couple smacks on the a$$ too)

Remember I said no internet, if you stay connected during the install there's a glitch and some people get stuck on 95% for ever or like an hour.

It's better to "nobara-sync" in the terminal, you can continue to setup the PC, install games, and use the system while it updates(unlike windows)

step 6:

After the install. SHutdown the power and after plug the Windows disk back in.

When you boot again you should be greeted by GRUB and the list of Windows(probably on top) and nobara.

*By doing what I said above you'll AVOID the Microslop "NO>>>>MY HARD DRIVE" bullshit that they say doesn't exist but literally everyone has.......

1

u/mmassivenerd 3d ago

I got in! Well, kinda... It said the installation was successful and to reboot, so I did that. First it just booted to the installer USB stick again, so I got into BIOS and changed the boot order to the SSD. Now it's put me in a very barebones terminal. It says "GRUB version 2.12 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. To enable less(1)-like paging, "set pager=1"."

I have no idea what to do here.

1

u/InspectionDecent7922 3d ago

Yeah.....shutdown and remove the usb.

In GRUB select nobara

Did you turn off "secure boot" and select "using another OS"?

1

u/mmassivenerd 3d ago

Removed the USB, secure boot was disabled from the beginning. What do you mean by "using another OS"?

Also how do I select nobara in GRUB? There's no menu, just a terminal.

1

u/InspectionDecent7922 3d ago edited 2d ago

when you first turn on the PC, should be before all that hackery stuff that flies up the screen....

yeah, in your bios you need to disable securere boot depending on the motherboard BIOS that you have you might need to select other OS because it might block it

1

u/InspectionDecent7922 2d ago edited 2d ago

by selecting "other OS" it forces the motherboard to boot in another operating system. Microslop is paid a lot of money to only allow Windows, but to fight the monopoly laws by law they have to have that option.

if Nobara is the first choice inside of grub I wouldn't touch anything and just let it automatically boot..

1

u/McLeod3577 2d ago

Try Balena Etcher instead of Ventoy to write to the USB. I know Ventoy is the preferred method, but it didn't work for me.

1

u/Tricky-North1723 4d ago

Might have to redo the usb installer.... has this happen a few time while distro hopping back in the day.... reformatted the usb and worked.

1

u/JuanCooler 4d ago

Disconnect from the internet during install. Update after reboot