"You are in emergency mode." Editing fstab - UUID instead of label

I have set up an LVM on a RAID10 with the generous help of computersavvy. Running a headless openmediavault5 server.

I was setting up my folder system through the OMV5 interface on the RAID10 LVM through PuTTy from my Windows10 machine and then rebooted. Then I couldn't get back in to the server.

Broke down and made a hard shutdown of the server and added monitor, keyboard and mouse and restarted. Got an error.

After some research, it appears that maybe the UUID needs to be used instead of the label in the fstab. Never edited it before. Trying to get familiar with Vi.

I am a noob and don't know if I am on the right track. If I am not please advise.

Did you create an mdadm.conf file? That's what is used to automatically assemble your array. You should also set up mdadm monitor to notify you if a disk fails.

Originally Posted by CJBIII After some research, it appears that maybe the UUID needs to be used instead of the label in the fstab. Never edited it before. Trying to get familiar with Vi.

It seems that the UUID is not found. Run blkid or lsblk -f to find the correct UUID. If you set a label on that filesystem, it will also be printed.

If you are afraid of vi, use nano, or sed:

sed -i s/INCORRECTUUID/CORRECTUUID/ /etc/fstab

(replace the all-caps text with appropriate values)

Instead of repairing the UUID, you can also comment that line in fstab, which allows the server to boot. Then repair it in the more comfortable multi-user environment.

If the RAID has not been assembled, you need to assemble it first, as smallpond remarks.

Better make a backup copy of fstab (or any other file) before trying to edit it.

EDIT:

I had not seen the blkid output among your screenshots. Yes, there is an unassembled MD RAID array. Since it is not assembled, the LVM structures on top of the RAID are not detected, and the filesystem on top of LVM isn't either.

I would start by commenting the line with UUID 2450... from fstab, boot normally, and work on the RAID problem when the system has started.

This command:

sed -i.bak '/UUID=245044/s/^/#/' /etc/fstab

copies /etc/fstab to /etc/fstab.bak, then inserts a hash sign in front of the offending line. This should allow you to boot normally.

In addition the output of blkid does not show the /dev/md0 as a LVM member or any logical volumes. As stated make sure the RAID is assembled and active.

Look at the output of the command:

cat /proc/mdstat
or
mdadm --detail /dev/md0

Once that is confirmed look at the output of the command
pvdisplay

These are the outputs for all of the requested.

I am looking to output pvdisplay, lvdiplay and vgdisplay. When I can I will post if needed.

I think I am in emergency.target mode, if that effects anyone's advice.

Physical Volume from sda-sde (md0) in a RAID10, Volume Group (mediaVG) and Logical Volume (mediaLV) were all created in LVM2 last week. ext4 was the file system.

I attempted to place my files in a folder (which I created called /one) through the graphical browser of openmediavault from a Windows10 machine. Many steps were done through OMV following online advice. When I rebooted I could no longer get into the server through PuTTY. I shutdown the computer the only way I could think of, hard, and I hooked up a monitor, keyboard and mouse and this is where I am.

Appreciate all the help.

I believe I understand. You created a GPT partition table and partitions within the RAID and within partition 1 created the LVM. As far as I know this does not work. You can create partitions on a RAID but that is accomplished when it is created.

https://raid.wiki.kernel.org/index.php/Partitionable

However, is a LVM or logical volumes necessary? If you really want LVM I would suggest following the Arch wiki
https://wiki.archlinux.org/index.php..._software_RAID

If not create a filesystem directly on the RAID.

You should partition the drives and then create RAID from the partitions. Creating whole-drive RAID means there are no labels on the drives, so no way to find boot information. The platform firmware does not understand Linux RAID so the EFI partition needs to be non-RAID as well.

As far as I know it should not matter since the RAID is just a data drive.