Re: can't upgrade using the last snapshot

[lists]

Mon, 11 Apr 2016 18:31:35 + Robert Peichaer 
> On Mon, Apr 11, 2016 at 07:22:31PM +0200, arrowscr...@mail.com wrote:
> > The snapshot can't find the mirror. It prints: "no address associated with 
> > this name".
> > I have tried many mirrors (inclusing the mother, ftp.openbsd.org), none 
> > work for me.
> > 
> > I has been a hard time to work with snapshots since last month... many bugs.
> > I'm using snapshots to help reporting bugs, of course, so I know that this 
> > kind of situation will happen some times. But, I can't crash the system 
> > everytime I do a new upgrade... I think it's time to just use stable.  
>  
> That means at the time when the installer tries to contact the mirror
> server, you either don't have network connectivity at all or that you
> don't have a working DNS.

An option is to download the sets in home and install from the local
partition.  This has worked as ever, and does eliminate the network
possible issues.  Before that, check your MEM and DISK for hardware
problems, reinsert modules, reseat cabling, vacuum main board slots,
run memory and disk tests, just to be sure you're not panicked there.

> If that's reproducable for you, watch closely if there are any error
> messages related to the network configuration right after the mounting
> of the root filesystem. You can switch to the shell and check the network
> config by entering a '! e.g. at the prompt that asks you about
> force checking clean non-root filesystems. (just 'exit' to continue)
> 
> The installer seems to work fine, I just upgraded using the latest snap
> (4th April).

Seconded.  If you're so inclined try with an older snapshot and report
results please.  It is important to not abandon early, go through the
problem diligently and find the culprit, if for your own practice only.

Re: can't upgrade using the last snapshot

[Juan Francisco Cantero Hurtado]

On Mon, Apr 11, 2016 at 08:53:44PM +0200, arrowscr...@mail.com wrote:
> I have network connectivity and DNS seems Ok. The build is 1459828632, from 
> Apr 5.
> And now the system is broken (panic):
> 
> Stopped at debugger+0x9: leave
> debugger() at debugger+0x9
> panic() at panic+0xfe
> setroot() at setroot+0xa59
> diskconf() at diskconf+0xe3
> main() at main+0x538

Use "boot obsd" in the bootloader and it will load the old kernel.

> 
> 
> Sorry, but I can't keep this. I need to have something (at least) working, 
> and snapshots are not. I'll just switch to stable.
> 

-- 
Juan Francisco Cantero Hurtado http://juanfra.info

Re: can't upgrade using the last snapshot

[Juan Francisco Cantero Hurtado]

On Mon, Apr 11, 2016 at 06:31:35PM +, Robert Peichaer wrote:
> On Mon, Apr 11, 2016 at 07:22:31PM +0200, arrowscr...@mail.com wrote:
> > The snapshot can't find the mirror. It prints: "no address associated with 
> > this name".
> > I have tried many mirrors (inclusing the mother, ftp.openbsd.org), none 
> > work for me.
> > 
> > I has been a hard time to work with snapshots since last month... many bugs.
> > I'm using snapshots to help reporting bugs, of course, so I know that this 
> > kind of situation will happen some times. But, I can't crash the system 
> > everytime I do a new upgrade... I think it's time to just use stable.
>  
> That means at the time when the installer tries to contact the mirror
> server, you either don't have network connectivity at all or that you
> don't have a working DNS.

Or maybe you're using a local DNS cache.

> 
> If that's reproducable for you, watch closely if there are any error
> messages related to the network configuration right after the mounting
> of the root filesystem. You can switch to the shell and check the network
> config by entering a '! e.g. at the prompt that asks you about
> force checking clean non-root filesystems. (just 'exit' to continue)
> 
> The installer seems to work fine, I just upgraded using the latest snap
> (4th April).
> 

-- 
Juan Francisco Cantero Hurtado http://juanfra.info

Re: can't upgrade using the last snapshot

[arrowscript]

I have network connectivity and DNS seems Ok. The build is 1459828632, from Apr 
5.
And now the system is broken (panic):

Stopped at debugger+0x9: leave
debugger() at debugger+0x9
panic() at panic+0xfe
setroot() at setroot+0xa59
diskconf() at diskconf+0xe3
main() at main+0x538


Sorry, but I can't keep this. I need to have something (at least) working, and 
snapshots are not. I'll just switch to stable.

Re: can't upgrade using the last snapshot

[Robert Peichaer]

On Mon, Apr 11, 2016 at 07:22:31PM +0200, arrowscr...@mail.com wrote:
> The snapshot can't find the mirror. It prints: "no address associated with 
> this name".
> I have tried many mirrors (inclusing the mother, ftp.openbsd.org), none work 
> for me.
> 
> I has been a hard time to work with snapshots since last month... many bugs.
> I'm using snapshots to help reporting bugs, of course, so I know that this 
> kind of situation will happen some times. But, I can't crash the system 
> everytime I do a new upgrade... I think it's time to just use stable.
 
That means at the time when the installer tries to contact the mirror
server, you either don't have network connectivity at all or that you
don't have a working DNS.

If that's reproducable for you, watch closely if there are any error
messages related to the network configuration right after the mounting
of the root filesystem. You can switch to the shell and check the network
config by entering a '! e.g. at the prompt that asks you about
force checking clean non-root filesystems. (just 'exit' to continue)

The installer seems to work fine, I just upgraded using the latest snap
(4th April).

can't upgrade using the last snapshot

[arrowscript]

The snapshot can't find the mirror. It prints: "no address associated with this 
name".
I have tried many mirrors (inclusing the mother, ftp.openbsd.org), none work 
for me.

I has been a hard time to work with snapshots since last month... many bugs.
I'm using snapshots to help reporting bugs, of course, so I know that this kind 
of situation will happen some times. But, I can't crash the system everytime I 
do a new upgrade... I think it's time to just use stable.