Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
Hi! The second problem I encountered was that neither my user account was created during installation nor was the root password set. This left the system fairly unusable until I used a rescue system to mount my encrypted disk, added a user to /etc/passwd and /etc/shadow (without a password) and subsequently added this user to the sudoers group. In this way I could aquire root on my new system. This is confusing; maybe your media was corrupted in some way since I don't remember of seeing this report and it is used in every installation. Could you try to reproduce it and report back to us? I actually tried twice, though with the same installation media. I don't have any plans to reinstall in the near future though (at least not until the multi-arch stuff screws up my system again.. ;) ) so sorry about that. I meet the same problem while installing unstable from debian-503-i386-businesscard.iso today. After solving some grub2 troubles and booting - can't login user at all! Boot into rescue mode - there is no user in /etc/passwd and /etc/shadow files. Steps to reproduce: 1. Boot from CD debian-503-i386-businesscard.iso 2. Advanced Installation - KDE - Expert mode 3. LVM: / and /home 4. unstable 5. targeted initrd 6. choose hide passwords and root login through sudo 7. can't login after boot Steps to login: 8. boot again from CD in rescue mode 9. enter shell and mount home 10. check there is no user in passwd and shadow 11. adduser 12. reboot and login user I had tried to reproduce the same with stable, max initrd and grub (not grub2) - everything was ok, withot errors. So, the problem is in point 4 or 5. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
Processing commands for cont...@bugs.debian.org: reassign 538086 user-setup 1.23 Bug #538086 [installation-reports] installation-reports: Installation works, but neither is user created nor a root password set Bug reassigned from package 'installation-reports' to 'user-setup'. Bug #538086 [user-setup] installation-reports: Installation works, but neither is user created nor a root password set Bug Marked as found in versions user-setup/1.23. retitle 538086 user-setup: Lenny version is incompatible with Squeeze/Sid Bug #538086 [user-setup] installation-reports: Installation works, but neither is user created nor a root password set Changed Bug title to 'user-setup: Lenny version is incompatible with Squeeze/Sid' from 'installation-reports: Installation works, but neither is user created nor a root password set' tags 538086 lenny wontfix Bug #538086 [user-setup] user-setup: Lenny version is incompatible with Squeeze/Sid Added tag(s) lenny and wontfix. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
reassign 538086 user-setup 1.23 retitle 538086 user-setup: Lenny version is incompatible with Squeeze/Sid tags 538086 lenny wontfix thanks On Wednesday 18 November 2009, Yaroslav Rozhylo wrote: Steps to reproduce: 1. Boot from CD debian-503-i386-businesscard.iso 2. Advanced Installation - KDE - Expert mode 3. LVM: / and /home 4. unstable 5. targeted initrd 6. choose hide passwords and root login through sudo 7. can't login after boot This is far from a standard installation... I had tried to reproduce the same with stable, max initrd and grub (not grub2) - everything was ok, withot errors. So, the problem is in point 4 or 5. It is your selection of unstable. Because it is impossible to anticipate on changes after a stable release, there is never a guarantee that a stable installer will work correctly to install testing or unstable. It looks like the problem you encountered is: http://bugs.debian.org/529475 Which was solved in the user-setup component of the installer in version 1.24: * No longer use the -m switch of chpasswd. It uses PAM now and no longer has this switch. The password will use settings from libpam-runtime, so MD5 by default. To install either testing or unstable, you should either - use the installer for Squeeze [1] - install stable using the Lenny installer and then upgrade BTW, you should have been able to find the cause of the problem fairly easily yourself by checking the syslog of the installation. Cheers, FJP [1] http://www.debian.org/devel/debian-installer/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
On Tue, Jul 28, 2009 at 12:04 PM, Otavio Salvador ota...@ossystems.com.br wrote: Hello, On Wed, Jul 22, 2009 at 8:09 PM, Dinyar Rabadydinyar.rab...@gmail.com wrote: The first problem I encountered while trying to install a system with an encrypted LVM was that the USB stick was taken to be /dev/sda while the harddisk was /dev/sdb. This changed at first boot when the usb stick was unplugged. This first problem could be fixed either by booting into a rescue system and first changing grub's menu.lst to point to (hd0,0) instead of (hd1,0) and then unpack the initrd.img file and change /conf/conf.d/cryptroot to point to /dev/sda instead of /dev/sdb, or alternatively I pulled the USB stick out right before detecting the harddisk. (priority=medium is helpfull for timing here.) This seemed to have no negativ effects on the installation. This is not going to happen in new Debian Installer release for Squeeze since we're not using UUID to avoid those problems. Would be nice if you could check a current snapshot if it indeed works for you and tell us. On the current daily image my harddisk is still listed as /dev/sdc. Is this ok? -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html Sent from Vienna, Austria -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
Alright, I've tried the daily image from 8th of october and this problem seems almost solved. When first booting after installation Grub finds my system partition, but decryption of my filesystem fails. The message with is displayed claims that either the passphrase is wrong or bad options. I'm very sure that my passphrase is correct and I'm reinstalling just now having used the trick where I pull out the usb-stick right before the harddisks are detected to see if the system boots now. On 2009-10-08 4:11 PM, Dinyar Rabady dinyar.rab...@gmail.com wrote: On Tue, Jul 28, 2009 at 12:04 PM, Otavio Salvador ota...@ossystems.com.br wrote: Hello, On Wed, Jul 22, 2009 at 8:09 PM, Dinyar Rabady dinyar.rab...@gmail.com wrote: The f... On the current daily image my harddisk is still listed as /dev/sdc. Is this ok? -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-... Sent from Vienna, Austria
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
on 01/08/09 20:17 Dinyar Rabady said the following: Hi, On Tue, Jul 28, 2009 at 12:04 PM, Otavio Salvadorota...@ossystems.com.br wrote: snipped The second problem I encountered was that neither my user account was created during installation nor was the root password set. This left the system fairly unusable until I used a rescue system to mount my encrypted disk, added a user to /etc/passwd and /etc/shadow (without a password) and subsequently added this user to the sudoers group. In this way I could aquire root on my new system. This is confusing; maybe your media was corrupted in some way since I don't remember of seeing this report and it is used in every installation. Could you try to reproduce it and report back to us? I actually tried twice, though with the same installation media. I don't have any plans to reinstall in the near future though (at least not until the multi-arch stuff screws up my system again.. ;) ) so sorry about that. I can confirm this- reproduced while installing with different daily builds (from yesterday, last week even one from May 2009) using different media with the same result as reported above. This might be an issue with one of the packages the installer uses, since it's also reproduced when using a netinst CD from May 11th, 2009. -E- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
on 01/08/09 20:17 Dinyar Rabady said the following: Hi, On Tue, Jul 28, 2009 at 12:04 PM, Otavio Salvadorota...@ossystems.com.br wrote: snipped The second problem I encountered was that neither my user account was created during installation nor was the root password set. This left the system fairly unusable until I used a rescue system to mount my encrypted disk, added a user to /etc/passwd and /etc/shadow (without a password) and subsequently added this user to the sudoers group. In this way I could aquire root on my new system. This is confusing; maybe your media was corrupted in some way since I don't remember of seeing this report and it is used in every installation. Could you try to reproduce it and report back to us? I actually tried twice, though with the same installation media. I don't have any plans to reinstall in the near future though (at least not until the multi-arch stuff screws up my system again.. ;) ) so sorry about that. I can confirm this- reproduced while installing with different daily builds (from yesterday, last week even one from May 2009) using different media with the same result as reported above. This might be an issue with one of the packages the installer uses, since it's also reproduced when using a netinst CD from May 11th, 2009. -E- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
Hi, On Tue, Jul 28, 2009 at 12:04 PM, Otavio Salvadorota...@ossystems.com.br wrote: Hello, On Wed, Jul 22, 2009 at 8:09 PM, Dinyar Rabadydinyar.rab...@gmail.com wrote: The first problem I encountered while trying to install a system with an encrypted LVM was that the USB stick was taken to be /dev/sda while the harddisk was /dev/sdb. This changed at first boot when the usb stick was unplugged. This first problem could be fixed either by booting into a rescue system and first changing grub's menu.lst to point to (hd0,0) instead of (hd1,0) and then unpack the initrd.img file and change /conf/conf.d/cryptroot to point to /dev/sda instead of /dev/sdb, or alternatively I pulled the USB stick out right before detecting the harddisk. (priority=medium is helpfull for timing here.) This seemed to have no negativ effects on the installation. This is not going to happen in new Debian Installer release for Squeeze since we're not using UUID to avoid those problems. Would be nice if you could check a current snapshot if it indeed works for you and tell us. I have not tryed this yet due to time constraints, but I'll report back as soon as I get round to it. The second problem I encountered was that neither my user account was created during installation nor was the root password set. This left the system fairly unusable until I used a rescue system to mount my encrypted disk, added a user to /etc/passwd and /etc/shadow (without a password) and subsequently added this user to the sudoers group. In this way I could aquire root on my new system. This is confusing; maybe your media was corrupted in some way since I don't remember of seeing this report and it is used in every installation. Could you try to reproduce it and report back to us? I actually tried twice, though with the same installation media. I don't have any plans to reinstall in the near future though (at least not until the multi-arch stuff screws up my system again.. ;) ) so sorry about that. Cheers, -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
Hello, On Wed, Jul 22, 2009 at 8:09 PM, Dinyar Rabadydinyar.rab...@gmail.com wrote: The first problem I encountered while trying to install a system with an encrypted LVM was that the USB stick was taken to be /dev/sda while the harddisk was /dev/sdb. This changed at first boot when the usb stick was unplugged. This first problem could be fixed either by booting into a rescue system and first changing grub's menu.lst to point to (hd0,0) instead of (hd1,0) and then unpack the initrd.img file and change /conf/conf.d/cryptroot to point to /dev/sda instead of /dev/sdb, or alternatively I pulled the USB stick out right before detecting the harddisk. (priority=medium is helpfull for timing here.) This seemed to have no negativ effects on the installation. This is not going to happen in new Debian Installer release for Squeeze since we're not using UUID to avoid those problems. Would be nice if you could check a current snapshot if it indeed works for you and tell us. The second problem I encountered was that neither my user account was created during installation nor was the root password set. This left the system fairly unusable until I used a rescue system to mount my encrypted disk, added a user to /etc/passwd and /etc/shadow (without a password) and subsequently added this user to the sudoers group. In this way I could aquire root on my new system. This is confusing; maybe your media was corrupted in some way since I don't remember of seeing this report and it is used in every installation. Could you try to reproduce it and report back to us? Cheers, -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set
Package: installation-reports Severity: grave Justification: renders package unusable -- Package-specific info: Boot method: USB stick with netboot Image version: ftp://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/netboot/ Date: Date and time of the install Machine: Lenovo Thinkpad x200s Partitions: df -Tl will do; the raw partition table is preferred dinyar-notebook:/home/dinyar# df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/dinyar--notebook-root ext3 295996296 5050720 275909776 2% / tmpfstmpfs 1979968 0 1979968 0% /lib/init/rw udev tmpfs 10240 148 10092 2% /dev tmpfstmpfs 1979968 0 1979968 0% /dev/shm /dev/sda1 ext2 25 44713176174 21% /boot 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: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[E] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: The first problem I encountered while trying to install a system with an encrypted LVM was that the USB stick was taken to be /dev/sda while the harddisk was /dev/sdb. This changed at first boot when the usb stick was unplugged. This first problem could be fixed either by booting into a rescue system and first changing grub's menu.lst to point to (hd0,0) instead of (hd1,0) and then unpack the initrd.img file and change /conf/conf.d/cryptroot to point to /dev/sda instead of /dev/sdb, or alternatively I pulled the USB stick out right before detecting the harddisk. (priority=medium is helpfull for timing here.) This seemed to have no negativ effects on the installation. The second problem I encountered was that neither my user account was created during installation nor was the root password set. This left the system fairly unusable until I used a rescue system to mount my encrypted disk, added a user to /etc/passwd and /etc/shadow (without a password) and subsequently added this user to the sudoers group. In this way I could aquire root on my new system. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20090123lenny3 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == umame -a: Linux dinyar-notebook 2.6.26-2-amd64 #1 SMP Sun Jun 21 04:47:08 UTC 2009 x86_64 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) lspci -knn: 00:03.0 Communication controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller [8086:2a44] (rev 07) lspci -knn: 00:03.2 IDE interface [0101]: Intel Corporation Mobile 4 Series Chipset PT IDER Controller [8086:2a46] (rev 07) lspci -knn: 00:03.3 Serial controller [0700]: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection [8086:2a47] (rev 07) lspci -knn: Kernel driver in use: serial lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82567LM Gigabit Network Connection [8086:10f5] (rev 03) lspci -knn: Kernel driver in use: e1000e lspci -knn: Kernel modules: e1000e lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) lspci -knn:
