Bug#294654: sarge-386-netinst stops during base system installation
Public PGP Key: http://woonjas.linuxnerd.org/nwestra.asc
s/MIME CA certificate: http://woonjas.linuxnerd.org/linuxnerdCA.cer
Joey Hess <email@example.com> wrote on 11-02-2005
> Ninke Westra wrote:
> > console 3 shows the following:
> > Selecting previously deselected package debconf.
> > (Reading database ... 2466 files and directories currently installed.)
> > Unpacking debconf (from ../debconf_220.127.116.11_all.deb) ...
> > dpkg: debconf: dependency problems, but configuring anyway as
> > debconf depends on debconf-i18n | debconf-english; however:
> > Package debconf-i18n is not installed.
> > Package debconf-english is not installed.
> > Setting up debconf (18.104.22.168) ...
> > Global symbol "$fields_base" requires explicit package
> > /usr/share/perl/5.8/base.pm line 104.
> That is a seriously strange problem. It implies that
> /usr/share/perl/5.8/base.pm is broken, but it doesn't look broken
> and I don't see this failure.
> One possibility might be disk corruption during the install or something
> like that.
> If you can reproduce this problem or still have the failed install,
> I'd try to mail a copy of your (/target)/usr/share/perl/5.8/base.pm
> this bug report so we can see what happened to it.
I ripped out 2*256 megs and replaced them with 2*64 that I had collecting
dust somewhere and tried again: different error this time around but again
while setting up debconf:
Setting up debconf (22.214.171.124) ...
Use of uninitialized value in subroutine entry at
/usr/lib/perl/5.8/Fcntl.pm line 170, <DEBCONF_CONFIG> chunk 3.
debconf: Problem setting up the database defined by
stanza 3 of /etc/debconf/conf.
is not a valid Fcntl macro at /usr/share/perl5/Debconf
DbDriver/File.pm line 34.
dpkg: error processing debonf (--install)
subprocess post-installation script returned
error exit status 2
Errors were encountered while processing:
umount: /target/dev/pts: No such file or directory
umount: /target/dev/shm: No such file or directory
umount: /target/proc/bus/usb: Invalid argument
--- so I the memory might not be the culprit here.
time to run some more diagnostics on the drive then.
Description: S/MIME Cryptographic Signature