Greetings,

I have successfully installed and run this JeOS for the Raspberry Pi:

openSUSE-13.1-ARM-JeOS-raspberrypi.armv7l-1.12.1-Build38.1.raw

Dated: 23-Jun-2014

Downloaded from:

http://download.opensuse.org/repositories/devel:/ARM:/13.1:/Contrib:/RaspberryPi/images/

But have noticed odd behavior with the filesystem tree.  Specifically,
running 'mount' produces this output:

<SNIP>
mqueue on /dev/mqueue type mqueue (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
proc on /proc type proc (rw)
configfs on /sys/kernel/config type configfs (rw)
/run on /var/run type none (rw,bind)
/run/lock on /var/lock type none (rw,bind)
<SNAP>

And the output of df -h:

<SNIP>
Filesystem      Size  Used Avail Use% Mounted on
/run            187M  1.1M  186M   1% /var/run
<SNAP>

It would appear that no root filesystem is mounted. And looking at
/etc/mtab we see:

<SNIP>
mqueue /dev/mqueue mqueue rw 0 0
debugfs /sys/kernel/debug debugfs rw 0 0
devpts /dev/pts devpts rw,mode=0620,gid=5 0 0
proc /proc proc rw 0 0
configfs /sys/kernel/config configfs rw 0 0
/run /var/run none rw,bind 0 0
/run/lock /var/lock none rw,bind 0 0
<SNAP>

Additionally, /etc/fstab contains only these entries:

<SNIP>
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc   /proc    proc   defaults        0 0
<SNAP>

Which seems to confirm that there is no root fs.
But if we look at fdisk -l:

<SNIP>
Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes, 15523840 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xa7e6536d

        Device Boot    Start       End      Blocks   Id  System
/dev/mmcblk0p1   *     2048      485383     241668    c  W95 FAT32 (LBA)
/dev/mmcblk0p2         487424    1980415      746496   83  Linux
<SNAP>

The structure looks ok (only missing a swap partition).

If we try to use YaST to resize /dev/mmcblk0p2, we get an error saying
the filesystem seems to be inconsistent.

But then we try to run fsck /dev/mmcblk0 it tells us:
<SNIP>
fsck from util-linux 2.23.2
e2fsck 1.42.8 (20-Jun-3013)
/dev/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
<SNAP>

This, plus the fact that the system runs fine seem to indicate that the
root fs is actually mounted.  I found the situation a bit puzzling, and
would be interested to hear any thoughts on it.

As a side note, it is possible to resize the root partition in a second
computer using YaST and then install software from the on-line repos.

-Alex


-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to