headers
George Harvey | 17 Mar 2012 00:51

6.0_BETA upgrade fails on Indy / Challenge S

Hi,

I've been attempting to give 6.0_BETA a try but without any success. I
have an external 4.3GB SCSI disk which currently boots 5.1 and which
I'm trying to upgrade to 6.0_BETA. I've tried three different
machines, all netbooting the install kernel, two failed extracting the
base set and the third got past base and failed extracting comp. The
machines are:

R4600/133 Indy with 96MB RAM, failed with malloc errors while
extracting base.tgz, I guess 96MB is no longer enough to run an
install.

R5000/180 Challenge S with 192MB RAM, failed extracting base.tgz with
strange errors like "Cannot rename ./usr/share/locale/uk_UA.KOI8-U/
to ./usr/share/locale /uk_UA.KOI8-U/LC_MESSAGES/SYS_LC_MESSAGES
(Not a directory)" and "Cannot set permissions on (null) (Bad address)".

R5000/150 Indy with 256MB RAM, succeeded in extracting base but failed
to extract comp.tgz with "Command ended on signal".

I might try an install next, instead of an upgrade, just to see if that
makes any difference.

George
Permalink | Reply | 5 comments |
headers
George Harvey | 19 Mar 2012 22:48

Re: 6.0_BETA upgrade fails on Indy / Challenge S

On Fri, 16 Mar 2012 23:51:20 +0000
George Harvey <fr30 <at> dial.pipex.com> wrote:

> I've been attempting to give 6.0_BETA a try but without any success. I
> have an external 4.3GB SCSI disk which currently boots 5.1 and which
> I'm trying to upgrade to 6.0_BETA. I've tried three different
> machines, all netbooting the install kernel, two failed extracting the
> base set and the third got past base and failed extracting comp. The
> machines are:
> 
> R4600/133 Indy with 96MB RAM, failed with malloc errors while
> extracting base.tgz, I guess 96MB is no longer enough to run an
> install.
> 
> R5000/180 Challenge S with 192MB RAM, failed extracting base.tgz with
> strange errors like "Cannot rename ./usr/share/locale/uk_UA.KOI8-U/
> to ./usr/share/locale /uk_UA.KOI8-U/LC_MESSAGES/SYS_LC_MESSAGES
> (Not a directory)" and "Cannot set permissions on (null) (Bad address)".
> 
> R5000/150 Indy with 256MB RAM, succeeded in extracting base but failed
> to extract comp.tgz with "Command ended on signal".
> 
> I might try an install next, instead of an upgrade, just to see if that
> makes any difference.

Tried an install on the R5000/150 Indy and it failed in the same place,
"Command ended on signal" just at the start of extracting the comp.tgz
set. Up until now, I'd been selecting a custom install and including the
comp, man and X11 sets. For my next attempt I tried just a minimal
install and that worked, it completed normally and I was able to boot
(Continue reading)

Permalink | Reply | 4 comments |
headers
John Klos | 20 Mar 2012 00:08

Re: 6.0_BETA upgrade fails on Indy / Challenge S

Hi,

> Next step was to reboot into the install kernel again and try adding
> the extra sets. This time comp was extracted without error but the next
> set, man, threw 'invalid header', data stream error', 'unexpected EOF
> and failed. This suggests that sysinst is running out of some resource,
> possibly RAM, when asked to extract multiple sets.

If the system were running out of some resource, it would fail to launch 
new processes or kill off running processes - it wouldn't randomly fail.

There's a possibility that there's something wrong with the install 
kernel. If you install and boot into a really basic install, then 
untargzip additional sets, does that work?

John
Permalink | Reply | 3 comments |
headers
George Harvey | 21 Mar 2012 00:42

Re: 6.0_BETA upgrade fails on Indy / Challenge S

On Mon, 19 Mar 2012 23:08:00 +0000 (UTC)
John Klos <john <at> ziaspace.com> wrote:

> > Next step was to reboot into the install kernel again and try adding
> > the extra sets. This time comp was extracted without error but the next
> > set, man, threw 'invalid header', data stream error', 'unexpected EOF
> > and failed. This suggests that sysinst is running out of some resource,
> > possibly RAM, when asked to extract multiple sets.
> 
> If the system were running out of some resource, it would fail to launch 
> new processes or kill off running processes - it wouldn't randomly fail.
> 
> There's a possibility that there's something wrong with the install 
> kernel. If you install and boot into a really basic install, then 
> untargzip additional sets, does that work?

