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

Re: Problems installing squeeze netinstall



On 05/29/11 at 02:31pm, Ethan Rosenberg wrote:
> At 12:21 PM 5/29/2011, William Hopkins wrote:
> >Do you get any other text on the screen when it hangs during boot?
> >What was the ps -ef output from the troubleshooting terminal of the installer?
> >
> +++++++
> From active terminal:
> Waarning: Untrusted versions of the following software will be installed!
> Untrusted packages could compromise your system's security
> You should only proceed with the installation if you are certain
> that this is what you want to do
> 
> in-target: dhcp3-client  dhcp3-common linux-image-2.6.26.-1-686
> in-target: Clinux-image-2.6.26.-2-686 tzdata
> in-target: do you want to ignorre this warning and proceed anyway?
> To contiue enter "Yes"; to abour enter "No":
> Yes [no response to this reply]

Interesting, something has gone wrong with your security keys. Possible reasons:

outdated CD (keys no longer valid)
corrupt CD (keys unreadable)
time issues
bad mirror
man-in-the-middle attack/repo poisoning (extremely unlikely)

You can try another CD (possibly downloaded&burned from a different machine than you used last time). Or you can use the 'advanced' option of the installer, and simply skip the software installation part. This *should* give you a working install without anything but the base OS. Then you can update your sources.list and install manually.

 
> output from ps -ef:
> 31637 root 1672s udpkg --configure --force-configure pkgsel
> 31638 root 1808 S /bin/sh /var/lib/dpkg/info/pkgsel.postinst configure
> 31659 root 1808 S /bin/sh /bin/in-target sh -c debconf-apt-progress --f
> 31686 root 1668 S log-output -t in-target chroot /target sh -c debconf-
> 31687 root 10212 S /usr/bin/perl -w /usr/share/defconf/frontend /usr/bin
> 31689 root 6416 S /usr/bin/perl -w /usr/bin/debconf-apt-progress --from
> 31690 root 50824 S aptitude -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o
> 31694 root 1812 R ps -ef

Looks normal. Clearly the issue is related to the key error you receive above.

-- 
Liam

Attachment: signature.asc
Description: Digital signature


Reply to: