Re: partitions - primary vs logical and bootability
At Sat, 10 Nov 2012 16:09:36 -0600, Charles Blair wrote: > >I am trying to set up a dual-boot windows 7 / wheezy. Can you install grub2 to the MBR and have it boot both debian and MSWindows? This worked fine to dual-boot WinXP. > As I understand it, / must be bootable, which seems to mean it must > be a primary partition. AFAIK, an MBR-installed grub doesn't care about partition boot flags. Only if you have a DOS MBR and grub installed to a PARTITION does the boot flag matter. Grub2 should be able to handle / and /boot on a logical partition. Actually, I prefer to use LVM rather than individual partitions, and grub2 CAN load kernels from an LVM / or /boot. Cheers, -ntd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k7nip6$ef1$1...@ger.gmane.org
LVM devices and symlinks
Hi, I'm having an issue (not quite a problem) creating LVM logical volumes. It seems that the way device files and symlinks are created has changed between Squeeze and Wheezy (or I have some bad configuration). Old (working) Behavior -- Performing an `lvcreate -L10G -nLVNAME VGNAME` would create: 1. New device file /dev/dm-N 2. Symlink /dev/mapper/VGNAME-LVNAME -> /dev/dm-N 3. Symlink /dev/VGNAME/LVNAME -> /dev/dm-N And everything was great. New (broken) Behavior Performing an `lvcreate -L10G -nLVNAME VGNAME` creates: 1. New device file /dev/mapper/VGNAME-LVNAME (and apparently nothing else) Then, lvcreate tries to open /dev/VGNAME-LVNAME, which fails because of no symlink with: /dev/VGNAME/LVNAME: not found: device not cleared Aborting. Failed to wipe start of new LV. Workarounds --- Here are a few workarounds I've figured out: 1. Give lvcreate the '-Z n' flag. This does create a usable logical volume, but won't work with snapshots. 2. Manually create a symlink '/dev/VGNAME/LVNAME -> /dev/mapper/VGNAME-LVNAME' before running lvcreate 3. Give lvcreate the '--noudevsync' option. In this case, lvcreate makes a symlink for '/dev/VGNAME/LVNAME -> /dev/mapper/VGNAME-LVNAME' on its own (apparently). Also, on a reboot of the machine, the device files end up in the original configuration, with both /dev/mapper/VGNAME-LVNAME and /dev/VGNAME/LVNAME as symlinks pointing to /dev/dm-N. While those workarounds are enough to get by, it would be nice to understand the underlying issue here. Can anyone shed some light on this? Thank you, -ntd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ka6124$em2$1...@ger.gmane.org
Re: LVM devices and symlinks
At Tue, 11 Dec 2012 10:15:54 +, Chris Davies wrote: > > Reboot the box after installing LVM. Ah, a reboot has lvcreate working properly, thank you. > Based on my empirical sample of two, there's some dependency that I > haven't tracked - and I must admit thought it was related to my weird > installation process - that blocks the symlink creation after installing > LVM but prior to a reboot. > > > Also, on a reboot of the machine, the device files end up in the > > original configuration, with both /dev/mapper/VGNAME-LVNAME and > > /dev/VGNAME/LVNAME as symlinks pointing to /dev/dm-N. > > Is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593375#25 (fixed) > a related issue? It looks plausible to me. Seems possible, though I didn't see any /dev/.udev/failed, and that bug was supposedly fixed with udev 163-1 while wheezy's at 175-7. Thanks, -ntd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ka8q62$lf1$1...@ger.gmane.org
Re: LVM devices and symlinks
At Wed, 12 Dec 2012 18:54:41 +, Roger Leigh wrote: > > > > > > Reboot the box after installing LVM. > > > > Ah, a reboot has lvcreate working properly, thank you. > > This is good to know. However, this should all be triggered > when the package is initially installed. Agree that "turning it off and on again" is not exactly a solution. However, I'm not sure that it's something missing from the LVM package installation since I'd already rebooted after initially installing LVM (/ was on a logical volume). > Please could you file a serious bug against the lvm package so that > this can be fixed. I can go ahead and file the report, but at the moment, I don't have any more detail than /sometimes/ lvcreate doesn't make the right files/symlinks. -ntd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/kablbr$emr$1...@ger.gmane.org
Re: LVM devices and symlinks
At Wed, 12 Dec 2012 18:54:41 +, Roger Leigh wrote: > > > > > > Reboot the box after installing LVM. > > > > Ah, a reboot has lvcreate working properly, thank you. > > This is good to know. However, this should all be triggered > when the package is initially installed. Agree that "turning it off and on again" is not exactly a solution. However, I'm not sure that it's something missing from the LVM package installation since I'd already rebooted after initially installing LVM (/ was on a logical volume). > Please could you file a serious bug against the lvm package so that > this can be fixed. I can go ahead and file the report, but at the moment, I don't have any more detail than /sometimes/ lvcreate doesn't make the right files/symlinks. -ntd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121213042532.93580149...@mail3.gatech.edu
