can't find sata disk kubuntu 7 beta

[jlord87]

I'm trying to install kubuntu feisty beta (i tried both the desktop and alternate i386) but the installer, and i think the kernel too, can't find my sata disk (i tried to "fdisk /dev/sda" but it replied "unable to open /dev/sda)

my motherboard is an "asrock 939dual-vsata"
 this is the output of lspci (i hope will help to find the problem)

00:00.0 Host bridge: ALi Corporation M1695 K8 Northbridge [PCI Express and HyperTransport]
00:01.0 PCI bridge: ALi Corporation PCI Express Root Port
00:02.0 PCI bridge: ALi Corporation PCI Express Root Port
00:03.0 PCI bridge: ALi Corporation PCI Express Root Port
00:04.0 Host bridge: ALi Corporation M1689 K8 Northbridge [Super K8 Single Chip]
00:05.0 PCI bridge: ALi Corporation AGP8X Controller
00:06.0 PCI bridge: ALi Corporation M5249 HTT to PCI Bridge
00:07.0 ISA bridge: ALi Corporation M1563 HyperTransport South Bridge (rev 70)
00:07.1 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:11.0 Ethernet controller: ALi Corporation ULi 1689,1573 integrated ethernet. (rev 40)
00:12.0 IDE interface: ALi Corporation M5229 IDE (rev c7)
00:13.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:13.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:13.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:13.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
03:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)
04:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon 9550]
04:00.1 Display controller: ATI Technologies Inc RV350 AS [Radeon 9550] (Secondary)

PS. ubuntu/kubuntu edgy/dapper works perfectly (even with the low latency kernel of feisty herd)

ProblemType: Bug
Architecture: i386
Date: Sat Mar 24 10:02:16 2007
DistroRelease: Ubuntu 7.04
Uname: Linux ubuntu 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux

[GabrielGrant (gabrielgrant)]

Hi!

Thanks a lot for your bug report, and for the lspci output. From that output, I see that you appear to have a JMicron AHCI controller. There is a known problem with that controller at boot time, for which a fix has recently been committed. Unfortunately it didn't quite make it in time for beta, but it should be available in the daily builds starting early next week, so your problem may be fixed once that is out. (Have a look at bug #84964 for details )

The problem you describe, however, does seem slightly different from most of those reported. Am I correct that you are able to boot into the livecd and are in the process of running the install?

If so, can you please attach a copy of the "dmesg" from Feisty to this bug report?

I'm not going to mark this as a duplicate of bug #84964 yet, but hopefully it is, since that's already been fixed :)

Thanks again!

-Gabriel

[GabrielGrant (gabrielgrant)]

Sorry, forgot to ask: can you please also attach your lspci -vv and lspci -vvn output as seperate text file attachements

Thanks!

[jlord87 (moro-87)]

