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

Bug#586382: marked as done (Installation Report)

Your message dated Fri, 19 Jul 2013 12:46:25 +0200
with message-id <201307191246.36235.holger@layer-acht.org>
and subject line dealing with old installation-reports and d-i related bugs
has caused the Debian Bug report #586382,
regarding Installation Report
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.)


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

Boot method: <How did you boot the installer? CD? floppy? network?>
CD
Image version: <Full URL to image you downloaded is best>
5.0.4 from the debian ftp site as of 5/15/10
Date: <Date and time of the install>
6/15/10

Machine: <Description of machine (eg, IBM Thinkpad R32)>
eeePC 901
Processor:
Intel Atom
Memory:
1GB
Partitions: <df -Tl will do; the raw partition table is preferred>
BROKEN BROKEN BROKEN!

Output of lspci -knn (or lspci -nn):

Base System Installation Checklist:
[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:     [e]
Partition hard drives:  [e]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:
I was trying for an encrypted set of partitions, root/home/swap and it failed horribly. I could not even do it manually (maybe with another half-dozen tries each requiring a wipe and reboot).
1. If you enable ANY LVM there is no way to delete it or reverse the process. It complains that partition/whatever is a member of LVM group XYZ and refuses to do anything with it. But the LVM options can't delete or resize any of their partitons either.
2. If I partitioned the media before and it had a LVM there it would detect and use it was no way to delete it as per the above, but what I would have to do is during the bootup go to a console and do "dd if=/dev/zero of=/dev/sda" to zap the media BEFORE the disk was detected or I would not be able to do anything.
3. Within the LVM, it doesn't seem to be able to edit or change the partitions within. There are selectable menu lines for LVM: xxx and the partition, but neither allow deletion or resizing.
4. "Guided" did 3:1 for home:root but I wanted 1:1. I also wanted more swap. Of course with the above problems I couldn't change anything, not even delete the partitions.
Summary: there needs to be a way to wipe a device and/or to detach, shutoff or otherwise unstick the LVM after it thinks there is a volume. There might be some obscure command line stuff beyond but it cannot be done from the menu in the installer.
To repeat it, take a blank medium (e.g. a large SD card you want to erase), do an encrypted guided with separate home, and let it create LVM volumes. Try to delete them. Reboot and let it detect them, and see if you can delete (or resize) the lvm partitions. 

<Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>

--- End Message ---
--- Begin Message --- 
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 have been from a development phase where things were not stable and/or
- they are (very) old, between 2.5 and >4 years (so thats 2 releases ago).

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: