NOOBS and partition question

[chadw]

Hello,

I used NOOBS 1.4 to setup a multi-boot SD card.
This works well, my Pi can boot Raspbian or OSMC.

However, on my Ubuntu laptop I have no way to mount one of the partitions.

Code: Select all

$ sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes
4 heads, 32 sectors/track, 121280 cylinders, total 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 identifier: 0x1660e00a

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            8192     1673828      832818+   c  W95 FAT32 (LBA)
/dev/mmcblk0p2         1679360    15333375     6827008    5  Extended
/dev/mmcblk0p3        15333376    15398911       32768   83  Linux
/dev/mmcblk0p5         1687552     1810431       61440    c  W95 FAT32 (LBA)
/dev/mmcblk0p6         1818624     9713663     3947520   83  Linux
/dev/mmcblk0p7         9715712     9879551       81920    c  W95 FAT32 (LBA)
/dev/mmcblk0p8         9887744    15325183     2718720   83  Linux

/dev/mmcblk0p6 is raspbian root partition, which mounts.
But I can't mount /dev/mmcblk0p8 on which OSMC is installed.

$ udisksctl mount -b /dev/mmcblk0p8
yields:
Error looking up object for device /dev/mmcblk0p8

$ sudo mount /dev/mmcblk0p8 /mnt/temp
yields:
mount: special device /dev/mmcblk0p8 does not exist

and GParted displays an error message too.

Do you have any idea what's going on ?

[beta-tester]

do you use ubuntu 15.04 on your desktop PC?
i have a similar problem since i dist-upgreadet to ubuntu 15.04 (from ubuntu 14.11)
viewtopic.php?f=28&t=105437

[chadw]

Ubuntu 14.04.2 on my PC.

[lmarmisa]

Devices names are different in RPi and laptop. You should use the correct names.

Use the names in Ubuntu according to the output of the command sudo fdisk -l. Yes, repeat the command in Ubuntu. They will be /dev/sdx for devices and /dev/sdxy for partitions. Names as /dev/mmcblk0 make no sense in your laptop.

[chadw]

Devices names are different in RPi and laptop. You should use the correct names.

Use the names in Ubuntu according to the output of the command sudo fdisk -l. Yes, repeat the command in Ubuntu. They will be /dev/sdx for devices and /dev/sdxy for partitions. Names as /dev/mmcblk0 make no sense in your laptop.

Output of "sudo fdisk -l" on ubuntu:

Code: Select all

[...]
Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes
4 heads, 32 sectors/track, 121280 cylinders, total 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 identifier: 0x1660e00a

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            8192     1673828      832818+   c  W95 FAT32 (LBA)
/dev/mmcblk0p2         1679360    15333375     6827008    5  Extended
/dev/mmcblk0p3        15333376    15398911       32768   83  Linux
/dev/mmcblk0p5         1687552     1810431       61440    c  W95 FAT32 (LBA)
/dev/mmcblk0p6         1818624     9713663     3947520   83  Linux
/dev/mmcblk0p7         9715712     9879551       81920    c  W95 FAT32 (LBA)
/dev/mmcblk0p8         9887744    15325183     2718720   83  Linux

[jojopi]

After inserting the card into the Ubuntu laptop, does "dmesg" show the same "mmcblk0: [CUMANA/ADFS] p1 [ADFS] p1" message that was reported in the other thread?

Can you confirm whether RISC OS is one of the systems currently installed on the card, or if it had previously been?

[chadw]

dmesg:

Code: Select all

[91463.467299] mmc0: cannot verify signal voltage switch
[91463.580376] mmc0: new ultra high speed SDR50 SDHC card at address aaaa
[91463.580603] mmcblk0: mmc0:aaaa SL08G 7.40 GiB 
[91463.589684]  mmcblk0: p1 p2 < p5 p6 p7 > p3
[91463.777081] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[91463.874592] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)

To my knowledge only Raspbian and OSMC have ever been installed on this card.

[DougieLawson]

To my knowledge only Raspbian and OSMC have ever been installed on this card.

That's consistent with the dmesg stuff you've posted.

P1 is NOOBS boot
P3 is NOOBS recovery
P5 is Raspbian boot
P6 is Raspbian root
P7 is OSMC

[chadw]

No.
p1 is RECOVERY (fat32)
p3 is SETTINGS (last one from top to bottom in gparted)
p5 is Raspbian boot (boot0)
p6 is Raspbian root
p7 is OSMC boot (boot-rbp2)
p8 is OSMC root (gparted shows a red exclamation mark)