yes, i am able to boot into the livecd (now i'm writing using konqueror from the live cd) and i was able to install this beta in the ide hd (identified as hda) but ther's no way (i think...) to "see" the sata disk that usually, in the stable ubuntu/kubuntu releases, is detected as sda...

in the attachment you'll find the requested info...

thanks for your time!

[GabrielGrant (gabrielgrant)]

Hi again,

Sorry for not getting back to this yesterday - I had to go into work. First off, the newest daily CD doesn't seems to have Ben Collins' latest patch for bug #84964 yet, but since you have a working install, you should be able to update your kernel on that. The easiest way to make sure everything is totally up to date is to run - could you give this a try to see if it has fixed your problem as well?

Thank you,
-Gabriel

[jlord87 (moro-87)]

Hi,
the updater works well...but the disk is still "invisible"...it's very strange, because the system works very well; if I connect an usb-pen, for example, the system automatically mount it, and it is identified as /dev/sda...while using a past version of kubuntu, ubuntu or xubuntu, edgy or dapper, /dev/sda was my sata hd...
if you want i could send theoutput to the last "apt-get upgrade"...

thank you

[GabrielGrant (gabrielgrant)]

Can you please attach the new output from "uname -a"? It should just be one line, so please just paste it into a comment.

Thanks

[Codink (herco)]

I can confirm this bug.

The jmicron driver found only pata disks.
If I use a pata cdrom player with a sata2pata converter, jmicron don't find it. My sata disks isn't detected to.

If I use my cdrom drive with pata interface connected to the jmicron then it is found.

[Codink (herco)]

Small mistake. The daily alternate build of 26-03, don't use 20.13 but 20.12. It has the 20.13 onboard, but doesn't use it.

But I can start the jmicron with 20.12 with means he has properly the same problem.
You can't use the updated kernel on a live CD, you must restart it, but then you use the old kernel again. It don't find the drives ever.

If the kernel is still .12 after you have updated then is my guess correct.

[jlord87 (moro-87)]

Hi world!
sorry for the late on writing but "sometimes" i had to study...
first of all, this is the output of uname -a, as asked by GabrielGrant

$ uname -a
Linux beta 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

@Codink
...I am not very shure to have understood what you have said...
the problem persists even updating the kernel to the latest version (2.6.20-13)?

[Lor3nzo (lor3nzo)]

I can confirm the same problem.

I have a 939Dual Motherboard, too, and it has a JMicron JMB360 controller with one SATA-2 drive attached on it.

With the daily build of March 28th (uname: 2.6.20-13-generic), controller is detected, but the serial ata HD is not.

I've tried the following things, unsuccessfully:
- force ide mode with sata2 hd
- disable floppy
- disable other controller (uli sata-1 raid)
- disable acpi

None of them let me see my sata-2 hard drive.

Please find attached my dmesg and lspci -vvn.

Greets,

Lor3nzo

N.B.: the actual configuration is:
- floppy controller disabled
- uli sata raid controller disabled
- sata2 controller (JMicron JMB360) working in IDE mode with 1x 80Gb SATA2 Hard Drive attached
- acpi disabled

[Lor3nzo (lor3nzo)]

I forgot to say, I'm using ubuntu - not kubuntu.

Hadn't read the title... sorry :-)

[Lor3nzo (lor3nzo)]

A BIOS update solved the problem.

I had v1.50 and upgraded to v2.30.

This is the link for the BIOS update:

*********************************

N.B. for the newbies: THIS BIOS UPGRADE IS ONLY FOR ASRock 939Dual-SATA2 MOTHERBOARDS!!!

*********************************

http://www.asrock.com/mb/download.asp?Model=939Dual-SATA2

Regards,

Lor3nzo

[jlord87 (moro-87)]

hi everybody!!
I'm very sorry but reading the post of Lor3nzo and trying what he wrote I have unfortunately discovered that my motherboard is not a "939Dual-Sata2" but a "939Dual-Vsata"...I'm very sorry for this mistake!
However I tried to update the bios, from the version 1.20 to the latest 1.30 but nothing has changed.

sorry a lot for the mistake (that I'm going to correct in the first post)

[GabrielGrant (gabrielgrant)]

Hi all,

I'm glad you've solved your problem, Lor3nzo, but it looks like we still have some digging to do before this is squashed. So, a few more things for you to try, jlord87:

First, since this doesn't seem to be the same as bug #84964, can you please try passing the "noapic", "nolapic", "acpi=off" and/or "irqpoll" options to the kernel (this can be done on the latest livecd by pressing "F6" at the livecd splash screen and typing the relevant command (without quotes) at the end of the boot command, but before the "--". You could also try removing the "quiet splash" part and see if you notice any error messages ). See if those help any.

Next, I am curious as to what hardware the system recognises as being attached and what drivers it is using to do that. Can you please attach the output of the following commands (both with and without the above kernel options):

ls /proc/ide/
ls /proc/scsi/
ls /dev/ | grep hd
ls /dev/ | grep sd
lsmod

And finally, a few questions specific to your hardware: first can you try checking in your BIOS settings to see if your SATA controller can be set to a different mode (AHCI, Legacy, Native, etc) and see if changing that fixes the problem? Sometimes things like this can really be a BIOS bug. Second, can you please describe what hardware is connected to which controller and what you expect to be seeing detected.

Here's what I gather from the dmesg:
*hda is a 30GB Maxtor drive (PATA)
*hdc is a DVDRW

Is that correct? What am I missing?

Possible abnormalities that I notice:
*dmesg - line 105: "[ 31.133208] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found."
*dmesg - line 134: "[ 31.313152] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15), disabled."
*dmesg - line 239: "[ 34.681674] ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707]"

Is any of that useful to a kernel dev?

Ok, that's all I have for tonight :)

Thanks a lot!
-Gabriel

[jlord87 (moro-87)]

Hi,
ok, proceeding step by step:
I launch the system from the livecd with the option you said (noapic, nolapic, acpi=off, irqpoll), Gabriel, and saved the output of the command to a file (see the attachment) and then I've done the same thing booting the system from the hard disk (pata, the only one recongized).
I tried booting without the option "quiet" but nothing appeared to be strange...

I checked into the bios for a sata controller page (and being not so expert i " transcribed" it into a text file) and the only thing strange, in my opinion, was that the sataII controller was set to IDE and not to SATA...i'll try to change it in the next reboot.

The hardware connected to the motherboard is a 30GB PATA HD (primary ide master), a DVDRW device (connected to the secondary ide master) and a 160GB SATA HD (that is connected to the sataII port);

that's all for now...if you need something more specific, i'll try to be the best to answer your question.

thanks for your help!

[jlord87 (moro-87)]

HI!!!
now it works!!
It's strange, or probably not, but changing in the bios the section Advanced-IDE-SATAII Operation Mode from [IDE] to [SATA] solved completly the problem!!
I was saying that it seems very strange because when I installed the past version of kubuntu I've never had this problem, so I've never looked into the bios how was this key setted...
Maybe before the bios update the mode was setted to SATA and not to IDE, and the bios update, setting the option to the default values changed it into IDE...i don't know...

now from my console i recive this fantastic output:

moro@beta:~$ ls /dev/ | grep sd
ptysd
sda
sda1
sda2
sda3
sda5
sda6
ttysd

Lot of thanks to all for your help, patience and time
francesco

[GabrielGrant (gabrielgrant)]

Thats great news, I'm glad to hear you've fixed it.

Would you be able to run a couple more tests, now that you've solved the problem, to help a) us ensure that this isn't a regression, and b) try to fix the issue so that other people don't have the same problem in the future?

First off, could you give us your newest lsmod, dmesg, lspci -vv and lspci -vvn output now that it is working. And second, could you please try booting an older version that worked (the more recent the better), changing the BIOS setting back to [IDE], and seeing if the disk is recognised. If it is, please provide those four outputs again, along with the "uname -a" line. Thanks a lot.

Finally, as a side note, could someone on QA please mark this as either "medium" or "High" importance, since it could be a showstopper, but only for a limited number of people (i.e. those who only have SATA disks)

Thank you very much for helping to improve Ubuntu!

-Gabriel

[Codink (herco)]

SATA mode in the BIOS is AHCI modefor real. IDE mode is the legacy mode for the controller. I think ubuntu must detectd both modes to solve the problems for humen beings. Further I preffer IDE mode for me, because it's faster then AHCI mode(not for all people) and the POST is going much faster.

[Cedric L'homme (rangzen)]

Same problem here and same resolution : IDE to SATA in the bios

The problem is that I just updated the bios and like it's write on the ASRock website, I reset to default values so it means that on ALL this motherboards IDE is actually the default, if you have a SATAII disk you will not be able to install feisty :/
And all people with Dapper who will try to update (like me) will have a very long night (or week like me) :/

I think it's more than medium ...

[jlord87 (moro-87)]

ok,
for now this is the requested output from the now-working-feisty-kubuntu-linux installed in my pata hd.

I don't have now an older version installed, but tonight i'll install an ubuntu dapper and after a system update i'll upload the output of the same command of this attachment.

[jlord87 (moro-87)]

Here I am!!
i've just installed ubuntu dapper and is up to date...the root is installed in the sata disk...and i've switched the bios from SATA to IDE...
and all works...

here you'll find the output required...

bye!

[GabrielGrant (gabrielgrant)]

Ok, thats awesome. Thank you very much for this extra bit of info.

We've clearly established that this is a regression from previous versions, and have all info that should be required, so I'm going to pass this off to the Ubuntu Kernel team and change the status to confirmed. Also, based on the criteria at https://wiki.ubuntu.com/Bugs/Importance I think that the importance level should be bumped up to "High", as it both "has a severe impact on a small portion of Ubuntu users" and is "a problem with an essential hardware component", so if someone from QA could do that, we'd appreciate it.

Thanks again everyone, and especially jlord87, for taking the time to help improve Ubuntu.

-Gabriel

[Cedric L'homme (rangzen)]

A come back for this bug since 2.6.20-16 :/

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.