Question about linux and AMD based chipsets/onboard raid

Brian Cluff brian at snaptek.com
Sun Oct 21 19:28:29 MST 2012


Aarrrg, sorry I had to 0 the whole drive without any payoff, I really 
thought that would yield results.

As for your current problem, at the grub prompt, press e and edit the 
boot line, delete the words quiet and splash and then press CTRL+x to 
boot.   That should allow you to see all the boot process in all it's 
glory including the line that it is getting stuck on.

With any luck it's actually getting hung up on the splash screen itself 
and will just boot.  Then all you'll have to do is remove those options 
from the /etc/default/grub file and then update-grub.

If not, you should at least have a better idea of what to look for now.

Brian Cluff

On 10/21/2012 02:25 PM, Stephen wrote:
> So after 0ing my drive, removing all other drives and still gettign no
> results i gave up on 12.04 install media. also having a failure wiht
> dist-upgradeing from 10.04 once it went to 12.04 i tried a 11.04
> server install media. dist upgrade it to current and was still able to
> boot. sheesh do not try this hardware combination. it has officially
> earned PITA status.
>
> new hiccup. I cannot get it to boot smoothly without intervention. if
> i let it boot (still entirely on its own drive) it gets out of grub
> and sits at a black screen. if i choose recovery then normal boot its
> fine. even after turning on lightDM. fun thing is i am not sure what i
> would be looking for on this. suggestions would be appreciated
> certainly.
>
> On Thu, Oct 18, 2012 at 8:06 PM, Stephen <cryptworks at gmail.com> wrote:
>> Funny thing is 10.10, 11.4, and 11.10 were fine with the array's in place
>> once 12.4 made the rounds it fell over. If i knew more about grub and udev i
>> could probably bring it back up.
>>
>> On Oct 18, 2012 7:28 PM, "Brian Cluff" <brian at snaptek.com> wrote:
>>>
>>> Hmmmm, that should have been good enough, but I guess they could have put
>>> it in the middle.  It's not unheard of.
>>>
>>> Like I said, something is triggering that device mapper on your drive, so
>>> there has to be something on the drive that it likes.
>>>
>>> Brian Cluff
>>>
>>> On 10/18/2012 07:04 PM, Stephen wrote:
>>>>
>>>> Generally i run the quick zero which is the first and last 300mb i hiess
>>>> the next step is finding a home for the data and the 10+ hours to zero
>>>> the long way.
>>>>
>>>> On Oct 18, 2012 6:45 PM, "Brian Cluff" <brian at snaptek.com
>>>> <mailto:brian at snaptek.com>> wrote:
>>>>
>>>>      Did you zero the drive all the way to the end, or just the first
>>>>      part. Also maybe you zeroed the partition and not the drive? Many of
>>>>      the raid superblocks are at the very end of the drive, and it would
>>>>      still be catching them if you haven't done the whole thing.
>>>>
>>>>      I really think this is whats happening since the Device Mapper is
>>>>      trying to grab hold of it.
>>>>
>>>>      Brian Cluff
>>>>
>>>>      On 10/18/2012 12:50 PM, Stephen wrote:
>>>>
>>>>          well  4 of the 6 drives involved are actively part of a raid.
>>>>          the one
>>>>          i am using for Linux was already 0ed for that very reason, i do
>>>>          still
>>>>          have a usb HDD still attached so i will try disconnecting that.
>>>>
>>>>          odd thing is i was able to boot a 10.10x64 no issue and installed
>>>>          there and have been doing dist-upgrades to current. i will take
>>>>          a 2nd
>>>>          look but its is really puzzling.
>>>>
>>>>          I will certainly have to keep an eye out. I haven't even figured
>>>> out
>>>>          how i'm going to configure grub yet to get multiple boot set up.
>>>>          i may
>>>>          leave it ghetto and just use bios.
>>>>
>>>>          On Thu, Oct 18, 2012 at 12:31 PM, Brian Cluff <brian at snaptek.com
>>>>          <mailto:brian at snaptek.com>> wrote:
>>>>
>>>>              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?
>>>>
>>>>
>>>>              ------------------------------__---------------------
>>>>              PLUG-discuss mailing list -
>>>>              PLUG-discuss at lists.plug.__phoenix.az.us
>>>>              <mailto:PLUG-discuss at lists.plug.phoenix.az.us>
>>>>              To subscribe, unsubscribe, or to change your mail settings:
>>>>
>>>> http://lists.PLUG.phoenix.az.__us/mailman/listinfo/plug-__discuss
>>>>
>>>> <http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>      ------------------------------__---------------------
>>>>      PLUG-discuss mailing list - PLUG-discuss at lists.plug.__phoenix.az.us
>>>>      <mailto:PLUG-discuss at lists.plug.phoenix.az.us>
>>>>      To subscribe, unsubscribe, or to change your mail settings:
>>>>      http://lists.PLUG.phoenix.az.__us/mailman/listinfo/plug-__discuss
>>>>      <http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------
>>>> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>>>
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
>



More information about the PLUG-discuss mailing list