http://bugzilla.novell.com/show_bug.cgi?id=617288 http://bugzilla.novell.com/show_bug.cgi?id=617288#c2 Mircea Kitsune changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Install Priority|P5 - None |P1 - Urgent URL| |http://forums.opensuse.org/ | |get-help-here/hardware/4370 | |39-opensuse-11-2-does-not-s | |ee-my-sata3-hard-disk-parti | |tions-2.html Component|Installation |Installation Version|Final |RC 1 Product|openSUSE 11.2 |openSUSE 11.3 Target Milestone|--- |RC 1 --- Comment #2 from Mircea Kitsune 2010-06-25 18:06:54 UTC --- Just tried the latest 11.3 release candidate (RC 1) 64bit. Unfortunately the issue is still there, so I won't be able to install 11.3 either :( The same problem occurs, and the installer does not detect my hard disk at all. In order to be sure it's not something on my end again, I also tried all possible jumper settings on the problematic HDD (it came without a jumper so i used one from a different SATA HDD), but that didn't change anything. I tried the BIOS FailSafe and Default configurations again, and also tried switching between IDE and AHCI mode again from bios. It still makes no difference whether I plug in the other HDD either (that one is always seen properly and this one is never seen by the installer). I hope 11.4 will work, or maybe through some miracle this can be fixed in 11.3 before it's released, if there's still time in 20 days. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=617288 http://bugzilla.novell.com/show_bug.cgi?id=617288#c3 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P5 - None Severity|Critical |Major --- Comment #3 from Stephan Kulow 2010-06-28 21:51:12 CEST --- you have no data loss, so it's not critical to our definitions. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=617288 http://bugzilla.novell.com/show_bug.cgi?id=617288#c5 --- Comment #5 from Mircea Kitsune 2010-06-28 22:17:09 UTC --- Created an attachment (id=372285) --> (http://bugzilla.novell.com/attachment.cgi?id=372285) 11.3 RC1 Yast installer logs -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=617288 http://bugzilla.novell.com/show_bug.cgi?id=617288#c7 --- Comment #7 from Mircea Kitsune 2010-06-28 22:27:15 UTC --- Posted the two requested files. Taken with the 11.3 RC1 64bit installer. If this information is important, the USB stick was used to store the logs to, which is why it was plugged in. And sorry for qualifying this bug to maximum priority. I did so because it can make installation impossible based on hardware, which felt like one of the biggest possible issues to me (but yes data loss would be worse). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=617288 http://bugzilla.novell.com/show_bug.cgi?id=617288#c9 --- Comment #9 from Mircea Kitsune 2010-06-29 00:33:47 UTC --- Created an attachment (id=372300) --> (http://bugzilla.novell.com/attachment.cgi?id=372300) 11.3 RC1 64bit installer I tested again with an older 11.3 Milestone 4 Live KDE DVD. To my surprise, both the partitioner and My Computer window showed my hard drive properly this time, which I find extremely weird. If I start any OpenSuse installer however (non-live CD), my hard disk is not seen. So this might be an installer only issue perhaps? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=617288 http://bugzilla.novell.com/show_bug.cgi?id=617288#c11 --- Comment #11 from Mircea Kitsune 2010-07-15 15:42:19 UTC --- Just tried 11.3 64bit which is now out, and the issue is still there. I hope 11.3 can be updated when this problem is solved, so users with my hardware won't have to wait for 11.4 to install. Also, I realized I haven't mentioned an important detail. My motherboard is a Gigabyte GA-X58A-UD7, with an X58 Express Intel ICH10R chipset. http://www.marketonline.ro/placi-de-baza/placa-de-baza-gigabyte-ga-x58a-ud7 I heard this might be an important part, so just in case it makes any difference. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=617288 http://bugzilla.novell.com/show_bug.cgi?id=617288#c13 --- Comment #13 from Mircea Kitsune 2010-08-02 18:22:20 UTC --- I'll try to remember to test that when I return home (in about a week and a half). Hope that can be a temporary workaround, and indicate the issue better as well. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=617288 https://bugzilla.novell.com/show_bug.cgi?id=617288#c16 --- Comment #16 from Mircea Kitsune 2011-03-12 02:38:40 UTC --- Well, 8 months have passed. I tried 11.4 today, and it's the same. It will not show nor detect my hard drive. At this point, I honestly find NO excuse for the OpenSuse devs any more. I even contacted Linus himself about this, and still no reply. I know that any project has its bugs, that the developers can't fix everything immediately... but this is over the line. It's a hardware incompatibility with basic hardware, that you cannot run OpenSuse without. All I'm trying to do is to install it! How can this still be happening, in a project as big and important as OpenSuse? >:( I don't want to upset anyone, and I really love OpenSuse. But god! Last spring, there was the excuse that my hard drive and mobo were newer models. But it's been a whole year, and two opensuse versions. Why such a lack of attention to such a huge issue? All you need to do is get unlucky when upgrading your hardware, and kiss OpenSuse goodbye for a few years. Please OpenSuse team... look into this issue more! Please :| -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=617288 https://bugzilla.novell.com/show_bug.cgi?id=617288#c18 --- Comment #18 from Greg Freemyer 2011-03-12 17:31:39 UTC --- (In reply to comment #16)

