[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#697915: marked as done (Problem with LVM when installing latest Debian Wheezy)

Your message dated Sat, 31 Aug 2013 12:52:13 +0200
with message-id <201308311252.51555.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #697915,
regarding Problem with LVM when installing latest Debian Wheezy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
697915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697915
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

Boot method: Cd "debian-wheezy-DI-b4-amd64-netinst.iso".
Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-netinst.iso
Date: Friday 11 January 2013.

Machine: Tested on VirtualBox and a Dell Optiplex 960 and a Dell PowerEdge R210.
Processor:
Memory:
Partitions: <df -Tl ; mais nous préférons la table des partitions>

Sys. fich.                Type     1K-blocks   Util. Disponible Uti% Monté sur
rootfs                    rootfs    19223252 1100720   17146048   7% /



udev                      devtmpfs     10240       0      10240   0% /dev
tmpfs                     tmpfs        37988     244      37744   1% /run
/dev/mapper/vglocal-slash ext4      19223252 1100720   17146048   7% /



tmpfs                     tmpfs         5120       0       5120   0% /run/lock
tmpfs                     tmpfs        75960       0      75960   0% /run/shm
/dev/sda1                 ext4         93207   23165      65230  27% /boot




fdisk -l 

Disque /dev/sda : 107.4 Go, 107374182400 octets
255 têtes, 63 secteurs/piste, 13054 cylindres, total 209715200 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets



taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x0004cbc3

Périphérique Amorce  Début        Fin      Blocs     Id  Système
/dev/sda1   *        2048      194559       96256   83  Linux
/dev/sda2          194560   209713151   104759296   8e  LVM Linux

Disque /dev/mapper/vglocal-slash : 20.0 Go, 19998441472 octets
255 têtes, 63 secteurs/piste, 2431 cylindres, total 39059456 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x00000000

Disque /dev/mapper/vglocal-swap : 998 Mo, 998244352 octets


255 têtes, 63 secteurs/piste, 121 cylindres, total 1949696 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x00000000


Résultat de lspci -knn (ou lspci -nn) :

00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)


00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000]

00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef]
00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02)



00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe]
00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01)



00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f]
00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08)
00:0b.0 USB controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c]



00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)


Installation du système de base :
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [O]
Configure network:      [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [E]
Install base system:    [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:          [O]
Install boot loader:    [O]
Overall install:        [O]

Comments/Problems:
Hi,

It seems there is a problem with partman and LVM.

I created a VirtualBox machine with a 107.4 GB hard drive (sparce file).

In the first place, I created 3 masters partitions with partman.

- /dev/sda1/ as /boot in ext4 - 98.6 MB

- /dev/sda2 as LVM partition - 50 GB

- /dev/sda3 as LVM partition - 57.3 GB

Next, I set up LVM and I created a VG with /dev/sda2.

I realised that /dev/sda3 is useless to me, so i deleted it.

Next, I deleted my VG and /dev/sda2. I created a new /dev/sda2 partition - 107.3 GB as LVM partition.

When I tried to configure LVM, it show /dev/sda2 with 50000 MB.

I should see the new size of my /dev/sda2.

I made an other VM with the same settings, and I found that if I made a LVM by mistake, the only way to display the correct size of /dev/sda2 is to recreate a default partition for /dev/sda.

I hope everything I said can help.
I can provide screenshot if you prefer.

Have a nice day

Benoît

--- End Message ---
--- Begin Message --- 
reassign 699136 partman
retitle 699136 partman hangs with specific mbr/usbsticks
tags 696755 +confirmed
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: