Partitions not recognized because of kernel option CONFIG_ACORN_PARTITION_CUMANA
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Tim Gardner | ||
Vivid |
Fix Released
|
Undecided
|
Tim Gardner | ||
Wily |
Fix Released
|
High
|
Tim Gardner |
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:/
"This is a consequence of enabling CONFIG_
a 1 in 256 probability of getting any random partition recognized
as CUMANA/ADFS. Solution: do not enable CONFIG_
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/
/dev/snd/
/dev/snd/
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_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 nouveaufb
1 inteldrmfb
ProcKernelCmdLine: file=/cdrom/
ProcVersionSign
RelatedPackageV
linux-
linux-
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.
dmi.board.name: B85M-HD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: B85M-HD3
dmi.product.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Related branches
CVE References
affects: | ubuntu → linux (Ubuntu) |
tags: | added: trusty vivid |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
tags: | added: patch |
Changed in linux (Ubuntu Vivid): | |
status: | In Progress → Fix Committed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1453117/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]