Well, 8 months have passed. I tried 11.4 today, and it's the same. It will not show nor detect my hard drive.

At this point, I honestly find NO excuse for the OpenSuse devs any more. I even contacted Linus himself about this, and still no reply.

Assuming its a kernel issue as someone said: If you don't think the openSUSE team is addressing it, the correct escalation path is to "IDE/ATA development list" . That is a linux kernel mailing list dedicated to ide / sata development. You don't need to subscribe to post. They have a reply all policy. So post your details their and see if they can help: ie. your skillset (kernel newbie? experienced kernel dev?) kernel: 2.6.37 from openSUSE 11.4 liveCD Drive: controller(s): motherboard: lspci output from the liveCD if you can get it And the output of a command line tool that fails, also dmesg error output if you can capture it. Good Luck -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=617288 https://bugzilla.novell.com/show_bug.cgi?id=617288#c20 --- Comment #20 from Mircea Kitsune 2011-03-13 16:25:39 UTC --- Alright. After a few more tests, I finally have good news on the matter. I used a boot setting suggested by someone on the other tracker, and it worked! The hard drive and its partitions were seen, and there were no more I/O errors happening. The option that got it working is libata.ignore_hpa=0 . I don't know what it does, but it seems to fix the problem. I haven't tried installing and partitioning yet, as I'm still scared of data loss until more is known. But this should be some helpful info, and a good workaround too :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=617288 https://bugzilla.novell.com/show_bug.cgi?id=617288#c22 --- Comment #22 from Mircea Kitsune 2011-03-22 22:36:58 UTC --- (In reply to comment #21) If I use hdparm on the hard drive when it's not working, it only gives me an I/O error as output. I can hdparm it while starting the Installer without HPA however, though I'm not sure if it still gives this info then. I'm not sure if this bug should be closed however, as IMO it could be an issue with how OpenSuse interprets the drive's HPA. Given that all other programs see the drive but Linux. If it was only the drive, I'm guessing Windows wouldn't be seeing it either. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=617288 https://bugzilla.novell.com/show_bug.cgi?id=617288#c24 --- Comment #24 from Greg Freemyer 2011-07-05 16:24:22 UTC --- First, if you're concerned about data loss, you need to make a backup. Absolutely nothing is going to ensure you have zero chance of corrupting the data. And the instructions below absolutely might cause data loss. So make a backup with Windows, or a live CD, or whatever before you proceed. == Per the kernel bugzilla you posted you can see the drive from a liveCD. If you do that, what does sudo /sbin/hdparm -N /dev/sda report? (obviously replace sda with the correct name if that is wrong). If it reports a HPA is in use and you don't know why, you need to just get rid of it in my opinion. Or understand why you have a HPA in the first place. You can do sudo /sbin/hdparm -N0 /dev/sda (that's "dash N zero") to kill it until you cycle power. That would allow you to reboot into the install CD and test things. And sudo /sbin/hdparm -Np0 /dev/sda to kill it forever. fyi: Nothing in this bugzilla sounds like a openSUSE bug to me. It sounds like you have a misconfigured drive to me at this point. I will know more once you post the current hpdarm -N output. If there is a problem, I suspect you will need to open a new bugzilla with a title like "openSUSE won't install onto a harddrive with a HPA". Personally I suspect your HPA is the size of the drive, so that is leaving openSUSE with no diskspace to install to. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=617288 https://bugzilla.novell.com/show_bug.cgi?id=617288#c26 --- Comment #26 from Mircea Kitsune 2011-12-05 16:12:07 UTC --- Just tested again with the latest OpenSuse release (12.1). I have some great news: The problem has finally been fixed! I started up the installer as usual, and when I got to the Disk / Partitioning step, my 2TB hard drive and its partitions were shown without any problem. I wasn't hoping to see the issue solved any more... but after almost 2 years, it finally appears to be working. I haven't risked installing yet, though I don't think there should be any read / write problems if the hard drive is shown. Many thanks to the Linux and OpenSuse devs for looking into this, whatever was causing it :D -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.