pata drive size being confused with sata drive

[Joe]

Ubuntu Hardy 2.6.24-19-server

I have a system with mixed pata and sata drives, the boot drive is the first sata drive (sdb1). sda1 is a 160G partition on a pata drive, sdb1 is a 10G partition on an sata drive. Parted and cfdisk both report the sizes correctly, however, If I try to put 15G of files on the /dev/sda1, it gives an out of space error. It appears that the system is using the size of sdb1 instead of sda1. Prior to installing Hardy, this system was using Debian Sid, and the drive sizes were correct.

output of: df -H

Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 10G 4.4G 5.1G 47% /
varrun 1.1G 234k 1.1G 1% /var/run
varlock 1.1G 0 1.1G 0% /var/lock
udev 1.1G 58k 1.1G 1% /dev
devshm 1.1G 0 1.1G 0% /dev/shm
/dev/sdb6 490G 369G 121G 76% /media/local/archive
/dev/sdd1 501G 473G 28G 95% /media/local/archive2
/dev/sdc1 751G 177G 574G 24% /media/local/tv
/dev/sda1 10G 157M 9.3G 2% /media/local/new

------------------------------------------------------------------------------------------------------
output of: parted /dev/sda1 print

Disk /dev/sda1: 164GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
 1 0.00kB 164GB 164GB ext3

------------------------------------------------------------------------------------------------------
output of: parted /dev/sdb1 print

Disk /dev/sdb1: 10.0GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
 1 0.00kB 10.0GB 10.0GB ext3

------------------------------------------------------------------------------------------------------
fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdb1
UUID=d788c819-fd29-4b1f-9d4b-7acb6fe35b5d / ext3 relatime,errors=remount-ro 0 1
# /dev/sdb5
UUID=2da8de0f-9969-4d50-99fe-ecf00b5f11d2 none swap sw 0 0
#/dev/sdb6
UUID="b3ada132-80de-447a-a2bb-695a0a8e76c6" /media/local/archive jfs defaults 0 1
#/dev/sdc1
UUID="0b5a1713-847e-457c-bf27-e00562a76a48" /media/local/archive2 jfs defaults 0 1
#/dev/sdd1
UUID="a5cabf7f-c228-437e-9db3-5a6ced2658ac" /media/local/tv jfs defaults 0 1
#/dev/sda1
UUID="d8a9f30b-4009-4990-9508-1d35904e6801" /media/local/new ext3 defaults 0 1

[Leann Ogasawara (leannogasawara)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.

[kernel-janitor (kernel-janitor)]

Hi jaoag,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 241552

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]