Ext4 external HDD can't be mounted with Karmic, but with Jaunty

Bug #479640 reported by Luis Cabellos
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: upstart

I have an external disk with ext4, its mounted on jaunty without problems, but in a Karmic one, I cant mount the disk. It show the problems:

{{{
:~$ sudo mount -t ext4 /dev/sdb2 temp_file
mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

:~$ dmesg | tail
[ 5017.861905] sdb: p2 size 567174762 exceeds device capacity, limited to end of disk
[ 5017.870427] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 5017.870436] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 5018.739036] EXT4-fs (sdb2): bad geometry: block count 70896845 exceeds size of device (70895475 blocks)
[ 5548.646033] EXT4-fs (sdb2): bad geometry: block count 70896845 exceeds size of device (70895475 blocks)

:~$ sudo fsck.ext4 /dev/sdb2
e2fsck 1.41.9 (22-Aug-2009)
The filesystem size (according to the superblock) is 70896845 blocks
The physical size of the device is 70895475 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no
/dev/sdb1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Luigi: 18900/17727488 ficheros (18.7% no contiguos), 19345557/70896845 bloques
}}}

ProblemType: Bug
Architecture: i386
Date: Tue Nov 10 00:07:27 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/init
NonfreeKernelModules: nvidia wl
Package: upstart 0.6.3-10
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: upstart
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Luis Cabellos (zhen-sydow) wrote :
Camille Appert (bibinou)
summary: - Ext4 externall HDD can't be mounted with Karmit, but with Jaunty
+ Ext4 externall HDD can't be mounted with Karmic, but with Jaunty
Revision history for this message
Erik Kronberg (eakron) wrote : Re: Ext4 externall HDD can't be mounted with Karmic, but with Jaunty

Can it still be mounted on a computer using Jaunty?

Changed in upstart (Ubuntu):
status: New → Incomplete
tags: added: needs-reassignment
Revision history for this message
Luis Cabellos (zhen-sydow) wrote :

Yes, it still can be mounted with a Jaunty computer.

summary: - Ext4 externall HDD can't be mounted with Karmic, but with Jaunty
+ Ext4 external HDD can't be mounted with Karmic, but with Jaunty
affects: upstart (Ubuntu) → linux (Ubuntu)
Erik Kronberg (eakron)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Syrou (arldn) wrote :

I consider this a critical bug, since it's not possible to mount a RAID 10 2 disk array with ext4 filesystem, even if it is done in Karmic. As a workaround, I have installed the Jaunty kernel. No problem since then.

Revision history for this message
Keith Allcock (keith-allcock) wrote :

I have this same issue but with a mirrored pair of internal disks.
Its not just an external drive issue...

dmesg shiws : EXT4-fs (md0): bad geometry: block count 244190000 exceeds size of device (244189984 blocks)

Revision history for this message
Conrad Knauer (atheoi) wrote :

Ack! I'm getting bitten by this bug too:

$ sudo mount -t ext4 /dev/sdb /home/conrad/Desktop/temp
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

$ dmesg | tail
[ 9496.925863] sd 13:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 9496.927439] sd 13:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 9496.927449] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[ 9496.936921] sd 13:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 9496.936934] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[ 9496.936950] sdb: sdb1
[ 9496.955599] sd 13:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 9496.955617] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[ 9496.955632] sd 13:0:0:0: [sdb] Attached SCSI disk
[ 9977.758268] EXT4-fs (sdb): VFS: Can't find ext4 filesystem

running Karmic 64-bit; drive is attached via USB. I had backed up all my files to that drive in Jaunty before I installed Karmic :)

Revision history for this message
jdonner (jeffrey-donner) wrote :

FWIW I had this problem with a new pair of raid drives formatted to ext4. Because it was new I was able to reformat to ext3, and that works.

Revision history for this message
Saha (smirta) wrote :

Confirm with Ubuntu 9.10 (32bit) and RAID-array (through mdadm)

Revision history for this message
fluxgate (chhnews) wrote :

I have the same problem on an New WD External USB Drive with 1,5TB . I'm using Karmic 64-bit.
There is no RAID! Only one Drive!

For a workaround, I'll try to get back to ext3...

Revision history for this message
Atte Saarela (attesaarela) wrote :

Confirmed on Ubuntu 10.04 (32-bit) and an internal Maxtor SCSI drive (80gb)

Install with both ext3 and ext4 fails

Revision history for this message
Urban Purkat (urban-purkat) wrote :

No update for a long time is usually not good :(

I see the same problem on 10.04 (2.6.32-24) after upgrade from kernel 2.6.28-18.
The physical size seems to be 30 blocks smaller than the value in the superblock.

Is there any workaround (except running old kernel)?

Revision history for this message
Jesse Mortenson (teknoj) wrote :

I am seeing this problem as well, running 10.04.1. Formatted two identical internal drives as ext4, then merged them with mdadm. Status looks fine in mdadm output and in palimpset, but trying to mount the drive gives the same errors mentioned above. Looks like I'll have to re-format down to ext3.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
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.