Same here. After update a few minutes ago I can no longer boot.
Western Digital sata disk. jkuhnert, could you elaborate on how you got
back to a bootable state. I'm forced to boot XP at the moment.
Downloading a live CD right now, hopefully that will help.
I see some ata errors similar to
My problem as described in the last comment is covered in bug #106063.
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This is _REALLY_ fucked up. Been debian experimental / unstable user
for years, switched to ubuntu and after few weeks such problems.
My machine just won't boot, I get the error other guys get (copied from
above)-
[ 9.064000] ata1.01: n_sectors mismatch 66055248 != 9670832
[ 9.064000] ata1.01:
I see there is, as of today, another kernel update, but I am cautious to
take it. Does this include the above patch (the one that I'm on now,
that fixed my system)? I see Bug #96857 and Bug #99648 referenced in
the changelog, but no Bug #82314. :) Regardless, thanks for all your
work Kyle,
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: In Progress = Fix Committed
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I noticed the update this morning as well. I updated and now both the
generic and 386 .14 kernels appear to be working.
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
To the last comment, yeah downloading a livecd should allow you to
chroot to your drive and fix the kernel issues by downgrading the kernel
version.
If you want to be mad at someone ultimately you can direct it towards
Linus Torvalds / Allen Cox. I stumbled upon a thread or two with them
Arghh! So which one is it? This is like russian roulette.
Nick, were you getting n_sectors mismatch errors or some other type of
error ?
I'm afraid just because there are other hosed people reporting things
that theoretically got pushed out this morning.
--
pata driver in libata is thwarted by
The update this morning is exactly what -broke- my machine in the first
place. By the way, my drive is not a Western Digital Sata as I
believed, but rather a Hitachi PATA drive, that seems to be mounted via
a scsi interface. I don't plan to do any more kernel updates until I
see positive
It fixed my problem! Thanks so much. With this testing kernel, feisty
now boots on my ThinkPad T41. Please have this in on the final release.
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member of Ubuntu
I already sent Ben and Kyle an e-mail about this but I thought I should
post my comments below in case other people have the same issue.
I tried the kernel from above and it did fix the end of device messages
but I came up with the following error message when my system was trying
to initialize
This kernel works fine 4 me - please please please put these changes in
the RC! In addition I have some problems in combination with my
soundblaster live! card - but maybe that one is broken.
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug
I've had a similar problem - boot hangs and I get ata2.00: failed to
set xfermode (err_mask=0x4). since upgrading to 2.6.20-14; 2.6.20-13
still boots fine. I was hoping this patch would fix me up, but it does
not...
--
pata driver in libata not mounting /home
I end up at the same place as before with this kernel, so it hasn't
fixed the problems I've been having on my T40. Booting an older kernel
works though. I get the attempt to access beyond errors. As some
people have mentioned I think, I'm not using RAID or anything similar,
just a single PATA
Gar !! The (as of a few minutes ago) 2.6.20-14 23 version kernel is now
giving me similar failure messages to those above (re-pasted from
above):
[ 9.064000] ata1.01: n_sectors mismatch 66055248 != 9670832
[ 9.064000] ata1.01: revalidation failed (errno=-19)
[ 9.064000] ata1.01: disabled
[
I am seeing the exact same thing as kuhnert. However only on one of the drives
connected to my controller. I have been running feisty fine for a little while
and today one drive gives me these errors. If it can help, I attached the
output from dmesg. I am also available to test new kernels.
I'm all done freaking out now, the hot to chroot thread on
ubuntuforums was very helpful in eventually getting me into a state
where I could downgrade the kernel from apt archives. ...
Damn you Linus / Allen!
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: High = Critical
Status: Confirmed = In Progress
Target: 7.04-beta = ubuntu-7.04
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member
Ok, here's a testing kernel that handles HPA capable drives:
http://people.ubuntu.com/~bcollins/kernels/bug-82314/
There's on for amd64 and i386.
NOTE: This will not be in the RC. If you want this to make it in for
release, please test ASAP, and email Kyle and myself directly with
results:
kernel update on feisty: kernel 2.6.20-13 boots fine; kernel 2.6.20-14:
failed to set xfermode (err_mask=4x0)
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
It gets further than before (with 2.6.20-13), always says there are
errors on sda1. Only kernel I have working (2.6.17-10) does not flag
these errors. After the error check pumps out more errors and boot
halts. I will photo the screen if needed.
--
pata driver in libata not mounting /home
Problem seems to be solved in 2.6.20-13 and is no back in 2.6.20-14
Also directories will be shown as unknown file formats.
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I'm seeing those messages, but nothing related to host protected area.
So should I be using the old drivers, or open a new bug report for this?
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Reed: I have got 2.6.17-10 booting fine on my system. My other kernels
will not boot (2.6.20-13, 2.6.20-12, 2.6.17-11).
I can confirm all the above problems (/dev/hda - /dev/sda), the beta cd
throws up the same dmesg as reported before.
--
pata driver in libata not mounting /home
We had to back out the changes as they broke booting on the MacBook.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Fix Released = Confirmed
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/82314
You received this bug notification because you are a member
Where can I find the .deb for an older kernel that will boot? Also, is
there a time frame for when we might have an update to a new, working
kernel? Are we to expect that this will be fixed in time for the final
release? Thanks.
BTW, It seems to me that the issue that myself, and several
Same problem here, Acer TravelMate 8000 (8006LMi).
attempt to access beyond end of device and boot halts
Using 2.6.17-10 atm to boot, which works fine.
This is clearly quite a new problem and I can't find any useful
information anywhere. I don't know enough to fix myself and this is my
work
I am having the same problem with Thinkpad A31 and with kernels
2.6.20-12 and 2.6.20-13. With 2.6.17* kernels my disks can be properly
mounted, but with the 2.6.20* I am getting these errors:
attempt to access beyond end of device
and I cannot mount my partitions.
--
pata driver in libata not
Scott,
when using the old (non-sata based) ata drivers, you see the disks as
hd*. When using the sata-based ata drivers, you see them as sd*.
This particular bugreport was opened for the scenario when the new sata-
based drivers were used for disks with a host-protected area (HPA)
present. In
It seems it boots successfully sometimes, but that (I think) depends on
the order the devices are enumerated. I grabbed a dmesg of both a fail
and success, and spotted a couple of differences (if it helps)--note I
don't see any line about HPA, yet the old ide driver detects it (Host
Protected
I experienced the same issues today with feisty (dist-upgrade today).
Suddenly my /dev/hda became /dev/sda and thought the partitions were damaged
and ran fsck on them, which failed every time.
When booting an older kernel (2.6.19.x) /dev/hda was identified and worked.
Now my system is totally
My (broken) system is also an IBM T41.
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is the only bug I could find that I thought might be related to my
issue. I was going to try blacklisting the ata drivers as suggested
above, but I'm not sure how to include all the necessary ones to get the
old IDE driver (for now). I started having problems with 2.6.20-12,
though -11 works
Still no success; the boot process hung in the same spot. I'm currently
downloading the new beta, and when I finish downloading, I'll reinstall
and then hopefully it will boot. I'll post back with my results.
Thanks.
Reed
--
pata driver in libata not mounting /home
:/ It appears things have regressed even with the beta. I couldn't get
to a console to get a dmesg by booting to the feisty I have installed,
so I booted up to the new beta cd I just burned and when I attempt an
install, the partitioner does not even show my existing partitions...
On the
FWIW, my system is a IBM Thinkpad T41.
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I could be wrong, but I think my problem may also be related. I
attempted a very standard install of Feisty Herd 5 alongside my Edgy
install. Here's my fdisk output:
[CODE]
$ sudo fdisk -l /dev/hda
Disk /dev/hda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units =
Reed:
ad1. your partition table is OK, just the logical order of the partition
is not the same as the physical order and the fdisk output is ordered by
the logical layout.
ad2. The problem attempt to access beyond end of device can belong to
this bug, please do what Kyle suggested:
If you're
The disk isn't detected, there's no way I can grab the dmesg... The
latest update doesn't work either, just -9. The grub keyboard issues
make it suboptimal to change kernel at boot (most of the times the
keyboard doesn't work).
I get the following errors:
ATA: abnormal status 0x7F on port 0x20CF
Reported already: https://launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/91940
:)
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ok, I booted -11, but the affected drive is driven by normal ide
drivers, not by libata. How can I tell it that it should use libata
instead? (possibly in a way that can be easily reverted in case of
problems).
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
Since -10 I became unable to boot a MacBook C2D with ata abnormal status
errors, could it be related to any of this?
Thanks :)
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Unlikely, but posting a dmesg would be useful...
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
2.6.20-10 contains beta quality HPA support for libata. Please give it
a test by booting it, and look for Host Protected Area detected.
If you're feeling brave, boot with libata.ignore_hpa=1 to disable the
host protected area (which should enable your whole disk). Please attach
dmesg whether it
The sooner I get testers, the sooner I can enable it by default. :)
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Fix Committed = Fix Released
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: In Progress = Fix Committed
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Moving milestone forward.
** Changed in: linux-source-2.6.20 (Ubuntu)
Target: herd-5 = beta
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Herd 6 should contain preliminary HPA support, will follow up closer to
the release. In the mean time, you can blacklist the libata modules in
/etc/modprobe.d/blacklist to revert to using the drivers/ide modules.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = In Progress
We're working on libata HPA support. Assigning to Kyle.
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Kyle McMartin
Status: Unconfirmed = Confirmed
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
Thanks for you comment. Not problem now?
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Not a problem in a sense that my computer is usable. But the real
solution would be fixing the via_pata driver in libata, not just using
the old ata driver. :)
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
With 2.6.20-6-generic this problem is gone.
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: Ubuntu
Sourcepackagename: None = linux-source-2.6.20
--
pata driver in libata not mounting /home
https://launchpad.net/bugs/82314
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
53 matches
Mail list logo
