New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/dev/nbdX timed out, dependancy filesystem check failed #31

Open
lilmike opened this Issue Apr 21, 2016 · 8 comments

Comments

5 participants
@lilmike

lilmike commented Apr 21, 2016

Hi,

I have been having a problem with my archlinux c1, where the second volume (/dev/nbd1) failed to mount automatically with /etc/fstab, and causes the boot process to hang for 1 minute 30 seconds, then go into emergency mode.
I added the nofail option to the /etc/fstab, and it boots, but is not mounted.
I added the _netdev and took off the nofail option, and it hangs for 1 min 30s, and then goes to the normal boot, except without /dev/nbd1 being mounted.

From all I have read, either

  1. the device is missing/improperly referenced (which as far as I can tell is not the case), or
  2. the kernel was not configured with CONFIG_FHANDLE=y if building a custom kernel.

I would think you guys would know about this, but that's the only one I can figure out. The /dev/nbd1 device mounts just fine after booting, it just doesn't automatically do so, which breaks some of my programs.

Thanks,
-Michael.

@moul moul added the bug label Apr 21, 2016

@moul

This comment has been minimized.

Contributor

moul commented Apr 21, 2016

Can I see your /etc/fstab ?

@moul moul self-assigned this Apr 21, 2016

@lilmike

This comment has been minimized.

lilmike commented Apr 21, 2016

Hi,
Apart from the comments, my /etc/fstab looks like this:

/dev/nbd0 / ext4  defaults,noatime  0 1
/dev/nbd1 /storage ext  defaults,noatime  0 2

Note that the second line is where I added _netdev or nofail to test.
Thanks,
-Michael.

@moul

This comment has been minimized.

Contributor

moul commented Apr 21, 2016

Ok thanks I will try to reproduce and find a fix for this issue

@moul moul assigned QuentinPerez and unassigned moul Apr 21, 2016

@lilmike

This comment has been minimized.

lilmike commented Apr 21, 2016

It's worth noting that this seems to happen on debian jesse and ubuntu after 14.04, according to the forums. This would be, I guess, when systemd >209 was added to them. Just a thought.
Michael.

Sent from my iPhone

On Apr 21, 2016, at 8:25 AM, Manfred Touron notifications@github.com wrote:

Ok thanks I will try to reproduce and find a fix for this issue


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

@QuentinPerez

This comment has been minimized.

Contributor

QuentinPerez commented Apr 21, 2016

Hi @lilmike

We have the same problem with debian, It works only with ubuntu and nobootwait.
We don't have a good way to fix that but you can use this hotfix.

$> cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>   <dump>  <pass>
/dev/nbd0 / ext4  defaults,noatime  0 1
/dev/nbd1 /storage ext4  rw,suid,dev,exec,nouser,async,nofail,noatime  0 2

$>  cat /etc/systemd/system/automount-nbd.service
[Unit]
Description=automount nbd

[Service]
ExecStart=/usr/bin/mount -a
Restart=on-failure
RestartSec=1s
SysVStartPriority=99

[Install]
WantedBy=multi-user.target

$> systemctl enable automount-nbd.service

Let me know if you need anything else

@lilmike

This comment has been minimized.

lilmike commented Apr 21, 2016

Hi,
Thanks. Can I recommend that this be put on the adding additional volumes help page?
Thanks,
Michael.

Sent from my iPhone

On Apr 21, 2016, at 11:08 AM, Quentin Perez notifications@github.com wrote:

Hi @lilmike

We have the same problem with debian, It works only with ubuntu and nobootwait.
We don't have a good way to fix that but you can use this hotfix.

$> cat /etc/fstab

/etc/fstab: static file system information

/dev/nbd0 / ext4 defaults,noatime 0 1
/dev/nbd1 /storage ext4 rw,suid,dev,exec,nouser,async,nofail,noatime 0 2

$> cat /etc/systemd/system/automount-nbd.service
[Unit]
Description=automount nbd

[Service]
ExecStart=/usr/bin/mount -a
Restart=on-failure
RestartSec=1s
SysVStartPriority=99

[Install]
WantedBy=multi-user.target

$> systemctl enable automount-nbd.service
Let me know if you need anything else


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@lukapaunovic

This comment has been minimized.

lukapaunovic commented Nov 26, 2017

I do not feel like this 'hot-fix' with service is a good fix.
I plan to use /home partition on external NBD disk and what if for some reason it won't boot, that would be a mess on a system.
I think Scaleway should do it in kernel, like they did it with main 50gb OS NBD, so whenever someone attach volume, he should have option to specify mountpoint and then scaleway should add it to kernel.

@camlafit

This comment has been minimized.

camlafit commented Jan 18, 2018

Hello

On debian system we've got same behavior. I've obtained an another workaround from scaleway support explained here :
https://community.online.net/t/automatic-mounting-of-additional-volumes-using-systemd-on-ubuntu/3102

Mounting step is delayed to end process and don't use fstab.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment