Re: boot0cfg on does not set default selection on gmirror device

2016-10-23 Thread Ian Smith 
On Sun, 23 Oct 2016 15:53:59 +0200, Patrick M. Hausen wrote:
 > > Am 22.10.2016 um 05:36 schrieb Ian Smith :
 > > [...]
 > > I wonder two things:
 > > 
 > > Do 'boot0cfg -v ada0' and 'boot0cfg -v ada1' both report the same?

Summary: yes, both equally wrong!

 > > Might it work properly if you upgraded the boot sectors to version 2, 
 > > which is what you should get if you reinstall from current boot0cfg, 
 > > presumably without touching the MBR data, but you'll have backups ..
 > 
 > Well ...
 > 
 > root@hd45:~ # boot0cfg -B mirror/m0
 > root@hd45:~ # boot0cfg -s 2 mirror/m0
 > root@hd45:~ # boot0cfg -v mirror/m0
 > #   flag start chs   type   end chs   offset size
 > 1   0x80  1:  0: 1   0xa5   1022:254:6316065 16418430
 > 2   0x00   1023:  0: 1   0xa5   1020:254:63 16434495 16418430
 > 3   0x00   1021:  0: 1   0xa5768:254:63 32852925   1920667140
 > 
 > version=2.0  drive=0x80  mask=0xf  ticks=182  bell=# (0x23)
 > options=packet,update,nosetdrv
 > volume serial ID b100-808f
 > default_selection=F2 (Slice 2)
 > 
 > root@hd45:~ # boot0cfg -v ada0
 > [...]
 > default_selection=F2 (Slice 2)
 > 
 > root@hd45:~ # boot0cfg -v ada1
 > [...]
 > default_selection=F2 (Slice 2)
 > 
 > Revert the change:
 > 
 > root@hd45:~ # boot0cfg -s 1 mirror/m0
 > root@hd45:~ # boot0cfg -v  mirror/m0
 > [...]
 > default_selection=F1 (Slice 1)
 > 
 > 
 > That did it! These machines have been in production for some time
 > starting with FreeBSD 8.x and have been upgraded via NanoBSD style
 > dd followed by reboot all the time up to 10.3, now. Hence I never touched
 > the bootcode.

Glad that one of my wild ill-informed wonderings was on target, and that 
gmirror is off the hook.

 > Actual reboot of this production machine in two weeks when we run our
 > regular updates. But I expect that to "just work".

Warner expected the existing boot0cfg code to "just work" too.  And it 
does, except that the upgrades to it failed to include a method to fix 
existing installations retrospectively!

cheers, Ian
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: boot0cfg on does not set default selection on gmirror device

2016-10-23 Thread Patrick M. Hausen 
Hi, Ian,

> Am 22.10.2016 um 05:36 schrieb Ian Smith :
> [...]
> I wonder two things:
> 
> Do 'boot0cfg -v ada0' and 'boot0cfg -v ada1' both report the same?

OK, situation before I try to change anything:

root@hd45:~ # boot0cfg -v mirror/m0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada1
[...]
default_selection=F1 (Slice 1)


Now try to change it to F2 through the mirror device:

root@hd45:~ # boot0cfg -s 2 mirror/m0
# No error message or other indication that something went wrong!

root@hd45:~ # boot0cfg -v mirror/m0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada0
[...]
default_selection=F1 (Slice 1)

root@hd45:~ # boot0cfg -v ada1
[...]
default_selection=F1 (Slice 1)


> Might it work properly if you upgraded the boot sectors to version 2, 
> which is what you should get if you reinstall from current boot0cfg, 
> presumably without touching the MBR data, but you'll have backups ..

Well ...

root@hd45:~ # boot0cfg -B mirror/m0
root@hd45:~ # boot0cfg -s 2 mirror/m0
root@hd45:~ # boot0cfg -v mirror/m0
#   flag start chs   type   end chs   offset size
1   0x80  1:  0: 1   0xa5   1022:254:6316065 16418430
2   0x00   1023:  0: 1   0xa5   1020:254:63 16434495 16418430
3   0x00   1021:  0: 1   0xa5768:254:63 32852925   1920667140

version=2.0  drive=0x80  mask=0xf  ticks=182  bell=# (0x23)
options=packet,update,nosetdrv
volume serial ID b100-808f
default_selection=F2 (Slice 2)

root@hd45:~ # boot0cfg -v ada0
[...]
default_selection=F2 (Slice 2)

root@hd45:~ # boot0cfg -v ada1
[...]
default_selection=F2 (Slice 2)

Revert the change:

root@hd45:~ # boot0cfg -s 1 mirror/m0
root@hd45:~ # boot0cfg -v  mirror/m0
[...]
default_selection=F1 (Slice 1)


That did it! These machines have been in production for some time
starting with FreeBSD 8.x and have been upgraded via NanoBSD style
dd followed by reboot all the time up to 10.3, now. Hence I never touched
the bootcode.

Actual reboot of this production machine in two weeks when we run our
regular updates. But I expect that to "just work".

Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: LOR in mpr(4)

2016-10-23 Thread geoffroy desvernay 
On 10/19/2016 06:39 PM, Pete Wright wrote:
> 
> the issue you are seeing is most likely not related to the LOR from the
> original email and PR I filed.  This looks like a media error with the
> disk device on your RAID controller.  A quick google search turn's up
> quite a few threads on this - ranging from bad RAID/JBOD controllers to
> out of date firmware.
> 
> Cheers,
> -pete
> 

Thank you for your response, I'll take more time checking around
controller. I just fear that this dell-repackaged avago controller may
have some 'dell' crapped firmware… I have to look closer then :)

Cheers,

dgeo.
-- 
*geoffroy desvernay*
C.R.I - Administration systèmes et réseaux
Ecole Centrale de Marseille
Tel: (+33|0)4 91 05 45 24
Fax: (+33|0)4 91 05 45 98
d...@centrale-marseille.fr

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"