/ not mounting, or?

[FullyP]

I have this in my fstab:
/dev/mmcblk0p1 /boot vfat defaults 0 0
/dev/mmcblk0p2 / ext4 defaults 0 1
UUID=1d646bc9-61b6-4f70-890b-cfc97c793716 /home ext4 defaults 0 0

but when I run 'lsblk -f' I get:
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
└─sda1 ext4 1d646bc9-61b6-4f70-890b-cfc97c793716 /home
mmcblk0
├─mmcblk0p1 vfat 44C8-CEF1 /boot
└─mmcblk0p2 ext4 fcee8534-f5f0-42ee-83ac-f943f878ee67

My / is not showing up on mmcblk0p2. However if i do 'mount | grep root I get:
/dev/root on / type ext4 (rw,relatime,data=ordered)

Is my / mounted on my second partition or not? Should I even care?

[sdjf]

mine looks like this, I think you are okay.

/dev/root on / type ext4 (rw,relatime,data=ordered)

But I think you would be able to see how everything is mounted better with the df command:

df -h

[maribu]

Hi, FullyP!

Your "/" is mounted. You configuration is fine.

An interesting fact: Your second partition of your SD-Card contains your complete system. Only the kernel and boot configuration is stored under the first partition of your card. If the second partition wouldn't mount under "/", your Pi would crash at boot up. The fact that you can type "lsblk -f" means, that you have mounted "/".

I think the reason "/" is not shown by "lsblk -f" and mount shows "/", but refers to "/dev/root" instead of "mmcblk0p2" is this: The root partition is not configured via /etc/fdisk but via command line in Arch Linux.

Look here:

Code: Select all

cat /boot/cmdline.txt 
smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=noop rootwait

and here:

Code: Select all

cat /etc/fstab 
# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
/dev/mmcblk0p1  /boot           vfat    defaults        0       0

you could add this line to /etc/fstab

Code: Select all

/dev/mmcblk0p2 / ext4 defaults 0 1

and then remove "root=/dev/mmcblk0p2 rootfstype=ext4" from cmdline. This way I think the output from "lsblk -f" would be "more correct". BUT: YOUR SYSTEM WOULDN'T BOOT WITHOUT INITRAMFS with this configuration (please correct me if I'm wrong, pepedog). And currently Arch Linux ARM uses no initramfs on the Pi (which is faster).

There is another reason except more readable output of mount for an initramfs: Currently the automatic filesystem check are handled via a hook in the initramfs. So there are no file system checks at boot in Arch Linux ARM at the moment. Maybe I will post configuration files (https://wiki.archlinux.org/index.php/Mkinitcpio) needed to run the Pi with an initramfs. But I'm not sure if I really want to slow down the most excellent boot up time of my Pi.

Regards,
Maribu

[pepedog]

Coincidence? I have been messing with initramfs on a cubox.

[KwaXi]

Is there any progress an this issue? There are some other tools which are confused, too.

E.g. quota can't be enabled because quota-tools can't deal with this situation.

Is there a special reason why udev doesn't simply create a symlink rootfs -> mmcblk0p2, which might solve the issue?

[pepedog]

Sorry, I'm going to sit back and wait for someone to tell me if I need change anything.
Or maybe collaborate.