Serveurs Dédiés Eco - Serveur dédié : Services (SSH, HTTP, etc.) ne démarrent plus après reboot
... / Serveur dédié : Services ...
< Previous question   -   Next question >
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Frage

Serveur dédié : Services (SSH, HTTP, etc.) ne démarrent plus après reboot

S
Von
SAS-LS
Erstellungsdatum 2024-05-20 09:49:08 (edited on 2024-09-04 11:33:48) in Serveurs Dédiés Eco

Bonjour,

J’ai depuis plus d’un an un serveur dédié Kimsufi KS-15 Soft RAID sur lequel tourne un serveur Nextcloud. J’avais depuis plusieurs jours quelques lenteurs sur le serveur ainsi que des « Internal Server Error » intempestifs, je me suis donc connecté en SSH sur le serveur pour essayer de régler le souci et j’ai eu la mauvaise idée de faire un reboot du serveur.
Depuis, plus aucun service ne démarre sur le serveur et tous les ports sont fermés.

PORT STATE SERVICE
21/tcp closed ftp
22/tcp closed ssh
23/tcp closed telnet
80/tcp closed http
110/tcp closed pop3
143/tcp closed imap
443/tcp closed https
3389/tcp closed ms-wbt-server

J’ai passé le serveur en mode rescue pour pouvoir me connecter en SSH.

root@rescue-customer-eu (ns3056801.ip-188-165-234.eu) ~ # fdisk -l
Disk /dev/ram0: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 50 MiB, 52428800 bytes, 102400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: HGST HUS724020AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6D3C7AED-4C42-43FC-91B5-674494A52340

Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 2101247 2097152 1G Linux RAID
/dev/sda3 2101248 3905976319 3903875072 1.8T Linux RAID
/dev/sda4 3905976320 3907024895 1048576 512M Linux filesystem
/dev/sda5 3907025072 3907029134 4063 2M Linux filesystem


Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: HGST HUS726020AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B2B0259B-7D5C-4000-B5A2-657F4A7E4F90

Device Start End Sectors Size Type
/dev/sdb1 2048 4095 2048 1M BIOS boot
/dev/sdb2 4096 2101247 2097152 1G Linux RAID
/dev/sdb3 2101248 3905976319 3903875072 1.8T Linux RAID
/dev/sdb4 3905976320 3907024895 1048576 512M Linux filesystem


Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: HGST HUS726020AL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 49F377C6-4627-4D05-BFED-37891E5E3D62

Device Start End Sectors Size Type
/dev/sdc1 2048 4095 2048 1M BIOS boot
/dev/sdc2 4096 2101247 2097152 1G Linux RAID
/dev/sdc3 2101248 3905976319 3903875072 1.8T Linux RAID
/dev/sdc4 3905976320 3907024895 1048576 512M Linux filesystem


Disk /dev/md127: 1.8 TiB, 1998648770560 bytes, 3903610880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


root@rescue-customer-eu (ns3056801.ip-188-165-234.eu) ~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 1G 0 part
├─sda3 8:3 0 1.8T 0 part
│ └─md127 9:127 0 1.8T 0 raid1 /mnt/root
├─sda4 8:4 0 512M 0 part
└─sda5 8:5 0 2M 0 part
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 1M 0 part
├─sdb2 8:18 0 1G 0 part
├─sdb3 8:19 0 1.8T 0 part
│ └─md127 9:127 0 1.8T 0 raid1 /mnt/root
└─sdb4 8:20 0 512M 0 part
sdc 8:32 0 1.8T 0 disk
├─sdc1 8:33 0 1M 0 part
├─sdc2 8:34 0 1G 0 part
├─sdc3 8:35 0 1.8T 0 part
│ └─md127 9:127 0 1.8T 0 raid1 /mnt/root
└─sdc4 8:36 0 512M 0 part

J’ai monté la partition et j’ai fait un chroot sur mon serveur pour essayer de redémarrer les services, mais j’ai pas l’impression de pouvoir faire grand chose (c’est peut-être normal en chroot ?).

mkdir /mnt/root
mount /dev/md127 /mnt/root
chroot /mnt/root

root@rescue-customer-eu:/# /etc/init.d/ssh status
* sshd is not running
root@rescue-customer-eu:/# /etc/init.d/ssh start
* Starting OpenBSD Secure Shell server sshd [ OK ]
root@rescue-customer-eu:/# /etc/init.d/ssh status
* sshd is not running
root@rescue-customer-eu:/# /etc/init.d/apache2 start
* Starting Apache httpd web server apache2 Invoking 'systemctl start apache2'.
Use 'systemctl status apache2' for more info.
Running in chroot, ignoring command 'start'
*
* The apache2 instance did not start within 20 seconds. Please read the log files to discover problems
root@rescue-customer-eu:/# systemctl status apache2
Running in chroot, ignoring command 'status'

Je sèche un peu et ne sais pas vraiment vers où chercher pour debugguer tout ça. Je ne suis pas assez calé en système et réseau.
Au niveau config, je ne pense pas avoir touché quoi-que-ce-soit depuis l’installation du serveur il y a plus d’un an. Idem pour le firewall, je ne me souviens pas avoir mis en place une config particulière. J’ai installé fail2ban à l’époque en suivant la procédure : https://help.ovhcloud.com/csm/fr-dedicated-servers-securing-server?id=kb_article_view&sysparm_article=KB0043978

