Lost my m-2 boot drive installed on endeavour z97-a board

Okay well if the other is RAID then I don’t know? I’m not sure how you set all this up? Was the other m.2 drive added later?

Sorry I’m a little slow at typing

no before.

So was the m.2 drive there in the boot order before?

yes

AHA so I’ll Check that.

Looks like I replied in the wrong place. I was referring to your post on the Iso whether it was MBR or UEFI

So the samsung is set up in raid. No wonder i didn’t understand the output. Did you set that up on Windows? Before Linux was installed?

no after I installed Endeavour.

Did you use the utility in the Bios to do that?
Edit: The reason I’m asking is setting up raid on linux isn’t that easy.

Can you give me the output of

sudo fdisk -l

Why can’t you post this?

Not sure what bumped out the drive and it doesn’t show up. What ever you decide if you end up reinstalling at some point make sure you UEFI settings are correct to give you a UEFI install. I’ve given you my opinion on the BIOs settings. Other OS, which turns off secure boot, and set CSM to Auto. Then when installing check the installer screen to make sure it’s installing in UEFI mode.

Edit: When the live ISO boots on MBR it’s a totally different look than UEFI. You can’t mistake it.

I don’t think so.
I’m getting the go private thing. Want to call it a night? But I will still check out partitioning on that nvme.

You don’t think so what?

sorry missed this one.

my head hurts!!! That was reply to a previous post.

I don’t know how to get to the post where I said I don’t think so.

sudo fdisk -l 

[bobcapp@ASUSZ97-A ~]$ sudo fdisk -l
[sudo] password for bobcapp:
Disk /dev/nvme0n1: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: KINGSTON SA2000M8250G
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: 0xf20a03f7

Device Boot Start End Sectors Size Id Type
/dev/nvme0n1p1 * 2048 488392064 488390017 232.9G 83 Linux

Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000LM007-1R81
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sdb: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SAMSUNG SSD PM84
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/sdc: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SAMSUNG SSD PM84
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/sdd: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SAMSUNG SSD PM84
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/sde: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SAMSUNG SSD PM84
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[bobcapp@ASUSZ97-A ~]$

Thanks. It’s definately installed in MBR (DOS)

Disk /dev/nvme0n1: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: KINGSTON SA2000M8250G
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: 0xf20a03f7

Device Boot Start End Sectors Size Id Type
/dev/nvme0n1p1 * 2048 488392064 488390017 232.9G 83 Linux

Like i said i don’t know the reason the drive isn’t showing up in the boot devices order. I can only tell you it’s not installed in UEFI so therefore it’s not a GPT partition and you can’t take advantage of the things that UEFI offers either such as efibootmgr etc. If you at some point reinstall then make sure as i pointed out above settings in Bios and check that it’s actually booted in UEFI on the live ISO and is going to install in UEFI mode.