Re: default LUKS/LVM names

[Luca Capello]

Hi there!

On Wed, 08 May 2013 11:00:34 +0200, Dmitrijs Ledkovs wrote:
> On 6 May 2013 06:04, Paul Wise  wrote:
>> The current default names for an LVM on LUKS setup are:
>>
>> _crypt
>> -root
>> -swap_1
>>
>> I would like something more consistent like these:
>>
>> -crypt
>> -root
>> -swap
>>
>> Any thoughts?
>>
>
> Something consistent and sensible would be nice.

While I was agreeing with Paul when I read his email, then I came to the
conclusion that _crypt and -* are two different things, so
having different names is reasonable.

I agree, however, that there is no reason to use 'swap_1' and that
'' (not ) is ugly:
=
$ ls -l /dev/mapper/
total 0
crw--T 1 root root 10, 236 May  7 15:31 control
lrwxrwxrwx 1 root root   7 May  7 15:31 gismo-home -> ../dm-3
lrwxrwxrwx 1 root root   7 May  7 15:31 gismo-root -> ../dm-2
lrwxrwxrwx 1 root root   7 May  7 15:31 gismo-swap -> ../dm-1
lrwxrwxrwx 1 root root   7 May  7 15:31 sda2_crypt -> ../dm-0
$ 
=

> Someone had a host / device name clash, and thus e.g. for LVM VG I
> added to use a suffix "-vg" in ubuntu and planning to push a similar
> change to debian, as otherwise unattended installations were failing
> and were not exactly unattended.

IIRC VG names with '-' inside are shown as '--' in /dev/mapper/ to
differentiate between '-' *within* the name as '-' in VG-LV, which is
quite ugly by default IMHO.

> ps. hostnames are often pre-assigned by dhcp in fully automated installations.

This is something you can control, either on the DHCP side or in the
preseed.

Thx, bye,
Gismo / Luca


pgpGvAM3rkcW0.pgp
Description: PGP signature

Bug#707604: debian-installer: Should warn if disk with GPT doesn't contain bios-grub partition

[Luca Capello]

block 691046 by 707604
thanks

Hi there!

On Thu, 09 May 2013 18:43:39 +0200, Christoph Reiter wrote:
> Possible solution:
>  - Warn if the disk doesn't contain a bios-grub partition.
>  - Explain what is needed and what happens if this partition is missing.

This is a known limitation, please read Steve's answer for a complete
explanation on why the above is not easily implementable code-side:

  

Thx, bye,
Gismo / Luca


pgphDelc8QSy7.pgp
Description: PGP signature

Processed: Re: Bug#707604: debian-installer: Should warn if disk with GPT doesn't contain bios-grub partition

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 691046 by 707604
Bug #691046 [installation-reports] installation-reports: manual partitioning 
for GPT does not suggest a BIOS Boot Partition
691046 was blocked by: 610184 620390
691046 was not blocking any bugs.
Added blocking bug(s) of 691046: 707604
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
691046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.136817576512227.transcr...@bugs.debian.org

Bug#707479: iso-scan: Indicate .iso files must be _Debian_ files

[Samuel Thibault]

Christian PERRIER, le Fri 10 May 2013 07:47:08 +0200, a écrit :
> If so, I would propose "scan hard drives for a supported installer ISO
> image"and a small update to the installation manual to mention
> that ISO images have to be named s specific way.

Note: the image does not need to be named specifically. iso-scan just
looks for *.iso. It is the content that matters.

Samuel


-- 
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/20130510085243.gc8...@type.youpi.perso.aquilenet.fr

Bug#707679: 3G modem blocks install

[Mikko V . Viinamäki]

Package: installation-reports

Boot method: CD
Image version: wheezy for i386 downloaded on 8th May 2013
Date: 9th May 2013 10:41:62 GMT+2

Machine: older HP laptop
Partitions: There were existing ntfs and fat32 partitions and empty space

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

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

Comments/Problems: The install failed (red background, won't proceed) at a 
point where it said configuring package manager and said apt cannot access the 
CD or something to that effect. Also, GRUB install failed. I ran the integrity 
check and it said all is good. I tried both the regular (text) install and 
expert install, same deal. Then I realized that a 3G USB network dongle (Huawei 
E220) was connected and sometimes such devices act as a CD containing drivers 
for windoze. Turns out much hunch was correct and unplugging the dongle allowed 
the install to finnish. Sorry don't have any logs but I guess this could be 
easily replicated. I believe such dongles are relatively common so this could 
be a big deal.

--
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/0c7d424d957547489e16a29d0d154334015f7a4ef...@amkms11.ad.turkuamk.fi

Bug#707570: Error

[Holger Wansing]

Hi,

Cam Davies  wrote:
> Package: installation-reports Boot method:  CD
> Image version: the 64 bit version on main page
>  Date: may 9th 2013
> Machine: acer laptop
> Processor: unknown
> Memory: unknown
> Partitions: unknown
>  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: [ e] 
> Detect CD: [ o] 
> Load installer modules: [ o] 
> Detect hard drives: [ o] 
> Partition hard drives: [ o] 
> Install base system: [ o] 
> Clock/timezone setup: [ o] User/password setup: [o ] 
> Install tasks: [o ] 
> Install boot loader: [ e] 
> Overall install: [ e] 


Miguel Figueiredo  wrote:
> Hi,
> 
>  From your description seems you login on a console based system, with 
> success.
> Please describe what went wrong.

>From above I read, that the subscriber used a CD as installation
medium, and the network configuration failed. 
So, it was an installation from a single CD, without network mirror.
This most probably leads to a console-only install, without X.
And I think, this is what the subscriber is missing: the graphical
interface.

Holger


-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://linuxcounter.net/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
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/20130510203230.24634347.li...@wansing-online.de

Bug#707570: Error

[Miguel Figueiredo]

Em 10-05-2013 19:32, Holger Wansing escreveu:

Hi,



[...]


From above I read, that the subscriber used a CD as installation

medium, and the network configuration failed.
So, it was an installation from a single CD, without network mirror.
This most probably leads to a console-only install, without X.
And I think, this is what the subscriber is missing: the graphical
interface.

Holger



I've been discussing this by email with the OP and so it seems.
If you don't oppose I will close the BR as it was a successful installation.

--
Melhores cumprimentos/Best regards,

Miguel Figueiredo


--
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/518d47d3.5030...@debianpt.org

Bug#707567: Installation finally worked after repartitioning and formatting

[Wolf-Dieter Groll]

Hello,

after I failed to install Wheezy, I tried to reinstall Squeeze on this
partition containing still  /home/, /boot/ and /etc/.
The Debian 6.0.3 installer failed almost the same way, even so the
former system has been installed from this very CD!
I tried the Ubuntu 12.04 LTS Installer, it failed also, reporting it was
unable to overwrite some files on the disk.
Checking the filesystem with fsck.ext3 and the RAM with MemCheck didn't
reported any odds!
Finally I decided to do a clean install with repartitioning the Harddisk
and formatting every partition -
and now Wheezy netinstall worked without any problems!

As the other installers failed too, I believe this bug report can be closed.

Either there was something wrong with the partiton table or a flaw in
the ext3-filesystem that fsck couldn't detect,
or there was an hardware-error like an unrecoverable sector on the disk
drive. Reading such an sector will fail, but
when it gets written, the hdd-controller will mark this sector as bad
and reallocate one of the spare sectors for it.
Unfortunately, I haven't checked the number of reallocated sectors
before and after formatting the drive.

Anyhow - Wheezy is up and running on this PC

-- 
best regards
  Wolf-Dieter


smime.p7s
Description: S/MIME Cryptographic Signature

Bug#707679: The exact error message FWIW

[Mikko V . Viinamäki]

[!!] configure the package manager -- apt configuration problem -- an attempt 
to configure apt to install additional packages from the CD failed.

(When the install originally failed, I powered down the machine and went for 
lunch. Then I had the idea and removed the modem and started the machine and 
restarted the install. Perhaps yanking it out in the middle of the install 
would have sufficed had I had the idea then.)

--
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/0c7d424d957547489e16a29d0d154334015f7a4ef...@amkms11.ad.turkuamk.fi

Bug#707570: Error

[Cam Davies]

I typed pinggoogle and it says Unknown host.  I ytied tasksel and it did 
nothing, I did debian desktop environent and it said command not found.  

Sent from my iPhone

On 2013-05-10, at 1:17 PM, "Miguel Figueiredo"  wrote:

> Em 10-05-2013 19:32, Holger Wansing escreveu:
>> Hi,
> 
> [...]
> 
>>> From above I read, that the subscriber used a CD as installation
>> medium, and the network configuration failed.
>> So, it was an installation from a single CD, without network mirror.
>> This most probably leads to a console-only install, without X.
>> And I think, this is what the subscriber is missing: the graphical
>> interface.
>> 
>> Holger
> 
> I've been discussing this by email with the OP and so it seems.
> If you don't oppose I will close the BR as it was a successful installation.
> 
> -- 
> Melhores cumprimentos/Best regards,
> 
> Miguel Figueiredo


--
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/blu404-eas38348073c653b5c687632fab...@phx.gbl

Debian installer build: failed or old builds

[Daily build aggregator]

Debian installer build overview
---

Failed or old builds:

* FAILED BUILD: amd64 May 11 00:05 buildd@barber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log

* FAILED BUILD: amd64 May 11 00:05 buildd@barber build_cdrom_gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log

* FAILED BUILD: amd64 May 11 00:05 buildd@barber build_cdrom-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log

* FAILED BUILD: amd64 May 11 00:05 buildd@barber build_netboot 
http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log

* FAILED BUILD: amd64 May 11 00:06 buildd@barber build_netboot-gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log

* FAILED BUILD: amd64 May 11 00:06 buildd@barber build_netboot-xen 

http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log

* FAILED BUILD: amd64 May 11 00:06 buildd@barber build_hd-media 

http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log

* FAILED BUILD: amd64 May 11 00:06 buildd@barber build_hd-media_gtk 

http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log

* FAILED BUILD: armel May 10 08:11 buildd@ancina build_iop32x_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log

* FAILED BUILD: armel May 10 08:12 buildd@ancina 
build_iop32x_network-console_glantank 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log

* FAILED BUILD: armel May 10 08:12 buildd@ancina 
build_iop32x_network-console_n2100 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log

* FAILED BUILD: armel May 10 08:13 buildd@ancina 
build_iop32x_network-console_ss4000e 

http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log

* FAILED BUILD: armel May 10 08:13 buildd@ancina build_kirkwood_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log

* FAILED BUILD: armel May 10 08:14 buildd@ancina build_kirkwood_netboot-gtk 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log

* FAILED BUILD: armel May 10 08:15 buildd@ancina build_kirkwood_network-console 

http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log

* FAILED BUILD: armel May 10 08:15 buildd@ancina build_orion5x_network-console 

http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log

* FAILED BUILD: armel May 10 08:16 buildd@ancina build_versatile_netboot 

http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log

* FAILED BUILD: i386 May 11 00:05 buildd@biber build_cdrom_isolinux 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log

* FAILED BUILD: i386 May 11 00:05 buildd@biber build_cdrom_gtk 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log

* FAILED BUILD: i386 May 11 00:06 buildd@biber build_cdrom-xen 

http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log

* FAILED BUILD: i386 May 11 00:06 buildd@biber build_netboot 
http://d-i.debian.org/daily-images/i386/daily/build_netboot.log

* FAILED BUILD: i386 May 11 00:06 buildd@biber build_netboot-gtk 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log

* FAILED BUILD: i386 May 11 00:06 buildd@biber build_netboot-xen 

http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log

* FAILED BUILD: i386 May 11 00:06 buildd@biber build_hd-media 
http://d-i.debian.org/daily-images/i386/daily/build_hd-media.log

* FAILED BUILD: i386 May 11 00:07 buildd@biber build_hd-media_gtk 

http://d-i.debian.org/daily-images/i386/daily/build_hd-media_gtk.log

* FAILED BUILD: ia64 May 11 00:13 buildd@alkman build_cdrom 
http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log

* FAILED BUILD: ia64 May 11 00:13 buildd@alkman build_netboot 
http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log

* OLD BUILD:kfreebsd-amd64 May 08 00:55 buildd@fano build_cdrom_grub 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log

* OLD BUILD:kfreebsd-amd64 May 08 00:55 buildd@fano build_cdrom_gtk 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_gtk.log

* OLD BUILD:kfreebsd-amd64 May 08 00:58 buildd@fano build_netboot 

http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log

* OLD BUILD:kfreebsd-amd64 May 08 01:01 buildd@fano build_netboot-9 

http://

Bug#707763: Installation Report, Macbook Pro, Bad Install.

[Geoffrey Boom]

Package: installation-reports

Boot method: CD.
Image version: I believe it was

[27 Apr 2013] Debian Installer 7.0 Release Candidate 2 release

although it might have been "3 release".

Date: ~ May 7 2013

Machine: Apple Intel Macbook Pro 15 inch.
Processor: 2.66 GHz Intel core i7
Memory: 4GB
Partitions: One for OSX, one for the debian instalation.

Output of lspci -knn (or lspci -nn): I'm assuming you mean to put it into
the terminal, I did on my mac, and it returned "command not found." So that
might not be all that helpful.

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

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

Comments/Problems:

I'm attatching photos of the problems I had booting up, for both MacOS and
for Debian. Reply if you have troubles getting them.

I had problems figuring out which install disk to choose. I used the AMD64
one. I really don't know how I'm supposed to know which of the installs I
need. Perhaps you need a detailed help page on which one to install,
including "what AMD64" means. I understand it has something to do with...
Processor? I'm aware that someone can find it on the web somewhere, but it
would be nice to have a concentrated center of knowledge on how to install,
because I was quite confused, despite my previous experience of installing
systems.

Well, I did the install on a seperate partition from my OSX partition which
I had created with an ubuntu instalation disk. It seemed to be working well
up until when I finished and tried booting up the computer under debian.
When I tried however, I got the result of the first image, which I have
attatched in the email. I then tried booting Mac OS, and it would not boot
either, neither of my systems would boot.
Woe is me.

I of course had a backup from a few days prior, and only lost minimal data
(a few programs I was fooling around with in mac) so I'm not too bothered,
however I think that corrupting bootloaders/breaking systems is something
you should be aware of! I was able to reinstall from a time machine backup,
and everything works fine again.


Of note:
I was doing it late at night, so I might or might not have done the
instalation properly. I was confused by a lot of the UI of the installer.
I'm used to very clear GUI, I guess, so I might have botched it of my own
doing. I've only ever installed Ubuntu, windows and mac before, but had
success with all of those. You might want to consider GUI alternatives in
addition to the regular text based which, say, my dad likes. I was freaked
out by the red backgrounds of certain warnings, although one might say
appropriately so.

TL:DR
Debian instalation broked my Mac, but I asserted my dominance and put it in
it's place.

Bug#707763: Installation Report, Macbook Pro, Bad Install.

[Charles Plessy]

Le Fri, May 10, 2013 at 07:01:54PM -0700, Geoffrey Boom a écrit :
> 
> I had problems figuring out which install disk to choose. I used the AMD64
> one. I really don't know how I'm supposed to know which of the installs I
> need. Perhaps you need a detailed help page on which one to install,
> including "what AMD64" means. I understand it has something to do with...
> Processor? I'm aware that someone can find it on the web somewhere, but it
> would be nice to have a concentrated center of knowledge on how to install,
> because I was quite confused, despite my previous experience of installing
> systems.

Dear Geoffrey,

there is a page on how to install Debian on MacBooks on our wiki.

http://wiki.debian.org/MacBook

Have you tried to follow the instructions from here ?

Have a nice week-end,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


-- 
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/20130511020927.gd15...@falafel.plessy.net

Bug#707570: Error

[Holger Wansing]

Hi,

Cam Davies  wrote:
> I typed pinggoogle and it says Unknown host.  I ytied tasksel and it did 
> nothing, I did debian desktop environent and it said command not found.  
> 

So I would suspect you still have some problem with the network site, as it was
during installation as well.
Because of this network error during installation, the desktop environment
was not installed. 
And without network connection, you still cannot install it afterwards now.

If you log in as root: what's the output of 
"ifconfig" ?
In the output of "lspci", is there a network card listed?


Holger



> On 2013-05-10, at 1:17 PM, "Miguel Figueiredo"  wrote:
> 
> > Em 10-05-2013 19:32, Holger Wansing escreveu:
> >> Hi,
> > 
> > [...]
> > 
> >>> From above I read, that the subscriber used a CD as installation
> >> medium, and the network configuration failed.
> >> So, it was an installation from a single CD, without network mirror.
> >> This most probably leads to a console-only install, without X.
> >> And I think, this is what the subscriber is missing: the graphical
> >> interface.
> >> 
> >> Holger
> > 
> > I've been discussing this by email with the OP and so it seems.
> > If you don't oppose I will close the BR as it was a successful installation.



-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 3.0.2
under  D e b i a n   G N U / L I N U X   6.0  ( S q u e e z e )
Registered LinuxUser #311290 - http://linuxcounter.net/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
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/20130511085434.0d76d3bf.li...@wansing-online.de