<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="fr">
	<id>https://futex.re/mediawiki/index.php?action=history&amp;feed=atom&amp;title=4.1_Divers</id>
	<title>4.1 Divers - Historique des versions</title>
	<link rel="self" type="application/atom+xml" href="https://futex.re/mediawiki/index.php?action=history&amp;feed=atom&amp;title=4.1_Divers"/>
	<link rel="alternate" type="text/html" href="https://futex.re/mediawiki/index.php?title=4.1_Divers&amp;action=history"/>
	<updated>2026-05-13T15:38:06Z</updated>
	<subtitle>Historique des versions pour cette page sur le wiki</subtitle>
	<generator>MediaWiki 1.39.17</generator>
	<entry>
		<id>https://futex.re/mediawiki/index.php?title=4.1_Divers&amp;diff=1314&amp;oldid=prev</id>
		<title>Futex le 16 mai 2012 à 13:55</title>
		<link rel="alternate" type="text/html" href="https://futex.re/mediawiki/index.php?title=4.1_Divers&amp;diff=1314&amp;oldid=prev"/>
		<updated>2012-05-16T13:55:48Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Nouvelle page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Problème au démarrage serveur :&lt;br /&gt;
code 546 :&lt;br /&gt;
hd5 mirroré et stale ou odm corrompu. Pour vérifier si hd5 OK : &lt;br /&gt;
  # getlvcb -AT hd5 . Si non ok :&lt;br /&gt;
Si pb bosboot. Supprimer hd5 et recréer &lt;br /&gt;
  # rmlv hd5&lt;br /&gt;
  # mklv -yhd5 -t boot -a e rootvg 1 hdisk0&lt;br /&gt;
Si pb de coherence disque boot :&lt;br /&gt;
booter en maitenance sans monter les FS et :&lt;br /&gt;
  # mount /dev/hd2 /usr&lt;br /&gt;
  # mount /dev/hd4 /mnt&lt;br /&gt;
  # mkdir /mnt/etc/objrepos/backup&lt;br /&gt;
  # cp /mnt/etc/objrepos/Cu* /mnt/etc/objrepos/backup&lt;br /&gt;
  # ls -l /mnt/etc/objrepos/backup&lt;br /&gt;
  # umount /mnt&lt;br /&gt;
  # savebase -d /dev/hdisk7&lt;br /&gt;
  # mount /dev/hd4 /mnt&lt;br /&gt;
  # cp /etc/objrepos/Cu* /mnt/etc/objrepos&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Lister les modules charger par le noyau&lt;br /&gt;
&lt;br /&gt;
  # genkex&lt;br /&gt;
  Text address     Size File&amp;lt;br&amp;gt;&lt;br /&gt;
  47a0000     4bd0 /usr/lib/drivers/perfvmmstat.mp&lt;br /&gt;
  47d8000     e2e8 /usr/lib/drivers/filter4&lt;br /&gt;
  47ce000     9700 /usr/lib/drivers/tunnel_if4&lt;br /&gt;
  47bf000     e858 /usr/lib/drivers/ipsec_cap4&lt;br /&gt;
  47b5000     9cb8 /usr/lib/drivers/tunnel_cache4&lt;br /&gt;
  47a8000     adf8 /usr/lib/drivers/random&lt;br /&gt;
  45d1000   1c6170 /usr/lib/drivers/nfs.ext&lt;br /&gt;
  4271000      430 /usr/lib/drivers/nfs_kdes.ext&lt;br /&gt;
  45b9000    17a38 /usr/lib/drivers/pdiagex&lt;br /&gt;
  4502000      398 /usr/lib/drivers/syscalls64.ext&lt;br /&gt;
  4530000     3728 /usr/lib/drivers/aiopin&lt;br /&gt;
  4537000     afb8 /usr/lib/drivers/aio.ext&lt;br /&gt;
  ....&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Monter ISO&lt;br /&gt;
  mklv -y cdtmp rootvg 50&lt;br /&gt;
  dd if=aaa.iso of=/dev/cdtmp bs=16k&lt;br /&gt;
  mount -rv cdrfs /dev/cdtmp /cdrom&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Si après reboot on ne peut plus varyonner les VG: &lt;br /&gt;
  {op}@ylai0012 # lspv&lt;br /&gt;
  hdisk0          00081a3a3723d5b4                    altinst_rootvg  &lt;br /&gt;
  hdisk9          00035b4e132f26f2                    vg01             &lt;br /&gt;
  hdisk10         00035b4e132f85dc                    vgsoft          &lt;br /&gt;
  hdisk11         00035b4e133093b9                    vg02            &lt;br /&gt;
  hdisk12         00035b4e1330a5d0                    vg02            &lt;br /&gt;
  hdisk13         00035b4e133121be                    vg03            &lt;br /&gt;
  hdisk14         00035b4e13317b72                    vg04            &lt;br /&gt;
  hdisk15         00035b4e4a2b86e4                    rootvg          active&amp;lt;br&amp;gt;&lt;br /&gt;
  {op}@ylai0012 # varyonvg vg01&lt;br /&gt;
  0516-082 varyonvg: Unable to access a special device file.&lt;br /&gt;
	 Execute redefinevg and synclvodm to build correct environment.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
  {op}@ylai0012 # redefinevg -d hdisk9 vg01&lt;br /&gt;
  {op}@ylai0012 # varyonvg vg0 &lt;br /&gt;
