Desktop boots to BIOS, no drives detected

My desktop has 5 drives. Everything was working super happy. One of those drives had movies, I accidentally unmounted it. Somehow I buggered up trying to remount it.

Now it boots into BIOs, says No Drives Detected when I check boot drives.
I have changed bios to UEIF which hasn’t done anything. Secure boot is disabled:

I would have had the most up-to-date stable on my drive.

I can boot into manjaro using my USB key, but as its super limited (no network, many features not installed) I cant figure out what to do to get everything back up and running again. I can see the /boot/efi partition and its mounted.

While attempting to fix, I most likely messed up the fstab file and am unsure how to fix that back to default

I have no idea what to try next. Please help.

can you boot on USB iso manjaro
open an terminal

inxi -Fza 
sudo parted -l
sudo lsblk -fs
sudo efibootmgr -v
test -d /sys/firmware/efi && echo efi || echo bios
sudo manjaro-chroot -a ( type 1 if only one line 0 )
cat /etc/fstab
exit ( quit chroot )

Thank you. Im still pretty nooby. I received an error stating -Fza doesn’t work.

I apologise for the potato pic, I don’t have any network when booting from usb

apparently I also cant post a pic of the error or a link to it. imgur. com /a/r6Sp3Zh

going to try to copy it out:

Error 7: One of the options you entered in your script parameters: -Fza is not supported. The option may require extra arguments to work. For supported options (and their arguments), check the help menu: inxi -h bio sudo manjaro-chroot -a cat /etc/fstab exit

Since you seem to have a phone could you use tethering to enable network connectivity?
First things first lets see what we have here as a system.Please provide the outputs of the commands
sudo inxi -Fazy
sudo parted -l
sudo lsblk -fs
sudo efibootmgr -v

[skaboomatude@skaboomatude-pc Desktop]$ sudo inxi -Fazy

/usr/bin/inxi: illegal option – a
Error 7: One of the options you entered in your script parameters: -Fazy
is not supported.The option may require extra arguments to work.
For supported options (and their arguments), check the help menu: inxi -h
[skaboomatude@skaboomatude-pc Desktop]$ sudo parted -l
Model: ATA ST4000DM000-1F21 (scsi)
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 135MB 134MB ext4
2 135MB 4001GB 4001GB ntfs Basic data partition msftdata

Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 2098kB 317MB 315MB fat32 boot, legacy_boot, esp
2 317MB 232GB 231GB ext4 Main SSD boot, esp
3 232GB 250GB 18.3GB linux-swap(v1)

Model: ATA ST4000VX000-1F41 (scsi)
Disk /dev/sdc: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
2 317MB 4001GB 4000GB ext4

Model: ATA WDC WD40EFRX-68W (scsi)
Disk /dev/sdd: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: pmbr_boot

Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB ntfs 4tbdrive msftdata

Model: ATA WDC WD20EFRX-68E (scsi)
Disk /dev/sde: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 2000GB 2000GB ntfs

Model: Generic Flash Disk (scsi)
Disk /dev/sdf: 2013MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32.8kB 1706MB 1706MB primary boot
2 1706MB 1710MB 4194kB primary esp

[skaboomatude@skaboomatude-pc Desktop]$ sudo lsblk -fs
NAME FSTYPE LABEL UUID MOUNTPOINT
sda1 ext4 7636d0ba-f716-480f-8911-608911173be6 /run/media/skaboomatude/7636d0ba-f716-480f-8911-608911173be6
└─sda
sda2 ntfs Uber Mega Bad Ass Drive C2B60143B6013985 /run/media/skaboomatude/Uber Mega Bad Ass Drive
└─sda
sdb1 vfat 99BE-629F
└─sdb
sdb2 ext4 d3ae9244-6b18-4f52-a155-c3959a4844ef /
└─sdb
sdb3 swap ffd5119e-1e13-4172-a6d4-0c983de01ea7 [SWAP]
└─sdb
sdc2 ext4 95f33ce0-ed81-47d8-93b1-0c3978b9ffb7 /run/media/skaboomatude/95f33ce0-ed81-47d8-93b1-0c3978b9ffb7
└─sdc
sdd1 ntfs 6A421778561C27DE /run/media/skaboomatude/6A421778561C27DE
└─sdd
sde ntfs red 089FC59901AFE458 /run/media/skaboomatude/red
sdf1 iso9660 MJRO1705 2017-09-16-10-13-30-00 /run/media/skaboomatude/MJRO1705
└─sdf iso9660 MJRO1705 2017-09-16-10-13-30-00
sdf2 vfat MISO_EFI 7723-A0BA
└─sdf iso9660 MJRO1705 2017-09-16-10-13-30-00
[skaboomatude@skaboomatude-pc Desktop]$ sudo efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002
Boot0001* UEFI: Generic Flash Disk 8.07 PciRoot(0x0)/Pci(0x14,0x0)/USB(10,0)/CDROM(1,0x32d884,0x8000)…BO
Boot0002* UEFI: Generic Flash Disk 8.07, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(10,0)/HD(2,MBR,0xaa3126b4,0x32d884,0x2000)…BO
[skaboomatude@skaboomatude-pc Desktop]$ ^C
[skaboomatude@skaboomatude-pc Desktop]$

  • maybe sda1 was a fat32 /boot/efi for windows , it has be formatted by ext4 ,
    you will need a USB iso windows for repair if this was the case

  • with gparted change , sdb1 for flag boot & esp only (remove legacy_boot ) ,
    for sdb2 remove flag boot & esp

  • missing entry boot in EFI you will need this under chroot

sudo manjaro-chroot -a ( type 1 if only one line 0 )
efibootmgr -c -d /dev/sdb -p 1 -L "Manjaro" -l "\EFI\Manjaro\grubx64.efi"
efibootmgr -v
exit ( for end chroot )

I would rather just reformat again than deal with windows in any form. I’ll see if I can format the SSD again with a different Manjaro ISO and start over.
I’m just amazed how me borking one file caused all this lol /facepalm

Please do continue. What file did you bork? I saw you writing something about the fstab file.
If possible could you post the content of it?

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=99BE-629F                            /boot/efi      vfat    defaults,noauto,x-systemd.automount 0 2
UUID=d3ae9244-6b18-4f52-a155-c3959a4844ef /              ext4    defaults,noatime,discard 0 1
UUID=ffd5119e-1e13-4172-a6d4-0c983de01ea7 swap           swap    defaults,noatime,discard 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

Is there a way to just backup my settings/drivers somewhere and just re-install? I think nuke and pave might be the easiest option