Avez-vous une idée de ce qui peut bloquer le démarrage des services ?
Merci d’avance pour votre aide.
Positive Bewertungen (0)
619 Ansichten
10 Antworten ( Latest reply on 2024-05-28 08:56:02 Von
SAS-LS
)
J

Bonjour,

mais là vous êtes en rescue, pourquoi vouloir démarrer les services que si le serveur avait boot normalement ?

Cordialement, janus57
Hilfreich (0)


Depuis, plus aucun service ne démarre sur le serveur et tous les ports sont fermés.


Bonjour, est-ce que le serveur boote correctement sur disque cependant ? Avez-vous pu vérifier qu'il pingait ? Qu'indiquent les logs dans le chroot (`journalctl -S -1day` par exemple)?
Hilfreich (0)
S

Quand je boot sur le disque, le serveur ping mais c'est tout, je n'ai plus du tout d'accès SSH ou HTTP. Tous les ports semblent fermés.

Voici ce que je trouve dans les dernières lignes du journal (la date correspond au jour où j'ai lancé le reboot) :

May 17 10:06:52 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:06:52 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:06:52 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Sense Key : Medium Error [current]
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Add. Sense: Unrecovered read error - auto>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 10 10 18 08 00 00 08 >
May 17 10:06:52 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 269490186 op 0x0:(>
May 17 10:06:52 ns3056801 kernel: ata4: EH complete
May 17 10:06:52 ns3056801 kernel: md/raid1:md3: read error corrected (8 sectors at 267388936 on sdb>
May 17 10:06:52 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0
May 17 10:06:52 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:06:52 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:06:52 ns3056801 kernel: ata4.00: cmd 60/08:18:10:18:10/00:00:10:00:00/40 tag 3 ncq dma 40>
res 43/40:08:10:18:10/00:00:10:00:00/00 Emask 0x409 (med>
May 17 10:06:52 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:06:52 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:06:52 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#3 FAILED Result: hostbyte=DID_OK driverbyte>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#3 Sense Key : Medium Error [current]
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#3 Add. Sense: Unrecovered read error - auto>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#3 CDB: Read(10) 28 00 10 10 18 10 00 00 08 >
May 17 10:06:52 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 269490192 op 0x0:(>
May 17 10:06:52 ns3056801 kernel: ata4: EH complete
May 17 10:06:52 ns3056801 kernel: md/raid1:md3: read error corrected (8 sectors at 267388944 on sdb>
May 17 10:06:52 ns3056801 kernel: md/raid1:md3: redirecting sector 267124736 to other mirror: sda3
May 17 10:06:52 ns3056801 systemd[1]: systemd-journald.service: Main process exited, code=killed, s>
May 17 10:06:52 ns3056801 systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
May 17 10:06:52 ns3056801 systemd[1]: systemd-journald.service: Scheduled restart job, restart coun>
May 17 10:06:52 ns3056801 systemd[1]: Stopped Journal Service.
May 17 10:06:52 ns3056801 systemd[1]: Starting Journal Service...
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC892: line_ou>
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0>
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0>
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: dig-out=0x11/0x1e
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: inputs:
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
May 17 10:06:52 ns3056801 kernel: snd_hda_codec_hdmi hdaudioC0D3: No i915 binding for Intel HDMI/DP>
May 17 10:06:52 ns3056801 kernel: hdaudio hdaudioC0D3: Unable to configure, disabling
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.>
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0>
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sou>
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:0>
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/000>
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00>
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00>
May 17 10:06:52 ns3056801 kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:>
May 17 10:06:52 ns3056801 systemd[1]: Reached target Sound Card.
May 17 10:06:52 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0
May 17 10:06:52 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:06:52 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:06:52 ns3056801 kernel: ata4.00: cmd 60/08:80:68:18:a4/00:00:12:00:00/40 tag 16 ncq dma 4>
res 43/40:04:6c:18:a4/00:00:12:00:00/00 Emask 0x409 (med>
May 17 10:06:52 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:06:52 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:06:52 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_OK driverbyt>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 Sense Key : Medium Error [current]
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 Add. Sense: Unrecovered read error - aut>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 12 a4 18 68 00 00 08>
May 17 10:06:52 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 312744044 op 0x0:(>
May 17 10:06:52 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 310378600
May 17 10:06:52 ns3056801 kernel: ata4: EH complete
May 17 10:06:52 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0
May 17 10:06:52 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:06:52 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:06:52 ns3056801 kernel: ata4.00: cmd 60/08:48:68:18:a4/00:00:12:00:00/40 tag 9 ncq dma 40>
res 43/40:01:6f:18:a4/00:00:12:00:00/00 Emask 0x409 (med>
May 17 10:06:52 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:06:52 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:06:52 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#9 Sense Key : Medium Error [current]
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#9 Add. Sense: Unrecovered read error - auto>
May 17 10:06:52 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#9 CDB: Read(10) 28 00 12 a4 18 68 00 00 08 >
May 17 10:06:52 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 312744047 op 0x0:(>
May 17 10:06:52 ns3056801 kernel: ata4: EH complete
May 17 10:06:52 ns3056801 kernel: md/raid1:md3: read error corrected (8 sectors at 310642792 on sdb>
May 17 10:06:52 ns3056801 kernel: md/raid1:md3: redirecting sector 310378600 to other mirror: sda3
May 17 10:06:52 ns3056801 systemd-journald[882]: Journal started
May 17 10:06:52 ns3056801 systemd-journald[882]: System Journal (/var/log/journal/4b4ec17fed6c4dfe9>
May 17 10:05:41 ns3056801 audit[839]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[839]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[839]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[837]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[837]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[836]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[838]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[838]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[838]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[838]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[845]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[843]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[844]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:41 ns3056801 audit[844]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[866]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[863]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[863]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[867]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[869]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[868]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[870]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[871]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[873]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[872]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[874]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[876]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[875]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[877]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:42 ns3056801 audit[878]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:45 ns3056801 audit[865]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:45 ns3056801 audit[864]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:05:45 ns3056801 audit[864]: AVC apparmor="STATUS" operation="profile_load" profile="uncon>
May 17 10:03:43 ns3056801 systemd[1]: Starting Create System Users...
May 17 10:05:41 ns3056801 dbus-daemon[810]: [system] AppArmor D-Bus mediation is enabled
May 17 10:06:52 ns3056801 systemd[1]: Started Journal Service.
May 17 10:03:43 ns3056801 systemd[1]: Finished Create System Users.
May 17 10:06:52 ns3056801 multipathd[565]: --------start up--------
May 17 10:06:52 ns3056801 multipathd[565]: read /etc/multipath.conf
May 17 10:06:52 ns3056801 multipathd[565]: path checkers start up
May 17 10:03:43 ns3056801 systemd[1]: Starting Create Static Device Nodes in /dev...
May 17 10:03:43 ns3056801 systemd[1]: Finished Load/Save Random Seed.
May 17 10:03:43 ns3056801 systemd[1]: Condition check resulted in First Boot Complete being skipped.
May 17 10:03:43 ns3056801 systemd[1]: Finished Create Static Device Nodes in /dev.
May 17 10:03:43 ns3056801 systemd[1]: Starting Rule-based Manager for Device Events and Files...
May 17 10:03:43 ns3056801 systemd[1]: Started Device-Mapper Multipath Device Controller.
May 17 10:03:43 ns3056801 systemd[1]: Reached target Preparation for Local File Systems.
May 17 10:03:43 ns3056801 systemd[1]: Mounting Mount unit for core20, revision 2264...
May 17 10:03:43 ns3056801 systemd[1]: Mounting Mount unit for core20, revision 2318...
May 17 10:03:43 ns3056801 systemd[1]: Mounting Mount unit for lxd, revision 27948...
May 17 10:03:43 ns3056801 systemd[1]: Mounting Mount unit for lxd, revision 28373...
May 17 10:03:44 ns3056801 systemd[1]: Mounting Mount unit for snapd, revision 21184...
May 17 10:03:44 ns3056801 systemd[1]: Mounting Mount unit for snapd, revision 21465...
May 17 10:03:44 ns3056801 systemd[1]: Started Rule-based Manager for Device Events and Files.
May 17 10:03:44 ns3056801 systemd[1]: Mounted Mount unit for core20, revision 2264.
May 17 10:06:52 ns3056801 apparmor.systemd[809]: Restarting AppArmor
May 17 10:06:52 ns3056801 apparmor.systemd[809]: Reloading AppArmor profiles
May 17 10:03:44 ns3056801 systemd[1]: Mounted Mount unit for core20, revision 2318.
May 17 10:06:52 ns3056801 apparmor.systemd[847]: Skipping profile in /etc/apparmor.d/disable: usr.s>
May 17 10:06:52 ns3056801 dbus-daemon[810]: dbus[810]: Unknown group "power" in message bus configu>
May 17 10:03:44 ns3056801 systemd[1]: Mounted Mount unit for lxd, revision 27948.
May 17 10:03:44 ns3056801 systemd[1]: Mounted Mount unit for lxd, revision 28373.
May 17 10:03:44 ns3056801 systemd[1]: Mounted Mount unit for snapd, revision 21184.
May 17 10:03:44 ns3056801 systemd[1]: Condition check resulted in Show Plymouth Boot Screen being s>
May 17 10:03:44 ns3056801 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
May 17 10:03:44 ns3056801 systemd[1]: Condition check resulted in Forward Password Requests to Plym>
May 17 10:03:44 ns3056801 systemd[1]: Reached target Local Encrypted Volumes.
May 17 10:03:44 ns3056801 systemd[1]: Mounted Mount unit for snapd, revision 21465.
May 17 10:03:44 ns3056801 systemd[1]: Reached target Mounted snaps.
May 17 10:03:44 ns3056801 systemd-udevd[584]: Using default interface naming scheme 'v249'.
May 17 10:06:52 ns3056801 snapd-apparmor[848]: main.go:125: Loading profiles [/var/lib/snapd/apparm>
May 17 10:06:52 ns3056801 snapd-apparmor[848]: lib/snapd/apparmor/profiles/snap.lxd.benchmark /var/>
May 17 10:06:52 ns3056801 snapd-apparmor[848]: re /var/lib/snapd/apparmor/profiles/snap.lxd.hook.in>
May 17 10:06:52 ns3056801 snapd-apparmor[848]: d /var/lib/snapd/apparmor/profiles/snap.lxd.migrate >
May 17 10:03:44 ns3056801 systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watc>
May 17 10:03:44 ns3056801 systemd-udevd[606]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto->
May 17 10:03:45 ns3056801 systemd-udevd[600]: sdc: Process '/usr/bin/unshare -m /usr/bin/snap auto->
May 17 10:03:45 ns3056801 systemd-udevd[588]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:45 ns3056801 systemd-udevd[585]: sdc1: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:45 ns3056801 systemd-udevd[601]: sda5: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:45 ns3056801 systemd-udevd[598]: sda4: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:45 ns3056801 systemd[1]: Found device HGST_HUS724020AL swap-sda4.
May 17 10:03:45 ns3056801 systemd-udevd[608]: sdc4: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:45 ns3056801 systemd[1]: Activating swap /dev/disk/by-uuid/bfc3eb4c-788a-4c0c-9496-c56>
May 17 10:03:45 ns3056801 systemd[1]: Found device HGST_HUS726020AL swap-sdc4.
May 17 10:03:45 ns3056801 systemd[1]: Activating swap /dev/disk/by-uuid/0bb54647-84e9-4fa0-9120-9fc>
May 17 10:03:48 ns3056801 systemd-udevd[592]: sda3: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:48 ns3056801 systemd-udevd[595]: sdc2: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:48 ns3056801 systemd-udevd[599]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:03:48 ns3056801 systemd-udevd[606]: sdc3: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:04:10 ns3056801 systemd-udevd[593]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto->
May 17 10:04:13 ns3056801 systemd-udevd[593]: sdb3: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:04:32 ns3056801 systemd-udevd[599]: sdb2: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:04:44 ns3056801 systemd-udevd[584]: md3: Spawned process 'bcache-export-cached /dev/md3' >
May 17 10:04:44 ns3056801 systemd-udevd[607]: md2: Spawned process 'bcache-export-cached /dev/md2' >
May 17 10:04:44 ns3056801 systemd-udevd[577]: 0000:00:1b.0: Worker [590] processing SEQNUM=2902 is >
May 17 10:04:44 ns3056801 systemd-udevd[577]: md3: Worker [584] processing SEQNUM=3382 is taking a >
May 17 10:04:44 ns3056801 systemd-udevd[577]: md2: Worker [607] processing SEQNUM=3381 is taking a >
May 17 10:04:52 ns3056801 systemd-udevd[592]: sdb4: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:04:52 ns3056801 systemd[1]: Found device HGST_HUS726020AL swap-sdb4.
May 17 10:04:52 ns3056801 systemd[1]: Activating swap /dev/disk/by-uuid/19bb666f-cf4f-4e57-8bfa-6e2>
May 17 10:04:55 ns3056801 systemd-udevd[588]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto>
May 17 10:05:09 ns3056801 systemd[1]: dev-disk-by\x2duuid-a419d483\x2de74c\x2d4a3d\x2dbe1c\x2d643a3>
May 17 10:05:09 ns3056801 systemd[1]: Timed out waiting for device /dev/disk/by-uuid/a419d483-e74c->
May 17 10:05:09 ns3056801 systemd[1]: Dependency failed for /boot.
May 17 10:05:09 ns3056801 systemd[1]: Dependency failed for Unattended Upgrades Shutdown.
May 17 10:05:09 ns3056801 systemd[1]: unattended-upgrades.service: Job unattended-upgrades.service/>
May 17 10:05:09 ns3056801 systemd[1]: Dependency failed for Local File Systems.
May 17 10:05:09 ns3056801 systemd[1]: local-fs.target: Job local-fs.target/start failed with result>
May 17 10:05:09 ns3056801 systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
May 17 10:05:09 ns3056801 systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependen>
May 17 10:05:09 ns3056801 systemd[1]: dev-disk-by\x2duuid-a419d483\x2de74c\x2d4a3d\x2dbe1c\x2d643a3>
May 17 10:05:09 ns3056801 systemd[1]: systemd-ask-password-console.path: Deactivated successfully.
May 17 10:05:09 ns3056801 systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
May 17 10:05:09 ns3056801 systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
May 17 10:05:09 ns3056801 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
May 17 10:05:09 ns3056801 systemd[1]: Reached target Timer Units.
May 17 10:05:09 ns3056801 systemd[1]: Starting Set console font and keymap...
May 17 10:05:09 ns3056801 systemd[1]: Starting Create final runtime dir for shutdown pivot root...
May 17 10:05:09 ns3056801 systemd[1]: Reached target Login Prompts.
May 17 10:05:09 ns3056801 systemd[1]: syslog.socket: Deactivated successfully.
May 17 10:05:09 ns3056801 systemd[1]: Closed Syslog Socket.
May 17 10:05:09 ns3056801 systemd[1]: Reached target Preparation for Logins.
May 17 10:05:09 ns3056801 systemd[1]: Condition check resulted in Store a System Token in an EFI Va>
May 17 10:05:09 ns3056801 systemd[1]: Condition check resulted in Commit a transient machine-id on >
May 17 10:05:09 ns3056801 systemd[1]: Starting Set console scheme...
May 17 10:05:09 ns3056801 systemd[1]: Reached target Cloud-init target.
May 17 10:05:09 ns3056801 systemd[1]: Reached target Path Units.
May 17 10:05:09 ns3056801 systemd[1]: Reached target Socket Units.
May 17 10:05:09 ns3056801 systemd[1]: Listening on D-Bus System Message Bus Socket.
May 17 10:05:09 ns3056801 systemd[1]: Starting Load AppArmor profiles...
May 17 10:05:09 ns3056801 systemd[1]: Started D-Bus System Message Bus.
May 17 10:05:12 ns3056801 systemd[1]: Started Emergency Shell.
May 17 10:05:12 ns3056801 systemd[1]: Reached target Emergency Mode.
May 17 10:05:12 ns3056801 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
May 17 10:05:12 ns3056801 systemd[1]: Starting Set Up Additional Binary Formats...
May 17 10:05:12 ns3056801 systemd[1]: Starting Uncomplicated firewall...
May 17 10:05:12 ns3056801 systemd[1]: Activated swap /dev/disk/by-uuid/bfc3eb4c-788a-4c0c-9496-c564>
May 17 10:05:12 ns3056801 systemd[1]: Activated swap /dev/disk/by-uuid/0bb54647-84e9-4fa0-9120-9fc0>
May 17 10:05:12 ns3056801 systemd[1]: Finished Set console font and keymap.
May 17 10:05:12 ns3056801 systemd[1]: Finished Create final runtime dir for shutdown pivot root.
May 17 10:05:12 ns3056801 systemd[1]: Finished Set console scheme.
May 17 10:05:12 ns3056801 systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.
May 17 10:05:12 ns3056801 systemd[1]: Finished Uncomplicated firewall.
May 17 10:05:12 ns3056801 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for >
May 17 10:05:12 ns3056801 systemd[1]: Created slice Slice /system/getty.
May 17 10:05:12 ns3056801 systemd[1]: Mounting Arbitrary Executable File Formats File System...
May 17 10:05:12 ns3056801 systemd[1]: Mounted Arbitrary Executable File Formats File System.
May 17 10:05:12 ns3056801 systemd[1]: Finished Set Up Additional Binary Formats.
May 17 10:05:13 ns3056801 systemd[1]: systemd-journal-flush.service: start operation timed out. Ter>
May 17 10:05:13 ns3056801 systemd[1]: systemd-journal-flush.service: Main process exited, code=kill>
May 17 10:05:13 ns3056801 systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'.
May 17 10:05:13 ns3056801 systemd[1]: Failed to start Flush Journal to Persistent Storage.
May 17 10:05:13 ns3056801 systemd[1]: Starting Create Volatile Files and Directories...
May 17 10:05:23 ns3056801 systemd[1]: Activated swap /dev/disk/by-uuid/19bb666f-cf4f-4e57-8bfa-6e27>
May 17 10:05:23 ns3056801 systemd[1]: Reached target Swaps.
May 17 10:05:41 ns3056801 systemd-udevd[607]: md2: Process '/usr/bin/unshare -m /usr/bin/snap auto->
May 17 10:05:41 ns3056801 systemd-udevd[584]: md3: Process '/usr/bin/unshare -m /usr/bin/snap auto->
May 17 10:05:41 ns3056801 systemd[1]: Finished Create Volatile Files and Directories.
May 17 10:05:41 ns3056801 systemd[1]: Started MD array monitor.
May 17 10:05:41 ns3056801 systemd[1]: Starting Network Time Synchronization...
May 17 10:05:41 ns3056801 systemd[1]: Starting Record System Boot/Shutdown in UTMP...
May 17 10:05:41 ns3056801 systemd[1]: Finished Record System Boot/Shutdown in UTMP.
May 17 10:05:41 ns3056801 systemd[1]: Starting Record Runlevel Change in UTMP...
May 17 10:05:41 ns3056801 systemd-update-utmp[846]: Failed to get new runlevel, utmp update skipped.
May 17 10:05:41 ns3056801 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfull>
May 17 10:05:41 ns3056801 systemd[1]: Finished Record Runlevel Change in UTMP.
May 17 10:05:41 ns3056801 systemd[1]: Finished Load AppArmor profiles.
May 17 10:05:41 ns3056801 systemd[1]: Starting Load AppArmor profiles managed internally by snapd...
May 17 10:05:41 ns3056801 systemd[1]: Condition check resulted in Authentication service for virtua>
May 17 10:05:41 ns3056801 systemd[1]: Condition check resulted in Service for virtual machines host>
May 17 10:05:41 ns3056801 systemd[1]: Starting Initial cloud-init job (pre-networking)...
May 17 10:05:41 ns3056801 systemd[1]: Started Network Time Synchronization.
May 17 10:05:41 ns3056801 systemd[1]: Reached target System Time Set.
May 17 10:05:45 ns3056801 systemd[1]: Finished Load AppArmor profiles managed internally by snapd.
May 17 10:06:40 ns3056801 systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
May 17 10:06:40 ns3056801 systemd[1]: systemd-journald.service: Killing process 527 (systemd-journa>
May 17 10:06:53 ns3056801 cloud-init[894]: Cloud-init v. 23.1.2-0ubuntu0~22.04.1 running 'init-loca>
May 17 10:06:55 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0
May 17 10:06:55 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:06:55 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:06:55 ns3056801 kernel: ata4.00: cmd 60/80:a0:00:18:24/00:00:30:00:00/40 tag 20 ncq dma 6>
res 43/40:7f:01:18:24/00:00:30:00:00/00 Emask 0x409 (med>
May 17 10:06:55 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:06:55 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:06:55 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:06:55 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_OK driverbyt>
May 17 10:06:55 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#20 Sense Key : Medium Error [current]
May 17 10:06:55 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#20 Add. Sense: Unrecovered read error - aut>
May 17 10:06:55 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#20 CDB: Read(10) 28 00 30 24 18 00 00 00 80>
May 17 10:06:55 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 807671809 op 0x0:(>
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306368
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306376
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306384
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306392
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306400
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306408
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306416
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306424
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306432
May 17 10:06:55 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 805306440
May 17 10:06:55 ns3056801 kernel: ata4: EH complete
May 17 10:06:58 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x10004 SErr 0x0 action 0x0
May 17 10:06:58 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:06:58 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:06:58 ns3056801 kernel: ata4.00: cmd 60/08:80:00:18:24/00:00:30:00:00/40 tag 16 ncq dma 4>
res 43/40:08:00:18:24/00:00:30:00:00/00 Emask 0x409 (med>
May 17 10:06:58 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:06:58 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:06:58 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:06:58 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_OK driverbyt>
May 17 10:06:58 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 Sense Key : Medium Error [current]
May 17 10:06:58 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 Add. Sense: Unrecovered read error - aut>
May 17 10:06:58 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 30 24 18 00 00 00 08>
May 17 10:06:58 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 807671808 op 0x0:(>
May 17 10:06:58 ns3056801 kernel: ata4: EH complete
May 17 10:06:58 ns3056801 kernel: md/raid1:md3: read error corrected (8 sectors at 805570560 on sdb>
May 17 10:06:58 ns3056801 kernel: md/raid1:md3: redirecting sector 805306368 to other mirror: sda3
May 17 10:06:58 ns3056801 kernel: md/raid1:md3: redirecting sector 805306376 to other mirror: sda3
May 17 10:06:58 ns3056801 kernel: md/raid1:md3: redirecting sector 805306384 to other mirror: sda3
May 17 10:07:01 ns3056801 kernel: md/raid1:md3: redirecting sector 805306392 to other mirror: sda3
May 17 10:07:01 ns3056801 kernel: md/raid1:md3: redirecting sector 805306400 to other mirror: sda3
May 17 10:07:04 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x3800002 SErr 0x0 action 0x0
May 17 10:07:04 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:04 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:04 ns3056801 kernel: ata4.00: cmd 60/08:08:28:18:24/00:00:30:00:00/40 tag 1 ncq dma 40>
res 43/40:01:2f:18:24/00:00:30:00:00/00 Emask 0x409 (med>
May 17 10:07:04 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:04 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:04 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:04 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte>
May 17 10:07:04 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Sense Key : Medium Error [current]
May 17 10:07:04 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Add. Sense: Unrecovered read error - auto>
May 17 10:07:04 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 30 24 18 28 00 00 08 >
May 17 10:07:04 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 807671855 op 0x0:(>
May 17 10:07:04 ns3056801 kernel: ata4: EH complete
May 17 10:07:04 ns3056801 kernel: md/raid1:md3: read error corrected (8 sectors at 805570600 on sdb>
May 17 10:07:04 ns3056801 kernel: md/raid1:md3: redirecting sector 805306408 to other mirror: sda3
May 17 10:07:07 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x20000008 SErr 0x0 action 0x0
May 17 10:07:07 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:07 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:07 ns3056801 kernel: ata4.00: cmd 60/08:e8:08:10:00/00:00:00:00:00/40 tag 29 ncq dma 4>
res 43/40:08:08:10:00/00:00:00:00:00/00 Emask 0x409 (med>
May 17 10:07:07 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:07 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:07 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:07 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_OK driverbyt>
May 17 10:07:07 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#29 Sense Key : Medium Error [current]
May 17 10:07:07 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#29 Add. Sense: Unrecovered read error - aut>
May 17 10:07:07 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#29 CDB: Read(10) 28 00 00 00 10 08 00 00 08>
May 17 10:07:07 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 4104 op 0x0:(READ)>
May 17 10:07:07 ns3056801 kernel: ata4: EH complete
May 17 10:07:07 ns3056801 kernel: md/raid1:md3: redirecting sector 805306416 to other mirror: sda3
May 17 10:07:10 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x1000 SErr 0x0 action 0x0
May 17 10:07:10 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:10 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:10 ns3056801 kernel: ata4.00: cmd 60/08:60:08:10:00/00:00:00:00:00/40 tag 12 ncq dma 4>
res 43/40:08:08:10:00/00:00:00:00:00/00 Emask 0x409 (med>
May 17 10:07:10 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:10 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:10 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:10 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyt>
May 17 10:07:10 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#12 Sense Key : Medium Error [current]
May 17 10:07:10 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#12 Add. Sense: Unrecovered read error - aut>
May 17 10:07:10 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#12 CDB: Read(10) 28 00 00 00 10 08 00 00 08>
May 17 10:07:10 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 4104 op 0x0:(READ)>
May 17 10:07:10 ns3056801 kernel: Buffer I/O error on dev sdb2, logical block 1, async page read
May 17 10:07:10 ns3056801 kernel: ata4: EH complete
May 17 10:07:10 ns3056801 kernel: md/raid1:md3: redirecting sector 805306424 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306432 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306440 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306448 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306456 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306464 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306472 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306480 to other mirror: sda3
May 17 10:07:11 ns3056801 kernel: md/raid1:md3: redirecting sector 805306488 to other mirror: sda3
May 17 10:07:15 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x8707effe SErr 0x0 action 0x0
May 17 10:07:15 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:15 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:15 ns3056801 kernel: ata4.00: cmd 60/48:08:00:18:24/00:00:3c:00:00/40 tag 1 ncq dma 36>
res 43/40:25:23:18:24/00:00:3c:00:00/00 Emask 0x409 (med>
May 17 10:07:15 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:15 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:15 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:15 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte>
May 17 10:07:15 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Sense Key : Medium Error [current]
May 17 10:07:15 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Add. Sense: Unrecovered read error - auto>
May 17 10:07:15 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 3c 24 18 00 00 00 48 >
May 17 10:07:15 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 1008998435 op 0x0:>
May 17 10:07:15 ns3056801 kernel: raid1_end_read_request: 6 callbacks suppressed
May 17 10:07:15 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006632992
May 17 10:07:15 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006633000
May 17 10:07:15 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006633008
May 17 10:07:15 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006633016
May 17 10:07:15 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006633024
May 17 10:07:15 ns3056801 kernel: ata4: EH complete
May 17 10:07:18 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x7018800f SErr 0x0 action 0x0
May 17 10:07:18 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:18 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:18 ns3056801 kernel: ata4.00: cmd 60/20:78:60:18:24/00:00:3c:00:00/40 tag 15 ncq dma 1>
res 43/40:18:68:18:24/00:00:3c:00:00/00 Emask 0x409 (med>
May 17 10:07:18 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:18 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:18 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:18 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#15 FAILED Result: hostbyte=DID_OK driverbyt>
May 17 10:07:18 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#15 Sense Key : Medium Error [current]
May 17 10:07:18 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#15 Add. Sense: Unrecovered read error - aut>
May 17 10:07:18 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#15 CDB: Read(10) 28 00 3c 24 18 60 00 00 20>
May 17 10:07:18 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 1008998504 op 0x0:>
May 17 10:07:18 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006633064
May 17 10:07:18 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006633072
May 17 10:07:18 ns3056801 kernel: md/raid1:md3: sdb3: rescheduling sector 1006633080
May 17 10:07:18 ns3056801 kernel: ata4: EH complete
May 17 10:07:38 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x798002 SErr 0x0 action 0x0
May 17 10:07:38 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:38 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:38 ns3056801 kernel: ata4.00: cmd 60/08:08:08:10:00/00:00:00:00:00/40 tag 1 ncq dma 40>
res 43/40:08:08:10:00/00:00:00:00:00/00 Emask 0x409 (med>
May 17 10:07:38 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:38 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:38 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte>
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Sense Key : Medium Error [current]
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 Add. Sense: Unrecovered read error - auto>
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 00 00 10 08 00 00 08 >
May 17 10:07:38 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 4104 op 0x0:(READ)>
May 17 10:07:38 ns3056801 kernel: ata4: EH complete
May 17 10:07:38 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x0
May 17 10:07:38 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:38 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:38 ns3056801 kernel: ata4.00: cmd 60/08:28:08:10:00/00:00:00:00:00/40 tag 5 ncq dma 40>
res 43/40:08:08:10:00/00:00:00:00:00/00 Emask 0x409 (med>
May 17 10:07:38 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:38 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:38 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte>
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#5 Sense Key : Medium Error [current]
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#5 Add. Sense: Unrecovered read error - auto>
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 00 00 10 08 00 00 08 >
May 17 10:07:38 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 4104 op 0x0:(READ)>
May 17 10:07:38 ns3056801 kernel: Buffer I/O error on dev sdb2, logical block 1, async page read
May 17 10:07:38 ns3056801 kernel: ata4: EH complete
May 17 10:07:38 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x200000 SErr 0x0 action 0x0
May 17 10:07:38 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:38 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:38 ns3056801 kernel: ata4.00: cmd 60/08:a8:20:18:24/00:00:3c:00:00/40 tag 21 ncq dma 4>
res 43/40:05:23:18:24/00:00:3c:00:00/00 Emask 0x409 (med>
May 17 10:07:38 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:38 ns3056801 kernel: ata4.00: error: { UNC }
May 17 10:07:38 ns3056801 kernel: ata4.00: configured for UDMA/133
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_OK driverbyt>
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#21 Sense Key : Medium Error [current]
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#21 Add. Sense: Unrecovered read error - aut>
May 17 10:07:38 ns3056801 kernel: sd 3:0:0:0: [sdb] tag#21 CDB: Read(10) 28 00 3c 24 18 20 00 00 08>
May 17 10:07:38 ns3056801 kernel: blk_update_request: I/O error, dev sdb, sector 1008998435 op 0x0:>
May 17 10:07:38 ns3056801 kernel: ata4: EH complete
May 17 10:07:38 ns3056801 kernel: md/raid1:md3: read error corrected (8 sectors at 1006897184 on sd>
May 17 10:07:38 ns3056801 kernel: md/raid1:md3: redirecting sector 1006632992 to other mirror: sda3
May 17 10:07:38 ns3056801 kernel: md/raid1:md3: redirecting sector 1006633000 to other mirror: sda3
May 17 10:07:38 ns3056801 kernel: md/raid1:md3: redirecting sector 1006633008 to other mirror: sda3
May 17 10:07:38 ns3056801 kernel: md/raid1:md3: redirecting sector 1006633016 to other mirror: sda3
May 17 10:07:38 ns3056801 kernel: md/raid1:md3: redirecting sector 1006633024 to other mirror: sda3
May 17 10:07:38 ns3056801 kernel: ata4.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0
May 17 10:07:38 ns3056801 kernel: ata4.00: irq_stat 0x40000008
May 17 10:07:38 ns3056801 kernel: ata4.00: failed command: READ FPDMA QUEUED
May 17 10:07:38 ns3056801 kernel: ata4.00: cmd 60/08:90:68:18:24/00:00:3c:00:00/40 tag 18 ncq dma 4>
res 43/40:08:68:18:24/00:00:3c:00:00/00 Emask 0x409 (med>
May 17 10:07:38 ns3056801 kernel: ata4.00: status: { DRDY SENSE ERR }
May 17 10:07:38 ns3056801 kernel: ata4.00: error: { UNC }


Par contre je ne sais pas du tout quelles infos chercher là dedans.
Hilfreich (0)
J

Bonjour,

vous avez visiblement un disque qui est sur le point de mourir (sdb).

Avez-vous tester vos disques en rescue ?
Votre RAID était bien surveillé ?

Cordialement, janus57
Hilfreich (0)
S

Bonjour janus57,

Merci pour votre aide. Pour répondre à vos questions :

- Non je n'ai pas testé les disques, je ne sais pas quels outils ou commandes utiliser pour cela
- Je ne sais pas si la surveillance du raid est comprise dans l'offre Kimsufi, de mon côté je n'ai rien mis en place en ce sens. Le serveur est destiné à une utilisation très restreinte qui ne nécessite pas pas de contrôle quotidien. Je n'ai pas non plus les compétence pour faire tout ça.

Comment cela se passe pour un problème matériel, dois-je le signaler au support OVH ?
Hilfreich (0)
J

Bonjour,

Vous avez un guide OVH pour vous aider : https://help.ovhcloud.com/csm/fr-dedicated-servers-hardware-diagnostics?id=kb_article_view&sysparm_article=KB0043509


Je ne sais pas si la surveillance du raid est comprise dans l'offre Kimsufi

non tout ce qui est logiciel est à votre charge, y compris la surveillance de vos disques et l'état de votre RAID


Le serveur est destiné à une utilisation très restreinte qui ne nécessite pas pas de contrôle quotidien.

désolé, mais un serveur nécessite une surveillance quotidienne (qui généralement est semi-automatisée).


Je n'ai pas non plus les compétence pour faire tout ça.

Se pose peut-être la question de passer sur un mutualisé si c'est une chose possible.


Comment cela se passe pour un problème matériel, dois-je le signaler au support OVH ?

oui, puis le support va vous demander les preuves/logs de la panne ainsi que le numéro de série le cas échéant.

Cordialement, janus57
Hilfreich (0)
S

Merci janus57 pour vos réponses. Je vais regarder tout ça.
Dans l'idéal je préfère rester sur du mutualisé mais j'étais contraint de passer par un dédié pour ce type d'application (et pour le stockage nécessaire).
Hilfreich (0)
J

Bonjour,


j'étais contraint de passer par un dédié pour ce type d'application (et pour le stockage nécessaire).

quelles sont vos contraintes ?

Car si vous ne savez pas manager un serveur, cela a quand même une chance non négligeable de se finir en perte de données à un moment (surtout si vous n'avez pas de sauvegardes).

Cordialement, janus57
Hilfreich (0)

Bonjour @SAS-LS,

Si un des différents retours répond à votre demande, je vous invite à marquer ce dernier comme solution.

Dans le cas contraire, n’hésitez pas à ajouter des informations afin qu’une nouvelle réponse vous soit apportée par la communauté.

^FabL
Hilfreich (0)
S

Le problème venait en effet du disque défectueux.
Tout est rentré dans l'ordre suite au remplacement du disque.
Encore merci @janus57 pour l'aide apportée.
Hilfreich (0)
Antworten sind derzeit für diese Frage deaktiviert.

An Diskussion teilnehmen