&lt;br /&gt;
Mais le LV est pas reconnu dans l&amp;#039;ODM&lt;br /&gt;
&lt;br /&gt;
  {op}@ylai0012 # lslv users&lt;br /&gt;
  LOGICAL VOLUME:     users                  VOLUME GROUP:   vg01&lt;br /&gt;
  LV IDENTIFIER:      003381bb00004c00000001098742d128.1 PERMISSION:     read/write&lt;br /&gt;
  VG STATE:           active/complete        LV STATE:       closed/syncd&lt;br /&gt;
  TYPE:               jfs2                   WRITE VERIFY:   off&lt;br /&gt;
  MAX LPs:            715                    PP SIZE:        32 megabyte(s)&lt;br /&gt;
  COPIES:             1                      SCHED POLICY:   parallel&lt;br /&gt;
  LPs:                715                    PPs:            715&lt;br /&gt;
  STALE PPs:          0                      BB POLICY:      relocatable&lt;br /&gt;
  INTER-POLICY:       minimum                RELOCATABLE:    yes&lt;br /&gt;
  INTRA-POLICY:       middle                 UPPER BOUND:    32&lt;br /&gt;
  MOUNT POINT:        /users                 LABEL:          /users&lt;br /&gt;
  MIRROR WRITE CONSISTENCY: on/ACTIVE                              &lt;br /&gt;
  EACH LP COPY ON A SEPARATE PV ?: yes                                    &lt;br /&gt;
  Serialize IO ?:     NO                                     &lt;br /&gt;
  lslv: open(): A file or directory in the path name does not exist.&amp;lt;br&amp;gt;&lt;br /&gt;
  {op}@ylai0012 # synclvodm -Pv vg01&lt;br /&gt;
  synclvodm: Physical volume data updated.&lt;br /&gt;
  synclvodm: Logical volume users updated.&lt;br /&gt;
  {op}@ylai0012 # mount /users&lt;br /&gt;
  {op}@ylai0012 # bosboot -ad hdisk15&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Si le déport console d&amp;#039;un serveur ne marche pas&lt;br /&gt;
  {op}@pyaicz # lscons&lt;br /&gt;
  NULL&lt;br /&gt;
Faire un&lt;br /&gt;
  {op}@pyaicz # chcons /dev/vty0&lt;br /&gt;
  chcons: console assigned to: /dev/vty0, effective on next system boot&lt;br /&gt;
Et rebooter&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Si la LED d&amp;#039;avertissement hardware est orange sur le chassis, et qu&amp;#039;il n&amp;#039;y a plus de problème hard, on peut la reseter comme suit:&lt;br /&gt;
 - diag&lt;br /&gt;
 - Task Selection&lt;br /&gt;
 - Identify and Attention Indicators&lt;br /&gt;
 - Set System Attention Indicator to NORMAL&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
En cas de message d&amp;#039;erreur &amp;quot; paramlist toolong &amp;quot;&lt;br /&gt;
Il s&amp;#039;agit du paramètre narg qui est trop petit&lt;br /&gt;
  # lsattr -El sys0 -a ncargs&lt;br /&gt;
  ncargs 24 ARG/ENV list size in 4K byte blocks True&lt;br /&gt;
&lt;br /&gt;
Il suffit de le changer &lt;br /&gt;
  # chdev -l sys0 -a ncargs=128&lt;/div&gt;</summary>
		<author><name>Futex</name></author>
	</entry>
</feed>