Messages postés par Mitch

Mitch

Erreur: Target directory access error

Que faire si j’ai ce message d’erreur ?

Simplement modifier les droits d’accès au répertoire DCS (et à l’ensemble de ses sous-dossiers):

Mitch

Bienvenue à toi @Théo ,

Si jamais tu veux faire du A-10C II (et oui, on est tous passés au 2), il y a la patrouille Archer

Mitch.

Mitch

Bonsoir Molok,

Bienvenue à la VEAF, et désolé pour le plantage du serveur en plein training… On espère avoir fixé le problème et te recroiser prochainement sur le tarmac ou en vol.

A+

Mitch.

Mitch

Issue github pour la postérité: https://github.com/VEAF/infra/issues/18

Mitch

Piste de solution:

https://gist.github.com/brunneis/0c27411a8028610117fefbe5fb669d10?permalink_comment_id=4214306#gistcomment-4214306

Mitch

Incident du lundi 12/02:

Feb 12 21:49:35 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <aa>
  TDT                  <f7>
  next_to_use          <f7>
  next_to_clean        <a9>
buffer_info[next_to_clean]:
  time_stamp           <1996c59d1>
  next_to_watch        <aa>
  jiffies              <1996c5bc8>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 12 21:49:37 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <aa>
  TDT                  <f7>
  next_to_use          <f7>
  next_to_clean        <a9>
buffer_info[next_to_clean]:
  time_stamp           <1996c59d1>
  next_to_watch        <aa>
  jiffies              <1996c5db8>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 12 21:49:39 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <aa>
  TDT                  <f7>
  next_to_use          <f7>
  next_to_clean        <a9>
buffer_info[next_to_clean]:
  time_stamp           <1996c59d1>
  next_to_watch        <aa>
  jiffies              <1996c5fb0>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 12 21:49:39 srv3.veaf.org kernel: nfs: server 5.196.74.132 not responding, timed out
Feb 12 21:49:40 srv3.veaf.org pvestatd[1028]: storage 'backup-storage' is not online
Feb 12 21:49:40 srv3.veaf.org pvestatd[1028]: status update time (5.107 seconds)
Feb 12 21:49:41 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <aa>
  TDT                  <f7>
  next_to_use          <f7>
  next_to_clean        <a9>
buffer_info[next_to_clean]:
  time_stamp           <1996c59d1>
  next_to_watch        <aa>
  jiffies              <1996c61a1>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 12 21:49:41 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly
Feb 12 21:49:41 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered disabled state

Mitch

Le 20 Février à 19h57:

Feb 20 19:57:44 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <56>
  TDT                  <91>
  next_to_use          <91>
  next_to_clean        <55>
buffer_info[next_to_clean]:
  time_stamp           <1a39f7811>
  next_to_watch        <56>
  jiffies              <1a39f7a01>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 19:57:46 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <56>
  TDT                  <91>
  next_to_use          <91>
  next_to_clean        <55>
buffer_info[next_to_clean]:
  time_stamp           <1a39f7811>
  next_to_watch        <56>
  jiffies              <1a39f7bf0>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 19:57:48 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <56>
  TDT                  <91>
  next_to_use          <91>
  next_to_clean        <55>
buffer_info[next_to_clean]:
  time_stamp           <1a39f7811>
  next_to_watch        <56>
  jiffies              <1a39f7de8>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 19:57:50 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <56>
  TDT                  <91>
  next_to_use          <91>
  next_to_clean        <55>
buffer_info[next_to_clean]:
  time_stamp           <1a39f7811>
  next_to_watch        <56>
  jiffies              <1a39f7fd8>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 19:57:50 srv3.veaf.org kernel: nfs: server 5.196.74.132 not responding, timed out
Feb 20 19:57:50 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly
Feb 20 19:57:50 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered disabled state
Feb 20 19:57:54 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 20 19:57:54 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered blocking state
Feb 20 19:57:54 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered forwarding state

Mitch

en recherchant plus loin, le 20 Février à 17h36:


Feb 20 17:35:56 srv3.veaf.org kernel: nfs: server 5.196.74.132 not responding, timed out
Feb 20 17:36:05 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <f7>
  TDT                  <46>
  next_to_use          <46>
  next_to_clean        <f6>
buffer_info[next_to_clean]:
  time_stamp           <1a37f0c36>
  next_to_watch        <f7>
  jiffies              <1a37f0e40>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 17:36:07 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <f7>
  TDT                  <46>
  next_to_use          <46>
  next_to_clean        <f6>
buffer_info[next_to_clean]:
  time_stamp           <1a37f0c36>
  next_to_watch        <f7>
  jiffies              <1a37f1038>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 17:36:09 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <f7>
  TDT                  <46>
  next_to_use          <46>
  next_to_clean        <f6>
buffer_info[next_to_clean]:
  time_stamp           <1a37f0c36>
  next_to_watch        <f7>
  jiffies              <1a37f1228>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 17:36:11 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <f7>
  TDT                  <46>
  next_to_use          <46>
  next_to_clean        <f6>
buffer_info[next_to_clean]:
  time_stamp           <1a37f0c36>
  next_to_watch        <f7>
  jiffies              <1a37f1421>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <7800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 20 17:36:11 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly
Feb 20 17:36:11 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered disabled state
Feb 20 17:36:15 srv3.veaf.org kernel: nfs: server 5.196.74.132 not responding, timed out
Feb 20 17:36:15 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 20 17:36:15 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered blocking state
Feb 20 17:36:15 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered forwarding state

