Lucid Asrock ION sata disk not detected?

Bug #567557 reported by X3
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned
Lucid
Won't Fix
Undecided
Unassigned

Bug Description

Minimal Lucid install 32 and 64bit have failed systematically up to and inclusive of files available on the 19th April.

Purpose is to test our xbmc complete installer (bash ncurses script) with the newer Ubuntu distro, since both Jaunty and Karmic are fully working and compatible as well as installing with no issues.. This project is affected by the non install possibility.

Expected the partitioner to detect disk and present normal partitioning options.

Inserting and running disks works ok until, system hangs and install does not proceed, when the disk partitioner starts detecting disks, this hangs at about 43%.

This is likely to affect all ION based systems, due to their similar hw profiles and components. (confirmed various ION based machines similar issue)

attached are some logs which hopefully help diagnose this and help fix.

If extra logs are needed please ask.

***Edit added partitioner as possible package at fault here. Not sure about that.

== Regression details ==
Discovered in version: Lucid
Last known good version: Karmic

Revision history for this message
X3 (x3lectric) wrote :
  • Logs Edit (718.5 KiB, application/rar)
description: updated
affects: dmraid (Ubuntu) → partitioner (Ubuntu)
description: updated
Revision history for this message
X3 (x3lectric) wrote :

Just tested the full desktop installer and it doesnt install either to hdd on system, whatever it is, Lucid is borked big time.

Revision history for this message
X3 (x3lectric) wrote :

Is anyone ever going to look at this?

description: updated
tags: added: lucid regression-potential
Revision history for this message
Andreas Noteng (andreas-noteng) wrote :

Hello and thanks for reporting this bug, I am sorry that nobody have had the time to look at this bug yet. I am however not familiar with the install process and not the right person to triage this bug.
To get some help/attention to this bug, irc might be a good place to start. #ubuntu+1 and #ubuntu-testing on irc.ubuntu.com might be a good place to ask.

Revision history for this message
X3 (x3lectric) wrote :

Hi

I would appreciate that if you could perhaps pass this to someone who can triage this, as it happens IRC and both channels you mention are very disappointing, in my experience it only fuels frustration.

Hope you can help otherwise this will never get looked at.

Revision history for this message
X3 (x3lectric) wrote :

can anyone pls have a look at this at all.

Revision history for this message
Daniel Holbach (dholbach) wrote :

X3: please don't subscribe random teams to bug reports.

The Ubuntu Community Council has nothing to do with development.
Subscribing the Ubuntu Developers team to the bug means that every single developer gets emails sent about this.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Which ISO did you use to install?

affects: partitioner (Ubuntu) → ubiquity (Ubuntu)
Revision history for this message
Colin Watson (cjwatson) wrote :

I'd look at your logs, but:

$ unrar -xf logs.rar

unrar 0.0.1 Copyright (C) 2004 Ben Asselstine, Jeroen Dekkers

Extracting from /home/cjwatson/logs.rar

Extracting logs/dmesg Failed
Extracting logs/hardware-summary Failed
Extracting logs/messages Failed
Extracting logs/syslog Failed
4 Failed

Could you attach the logs in a friendlier format? Usually it's best to just attach each of them as separate attachments.

I don't need dmesg, hardware-summary, or messages, but I do need the partman log in addition to syslog.

Revision history for this message
X3 (x3lectric) wrote :

@ daniel

used the isos available now from here http://cdimages.ubuntu.com/netboot/lucid/ and also all the available desktop install images from http://cdimages.ubuntu.com/releases/10.04/release/

@ colin

the syslog is 8MB

The partman log I cant find for the minimal karmic install and since the lucid fails no logs are created.

I did a full search for partman and no yielded results, please let me know if I can create the information required for you using my current install.

Revision history for this message
Plecebo (larry-schwerzler) wrote :

I ran into a similar issue on a full desktop install on another machine and found that dmraid was causing the issue.

For me the disk partitioner in the installer was hanging, showing no hard drives. I couldn't continue, all I could do was quit.

For me the fix was to remove dmraid

Not sure how to do it with the netboot iso, but with the full x86 iso I booted into the live cd (works fine). and opened a terminal and ran:

sudo apt-get remove dmraid

after it was removed the installer detected the hd.

Perhaps something similar could be done in the netboot iso?

I have a ION machine at home that I was hoping to install 10.4 on tonight. I'll give it a shot and see what I can come up with.

NOTE: In the full .iso there is an F6 option for nodmraid or some such.... this STILL causes the HD to not be detected.

Hope that is helpful.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

X3, did you tried Maverick, and if so, is it still an issue ?

tags: added: regression-release
removed: regression-potential
description: updated
Changed in ubiquity (Ubuntu Lucid):
status: New → Confirmed
Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
X3 (x3lectric) wrote :

No I didnt try maverick, nor is there any point, simply because the xbmc is barely now supporting lucid, I dont think dismissing lucid altogether, without fixing it there is a solution, not that t matters, since I doubt a fix will ever appear.

One waits months here just to get irrelevant questions.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in ubiquity (Ubuntu Lucid):
status: Confirmed → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.