/etc/fstab down't work with RPI2

[pirulloz]

Hello,

/etc/fstab doens't work in RPI2. Simply it doesn't mount anything.

You can see here a lot of people with this problem:
http://www.raspberrypi.org/forums/viewtopic.php?f=28&t=99491

[notro]

It does at least mount nfs for me on RPI2:

192.168.10.92:/home/pi  /home/pi/work   nfs     rw      0       0

[popcornmix]

@pirulloz
Does same /etc/fstab mount okay on Pi1 with 3.18 kernel?

@notro any guesses?

[pirulloz]

Yes, with 3.18.6+ on RPI1 it works good.

[popcornmix]

Can you add maxcpus=1 to end of cmdline.txt and report if it works?

[pirulloz]

I've tried. With that command it works fine.....

But now am i limited to 1 core? I don't know how that line works

[popcornmix]

Yes, my suspicion was that /etc/fstab is being parsed before the disks have been identified (possibly through different parts of boot being done in parallel). There must be a way of ensuring /etc/fstab only occurs after disks are identified...

[pirulloz]

ok.... i understand..... so i wait for a patch from you :)

If you need some support please let me know. I can do some tests.....

[notro]

Similar issue: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/367782

[popcornmix]

@pirulloz
can you remove maxcpus and add rootdelay=10 to cmdline.txt?
If that fixes it does a smaller number work?

I've got a USB ssd disk here, but it seems to be mounted just fine (without any cmdline.txt changes)

[rutger1140]

@popcornmix rootdelay=10 makes /etc/fstab work for me. Will try with lower values later on.

[pirulloz]

With rootdelay=10 it works fine.
With rootdelay=5 it works fine
With rootdelay=2 it doesn't work

[keithellis74]

I can confirm rootdelay=5 works fine for me.
Just as a bit of background, I did not have this problem with kernel 3.18.5 but when upgrading to 3.18.7 was when the issues started. All kernel versions worked find in a Pi rev 2 model B

[popcornmix]

@keithellis74
Can you confirm that downgrading kernel avoids the requirement of rootdelay?

Look here: https://github.com/Hexxeh/rpi-firmware/commits/master
each firmware update has a git hash (hex number) at the end of the URL. Run:

sudo rpi-update <hash>

To get a specific version. E.g.

sudo rpi-update 96f2257f57196817ebb030096993823be721fb27

will get the initial 3.18.5 kernel. Try to identify the first kernel that fails to mount disk without rootdelay.

[keithellis74]

Hi, just tried to downgrade to 3.18.5 and get the following error.

*** Updating kernel modules
cp: cannot start '//root/.rpi-firmware/modules/*': No such file or directory

Keith Ellis

On 16 Feb 2015, at 14:14, popcornmix notifications@github.com wrote:

@keithellis74
Can you confirm that downgrading kernel avoids the requirement of rootdelay?

Look here: https://github.com/Hexxeh/rpi-firmware/commits/master
each firmware update has a git hash (hex number) at the end of the URL. Run:

sudo rpi-update
To get a specific version. E.g.

sudo rpi-update 96f2257f57196817ebb030096993823be721fb27
will get the initial 3.18.5 kernel. Try to identify the first kernel that fails to mount disk without rootdelay.

—
Reply to this email directly or view it on GitHub.

[keithellis74]

Ok, I had a play about this morning. I downgraded to 3.18.6 using commit 3f11b3fb1f390b60daa22f2ca2ecda5266295a84 and still had the same problem. It booted using rootdelay=5 but once removed it failed to boot again.

I then tried to downgrade to 3.18.5 using commit 67197d9d73c56570578cb2c6c188af263a37ecd9 (with the missing modules) This applies without any errors but upon reboot with rootdelay=5. uname -a reports kernel version 3.18.6 which is rather confusing. When rootdelay=5 is removed is fails to boot agian.