Comment 4 for bug 21175

(In reply to comment #3)
> Does the kernel see the partitions and can you mount them yourself? Can you send
> the output of /proc/partitions on hoary and breezy kernels.

I only have Breezy installed. Here is the output:

matt@kalliope:~$ cat /proc/partitions
major minor #blocks name

   8 0 39070080 sda
   8 1 14651248 sda1
   8 2 4142880 sda2
   8 3 19406520 sda3
   8 4 1 sda4
   8 5 859446 sda5
 253 0 14651248 dm-0
 253 1 4142880 dm-1
 253 2 19406520 dm-2
 253 3 859446 dm-3

Here is my partition table:

matt@kalliope:~$ sudo fdisk -l /dev/sda

Disk /dev/sda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 1 1824 14651248+ 7 HPFS/NTFS
/dev/sda2 * 4348 4864 4142880 2 XENIX root
Partition 2 does not end on cylinder boundary.
/dev/sda3 1825 4240 19406520 83 Linux
/dev/sda4 4241 4347 859477+ 5 Extended
/dev/sda5 4241 4347 859446 82 Linux swap / Solaris

Partition table entries are not in disk order

and here is what I get when I try to mount /dev/sda1:

matt@kalliope:~$ sudo mount -t ntfs /dev/sda1 /mnt/test
mount: wrong fs type, bad option, bad superblock on /dev/sda1,

[4296730.205000] NTFS driver 2.1.22 [Flags: R/O MODULE].
[4296730.245000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Primary
boot sector is invalid.
[4296730.245000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount
option errors=recover not used. Aborting without trying to recover.
[4296730.245000] NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.
[4296745.723000] NTFS-fs error (device sda2): read_ntfs_boot_sector(): Primary
boot sector is invalid.
[4296745.723000] NTFS-fs error (device sda2): read_ntfs_boot_sector(): Mount
option errors=recover not used. Aborting without trying to recover.
[4296745.723000] NTFS-fs error (device sda2): ntfs_fill_super(): Not an NTFS volume.
[4296749.694000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Primary
boot sector is invalid.
[4296749.694000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount
option errors=recover not used. Aborting without trying to recover.
[4296749.694000] NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.
[4296809.817000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Primary
boot sector is invalid.
[4296809.817000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount
option errors=recover not used. Aborting without trying to recover.
[4296809.817000] NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.

Dunno if this helps, but it is certainly weird. Windows was working fine since
my massive dist-upgrade yesterday.