Re: Question about linux and AMD based chipsets/onboard raid
Question, Is the video one of the older/non supported AMD chipsets (HD 4000 and older)? Are you using Catalyst driver? If yes to both then see http://www.unixmen.com/ubuntu-12-10-and-amd-catalyst-problem-solved/ It sounds like this may be what you are running into. James C. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
No onboard/AMD video. Just the 550ti nvidia gpu On Oct 22, 2012 7:32 PM, James Crawford jre...@gmail.com wrote: Question, Is the video one of the older/non supported AMD chipsets (HD 4000 and older)? Are you using Catalyst driver? If yes to both then see http://www.unixmen.com/ubuntu-** 12-10-and-amd-catalyst-**problem-solved/http://www.unixmen.com/ubuntu-12-10-and-amd-catalyst-problem-solved/ It sounds like this may be what you are running into. James C. --**- PLUG-discuss mailing list - plug-disc...@lists.plug.**phoenix.az.usPLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.**us/mailman/listinfo/plug-**discusshttp://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
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 cryptwo...@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 br...@snaptek.com wrote: H, 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 br...@snaptek.com mailto:br...@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 br...@snaptek.com mailto:br...@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
Re: Question about linux and AMD based chipsets/onboard raid
and i forget the most important thing, this seems to be graphical only. if i try i can ssh intot he box from the outside. so the machine is booting, it just doesn't seem to like the graphical part of the boot process. On Sun, Oct 21, 2012 at 2:25 PM, Stephen cryptwo...@gmail.com 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 cryptwo...@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 br...@snaptek.com wrote: H, 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 br...@snaptek.com mailto:br...@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 br...@snaptek.com mailto:br...@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
Re: Question about linux and AMD based chipsets/onboard raid
On 10/21/2012 02:27 PM, Stephen wrote: and i forget the most important thing, this seems to be graphical only. if i try i can ssh intot he box from the outside. so the machine is booting, it just doesn't seem to like the graphical part of the boot process. What motherboard and video hardware are you using? -- KevinO --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
GA-MA770T-UD3P and a GTX 550Ti On Sun, Oct 21, 2012 at 2:31 PM, KevinO ke...@kevino.org wrote: On 10/21/2012 02:27 PM, Stephen wrote: and i forget the most important thing, this seems to be graphical only. if i try i can ssh intot he box from the outside. so the machine is booting, it just doesn't seem to like the graphical part of the boot process. What motherboard and video hardware are you using? -- KevinO --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- 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 - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
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 cryptwo...@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 br...@snaptek.com wrote: H, 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 br...@snaptek.com mailto:br...@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 br...@snaptek.com mailto:br...@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
Re: Question about linux and AMD based chipsets/onboard raid
0ing the drive was not a bad thing. When trying to mount it via rawdisk in virtualbox i was getting some odd errors and then i had some directories populate and it got strange from there. It also eliminated some errors so something was lingering someplace. Will know more about the splash screen when i get home. Thanks for the tip! On Oct 21, 2012 7:28 PM, Brian Cluff br...@snaptek.com wrote: 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 cryptwo...@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 br...@snaptek.com wrote: H, 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 br...@snaptek.com mailto:br...@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 br...@snaptek.com mailto:br...@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
Re: Question about linux and AMD based chipsets/onboard raid
well it still stalls a bit, but it booted when i got home.not sure what thats all about but ill take it. On Sun, Oct 21, 2012 at 7:34 PM, Stephen cryptwo...@gmail.com wrote: 0ing the drive was not a bad thing. When trying to mount it via rawdisk in virtualbox i was getting some odd errors and then i had some directories populate and it got strange from there. It also eliminated some errors so something was lingering someplace. Will know more about the splash screen when i get home. Thanks for the tip! On Oct 21, 2012 7:28 PM, Brian Cluff br...@snaptek.com wrote: 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 cryptwo...@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 br...@snaptek.com wrote: H, 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 br...@snaptek.com mailto:br...@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 br...@snaptek.com mailto:br...@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
Re: Question about linux and AMD based chipsets/onboard raid
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 cryptwo...@gmail.com 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 - PLUG-discuss@lists.plug.phoenix.az.us 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 - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
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 cryptwo...@gmail.com mailto:cryptwo...@gmail.com 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 - PLUG-discuss@lists.plug.phoenix.az.us mailto:PLUG-discuss@lists.plug.phoenix.az.us 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
Re: Question about linux and AMD based chipsets/onboard raid
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@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
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 br...@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@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss -- 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 - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
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 br...@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@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@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: Question about linux and AMD based chipsets/onboard raid
H, 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 br...@snaptek.com mailto:br...@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 br...@snaptek.com mailto:br...@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-disc...@lists.plug.__phoenix.az.us mailto:PLUG-discuss@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-disc...@lists.plug.__phoenix.az.us mailto:PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.__us/mailman/listinfo/plug-__discuss
Re: Question about linux and AMD based chipsets/onboard raid
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 br...@snaptek.com wrote: H, 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 br...@snaptek.com mailto:br...@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 br...@snaptek.com mailto:br...@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-disc...@lists.plug.__phoe**nix.az.ushttp://phoenix.az.us mailto:PLUG-discuss@lists.**plug.phoenix.az.usPLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az._**_us/mailman/listinfo/plug-__* *discuss
Question about linux and AMD based chipsets/onboard raid
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 - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
