[Bug 82314] Re: pata driver in libata not mounting /home
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 feedback in bug #106063. -- pata driver in libata is thwarted by HPA 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 HPA 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 discussing these sorts of issues. I ~guess~ they aren't the ones that applied whatever this f-ed up patch is and deployed it to us as a ~minor~ kernel update but oh well...I hope they fix it soon. -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
** 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. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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, Ben, and others. You're doing great. -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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: revalidation failed (errno=-19) [ 9.064000] ata1.01: disabled [ 9.064000] ata1: failed to recover some devices, retrying in 5 secs So- it disables my only (pata) hard drive and of course after disabling hard drive it can't boot. Only 2.6.17.something boots (not 2.6.20.x) BUT there are no headers for 2.6.17 so I can't get into X with multiple monitor support (because I can't compile nvidia module). So- are there any workarounds; is it possible to disable that behavior in GRUB? I'm really not into compiling custom kernel (and got overdriven in 1 day after new kernel is released). -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 those above. -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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. Here is a snip that I think is relevent: [4.016359] ata6: SATA max UDMA/133 cmd 0x0001ef88 ctl 0x0001ef86 bmdma 0x0001ee60 irq 18 [4.016459] ata7: SATA max UDMA/133 cmd 0x0001ef68 ctl 0x0001ef82 bmdma 0x0001ee68 irq 18 [4.016530] scsi5 : ata_piix [4.186310] ata6.00: ata_hpa_resize 1: sectors = 488397168, hpa_sectors = 1857904 [4.186381] ata6.00: ATA-7: WDC WD2500KS-00MJB0, 02.01C03, max UDMA/133 [4.186435] ata6.00: 488397168 sectors, multi 16: LBA48 [4.198303] ata6.00: n_sectors mismatch 488397168 != 31170441795952 [4.198357] ata6.00: revalidation failed (errno=-19) [4.198410] ata6.00: limiting speed to UDMA/133:PIO3 ** Attachment added: "dmesg output" http://librarian.launchpad.net/7315596/dmesg-20070414-2242.gz -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 [ 9.064000] ata1: failed to recover some devices, retrying in 5 secs The module is of course sata_nv on a western digital sata disk via nvidia nvforce motherboard. Is there no magic kernel boot option that will save me ? Irqpoll did it on the last kernel update but I'm totally dead in the water now. Oh well, I should know better than to be on unstable dev streams anyways... ;) -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: 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 disk. -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 my 400gb secondary drive. [9.064000] ata1.01: n_sectors mismatch 66055248 != 9670832 [9.064000] ata1.01: revalidation failed (errno=-19) [9.064000] ata1.01: disabled [9.064000] ata1: failed to recover some devices, retrying in 5 secs Ben responded back promptly with the following: "Thanks for testing. I actually knew about this little bug already, and have fixed it locally (didn't get a chance to rebuild new images yet)." So hopefully a new image will be up and ready to go soon. Thanks again. -- 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 [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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: [EMAIL PROTECTED], [EMAIL PROTECTED] Thanks -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
** 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 of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: 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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
I just noticed that today is the kernel freeze on the release schedule. Does that mean feisty is stuck w/ a kernel that won't boot on our systems? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 others here are experiencing is different/distinct from the initial issue that Istvan Szekeres was experiencing. Can/should we split this bug report? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: 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 of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 system that I need so I can't mess about too much either. Knew I should have waited for the release before upgrading... least I have a kernel that boots :) -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 mounting /home https://launchpad.net/bugs/82314 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 Area detected, followed by disabled) so I apparently do have it... (- is fail, + is successful boot): -ata1.00: 78125000 sectors, multi 16: LBA +ata1.00: 80043264 sectors, multi 16: LBA -SCSI device sda: 78125000 512-byte hdwr sectors (4 MB) +SCSI device sda: 80043264 512-byte hdwr sectors (40982 MB) -SCSI device sda: 78125000 512-byte hdwr sectors (4 MB) +SCSI device sda: 80043264 512-byte hdwr sectors (40982 MB) - sda: p3 exceeds device capacity -attempt to access beyond end of device -sda: rw=0, want=80043080, limit=78125000 -Buffer I/O error on device sda3, logical block 9864768 Besides the obvious disk size discrepancy, the only other noticable difference is that my network card gets initialized BEFORE the ATA driver in the successful bootand AFTER the ATA driver in the failed boot... so maybe it's an ACPI issue? HTH, I see Kyle mentioned testers a couple of weeks ago, I'm not sure if that's what was in mind :). -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 these cases you could see messages like this: [ 663.015850] attempt to access beyond end of device [ 663.015854] sdc: rw=0, want=234484734, limit=66055248 -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 fine. Like other symptoms reported here, it's
detecting my devices as SCSI sda devices rather than the usual hda
stuff, and I'm not sure whether this is an issue or by design, but -12
and -13 won't boot.
I managed to get a dmesg with -12 as /boot (hda1, though it saw it as
sda1) managed to mount properly. I was getting warnings with -13, but I
don't care, there's nothing valuable on this machine :). Cheers.
-Scott
** Attachment added: "3 dmesg from 2.6.20-{13,12,11} (in that order)"
http://librarian.launchpad.net/6991211/tmp.txt
--
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
[Bug 82314] Re: pata driver in libata not mounting /home
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
[Bug 82314] Re: pata driver in libata not mounting /home
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 f%(/" up. http://home.danielnylander.se/vadda-fel.png -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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
[Bug 82314] Re: 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 prepare partitions dialog (step four, after I select to manually prepare disk space), the only device listed is /dev/sda. I don't even have an sda; it should be hda. No other partitions or devices are listed. >From the live cd, I ran a dmesg. It is attached, but I appologize, its very long - cluttered with "attempt to access beyond end of device," messages. I hope this helps. ** Attachment added: "dmesg ran from feisty beta live cd" http://librarian.launchpad.net/6904307/dmesg -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 https://launchpad.net/bugs/82314 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 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 > wasű > successful or not. -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1298023936818+ 83 Linux #Edgy /dev/hda247374864 1028160 82 Linux swap / Solaris /dev/hda32981473614105070 83 Linux #Feisty Partition table entries are not in disk order [/CODE] Feisty's boot hangs very early in the boot process. When in recovery mode, here's my final output: [CODE] Begin: Running /script/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... Done. [5.64] attempt to access beyond end of device [5.64] sda:rw=32, want=71990972, limit=70501362 [5.64] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=1733313, block=3473410 init: Unable to execute "/bin/sh" for rcS: Permission denied init: rcS process (2342) terminated with status 255 init: Unable to execute "/bin/sh" for rc-default: Permission denied init: rc-default process (2343) terminated with status 255 [/CODE] Thanks, and sorry if in missinterpreted something, this is my first time on launchpad. -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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
[Bug 82314] Re: pata driver in libata not mounting /home
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 ATA: abnormal status 0x7F on port 0x20CF ATA: abnormal status 0x7F on port 0x20CF ata1.01: qc timeout (cmd 0x27) ata1.01: failed to set xfermode (err_mask=0x40) ata1.01: limiting speed to PIO0 ata1: failed to recover some devices, retrying in 5 secs ATA: abnormal status 0x7F on port 0x20CF ATA: abnormal status 0x7F on port 0x20CF ATA: abnormal status 0x7F on port 0x20CF ata1.01: qc timeout (cmd 0x27) ata1.01: failed to set xfermode (err_mask=0x40) ata1.01: disabled ATA: abnormal status 0x7F on port 0x20C7 Then drops to a shell on the initramfs. I'll try this next: http://www.odi.ch/prog/macbookpro/index.php#4 -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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
[Bug 82314] Re: pata driver in libata not mounting /home
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 was successful or not. Thanks! Kyle -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
** 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
[Bug 82314] Re: pata driver in libata not mounting /home
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
[Bug 82314] Re: pata driver in libata not mounting /home
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 Target: None => herd-5 -- 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
[Bug 82314] Re: pata driver in libata not mounting /home
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82314] Re: pata driver in libata not mounting /home
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
[Bug 82314] Re: pata driver in libata not mounting /home
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
[Bug 82314] Re: pata driver in libata not mounting /home
** 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
