recognized partitions incomplete on 14.04.2 and 15.04

Bug #1457526 reported by beta-tester
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

on ubuntu 15.04, 14.04.2 the system shows me after plugging a SD card the following information (where sdc the SD card is)

me@my-Linux:~$ cat /proc/partitions
major minor #blocks name
...
   8 32 15558144 sdc
   8 33 3807232 sdc1

me@my-Linux:~$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 14,9 GiB, 15931539456 bytes, 31116288 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
Disklabel type: dos
Disk identifier: ...

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 244140 242093 118,2M e W95 FAT16 (LBA)
/dev/sdc2 245760 31050751 30804992 14,7G 85 Linux extended
/dev/sdc3 31050752 31116287 65536 32M 83 Linux
/dev/sdc5 253952 581631 327680 160M c W95 FAT32 (LBA)
/dev/sdc6 589824 13869055 13279232 6,3G 83 Linux
/dev/sdc7 13877248 14000127 122880 60M c W95 FAT32 (LBA)
/dev/sdc8 14008320 31047679 17039360 8,1G 83 Linux

Partition table entries are not in disk order.

none of the partitions are able to mount.

the exact same SD card and same USB/SD card reader but using ubuntu 14.04 or 12.04 shows me the correct information:
me@my-Linux:~$ cat /proc/partitions
major minor #blocks name
...
   8 16 15558144 sdc
   8 17 121046 sdc1
   8 18 1 sdc2
   8 19 32768 sdc3
   8 21 163840 sdc5
   8 22 6639616 sdc6
   8 23 61440 sdc7
   8 24 8519680 sdc8

tested environments:
with that issue (wrong/incomplete partition information)
ubuntu 15.04 amd64 (dist-upgraded from 14.10 to 15.04)
ubuntu 15.04 liveDVD amd64 (from 2015)
ubuntu 14.04.2 liveDVD amd64 (from 2015)

without that issue (correct partition information)
ubuntu 12.04 liveDVD amd64
ubuntu 14.04 liveDVD amd64 (~2014)
debian 8.0.0 liveCD amd64 LXDE (from 2015)

see here for more details:
https://www.raspberrypi.org/forums/viewtopic.php?p=762666#p762666
---
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2149 F.... pulseaudio
CasperVersion: 1.360
DistroRelease: Ubuntu 15.04
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: initrd=/nfs/hostname/amd64/casper/initrd.lz netboot=nfs nfsroot=10.11.12.181:/srv/tftp/nfs/hostname/amd64 file=/cdrom/preseed/hostname.seed boot=casper -- debian-installer/language=de console-setup/layoutcode?=de locale=de_DE BOOT_IMAGE=/nfs/hostname/amd64/casper/vmlinuz.efi
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic N/A
 linux-firmware 1.143.1
RfKill:

Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 09/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2105
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2105:bd09/06/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Why did you select ubuntu-docs (the desktop documentation) as the affected package when reporting this bug?

affects: ubuntu-docs (Ubuntu) → util-linux (Ubuntu)
Revision history for this message
beta-tester (alpha-beta-release) wrote :

oops... was done so by accident

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Ok.

Revision history for this message
Phillip Susi (psusi) wrote :

How large is this sd card supposed to be, and how large does it appear under 12.04? Because right now it appears to be just under 16 GB which is not large enough to hold the partitions listed in the partition table. The output of lsblk from both the working and non working kernel would be helpful.

