Static mount causes crash on restart

Node Operators troubleshooting
1

if I follow the static mount directions and add my STORJ hard drive to the etc/fstab file I end up in emergency mode if I restart the PC.

This is what my etc/fstab file looks like:

Screenshot from 2022-12-17 13-19-14
Screenshot from 2022-12-17 13-19-141246×497 42.6 KB

And this where I end up upon restarting:

Screenshot from 2022-12-16 23-54-09
Screenshot from 2022-12-16 23-54-09848×153 44.3 KB

From emergency mode I can edit the etc/fstab file and delete the line for the STORJ drive. Then I can reboot and get into ubuntu just fine. From there I can just put the STORJ drive line back into the fstab file and run “mount -a.” In other words, I currently have a work around to keep the node up and the PC running.

However, this work around is not ideal because while the PC is an “always on” PC there is still the potential for a brown out or something else causing the PC to restart. Ideally the node is up and running on start up.

I also cannot seem to figure out what’s causing my QUIC to be misconfigured. I don’t think the issues are related but I’m not an expert on node operating or computers by any means

Anyone have any ideas on what might be the problem?

Thanks in advance.

2

For some reason your /mnt/STORJ file system is just not available early enough during the boot process. There might be many such reasons, you probably need to look into logs (journalctl, dmesg and such) to find out why.

What is the Linux distribution you are using? Can you post the output of lsblk (you may limit it to the drive with /mnt/STORJ)?

3

you can add two options to the fstab: ‘x-systemd.device-timeout’ and ‘nofail’

the first one waits for the specified time for the drive & the second allows the continuation of the booting in case that the device is not ready

like this:

UUID=xxxxx /mnt/storj ext4 defaults,nofail,x-systemd.device-timeout=30s 0 0

try playing with different timeouts to ENSURE that the disc is mounted, because if the node starts automatically at the end of the system boot, it will be missing its path and probably fail.

2 Likes
4

@mgonzalezm your suggestions was successful including mounting on start up!! Thank you kindly for your help.