Do you have any flash drives or anything connected it's getting confused with? Occasionally my computer will reboot with a few flash drives I have I forget can/are bootable and my system will boot foreignly freaking me out for 2 seconds until I scowl and disconnect the flash. When I don't, I go on a goose chase forgetting about it, and usually ends up a flash disk plugged in somewhere.

Otherwise I'll say your system is still seeing the disks and trying to boot a raw partition vs using the fakeraid labels. Windoze loves mbr, linux tends to be partition based with supersector, add in fakeraid, and I never had a good time trying. The os usually still sees the disks present, so wouldn't surprise me if the bootloader and kernel get them confused in reference as udev builds device resources. Might need to hack around with udev to NOT see them if the bios doesn't have an option to hide them entirely (or fix a bug potentially not hiding them).

I insisted on raid1 for both, what usually worked for me was using linux first, or your /boot partition first, then windoze, then another partition as a lvm for ubuntu. If windoze is first, it always screws with it, aside from just frying your mbr. As long as the first partition is neutral, they seem to both behave. I made the raid disk partition a first 200mb slice to use for /boot first, second a win partition, third linux. Partition the three with a bootable linux cd/flash first to the /dev/mapper/<raid disk> devices but don't install it, reboot/install windoze (xp at least, ymmv above as I don't know), then install ubuntu with /boot on first and everything else in the third (I do lvm pv here), and install grub to mbr to overwrite windoze's.

This worked reliably with both then until a nforce bios update incident changed the uuid hash for it and breaking grub and windoze from booting. I was not amused, and put a knife into ever using fakeraid again. Google the term and you'll read the hate stories too rife with issues. By that point I used only ubuntu anyways, so just ran software raid since mostly reliably.

Windoze lives in a vm entirely for me nowadays, but then again I don't game on it either, so I can. Vbox 3d drivers in win vm are still poop and made the host unstable for me to try and game. Only purpose I has for windoze was games and visio, visio works dandy in 2d. Rest I have consoles for, though I can't do fps without wsad and a mouse for the life of me.

-mb


On 10/18/2012 07:30 AM, Dazed_75 wrote:
You said you were installing ubuntu to the independent drive (and one of
the messages indicates sdb), but where is it putting GRUB?  You may need
to use the advanced option to place GRUB on that same drive.  Sorry, I
don't know what screen the option is on during install but it used to be
in the lower right corner.  Seems like it would be on the screen where
you accept all the changes before actually proceeding with the install.

On Wed, Oct 17, 2012 at 7:42 PM, Stephen <[email protected]
<mailto:[email protected]>> wrote:

    I have an AMD based chiset and i am trying to get ubuntu to boot right
    now and it is stalling, and i am having trouble ironing out what is
    going on.

    I have onbaord raid drives attached to the onboard raid chipset
    (SB710) however i am not intending to install to those drives the
    drive i wish to install to is actually a SATA connected single drive
    but i am having the worst time getting Ubuntu 12.04 to even finish its
    boot cycle. and im not getting allot of feedback.

    The errors i am getting are ata_id[336]: HDIO_GET_IDENTITY failed for
    '/dev/sdb': Invalid argument
    - this is with all Raid disks disconnected and raid turned off in
    bios. just a single SATA HDD

    I get one of the two following errors if i have raid disks attached

    A similar entry as above comes up or i get
    udevd[167] inotify_add_watch(6, /dev/dm-1, 10) failed: No Such file
    or directory

    the most promising option i have so far is booting with nodmraid but
    it seems to just hang and go no place after detecting my CDrom devices

    This is rather perplexing overall.

    Ideally i would like my 2 onboard raids to be connected running
    windows and then let linux run amok on my extra sata hdd but it either
    is really pissed off in a way i cannot figure out or it really does
    not like that port.

    Anyone have any thoughts?
    --
    A mouse trap, placed on top of your alarm clock, will prevent you from
    rolling over and going back to sleep after you hit the snooze button.

    Stephen
    ---------------------------------------------------
    PLUG-discuss mailing list - [email protected]
    <mailto:[email protected]>
    To subscribe, unsubscribe, or to change your mail settings:
    http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss




--
Dazed_75 a.k.a. Larry

Please protect my address like I protect yours. When sending messages to
multiple recipients, always use the BCC: (Blind carbon copy) and not To:
or CC:. Remove all addresses from the message body before sending a
Forwarded message. This can prevent spy programs capturing addresses
from the recipient list and message body.


---------------------------------------------------
PLUG-discuss mailing list - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - [email protected]
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

Reply via email to