kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #129922
[Bug 1453117] Re: Partitions not recognized because of kernel option CONFIG_ACORN_PARTITION_CUMANA
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-vivid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1453117
Title:
Partitions not recognized because of kernel option
CONFIG_ACORN_PARTITION_CUMANA
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Fix Released
Bug description:
I am having trouble installing Ubuntu on a newly built system (M/B: Gigabyte B85M-HD3, SSD: Transcend 370 128GB)
The disk was partitioned with Windows installer (Windows 7) with the legacy BIOS (MBR) setting
However the two partitions created by Windows are seen as corrupt by Ubuntu installer disk.
ls /dev/sda* only shows "/dev/sda /dev/sda1" and not /dev/sda2 (sda1 is windows boot partition and sda2 its main partition)
gparted says /dev/sda1 is lacking NTFS signature and /dev/sda2 doesn't exist
This behavior appears in both Ubuntu 15.04 and 14.04.2
However:
Both partitions are correctly recognized and mounted by every other linux distribution I have tried (Arch installer of April 2015, Linux Mint 17.1, Crunchbang). Windows works fine as well.
A relevant fragment from dmesg:
[ 3.326601] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[ 3.326680] sd 0:0:0:0: [sda] Write Protect is off
[ 3.326683] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.326705] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.327072] sda: [CUMANA/ADFS] sda1 [ADFS] sda1
[ 3.327076] sda: partition table partially beyond EOD, enabling native capacity
[ 3.340753] sda: [CUMANA/ADFS] sda1 [ADFS] sda1
[ 3.340754] sda: partition table partially beyond EOD, truncated
[ 3.340756] sda: p1 size 4067027304 extends beyond EOD, truncated
[ 3.340929] sd 0:0:0:0: [sda] Attached SCSI disk
I compared this to dmesg I get from booting Arch installer and the lines about "partition table partially beyond EOD, truncated" don't appear there. Instead I see something like
[ 3.448351] sda: sda1 sda2
[ 3.448597] sd 0:0:0:0: [sda] Attached SCSI disk
and the partitions are recognized
Output of fdisk -l
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 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: 0xe4e835e9
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 250066943 249860096 119.1G 7 HPFS/NTFS/exFAT
Found this: https://bugzilla.kernel.org/show_bug.cgi?id=4054
"This is a consequence of enabling CONFIG_ACORN_PARTITION_CUMANA:
a 1 in 256 probability of getting any random partition recognized
as CUMANA/ADFS. Solution: do not enable CONFIG_ACORN_PARTITION_CUMANA."
I don't think this option is relevant to Ubuntu installations, would
you consider disabling it?
---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 1882 F.... pulseaudio
/dev/snd/controlC1: ubuntu 1882 F.... pulseaudio
/dev/snd/controlC0: ubuntu 1882 F.... pulseaudio
CasperVersion: 1.360
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.04
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Gigabyte Technology Co., Ltd. B85M-HD3
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 nouveaufb
1 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
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
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: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FF
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-HD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFF:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: B85M-HD3
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453117/+subscriptions