Was editing my ssd to have two partitions, restarted my computer and now won't boot, please help :)
 

Hello! I'm not able to boot ��

I was in the process of taking my 2tb ssd and making two partitions, one in xfat and one in xfs. I wanted to be able to access files via windows with the first, and game on the second. Which I think I did this successfully. But then I restarted my computer and now it won't open. So I think it's a mount issue. But I don't know enough about Linux to diagnose the problem myself.

On the black screen with white letters it says:

[0.316196] ACPI BIOS Error (bug): Could not resolve symbol and a bunch of other stuff. But it's too long to type out. I would attach a photo of it if I could.

Thanks in advance!

Welcome to LinuxQuestions.

We need a bit more information. I assume this is a dual boot PC?

What linux distribution are you using?

Is the 2 TB drive where the operating systems are installed?

How did you create the two partitions?

And do you still have the USB you used to create the Linux install ?.

Sounds like you have overwritten the boot loader when changing file systems...re install.

Rubbish - you don't get kernel log if the boot-loader is trashed. Let's get some input rather than knee-jerk "re install" ... :sheesh:

@OP: Ignore the ACPI stuff. Most computers produce ACPI errors when they boot because their BIOSes don't use correct international ACPI code and the Linux kernel gets sniffy over it! But that almost never causes real problems. The errors you need to look at will be reported further down the screen.

As syg00 has pointed out, your kernel has booted but seems to have panicked. I suspect it is having problems finding and using your new root partition. We need to look at the boot report and there are various ways in which you could help us. You could try booting from a rescue image on a stick (your installer image would probably do) and see if the kernel got far enough to at least create a log file for the failed boot in /var/log. If so, you could attach it to a post. If the kernel hasn't been able to write to disk at all, then a photograph of the screen with the final error messages would be the next best thing. There are various sites where you can put up such an image and then provide a link to it.

As a newbie, it will be the quickest way to get up & running again... simple as that...

Yes, but then you haven't learned anything, have you. The first thing I ever learned about Linux is that when it goes wrong, you can usually fix it.

1. No, it's not a dual boot. I'm running linux only.
2. Using Ubuntu 22.04
3. No, my operating system is installed on my laptop's internal hard drive.
4. I created the two partitions via a "Gary Explains" video on youtube, using $ sudo cfdisk /dev/sda

Thanks for your help :)

Yes, I still have the original 30GB usb drive that I used to install Linux.

When did you install that ubuntu?
Did you create those partitions using this ubuntu? I mean you edited the partitions of a living (running) system?

When I boot, the screen comes up with the ability to select Ubuntu, advanced options for ubuntu, and uefi Firmware settings. Then when I attempt to select ubuntu, it almost works, and then this line of text appears, I've uploaded a photo of it at this link: https://imgur.com/a/1ZXveW7

As for the /var/log, is that something I'm able to access from the command line/grub by chance?

I installed ubuntu on my computer several months ago. And I created partitions on an external 2T ssd, not on the computer's hard drive. That's why I was surprised that I messed something up with my computer since I was changing the ssd, not my actual computer. I suspect this is a mount issue.

Are you sure it is your external 2TB SSD?

Using the USB live version post the output of the command lsblk.

Since you are not dual booting there is no need to create a separate partition for Windows but still not enough information as to what you are trying to accomplish nor why the additional xfs partition. Ubuntu uses ext4 by default.

I missed the post where the 2TB drive was external. I see the internal drive is nvme.