On Sun, 2011-10-02 at 23:13 -0500, tclug-list-request at mn-linux.org wrote: > Send tclug-list mailing list submissions to > tclug-list at mn-linux.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > or, via email, send a message with subject or body 'help' to > tclug-list-request at mn-linux.org > > You can reach the person managing the list at > tclug-list-owner at mn-linux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tclug-list digest..." > > > Today's Topics: > > 1. Re: tclug-list Digest, Vol 82, Issue 2 (gk) > 2. Re: can't make partition bootable with in Ubuntu 10.10 > Alternate install (Mike Miller) > 3. Re: can't make partition bootable with in Ubuntu 10.10 > Alternate install (Mike Miller) > 4. Re: can't make partition bootable with in Ubuntu 10.10 > Alternate install (kelly) > 5. Re: can't make partition bootable with in Ubuntu 10.10 > Alternate install [SOLVED] (Mike Miller) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 02 Oct 2011 12:01:50 -0500 > From: gk <gm5729 at gmail.com> > To: tclug-list at mn-linux.org > Subject: Re: [tclug-list] tclug-list Digest, Vol 82, Issue 2 > Message-ID: <1317574910.13897.4.camel at localhost> > Content-Type: text/plain; charset="utf-8" > > On Sun, 2011-10-02 at 12:00 -0500, tclug-list-request at mn-linux.org > wrote: > > Send tclug-list mailing list submissions to > > tclug-list at mn-linux.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > or, via email, send a message with subject or body 'help' to > > tclug-list-request at mn-linux.org > > > > You can reach the person managing the list at > > tclug-list-owner at mn-linux.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of tclug-list digest..." > > > > > > Today's Topics: > > > > 1. Re: can't make partition bootable with in Ubuntu 10.10 > > Alternate install (Mike Miller) > > 2. Re: can't make partition bootable with in Ubuntu 10.10 > > Alternate install (Thomas Lunde) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sat, 1 Oct 2011 18:40:46 -0500 (CDT) > > From: Mike Miller <mbmiller+l at gmail.com> > > To: TCLUG Mailing List <tclug-list at mn-linux.org> > > Subject: Re: [tclug-list] can't make partition bootable with in Ubuntu > > 10.10 Alternate install > > Message-ID: <alpine.DEB.2.00.1110011831350.4486 at taxa.psych.umn.edu> > > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > > > I put this off for awhile and now I'm back at it. I find it extremely > > disheartening that every set of instructions I find anywhere fails. They > > all fail and this is such a simple problem. I just want to install Ubuntu > > 10.10 with RAID 1 on a pair of identical 2.0 TB disks. I have done it > > maybe 20 times and it has never once been able to boot. > > > > I was hoping to be able to use these instructions from B-o-B... > > > > > > On Tue, 12 Jul 2011, Mr. B-o-B wrote: > > > > > Try to do the raid prep/setup outside of the Ubuntu installer first. > > > > > > This is how I setup software RAID 1's, and this has worked every time > > > for me. I have to be honest I haven't done this on Ubuntu, but I did > > > just load the latest Ubuntu live cd to check, and all the commands exist > > > so this should work fine. I have done this >30 times on Slackware, and > > > a handful of times on Centos & Fedora. I actually used a Slackware > > > install disk to setup the raid's on Fedora & Centos, but this is not > > > necessary. The Ubuntu disk will work just fine. > > > > > > I personally like fdisk to create my partitions, but can use cfdisk (or > > > anything else Ubuntu might have that you like). One disk 1 (lets call > > > it /dev/sda) Create at least two partitions (one for swap & one for /). > > > Change the types on both partitions to "Linux RAID autodetect" type > > > "FD". > > > > I couldn't get through even that part. > > > > The first problem is that fdisk says that I have a GUID partition and I > > should use GNU parted. In gparted I can delete partitions but not so much > > that fdisk doesn't complain about the GUID partitioning. So I need to > > know what I am supposed to be doing with fdisk here. Do I really want an > > msdos partition? How is this done? > > > > Unfortunately, the detailed B-o-B instructions didn't help me (though I am > > dying to try them) because I couldn't get past this initial step. > > > > Every other set of instructions I've found on the web fails at some point. > > With at least one of them I get all the way through, it seems like it has > > worked, but then I try to start the machine and it won't boot. Next I > > look for ways to fix that and I haven't been able to fix it. So I delete > > everything and start over. > > > > After working on this for dozens of hours I am ready to pay someone to do > > it for me. Can any of you do this? How much do you want? > > > > Mike > > > > > > ------------------------------ > > > > Message: 2 > > Date: Sun, 2 Oct 2011 07:19:16 -0500 > > From: Thomas Lunde <tlunde at gmail.com> > > To: TCLUG Mailing List <tclug-list at mn-linux.org> > > Subject: Re: [tclug-list] can't make partition bootable with in Ubuntu > > 10.10 Alternate install > > Message-ID: <263B410A-21E3-4D43-8EC0-490DB6510A62 at gmail.com> > > Content-Type: text/plain; charset=us-ascii > > > > Mike - > > > > If you don't care about the current contents of either disk, here is one way to get rid of the error message about GUID partitions being present. > > > > Boot from a live CD with just these two hard drives attached to the system. Once booted, open up a terminal window. Use the df command to see if anything on either drive has been mounted. If so, they will appear as /dev/sda1 (or similar). No partitions may have been mounted, if there is just junk on the drives. If a partition has been mounted, use the command sudo umount /dev/sda1 (or whatever sd partitions you saw from the df command) to remove them from the df output. > > > > Use the command ls /dev/sd* to verify that the system "sees" the two drives and that they are listed as sda and sdb. (You'll want to adjust the letters below if they come up as something else.) > > > > Then, issue this command: > > sudo dd if=/dev/zero of=/dev/sda bs=1024 count=1024 > > and do it again for sdb and any partition tables on the drives will be gone. > > > > Now, you should be able to follow the installation instructions you've had. > > > > Thomas > > > > > > > > On Oct 1, 2011, at 6:40 PM, Mike Miller <mbmiller+l at gmail.com> wrote: > > > > > I put this off for awhile and now I'm back at it. I find it extremely disheartening that every set of instructions I find anywhere fails. They all fail and this is such a simple problem. I just want to install Ubuntu 10.10 with RAID 1 on a pair of identical 2.0 TB disks. I have done it maybe 20 times and it has never once been able to boot. > > > > > > I was hoping to be able to use these instructions from B-o-B... > > > > > > > > > On Tue, 12 Jul 2011, Mr. B-o-B wrote: > > > > > >> Try to do the raid prep/setup outside of the Ubuntu installer first. > > >> > > >> This is how I setup software RAID 1's, and this has worked every time for me. I have to be honest I haven't done this on Ubuntu, but I did just load the latest Ubuntu live cd to check, and all the commands exist so this should work fine. I have done this >30 times on Slackware, and a handful of times on Centos & Fedora. I actually used a Slackware install disk to setup the raid's on Fedora & Centos, but this is not necessary. The Ubuntu disk will work just fine. > > >> > > >> I personally like fdisk to create my partitions, but can use cfdisk (or anything else Ubuntu might have that you like). One disk 1 (lets call it /dev/sda) Create at least two partitions (one for swap & one for /). Change the types on both partitions to "Linux RAID autodetect" type "FD". > > > > > > I couldn't get through even that part. > > > > > > The first problem is that fdisk says that I have a GUID partition and I should use GNU parted. In gparted I can delete partitions but not so much that fdisk doesn't complain about the GUID partitioning. So I need to know what I am supposed to be doing with fdisk here. Do I really want an msdos partition? How is this done? > > > > > > Unfortunately, the detailed B-o-B instructions didn't help me (though I am dying to try them) because I couldn't get past this initial step. > > > > > > Every other set of instructions I've found on the web fails at some point. With at least one of them I get all the way through, it seems like it has worked, but then I try to start the machine and it won't boot. Next I look for ways to fix that and I haven't been able to fix it. So I delete everything and start over. > > > > > > After working on this for dozens of hours I am ready to pay someone to do it for me. Can any of you do this? How much do you want? > > > > > > Mike > > > _______________________________________________ > > > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > > > tclug-list at mn-linux.org > > > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > > > > > ------------------------------ > > > > _______________________________________________ > > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > > tclug-list at mn-linux.org > > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > > > End of tclug-list Digest, Vol 82, Issue 2 > > ***************************************** > > Your limitation may be the Bios with how many drives it can see. ie 2tb > limit vs 4tb. GRUB 2 should always be used with the GRUB2 Utility disk available. GRUB2 has to have a special 7E partition BEFORE the /boot partition which also needs to be separate. Then you can for the sake of argument have just a / partition. The numbering scheme is different for GRUB2 than GRUB1 and I have foundit best to use something like this.... /(hd0,1)/vmlinuz...... the same holds true with the kernel line. A set command will tell where the /root is located for example (hd0,2). That is why the Utility disk recommendation because sometimes the installer won't find the proper partition. The phrase "boot" always ends the section. I know this is not GRUB2 here but the mapping is a declaration that is made not only in fstab, but it MUST be declared in your modules that load at boot time. In my case loop/luks and fuse are declared and generated by mkinitcpio each time in specific order so the proper module will be available when needed. In this example it was easier to use labels vs. UUIDS which I prefer but UUIDS are used in in fstab. GRUB1 example for mapped devices akin to mapped for RAID # (0) Arch Linux title Arch Linux Stock Kernel lock root (hd0,0) kernel /vmlinuz-linux root=/dev/mapper/masayana cryptdevice=/dev/sda2:masayana ro nodma vga=791 initrd /initramfs-linux.img boot # /etc/fstab: static file system information # # <file system> <dir> <type> <options> <dump> <pass> devpts /dev/pts devpts defaults 0 0 shm /dev/shm tmpfs nodev,nosuid,noexec 0 0 tmpfs /tmp tmpfs defaults,nodev,nosuid,mode=1777 0 0 /dev/mapper/masayana / ext2 defaults 0 1 UUID=166a497e-6435-4ef4-8198-dc781ce73678 /boot ext2 defaults,noatime 0 1 #/dev/sdb1: UUID="8d71988a-7103-4f6a-a119-145960e2d94e" TYPE="crypto_LUKS" #/dev/sda1: LABEL="boot" UUID="166a497e-6435-4ef4-8198-dc781ce73678" TYPE="ext2" #/dev/sda2: UUID="2ecb1abd-5cfc-4c44-943e-3c78c6faf967" TYPE="crypto_LUKS" #/dev/sdc1: UUID="a47f96ae-db52-48ce-b99d-752daa4a482d" TYPE="crypto_LUKS" #/dev/mapper/masayana: LABEL="ourhouse" UUID="92102d0f-5efb-49a7-8d83-2b1daf1605e6" TYPE="ext2" Hope this helps. -- -- gk http://gm5729.blogspot.com Please conserve natural resources and print out this email if absolutely necessary. If you need a copy save as a PDF/DJVU format on your computer. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20111003/e2f7a177/attachment.pgp>