Mitch

Logs de ce soir, qui correspondent à la coupure réseau rencontrée:

Feb 23 22:16:56 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <83>
  TDT                  <6d>
  next_to_use          <6d>
  next_to_clean        <83>
buffer_info[next_to_clean]:
  time_stamp           <1a79c19de>
  next_to_watch        <84>
  jiffies              <1a79c1b50>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <3800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 23 22:16:58 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <83>
  TDT                  <6d>
  next_to_use          <6d>
  next_to_clean        <83>
buffer_info[next_to_clean]:
  time_stamp           <1a79c19de>
  next_to_watch        <84>
  jiffies              <1a79c1d41>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <3800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 23 22:17:00 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <83>
  TDT                  <6d>
  next_to_use          <6d>
  next_to_clean        <83>
buffer_info[next_to_clean]:
  time_stamp           <1a79c19de>
  next_to_watch        <84>
  jiffies              <1a79c1f38>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <3800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 23 22:17:00 srv3.veaf.org kernel: nfs: server 5.196.74.132 not responding, timed out
Feb 23 22:17:01 srv3.veaf.org pvestatd[1028]: storage 'backup-storage' is not online
Feb 23 22:17:01 srv3.veaf.org pvestatd[1028]: status update time (5.070 seconds)
Feb 23 22:17:01 srv3.veaf.org CRON[2090299]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 23 22:17:01 srv3.veaf.org CRON[2090300]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 23 22:17:01 srv3.veaf.org CRON[2090299]: pam_unix(cron:session): session closed for user root
Feb 23 22:17:02 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <83>
  TDT                  <6d>
  next_to_use          <6d>
  next_to_clean        <83>
buffer_info[next_to_clean]:
  time_stamp           <1a79c19de>
  next_to_watch        <84>
  jiffies              <1a79c2128>
  next_to_watch.status <0>
MAC Status             <40080083>
PHY Status             <796d>
PHY 1000BASE-T Status  <3800>
PHY Extended Status    <3000>
PCI Status             <10>
Feb 23 22:17:03 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly
Feb 23 22:17:03 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered disabled state
Feb 23 22:17:06 srv3.veaf.org kernel: nfs: server 5.196.74.132 not responding, timed out
Feb 23 22:17:07 srv3.veaf.org kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 23 22:17:07 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered blocking state
Feb 23 22:17:07 srv3.veaf.org kernel: vmbr0: port 1(eno1) entered forwarding state

Mitch

Bonjour à toi et bienvenue !

Mitch

Bonjour FurieKest et bienvenue à toi !

Mitch

Bienvenue à toi @Maveric !

Mitch

Bienvenue à toi Raven !

Mitch

Mitch / Valence-Chabeuil / Drôme (26) - LFLU

Mitch

Quelques vidéos pour le F-16C:

A/G:

AGM-65D VIS mode (visée directe) - 60 secondes
GBU-31 - JDAM - 60 secondes
HARM w/HAD - 60 secondes
Rockets - 60 secondes

A/A:

A-A Gun - 60 secondes
AIM-120 RWS - cible unique - 60 secondes
AIM-120 TWS - cibles multiples - 60 secondes

Mitch

Bonjour @hubertgermain,

Ce sujet concerne la présentation de Scouver (qui n’a pas donné signe de vie depuis Mars 2020 …).

Si tu as des questions, le mieux est:

d’ouvrir un nouveau sujet ici: https://community.veaf.org/category/12/la-taverne-des-oiseaux
ou poser des questions sur notre discord ici: https://www.veaf.org/discord
ou en parler sur Teamspeak (https://www.veaf.org/teamspeak)

A bientôt,

Mitch.

Mitch

@maxx a dit dans Presentation Maxx VEAF :

su25T

Bonjour à toi Maxx !

N’hésite pas à me contacter sur Discord si tu veux une petite initiation sur le Su-25T (je suis pas tout le temps disponible mais n’hésite pas !).

Mitch.

Mitch

Procédure

Sur Proxmox:
Datacenter, 101 dcs, Hardware, Hard Disk (scsi0), Disk Action, Resize
Size Increment: 50 GiB

L’espace est donc passé de 300 à 350 GiB

Créer un snapshot (on est jamais trop prudent).

Dans Windows:
ouvrir Disk Management

l’espace non alloué se trouve à la fin du Disk 0, après une partition de Recovery…
Merci les gens de chez Microsoft pour présenter un schéma de partitionnement aussi idiot…

run as administrator diskpart
list disk
select disk 0
list partition

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           450 MB  1024 KB
  Partition 2    System             100 MB   451 MB
  Partition 3    Reserved            16 MB   551 MB
  Partition 4    Primary            298 GB   567 MB
  Partition 5    Recovery           515 MB   299 GB

select partition 5

gpt attributes=0x8000000000000000

delete partition

exit

à partir de là, on peut terminer dans Disk Management d’étendre la partition:

on confirme la place libre ici:
2022-06-23 19_27_44-Window.jpg

ps: la prochaine fois, la deuxième partition recovery ne sera plus là, on pourra direct passer à l’étape 2

post intervention: je supprime le snapshot

Mitch

Hello @zip ,

En l’état, on a aucun problème pour agrandir le disque virtuel, il nous reste de l’espace physique disponible:

Nous nous sommes toujours montré très économes sur les différentes VM, je vais donc rajouter de la place.

Mitch

Bienvenue à toi Aki !

En espérant te croiser prochainement dans les airs ! Brrrrrrttttt