affects: util-linux (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1457526

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
beta-tester (alpha-beta-release) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected vivid
description: updated
Revision history for this message
beta-tester (alpha-beta-release) wrote : CRDA.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : CurrentDmesg.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : JournalErrors.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : Lspci.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : Lsusb.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : ProcInterrupts.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : ProcModules.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : UdevDb.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote : WifiSyslog.txt

apport information

Revision history for this message
beta-tester (alpha-beta-release) wrote :

@Brad Figg (brad-figg): i called that 'apport-collect' as you can see...
hopefully successfully and complete.

@Phillip Susi (psusi): the plugged SD card is a 16GB SanDisk microSD.
it is used for a Raspberry Pi and is partitionized by NOOBS 1.4 to severyl different partitions.
the thing is, when i plugged that SD card to my Desktop PC with ubuntu 15.04 or 14.04.2 its most recent version from 2015 via LiveDVD or installed on HDD.
cat /proc/partitions shows me not the partitions that are on the SD card.
but fdisk -l do so - but none of the listed partitions are able to mount.

when i use the exact same SD card on the exact same desktop PC, but this time using ubuntu 14.04 (from 2014) or 12.04 (from 2012) via LiveDVD,
i have all partitions listed by cat /proc/partitions and fdisk -l and i am able to mount all of its partitions successfully and can access them.

also other Raspberry Pi user are having similar issues with ubuntu 15.04 and 14.04.2 as i could notice

Revision history for this message
beta-tester (alpha-beta-release) wrote :
Download full text (7.3 KiB)

@Philip Susi (psusi): oops, i didn't really answered your question...
the size of blocks appears on ALL systems as expected with (14,9 GiB, 15931539456 bytes, 31116288 sectors).
here the outputs of the different Ubuntu versions + debian:

--------------------
Debian 8.0.0 LiveCD LXDE
dmesg:
[ 3.153986] scsi 8:0:0:0: Direct-Access SD/MMC Card Reader 1.00 PQ: 0 ANSI: 0
[ 3.156776] sd 8:0:0:0: Attached scsi generic sg3 type 0
[ 3.390080] sd 8:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[ 3.394821] sd 8:0:0:0: [sdc] Write Protect is off
[ 3.397416] sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 3.399569] sd 8:0:0:0: [sdc] No Caching mode page found
[ 3.402135] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 3.438526] sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 > sdc3
[ 3.454048] sd 8:0:0:0: [sdc] Attached SCSI removable disk
[ 35.537446] EXT4-fs (sdc8): mounted filesystem with ordered data mode. Opts: (null)
[ 35.564251] FAT-fs (sdc7): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 35.597981] FAT-fs (sdc7): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 35.759060] EXT4-fs (sdc6): mounted filesystem with ordered data mode. Opts: (null)
[ 35.799686] FAT-fs (sdc5): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 35.858976] FAT-fs (sdc5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 35.910946] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null)
----------
lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdc 8:32 1 14,9G 0 disk
|-sdc1 8:33 1 118,2M 0 part
|-sdc2 8:34 1 1K 0 part
|-sdc3 8:35 1 32M 0 part /media/user/SETTINGS
|-sdc5 8:37 1 160M 0 part /media/user/0332-85B5
|-sdc6 8:38 1 6,3G 0 part /media/user/b0f5d83c-52fb-4181-9165-18c086e8be4c
|-sdc7 8:39 1 60M 0 part /media/user/boot
`-sdc8 8:40 1 8,1G 0 part /media/user/root

--------------------
Ubuntu 12.04 LiveDVD
dmesg:
[ 5.659331] scsi 8:0:0:0: Direct-Access SD/MMC Card Reader 1.00 PQ: 0 ANSI: 0
[ 5.659716] sd 8:0:0:0: Attached scsi generic sg3 type 0
[ 5.901090] sd 8:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[ 5.903212] sd 8:0:0:0: [sdc] Write Protect is off
[ 5.903214] sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 5.905334] sd 8:0:0:0: [sdc] No Caching mode page present
[ 5.905336] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 5.914826] sd 8:0:0:0: [sdc] No Caching mode page present
[ 5.914828] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 5.938801] sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 > sdc3
[ 5.950926] sd 8:0:0:0: [sdc] No Caching mode page present
[ 5.950928] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 5.950930] sd 8:0:0:0: [sdc] Attached SCSI removable disk
[ 8.328996] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null)
[ 8.793824] EXT4-fs (sdc6): mounted filesystem with ordered data mode. Opts: (null)
[ 9.109466] EXT4-fs (sdc8): mounted fi...

Read more...

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

Ahh, I see now. You seem to have two conflicting partition tables on the drive. The MBR/DOS one, and an Acorn partition table. The newer kernels are recognizing and using the Acorn one. You will need to get rid of that. From what I can tell from a quick glance at the kernel sources, its primary information is stored in sector 6. Zeroing that out with dd should get rid of it.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
beta-tester (alpha-beta-release) wrote :

indeed, there is RISCOS partition stuff on the same SD card.
and zero'ing out that will prevent the newer kernel to mess up.

so maybe i have to bounce back the issue to the raspberry pi team,
that the way they prepare the NOOPS partition tables for installing and booting multiple different OS'es is problematic to newer ubuntu kernels.

or is there a practical way on ubuntu site to handle these conflicts more nicer... like it was before with older kernels...?

Revision history for this message
Phillip Susi (psusi) wrote :

The older kernels probably just did not have support for Acorn partition tables and so didn't recognize it. Now that it does, it uses it, and it is broken since it describes partitions that you have no intention of using.

Revision history for this message
beta-tester (alpha-beta-release) wrote :

ok, thank you, i got it.
maybe the raspberry pi NOOBS team will find a solution to create a nice separated and non-conflicting partition table setup.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.