Re: Manual Partitioning and LVM, Re: Puzzled
On Thu, Dec 06, 2012 at 15:36:29 -0500, Gene Czarcinski wrote: The problem turned out to be an "old" mobo with an enabled floppy interface with nothing attached. Disable the interface in the BIOS and things work. However, that should not have hung up the install. This issue sounds familiar. There have been discussions about whether the floppy driver should be loaded by default, because with some BIOS' booting can take several minutes to determine that there really isn't an attached floppy drive. Disabling the floppy controller in the BIOS when that aren't any floppy drives attached to it helps in many cases. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/06/2012 12:19 PM, Gene Czarcinski wrote: On 12/06/2012 10:12 AM, Gene Czarcinski wrote: On 12/05/2012 09:07 PM, Chris Murphy wrote: On Dec 5, 2012, at 11:24 AM, Gene Czarcinski wrote: No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. This is DVD? Netinst? Or LiveCD? I'm using a LiveCD, and VGs are active already. Did a vgchange -a y and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. On Dec 5, 2012, at 1:00 PM, Gene Czarcinski wrote: OK, I boot up the "live" gnome desktop and used it to install. Yes, all of the LVs were there and it figured out all of the installed/bootable systems. I was able to manually configure and re-use partitions. OK so you're saying it works with the LiveCD but doesn't with DVD or Netinst? Please file a bug. And reproduce the problem, once you get to Manual Partitioning, go to a shell and grab the .log files from /tmp and post those to the bug report. This is arguably a release blocking bug if it's reproducible. Yup! To be clear, I did not try the netinstall. It will be later today but I will run the install yet again, collect the info and file a bug report. Just in case it is something about the specific hardware, I will also attempt doing this with another system. Son of a gun! Booted up the install DVD on another system and it looks great! Partitions, LVs, other systems (it is multi-boot) just like the live one did. OK, there still seems to be some systems (at least mine) that does have a problem so I will collect what info I can and submit a bug report. BUT, it did not offer me a choice of where to install grub2 (MBR or boot partition) … it did MBR which was not too bad because I could easily recover. In beta, anaconda 18.29 has an option to not install a bootloader. 1.) It doesn't work, that's fixed in the 18.34 and 18.35 I've tested yesterday; and 2.) there is no option to install GRUB 2 to a partition because it's not recommended by upstream for ext4 to take block lists, which is the only way to get GRUB to install to an ext4 partition since ext4 only has 1024 bytes of boot sector padding. So if you want GRUB2 on a partition, you have to 'grub2-install --force /dev/sdaX' yourself. Or better, if you're using some other instance of GRUB2, is to add a menu entry for that GRUB's My current "don't likes are: 1. Of course the first one is that I cannot specify predefined LVs with the installation DVD. Unless this is fixed, I am likely to be a big user of fedup. 2. It sure would be nice and a lot clearer if "reclaim" was changed to something that did not imply (to me) that I could lose my disks. 3. Software selection needs to be expanded. Yes, I know this can be done once the basic system is in but I am used to doing it all up front. I can live with the current situation. 4. Grub2 and no option to install in a partition. Not really an issue. I knew that I would need to figure out and implement a new way to have multi-boot systems. The problem turned out to be an "old" mobo with an enabled floppy interface with nothing attached. Disable the interface in the BIOS and things work. However, that should not have hung up the install. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/06/2012 10:12 AM, Gene Czarcinski wrote: On 12/05/2012 09:07 PM, Chris Murphy wrote: On Dec 5, 2012, at 11:24 AM, Gene Czarcinski wrote: No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. This is DVD? Netinst? Or LiveCD? I'm using a LiveCD, and VGs are active already. Did a vgchange -a y and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. On Dec 5, 2012, at 1:00 PM, Gene Czarcinski wrote: OK, I boot up the "live" gnome desktop and used it to install. Yes, all of the LVs were there and it figured out all of the installed/bootable systems. I was able to manually configure and re-use partitions. OK so you're saying it works with the LiveCD but doesn't with DVD or Netinst? Please file a bug. And reproduce the problem, once you get to Manual Partitioning, go to a shell and grab the .log files from /tmp and post those to the bug report. This is arguably a release blocking bug if it's reproducible. Yup! To be clear, I did not try the netinstall. It will be later today but I will run the install yet again, collect the info and file a bug report. Just in case it is something about the specific hardware, I will also attempt doing this with another system. Son of a gun! Booted up the install DVD on another system and it looks great! Partitions, LVs, other systems (it is multi-boot) just like the live one did. OK, there still seems to be some systems (at least mine) that does have a problem so I will collect what info I can and submit a bug report. BUT, it did not offer me a choice of where to install grub2 (MBR or boot partition) … it did MBR which was not too bad because I could easily recover. In beta, anaconda 18.29 has an option to not install a bootloader. 1.) It doesn't work, that's fixed in the 18.34 and 18.35 I've tested yesterday; and 2.) there is no option to install GRUB 2 to a partition because it's not recommended by upstream for ext4 to take block lists, which is the only way to get GRUB to install to an ext4 partition since ext4 only has 1024 bytes of boot sector padding. So if you want GRUB2 on a partition, you have to 'grub2-install --force /dev/sdaX' yourself. Or better, if you're using some other instance of GRUB2, is to add a menu entry for that GRUB's My current "don't likes are: 1. Of course the first one is that I cannot specify predefined LVs with the installation DVD. Unless this is fixed, I am likely to be a big user of fedup. 2. It sure would be nice and a lot clearer if "reclaim" was changed to something that did not imply (to me) that I could lose my disks. 3. Software selection needs to be expanded. Yes, I know this can be done once the basic system is in but I am used to doing it all up front. I can live with the current situation. 4. Grub2 and no option to install in a partition. Not really an issue. I knew that I would need to figure out and implement a new way to have multi-boot systems. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/05/2012 09:07 PM, Chris Murphy wrote: On Dec 5, 2012, at 11:24 AM, Gene Czarcinski wrote: No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. This is DVD? Netinst? Or LiveCD? I'm using a LiveCD, and VGs are active already. Did a vgchange -a y and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. On Dec 5, 2012, at 1:00 PM, Gene Czarcinski wrote: OK, I boot up the "live" gnome desktop and used it to install. Yes, all of the LVs were there and it figured out all of the installed/bootable systems. I was able to manually configure and re-use partitions. OK so you're saying it works with the LiveCD but doesn't with DVD or Netinst? Please file a bug. And reproduce the problem, once you get to Manual Partitioning, go to a shell and grab the .log files from /tmp and post those to the bug report. This is arguably a release blocking bug if it's reproducible. Yup! To be clear, I did not try the netinstall. It will be later today but I will run the install yet again, collect the info and file a bug report. Just in case it is something about the specific hardware, I will also attempt doing this with another system. BUT, it did not offer me a choice of where to install grub2 (MBR or boot partition) … it did MBR which was not too bad because I could easily recover. In beta, anaconda 18.29 has an option to not install a bootloader. 1.) It doesn't work, that's fixed in the 18.34 and 18.35 I've tested yesterday; and 2.) there is no option to install GRUB 2 to a partition because it's not recommended by upstream for ext4 to take block lists, which is the only way to get GRUB to install to an ext4 partition since ext4 only has 1024 bytes of boot sector padding. So if you want GRUB2 on a partition, you have to 'grub2-install --force /dev/sdaX' yourself. Or better, if you're using some other instance of GRUB2, is to add a menu entry for that GRUB's My current "don't likes are: 1. Of course the first one is that I cannot specify predefined LVs with the installation DVD. Unless this is fixed, I am likely to be a big user of fedup. 2. It sure would be nice and a lot clearer if "reclaim" was changed to something that did not imply (to me) that I could lose my disks. 3. Software selection needs to be expanded. Yes, I know this can be done once the basic system is in but I am used to doing it all up front. I can live with the current situation. 4. Grub2 and no option to install in a partition. Not really an issue. I knew that I would need to figure out and implement a new way to have multi-boot systems. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Dec 5, 2012, at 7:07 PM, Chris Murphy wrote: > Or better, if you're using some other instance of GRUB2, is to add a menu > entry for that GRUB's cute. I stop thinking, stop typing and hit send… add a menu entry to that first GRUB's grub.cfg using configfile to point to the Fedora grub.cfg. No sense in using grub to chain load another grub. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Wed, 2012-12-05 at 07:39 -0500, Scott Robbins wrote: > On Wed, Dec 05, 2012 at 06:45:08AM -0500, Gene Czarcinski wrote: > > On 12/04/2012 05:55 PM, Chris Murphy wrote: > > > > >On Dec 4, 2012, at 3:13 PM, Chris Murphy wrote: > > > > > > > > >Slightly off topic, I'm kinda liking system-storage-manager new to F18 and > > >installable from the live cd. > > >yum install system-storage-manager > > >ssm list > > > > > >And you'll get a listing of all devices, pools, volumes, and their mount > > >points, better layout all in one place rather than having to go dig for > > >info with multiple tools: fdisk, df, pvscan, lvscan, etc. > > > > > > > > You are right ... ssm is nice. I wonder if there is a gui version planned? > > You mean what mount used to show before systemd? well, no, not at all. the main 'nice thing' about ssm is that it can handle LVM and btrfs nicely, which isn't at all to do with the output of mount. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Dec 5, 2012, at 11:24 AM, Gene Czarcinski wrote: > No Logical Volumes listed. There are only the regular partitions and the > Physical Volume partitions listed under unknown. > > Did a pvscan which showed the three VGs on this system. Then I did a lvscan > which listed all of the Logical Volumes and showing them inactive. This is DVD? Netinst? Or LiveCD? I'm using a LiveCD, and VGs are active already. > Did a vgchange -a y and a of the LVs showed active. I did the > just after the first gui screen came up. > > When I got the manual storage configuration, no LVs shown. On Dec 5, 2012, at 1:00 PM, Gene Czarcinski wrote: >> > OK, I boot up the "live" gnome desktop and used it to install. Yes, all of > the LVs were there and it figured out all of the installed/bootable systems. > I was able to manually configure and re-use partitions. OK so you're saying it works with the LiveCD but doesn't with DVD or Netinst? Please file a bug. And reproduce the problem, once you get to Manual Partitioning, go to a shell and grab the .log files from /tmp and post those to the bug report. This is arguably a release blocking bug if it's reproducible. > > BUT, it did not offer me a choice of where to install grub2 (MBR or boot > partition) … it did MBR which was not too bad because I could easily recover. In beta, anaconda 18.29 has an option to not install a bootloader. 1.) It doesn't work, that's fixed in the 18.34 and 18.35 I've tested yesterday; and 2.) there is no option to install GRUB 2 to a partition because it's not recommended by upstream for ext4 to take block lists, which is the only way to get GRUB to install to an ext4 partition since ext4 only has 1024 bytes of boot sector padding. So if you want GRUB2 on a partition, you have to 'grub2-install --force /dev/sdaX' yourself. Or better, if you're using some other instance of GRUB2, is to add a menu entry for that GRUB's Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/05/2012 01:24 PM, Gene Czarcinski wrote: On 12/05/2012 06:57 AM, Gene Czarcinski wrote: As far as getting F18 installed, some of this is OBE because I used fedup and it worked just fine so I now have a live F18 system for testing. However, I would like the installer to work and of all the parts that I consider critical, storage configuration is first in line. I believe that the best way I can duplicate the problem and get some documentation is to replicate it virtually and get some screenshots. I wonder if the remote display still works? I used that in the past. Now, if only I can remember how to do it. On 12/05/2012 02:41 AM, Chris Murphy wrote: On Dec 4, 2012, at 11:52 PM, Gene Czarcinski wrote: I am not sure how things are suppose to work but I do not see ANY LVs In Manual Partitioning, on the left side, you do not have an +Unknown listing located under -New Fedora 18 Installation? Or there are no LV's listed? I will go back and double check but I do not remember seeing an LVs. No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. Did a vgchange -a y and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. ?? And, yes, I want to re-use previously allocated LVs for my install. There are regular old partitions which I can use for /boot but all of the rest of my disk space is in PVs. What do you get for pvscan and lvscan? Are there inactive LVs? I will need to check. IMO, the whole way storage is being handled in F18 needs to be rethought! Guessing how to do something should never happen. I agree. But I think in your case the trail is leading to a bug not flawed design. I am sure this is a bug. However, I would like some button or whatever "earlier" in the process that says "I know what I am doing, let me manually configure existing partitions and/or LVs or allocate new ones on mount points. Getting a screenshot in anaconda does not work anymore or I would give you one. Suggestions? OK, I boot up the "live" gnome desktop and used it to install. Yes, all of the LVs were there and it figured out all of the installed/bootable systems. I was able to manually configure and re-use partitions. BUT, it did not offer me a choice of where to install grub2 (MBR or boot partition) ... it did MBR which was not too bad because I could easily recover. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/05/2012 06:57 AM, Gene Czarcinski wrote: As far as getting F18 installed, some of this is OBE because I used fedup and it worked just fine so I now have a live F18 system for testing. However, I would like the installer to work and of all the parts that I consider critical, storage configuration is first in line. I believe that the best way I can duplicate the problem and get some documentation is to replicate it virtually and get some screenshots. I wonder if the remote display still works? I used that in the past. Now, if only I can remember how to do it. On 12/05/2012 02:41 AM, Chris Murphy wrote: On Dec 4, 2012, at 11:52 PM, Gene Czarcinski wrote: I am not sure how things are suppose to work but I do not see ANY LVs In Manual Partitioning, on the left side, you do not have an +Unknown listing located under -New Fedora 18 Installation? Or there are no LV's listed? I will go back and double check but I do not remember seeing an LVs. No Logical Volumes listed. There are only the regular partitions and the Physical Volume partitions listed under unknown. Did a pvscan which showed the three VGs on this system. Then I did a lvscan which listed all of the Logical Volumes and showing them inactive. Did a vgchange -a y and a of the LVs showed active. I did the just after the first gui screen came up. When I got the manual storage configuration, no LVs shown. ?? And, yes, I want to re-use previously allocated LVs for my install. There are regular old partitions which I can use for /boot but all of the rest of my disk space is in PVs. What do you get for pvscan and lvscan? Are there inactive LVs? I will need to check. IMO, the whole way storage is being handled in F18 needs to be rethought! Guessing how to do something should never happen. I agree. But I think in your case the trail is leading to a bug not flawed design. I am sure this is a bug. However, I would like some button or whatever "earlier" in the process that says "I know what I am doing, let me manually configure existing partitions and/or LVs or allocate new ones on mount points. Getting a screenshot in anaconda does not work anymore or I would give you one. Suggestions? Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Wed, Dec 05, 2012 at 06:45:08AM -0500, Gene Czarcinski wrote: > On 12/04/2012 05:55 PM, Chris Murphy wrote: > >On Dec 4, 2012, at 3:13 PM, Chris Murphy wrote: > > > > > >Slightly off topic, I'm kinda liking system-storage-manager new to F18 and > >installable from the live cd. > >yum install system-storage-manager > >ssm list > > > >And you'll get a listing of all devices, pools, volumes, and their mount > >points, better layout all in one place rather than having to go dig for info > >with multiple tools: fdisk, df, pvscan, lvscan, etc. > > > > > You are right ... ssm is nice. I wonder if there is a gui version planned? You mean what mount used to show before systemd? Sometimes, though I will FREELY admit this is probably just old curmudgeon-ness, it seems that we keep getting new tools to do what the old ones did. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Spike: Willow, tell 'em what I did. Willow: You said you were gonna kill me, then Buffy. Spike: Yes, bad, but let's skip that part and get to the part where I couldn't bite you. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
As far as getting F18 installed, some of this is OBE because I used fedup and it worked just fine so I now have a live F18 system for testing. However, I would like the installer to work and of all the parts that I consider critical, storage configuration is first in line. I believe that the best way I can duplicate the problem and get some documentation is to replicate it virtually and get some screenshots. I wonder if the remote display still works? I used that in the past. Now, if only I can remember how to do it. On 12/05/2012 02:41 AM, Chris Murphy wrote: On Dec 4, 2012, at 11:52 PM, Gene Czarcinski wrote: I am not sure how things are suppose to work but I do not see ANY LVs In Manual Partitioning, on the left side, you do not have an +Unknown listing located under -New Fedora 18 Installation? Or there are no LV's listed? I will go back and double check but I do not remember seeing an LVs. And, yes, I want to re-use previously allocated LVs for my install. There are regular old partitions which I can use for /boot but all of the rest of my disk space is in PVs. What do you get for pvscan and lvscan? Are there inactive LVs? I will need to check. IMO, the whole way storage is being handled in F18 needs to be rethought! Guessing how to do something should never happen. I agree. But I think in your case the trail is leading to a bug not flawed design. I am sure this is a bug. However, I would like some button or whatever "earlier" in the process that says "I know what I am doing, let me manually configure existing partitions and/or LVs or allocate new ones on mount points. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/04/2012 05:55 PM, Chris Murphy wrote: On Dec 4, 2012, at 3:13 PM, Chris Murphy wrote: You'll need to make sure you've manually created an LV because neither anaconda autopart or Manual Partitioning can create an LV from available VG free space. By this I mean, create the LV outside of anaconda. Slightly off topic, I'm kinda liking system-storage-manager new to F18 and installable from the live cd. yum install system-storage-manager ssm list And you'll get a listing of all devices, pools, volumes, and their mount points, better layout all in one place rather than having to go dig for info with multiple tools: fdisk, df, pvscan, lvscan, etc. You are right ... ssm is nice. I wonder if there is a gui version planned? Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Dec 4, 2012, at 11:52 PM, Gene Czarcinski wrote: >> > I am not sure how things are suppose to work but I do not see ANY LVs In Manual Partitioning, on the left side, you do not have an +Unknown listing located under -New Fedora 18 Installation? Or there are no LV's listed? > There are regular old partitions which I can use for /boot but all of the > rest of my disk space is in PVs. What do you get for pvscan and lvscan? Are there inactive LVs? > IMO, the whole way storage is being handled in F18 needs to be rethought! > Guessing how to do something should never happen. I agree. But I think in your case the trail is leading to a bug not flawed design. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Wed, 2012-12-05 at 01:52 -0500, Gene Czarcinski wrote: > I am not sure how things are suppose to work but I do not see ANY LVs > > There are regular old partitions which I can use for /boot but all of > the rest of my disk space is in PVs. IMO, the whole way storage is > being handled in F18 needs to be rethought! Guessing how to do > something should never happen. Well, your mail rather gave the impression you wanted to re-use existing LVs as backing for the F18 mount points. If that's not the case, obviously the instructions we gave you don't apply. > Can someone point me to some documentation which describes (and maybe > has some pictures) how to do manual allocation using pre-defined LVM > partitions? We are trying to help you here, but it's not easy, as you aren't explaining what it is you want to do exactly very well. So to clarify, you have existing PVs but no LVs, and you want to create new LVs? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On 12/04/2012 05:37 PM, Adam Williamson wrote: On Tue, 2012-12-04 at 15:13 -0700, Chris Murphy wrote: On Dec 4, 2012, at 1:43 PM, Gene Czarcinski wrote: My problem is that I have a test system with almost all of the disk space pre-allocated into various partitions. There are /boot partitions on the sda disk but the remainder are in lvm. I cannot seem to be able to get to the lvm configurations. What am I missing. They are in Manual Partitioning, probably listed inside "Unknown". You'll need to make sure you've manually created an LV because neither anaconda autopart or Manual Partitioning can create an LV from available VG free space. When I click on a VG that contains free space (no LVs) I get a message: "This device cannot be edited directly. You can remove it or select a different device. If I have a VG with many LVs, but still has free space, I can't get anaconda to make new LVs. I believe this is intended to be implemented but not done yet. I'm not sure if it's expected to show up between 18 Beta and Final, or if it'll only show up in 19. Gene, as Chris says, if you have existing LVs you want to use in the F18 install, they should appear in the 'Unknown' group on the left-hand pane of custom partitioning. You can select the LV you want to use for / , and enter '/' in the 'Mount point' box on the right, then do the same for an LV you want to use for /home or /var or whatever. Then if you like you can hit 'Apply Changes' and you should see those LVs show up as the relevant partitions in the 'New Fedora 18 Beta installation' group at the top of the left-hand pane. I am not sure how things are suppose to work but I do not see ANY LVs There are regular old partitions which I can use for /boot but all of the rest of my disk space is in PVs. IMO, the whole way storage is being handled in F18 needs to be rethought! Guessing how to do something should never happen. Can someone point me to some documentation which describes (and maybe has some pictures) how to do manual allocation using pre-defined LVM partitions? I sure hope the fedup [boy oh boy, this sure seems to be an appropriately named package] works because that may be the only way to install F18 as far as I am concerned. BTW, I am no happy about software selection either but I can live it that. The current dusk configuration stuff, no I will not be using it. And, I am not blaming the developers here. They are trying their best. I do hold F18 leadership responsible! Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Dec 4, 2012, at 3:13 PM, Chris Murphy wrote: > You'll need to make sure you've manually created an LV because neither > anaconda autopart or Manual Partitioning can create an LV from available VG > free space. By this I mean, create the LV outside of anaconda. Slightly off topic, I'm kinda liking system-storage-manager new to F18 and installable from the live cd. yum install system-storage-manager ssm list And you'll get a listing of all devices, pools, volumes, and their mount points, better layout all in one place rather than having to go dig for info with multiple tools: fdisk, df, pvscan, lvscan, etc. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Tue, 2012-12-04 at 15:13 -0700, Chris Murphy wrote: > > On Dec 4, 2012, at 1:43 PM, Gene Czarcinski wrote: > > > My problem is that I have a test system with almost all of the disk > > space pre-allocated into various partitions. There are /boot > > partitions on the sda disk but the remainder are in lvm. I cannot > > seem to be able to get to the lvm configurations. What am I > > missing. > > They are in Manual Partitioning, probably listed inside "Unknown". > You'll need to make sure you've manually created an LV because neither > anaconda autopart or Manual Partitioning can create an LV from > available VG free space. > > > When I click on a VG that contains free space (no LVs) I get a > message: "This device cannot be edited directly. You can remove it or > select a different device. > > > > If I have a VG with many LVs, but still has free space, I can't get > anaconda to make new LVs. I believe this is intended to be implemented but not done yet. I'm not sure if it's expected to show up between 18 Beta and Final, or if it'll only show up in 19. Gene, as Chris says, if you have existing LVs you want to use in the F18 install, they should appear in the 'Unknown' group on the left-hand pane of custom partitioning. You can select the LV you want to use for / , and enter '/' in the 'Mount point' box on the right, then do the same for an LV you want to use for /home or /var or whatever. Then if you like you can hit 'Apply Changes' and you should see those LVs show up as the relevant partitions in the 'New Fedora 18 Beta installation' group at the top of the left-hand pane. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Manual Partitioning and LVM, Re: Puzzled
On Dec 4, 2012, at 1:43 PM, Gene Czarcinski wrote: > My problem is that I have a test system with almost all of the disk space > pre-allocated into various partitions. There are /boot partitions on the sda > disk but the remainder are in lvm. I cannot seem to be able to get to the > lvm configurations. What am I missing. They are in Manual Partitioning, probably listed inside "Unknown". You'll need to make sure you've manually created an LV because neither anaconda autopart or Manual Partitioning can create an LV from available VG free space. When I click on a VG that contains free space (no LVs) I get a message: "This device cannot be edited directly. You can remove it or select a different device. If I have a VG with many LVs, but still has free space, I can't get anaconda to make new LVs. Chris Murphy-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Puzzled
I have been trying to install F18 beta on real hardware and seem to have it a problem concerning disk allocation. I have successfully installed the beta into a virtual systems. My problem is that I have a test system with almost all of the disk space pre-allocated into various partitions. There are /boot partitions on the sda disk but the remainder are in lvm. I cannot seem to be able to get to the lvm configurations. What am I missing. Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