[DougieLawson]

Partition#8 wasn't detected when you booted Raspbian.

[lmarmisa]

Curious. This is the equivalent output on my Ubuntu:

Code: Select all

..
Disk /dev/sdd: 16.0 GB, 16009658368 bytes
64 heads, 32 sectors/track, 15268 cylinders, total 31268864 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 identifier: 0x000e642a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1            2048      133119       65536    c  W95 FAT32 (LBA)
/dev/sdd2          133120    31137791    15502336    5  Extended
/dev/sdd3        31137792    31268863       65536   83  Linux
/dev/sdd5          135168      659455      262144    c  W95 FAT32 (LBA)
/dev/sdd6          661504    10901503     5120000   83  Linux
/dev/sdd7        10903552    11427839      262144    c  W95 FAT32 (LBA)
/dev/sdd8        11429888    21669887     5120000   83  Linux
/dev/sdd9        21671936    22196223      262144    c  W95 FAT32 (LBA)
/dev/sdd10       22198272    31137791     4469760   83  Linux

If the problematic partition is not mounted, you can run the command fsck. This example will cause fsck to avoid attempting to repair any problems, but simply report such problems:

Code: Select all

sudo fsck -fn /dev/mmcblk0p8

[chadw]

Even though fdisk listing shows a p8 partition, there is no such thing as /dev/mmcblk0p8: it's missing.

I will try to boot on some livecd or liveusb system later to see whether it makes a difference.

[lmarmisa]

If you are able to boot into raspbian and OSMC, the partition /dev/mmcblk0p8 is not missing. This is the root partition of your system #2. Its kernel is stored in the fat partition /dev/mmcblk0p7.

Anyway. If I remove the sd from my RPi, and I insert it on my laptop running Ubuntu, the device name assigned to the sd device is /dev/sdd. Your case seems different because the RPi name remains the same. Do you move your SD from RPi to laptop too or are you connected to RPi from your laptop with ssh?.

[chadw]

If you are able to boot into raspbian and OSMC, the partition /dev/mmcblk0p8 is not missing. This is the root partition of your system #2. Its kernel is stored in the fat partition /dev/mmcblk0p7..

Right, but I meant it's missing from /dev when the sd card is plugged into the ubuntu laptop.

Anyway. If I remove the sd from my RPi, and I insert it on my laptop running Ubuntu, the device name assigned to the sd device is /dev/sdd. Your case seems different because the RPi name remains the same. Do you move your SD from RPi to laptop too or are you connected to RPi from your laptop with ssh?.

I plug the sd card in my laptop.

[beta-tester]

Ubuntu 14.04.2 on my PC.

even ubuntu 14.04.2 shows up that issue...
(ubuntu 14.04 of 2014 not)
i opened a bug-report on ubuntu and will see, what will happen...
https://bugs.launchpad.net/ubuntu/+sour ... ug/1457526
ubuntu 12.04 (LiveDVD from 2012) -> ok,
ubuntu 14.04 (LiveDVD from 2014) -> ok,
ubuntu 14.04.2 (LiveDVD from 2015) -> failed,
ubuntu 15.04 (LiveDVD from 2015) -> failed,
debian 8.0.0 (LiveDVD from 2015) -> ok.

[jojopi]

even ubuntu 14.04.2 shows up that issue...

This is not the same problem as in the other thread. Your problem is that Ubuntu ignores the MSDOS/MBR partition table because it thinks it has found a CUMANA/ADFS (RISC OS) partition table that takes precedence.

In this thread Ubuntu recognises the MSDOS/MBR partition table, but for some reason does not see partition number 8.

While I am here, a workaround for mounting unrecognised partitions is to take the "start" sector number such as 9887744 from "fdisk -l", and use a loopback device:

Code: Select all

mount -oloop,offset=$((512*9887744)) /dev/mmcblk0 /mnt

To run fsck on an unrecognised partition you need to create the loop device as a separate step:

Code: Select all

losetup -o $((512*9887744)) /dev/loop7 /dev/mmcblk0
fsck /dev/loop7
losetup -d /dev/loop7

It is best to have no other partitions of the same device automatically mounted at the time.

[chadw]

Thank you for the workaround.

Also: I rebooted on gparted liveUSB, there it is possible to mount partition #8 (on the command line).