Dapper, Feisty, and Gutsy -- Disk errors when trying to install from CD, but works via apt-get dist-upgrade

Bug #151792 reported by Slackjaw77
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Hello,

  I initially installed breezy on my AMD64 machine, but installed it with the 32bit version. Now that the 64bit apps have matured to a more agreeable state, I want to migrate my installation to a 64bit one. The problem I now have is with the CD for Dapper, Feisty, and Gutsy, is that the refuse to activate my SATAII 1.5gb/s disks.

  My system setup is as follows.
GA-M55SLI-S4 (rev 1.0)
  2 x Seagate ST3250823AS (250GB sata II 1.5gb/s) (firmware rev 3.03, 3.06)
2 x 1420SA (JBOD configuration)
  6 x Seagate ST3500630AS (500Gb sata II 1.5gb/s) (firmware rev 3.AAE)

Breezy saw my 6 ST3500630AS's and so did Dapper, and Feisty when I went through the apt-get dist-upgrade process. it works fine right now in fact.

No I've broken off my mirror that consisted of the 2 ST3250823AS's. I've attempted to install Dapper, Feisty, and Gutsy directly from the CD (32 bit, and 64bit), but each installation has a very very hard time activating the 6 ST3500630AS's, if it happens at all. Now it's possible that they are trying to utilize the hostraid function on the cards, but I don't know how to disable that, as I'm not using it as anything other than a JBOD configuration. Maybe there are some residuals left from the breezy days that haven't been completed dist-upgraded away (which is a good thing in my case)?

What info will help for diagnosis of this problem?

TIA,

Slackjaw-

description: updated
Revision history for this message
Slackjaw77 (alienresidents) wrote :

files included in tarball...

/var/log/messages
hdparm -I /dev/sd[a-h]
lspci -vvv
uname -a

Slackjaw-

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

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

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!

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.