Bug#760553: debian-installer: changing from guided to manual with LVM results in corrupt LVM metadata
Package: debian-installer Version: debian-7.6.0-amd64-netinst.iso Severity: important hi, I've set Version: to the ISO I used for install as I'm not sure what version of d-i that correlates to, nor whether this is a bug fixed since. I recently performed an install and opted for guided - use LVM initially. When presented with the results, I was not satisfied (I didn't want the entire device filled up with a root LV - see also #651280) so I went back to manual and started over: I deleted each LV and the partition housing the PV, then created a new (smaller) partition for the LV and re-created the LVs. The GPT partition table I ended up with is as follows > Model: ATA ST1000LM024 HN-M (scsi) > Disk /dev/sdb: 1000GB > Sector size (logical/physical): 512B/4096B > Partition Table: gpt > Disk Flags: > > Number Start End SizeFile system Name Flags > 1 1049kB 512MB 511MB fat32EFI System Partition boot, esp > 2 512MB 768MB 256MB ext2 msftdata > 3 768MB 10.8GB 10.0GB lvm > 4 10.8GB 10.9GB 132MB fat16FREEDOS msftdata Note that I created partition #4 via parted post-installation (an experiment which failed: UEFI-boot for BIOS flashing is a no-go). However, I have just noticed that the LVM volume has corrupt metadata: > # vgs > VG #PV #LV #SN Attr VSize VFree > qusp_vg 1 2 0 wz--n- 930.80g 921.49g > # pvs > PVVG Fmt Attr PSize PFree > /dev/sdb3 qusp_vg lvm2 a-- 930.80g 921.49g Note that the above shows that it thinks the PV is approx 1T in size, but as parted shows, it's only ~10G. I was just about to create a new LV but if I had done so, I believe it would have started to overwrite partition #4 above and resulted in corruption. 'pvscan' didn't cure the issue, but 'pvresize' seems to have got things to where they should be > # pvresize /dev/sdb3 > Physical volume "/dev/sdb3" changed > 1 physical volume(s) resized / 0 physical volume(s) not resized I think the problem appears to be within d-i/partman and handling of deleting PVs or deleting partitions upon which PVs are stored. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905085835.ga30...@bryant.redmars.org
Bug#326243: #326243: misleading description about --install
On Tue, Oct 10, 2006 at 12:04:16PM +0200, Roland Stigge wrote: > Yes, the respective sentence in the Description is just > wrong. Consider the attached patch. I've just been bitten by this one, and your patch would have prevented that. However, it would be nice if the original description was accurate, and if busybox did behave in the way it describes... -- Jon Dowland signature.asc Description: Digital signature
Bug#278085: debian-installer report
Package: installation-reports Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/i386/current/sarge-i386-businesscard.iso 23-Oct-2004 23:10 uname -a: Linux konishi 2.4.27-1-k7 #1 Fri Sep 3 06:21:29 UTC 2004 i686 GNU/Linux Date: from Oct 24 18:59:37 to Oct 24 20:47:51 BST 2004 Method: the business card cd image listed above: boot from that. apt source set to a http mirror. No proxy necessary Machine: Medion multimedia PC Processor: XP2600+ Memory: 512MB Root Device: /dev/hdc7 on / type ext3 (rw,errors=remount-ro) (IDE) Root Size/partition table: Device Boot Start End Blocks Id System /dev/hdc1 1765061448593+ 7 HPFS/NTFS /dev/hdc27651 1459355769647+ f W95 Ext'd (LBA) /dev/hdc5 14084 14593 4096543+ b W95 FAT32 /dev/hdc676517772 979902 82 Linux swap /dev/hdc7 *7773 1408350693076 83 Linux Output of lspci and lspci -n: see attached files (lspci and lspci-n) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Generally I was very impressed with the installer. There are just a few suggestions I would make. The installer attempted to configure the network with DHCP but there is no DHCP server on my LAN. I'm not sure if I missed an option to configure manually, but I disliked having to wait for the DHCP requests to timeout before being offered manual configuration. When partitioning manually, the advice offered should include the size of SWAP partition necessary. I went for 2*(memory) but I wasn't sure if this is necessary anymore. When opting to NOT put grub in the MBR, the 'where should I put' screen was horrible. I couldn't remember that my HD was hdc not hda; so the /dev/hdx notation was a no-go. A list of partitions here would have helped. The grub notation also is hard for a novice (fair enough the off-by-one, but when logical partitions are numbered 5+ it gets a bit confusing). I gave up trying to select the / partition and opted for MBR after all (which I wanted to avoid). Putting the hdx entries in /dev on the cd would really help here, as we could go to another console and open up c?fdisk as necessary to make decisions. After the grub stuff the installer seemed to go into some sort-of debug mode and I was prompted as to what stage to use after each step. I opted for none of the package-groups (e.g. desktop) selecting only 'manual configuration'. I thought the number of selected packages in aptitude was rather large, and removed most of them before going ahead with the install. I got it down to 15MB of packages to download which was more satisfying. A more bare-bones option? I think most of the package configuration went well, although there were three prompts for SSH: the first relevant to the client and server, the second only for the server, and the third asking if you wanted to use the server. If the third prompt came before the second, opting not to use the daemon would remove the need for the second question altogether. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#278085: missing attachments (apologies)
See attached. :00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge :00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge :00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS) :00:07.0 Communication controller: Intel Corp. 536EP Data Fax Modem :00:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 80) :00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) :00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) :01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4200 AGP 8x] (rev a1) :00:00.0 0600: 1106:3189 :00:01.0 0604: 1106:b168 :00:06.0 0200: 10ec:8029 :00:07.0 0780: 8086:1040 :00:0c.0 0c00: 1106:3044 (rev 46) :00:10.0 0c03: 1106:3038 (rev 80) :00:10.1 0c03: 1106:3038 (rev 80) :00:10.2 0c03: 1106:3038 (rev 80) :00:10.3 0c03: 1106:3104 (rev 82) :00:11.0 0601: 1106:3177 :00:11.1 0101: 1106:0571 (rev 06) :00:11.5 0401: 1106:3059 (rev 50) :00:12.0 0200: 1106:3065 (rev 74) :01:00.0 0300: 10de:0281 (rev a1)
Bug#278085: /sbin/cfdisk: confirmation : and from a d-i install, no less
Package: util-linux Version: 2.12-10 Followup-For: Bug #67185 I experience similar problems # cfdisk /dev/hdc FATAL ERROR: Bad logical partition 6: enlarged logical partitions overlap Press any key to exit cfdisk Partition layout (from fdisk): Disk /dev/hdc: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1765061448593+ 7 HPFS/NTFS /dev/hdc27651 1459355769647+ f W95 Ext'd (LBA) /dev/hdc5 14084 14593 4096543+ b W95 FAT32 /dev/hdc676517772 979902 82 Linux swap /dev/hdc7 *7773 1408350693076 83 Linux Partition table entries are not in disk order Note: partitioning was done with a debian-installer build: See #278085 for the installation report. Note #2: It is my intention to re-title this bug to be more descriptive. Whilst sifting through the 300 or so bugs against util-linux, descriptive bug titles are very very handy! ;) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB Versions of packages util-linux depends on: ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libncurses5 5.4-4Shared libraries for terminal hand ii slang1a-utf81.4.9dbs-8 The S-Lang programming library wit ii zlib1g 1:1.2.1.1-7 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How about playing a game while installing Debian?
On Sat, Apr 11, 2009 at 05:51:09PM +0200, Evgeni Golov wrote: > Please add your 0.02€ to the bin, and tell us whether you like the idea (and > if so, which games you'd love to see). If we had a livecd-based installer, the user could play a regular game at the same time as the installer process ran, from the livecd environment. Then we just need to work out what would be reasonable to fit into the livecd environment. This is where Ubuntu are afaik. Obviously Debian should not be exclusively livecd-installer based as this is only applicable to a single (or a small number) of hardware configurations and usage scenarios. But I think in many cases this set coincides with those where playing games would be useful (I.e. you aren't going to play games during a FAI install, are you?) -- Jon Dowland -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642115: debian-installer: guided full disk encryption + LVM complains about insecure swap
Package: debian-installer Severity: normal Hi, Using a daily build: -rw-r--r-- 1 libvirt-qemu kvm 240M Sep 16 10:00 debian-testing-i386-netinst.iso If you choose Guided / Encrypted / LVM as the partitioning type, the resulting scheme chosen by d-i basically looks like (physical partition) → (encrypted volume) → (LVM) → (swap) Thus, the swap is encrypted, but LVM sits between them. After choosing that partitioning scheme, you are then asked to input the encryption pass-phrase. You are then shown the scheme layed out like with the manual partitioner. After you accept this, you are warned that the swap space is unsafe. d-i refuses to proceed at this point. If you set the swap LV to "do not use", you can proceed (without swap) and fix it later on. I think this is incorrect and the swap space *is* safe, since it is sitting on top of an encrypted partition. However either way, the guided partitioner should suggest a scheme which is safe. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110919144713.ga19...@inoshiro.ncl.ac.uk
Bug#642115: debian-installer: guided full disk encryption + LVM complains about insecure swap
On Mon, Sep 19, 2011 at 11:56:49AM -0400, Joey Hess wrote: > The code is this, and Max changed it most recently: > > # Accept e.g. swap on lvm on crypto > if echo $device | grep -q "^/dev/mapper/"; then > if dm_is_safe "$device"; then > continue > fi > fi > > I wonder if perhaps the device for LVM does not look like > /dev/mapper/ anymore. Perhaps it's seeing /dev// instead? I've just monkey-patched this instance of d-i to write $device to a temporary file. It contains: /dev/mapper/debian-root /dev/mapper/debian-swap_1 Thus the outer-if is passing. dm_is_safe looks fine to me, at least it invokes dm_dev_is_safe, I'll try to look at dm_dev_is_safe next. -- Jon Dowland -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110920105413.GA27023@pris
Bug#642115: debian-installer: guided full disk encryption + LVM complains about insecure swap
On Tue, Sep 20, 2011 at 11:54:21AM +0100, Jon Dowland wrote: > Thus the outer-if is passing. dm_is_safe looks fine to me, at least it > invokes dm_dev_is_safe, I'll try to look at dm_dev_is_safe next. I think this is where the problem is. crypto-base.sh, dm_dev_is_safe: dminfo=$(dmsetup table -j$mag -m$min 2> /dev/null | \ head -n1 | cut -d' ' -f3) || return 1 dm_dev_is_safe calls itself recursively for each dependency of the supplied device (supplied as a major/minor number pair). The swap partition has sda5 as a dependency (the first logical partition, used as the crypt base). dmsetup table -j$mag -m$min returns: sda5_crypt: 0 16269312 crypt … the above command results in $dminfo being 16269312. It is then checked against 'crypt': if [ "$dminfo" = "crypt" ]; then return 0 fi This seems to be an off-by-one problem. field 4 would be 'crypt' and would correctly return success. I hypothesise that the prefixed 'sda5_crypt:' is new. -- Jon Dowland -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110920123733.GB27023@pris
Btrfs limitations in the Debian installer 7.0 beta4 release
Forwarding this interesting message re d-i feedback and using BTRFS in the installer from -devel. - Forwarded message from Aaron Toponce - From: Aaron Toponce Subject: Btrfs limitations in the Debian installer 7.0 beta4 release Date: Thu, 13 Dec 2012 09:43:20 -0700 To: debian-de...@lists.debian.org Recently, I decided to put down a Btrfs root on my workstation using the latest release of the installer. I found that given my hardware configuration, this is not possible, and would require using another installer or debootstrap the installation, which is far from ideal. I have two 250 GB drives I would like to put into a RAID-1 mirror. I want Btrfs to handle the RAID, rather than mdadm. It appears that this is not possible in the installer, as when you are at the partitioning screen, it forces you to decide which partition gets mounted to root. Instead, I'll pull up tty2, and manually build the array. Suppose they are identified as /dev/sda and /dev/sdb. I would like to partition the drives, such that /dev/sda1 and /dev/sdb1 make up the root Btrfs filesystem, and /dev/sda2 and /dev/sdb2 make up a ZFS /home. After partitioning the devices, I run the following command to create the Btrfs RAID: # mkfs.btrfs -d raid1 -m raid1 /dev/sda1 /dev/sdb1 # mount /dev/sda1 /target/ Now, I would prefer to have the root into a subvolume. So, I run the following command: # cd /target/ # btrfs subvolume create root # cd # umount /target/ # mount -t btrfs -o defaults,subvol=root /dev/sda1 /target/ Recognize that I am effectively mounting /dev/sda1/root (if such a device actually existed) to /target/, and not /dev/sda1. However, the partitioning utility will not allow me to modify the mount options when specifying which subvolume should be mounted to /. So, if I specify /dev/sda1 to be /, the debian installer will "umount /target/" and "mount /dev/sda1 /target/" which is not what I want. Further, asside from pulling up a terminal in the installer, there is now way in the partitioning utility to setup Btrfs volumes using multiple devices. You must set that up in tty2 or tty3. (As a tangent gripe, the partitioner will also not allow you to setup an encrypted partition. You must do encrypted volumes with LVM. You can defeat this by again going to a TTY.) Doing a GRUB install on both /dev/sda and /dev/sdb is not a problem, and I can configure GRUB to assemble the Btrfs volume, and I can make the necessary changes to notify the kernel where the root filesystem is. However, all of these require stepping out of the Debian installer, and using another vendor's install, such as Ubuntu or Fedora, to bootstrap it. Again, far from ideal. It would be nice if the partitioning utility allowed the administrator to specify mount options (asside from checkboxes with 'noatime', 'relatime', etc). This way, I could tell the installer to mount the subvolume as root, and not the partition. I can file a feature request, if needed. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o - End forwarded message - -- I pledge not to post to any systemd-related thread on -devel until (at least) 2013. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121214095603.GB14161@debian
Re: Wheezy release: CDs are not big enough any more...
On Mon, May 14, 2012 at 09:34:39AM -0700, Steve Langasek wrote: > So to use the image you need either a DVD or a USB stick, and if you're using > a write-once DVD you're perhaps wasting the unused space; but the download > time and install footprint are still kept low and in the range of what a CD > would give. In the UK at least, the price of a CD-R and a DVD+R is approximately the same, although CD-Rs are becoming rarer in brick-and-mortar shops. I still attempt to use CD-R media when burning install discs, but that's only if I happen to have some (and I don't mind the wasted space burning netinst to a 700M CD-R). I think what I'm saying is I agree with you for my use-cases at least. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120515092100.GD24635@debian
Bug#687804: installation-reports: users are not able to review external documentation while stuck in the installer
The installer (in expert mode) supports an ssh client on an alternative VT, afaik. One can connect to another machine with stuff already installed via this if necessary. Surely this is sufficient to address the request. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120917122740.GB20063@debian