No, I get similar errors to those I saw with sysinst. I booted the
GENERIC kernel from local disk and tried installing the remaining
sets from local disk. The first few unpacked OK but xcomp failed with
unexpected EOF. Checking the md5 sums, it seems that xcomp was the
right length but wrong md5. I re-copied it using FTP and this time the
md5 sum was OK. However, when I tried again to unpack it I got weird
errors like 'cannot set file uid/gid of ()'. So it's looking more like
a kernel bug and not a problem with sysinst.

George
Permalink | Reply | 2 comments |
headers
Robert Dörfler | 21 Mar 2012 06:30

Re: 6.0_BETA upgrade fails on Indy / Challenge S

On 21.03.2012 00:42, George Harvey wrote:
> On Mon, 19 Mar 2012 23:08:00 +0000 (UTC)
> John Klos<john <at> ziaspace.com>  wrote:
>
>>> Next step was to reboot into the install kernel again and try adding
>>> the extra sets. This time comp was extracted without error but the next
>>> set, man, threw 'invalid header', data stream error', 'unexpected EOF
>>> and failed. This suggests that sysinst is running out of some resource,
>>> possibly RAM, when asked to extract multiple sets.
>>
>> If the system were running out of some resource, it would fail to launch
>> new processes or kill off running processes - it wouldn't randomly fail.
>>
>> There's a possibility that there's something wrong with the install
>> kernel. If you install and boot into a really basic install, then
>> untargzip additional sets, does that work?
>
> No, I get similar errors to those I saw with sysinst. I booted the
> GENERIC kernel from local disk and tried installing the remaining
> sets from local disk. The first few unpacked OK but xcomp failed with
> unexpected EOF. Checking the md5 sums, it seems that xcomp was the
> right length but wrong md5. I re-copied it using FTP and this time the
> md5 sum was OK. However, when I tried again to unpack it I got weird
> errors like 'cannot set file uid/gid of ()'. So it's looking more like
> a kernel bug and not a problem with sysinst.

I guess i got the same "unexpected EOF"-Errors on my O2. I installed the
packages via ftp/http and tests.tar.gz failed repeatable. ( even after
choosing a different way to get package ftp/http )
(Continue reading)

Permalink | Reply | 1 comment |
headers
Robert Doerfler | 21 Mar 2012 20:12

Re: 6.0_BETA upgrade fails on Indy / Challenge S

Robert Dörfler <rodo <at> zlug.org> schrieb:
> On 21.03.2012 00:42, George Harvey wrote:
>> On Mon, 19 Mar 2012 23:08:00 +0000 (UTC)
>> John Klos<john <at> ziaspace.com>  wrote:
>>
>>>> Next step was to reboot into the install kernel again and try adding
>>>> the extra sets. This time comp was extracted without error but the next
>>>> set, man, threw 'invalid header', data stream error', 'unexpected EOF
>>>> and failed. This suggests that sysinst is running out of some resource,
>>>> possibly RAM, when asked to extract multiple sets.
>>>
>>> If the system were running out of some resource, it would fail to launch
>>> new processes or kill off running processes - it wouldn't randomly fail.
>>>
>>> There's a possibility that there's something wrong with the install
>>> kernel. If you install and boot into a really basic install, then
>>> untargzip additional sets, does that work?
>>
>> No, I get similar errors to those I saw with sysinst. I booted the
>> GENERIC kernel from local disk and tried installing the remaining
>> sets from local disk. The first few unpacked OK but xcomp failed with
>> unexpected EOF. Checking the md5 sums, it seems that xcomp was the
>> right length but wrong md5. I re-copied it using FTP and this time the
>> md5 sum was OK. However, when I tried again to unpack it I got weird
>> errors like 'cannot set file uid/gid of ()'. So it's looking more like
>> a kernel bug and not a problem with sysinst.
>
> I guess i got the same "unexpected EOF"-Errors on my O2. I installed the
> packages via ftp/http and tests.tar.gz failed repeatable. ( even after
> choosing a different way to get package ftp/http )
(Continue reading)

Permalink | Reply | 0 comments |

Gmane