Question about linux and AMD based chipsets/onboard raid

[Brian Cluff]

The fact that the device mapper is getting involved with the drive leads 
me to believe that the drive was part of a raid, or at least configured 
by your raid controller at one time and there is now a superblock on it 
that is messing up everything.
You'll probably need to zero out that superblock before things will 
start to behave correctly.

Brian Cluff

On 10/17/2012 07:42 PM, Stephen 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?
>