Solved Server wont boot

[ericosman]

Hi all,

I'm setting up a new server, and i think after using the following command:

mkdir /home2
echo "/dev/sdbnvme2n1 /home2 ext4 defaults 1 2" >> /etc/fstab
mount /dev/sdbnvme2n1 /home2

The server doesnt like to boot anymore, now i'm waiting for a KVM console so i can check.
But how would i remove this from the fstab?

 

[Richard G]

But how would i remove this from the fstab?

That's odd. My nvme devices are just named /dev/sda and /dev/sdb but not /dev/sdbnvme2n1 or something like that.

As for your question, just remove the line:
/dev/sdbnvme2n1 /home2 ext4 defaults 1 2
from /etc/fstab and you should be fine after reboot.

Why did you use 1 2 and not 0 0 or 0 1 or something like that? I've read the first 1 is the dump command which is rarely used anymore.

 

[Richard G]

Maybe if the device is correct the first 1 is wrong, unless you installed dump. Normally this is always always always a 0, for many years already.
The 2 is for the file check. So if the device is correct, you could also try 0 2 at the end to see if it boots. But never use 1 in the dump value.

 

[Zhenyapan]

also fstab always must be finished by new line, and looks like you put your text to last line. Try edit file and add to end new empty line

 

[ericosman]

Well, during start i have this
"a start job is running for dev-sdbnvme2n1.device" (..s / 1min 30)"

Then
Timed out waiting for device dev-sdbnvme2n1.device."
Dependency failed for File system check on /dev/sdbnvme2n1
Dependency failed for /home2
Dependency failed for local File systems
Dependency failed for Mark the need to relabel after reboot.


Now i edit the file /etc/fstab
And put a # at the arrows:

https://imgur.com/0xv0Vc0

Now during reboot i get "Failed to mount /home2"

 

[Zhenyapan]

very strange dev-address, remove this string, boot normally without it. check correct UUID and mount it by UUID.
you can check UUID with "blkid" command
like on screen

 

[ericosman]

Now the file looks like this;

https://imgur.com/C1dipiW

So luckly the server itself boots, now lets see why da doesnt boot

 

[Zhenyapan]

and why mount point cropped? where filesystem and mount options? for last line.

 

[ericosman]

I dont understand?

 

[Zhenyapan]

this

 

[ericosman]

Now when i open the file i see "File /etc/fstab is unwritable" eventho i'm sudo

 

[Richard G]

Did you een create a /home2 directory before you started your mount commands?
After /etc/fstab changes in Alma I normally also have to make the final with this command:
systemctl daemon-reload

File /etc/fstab is unwritable" eventho i'm sudo

Most likely your main root system is now mounted as readonly.

 

[Richard G]

Also your third line is wrong, you either use the uid of the disk or the device name, not both.

I have mounted a seperate disk like this (I masked the uuid a bit).
First I create a directory like /backup2 on my / system.
Then added it like this in the /etc/fstab file:

UUID=39edf4f1-xxx-4677-xxx-79a4fd40bd01 /backup2   ext4   defaults   0   0

Then ran the command:
systemctl daemon-reload

And ready. Also works after reboot.

 

[ericosman]

Well, for now this makes me able to boot into alma, now DA doesnt run.
But will see that after i get DA to run (error opening mysql database error=dial tcp 127.0.0.1:3306: connect: connection refused)

Well, it's everything DA related that fails.

 

[Richard G]

Lets go further in pm. Fix original fstab first like suggested. Fix mysql later, first decent boot.

 

[Ohm J]

Your server still in read-only mode, that's why other service can't start/running.

So everything relate or not to DA will all fail.

 

[Richard G]

It's alraedy partly fix via pm with @Zhenyapan and me so everything is running now again as before, but without the extra /home2 partition.
But he will try again tomorrow. I gave some tips for him to test if all is correct, before doing a reboot.

 

[ericosman]

The heroes @Richard G and @Zhenyapan helped me getting my server back online