We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

Serveur bloque sur ce message : /dev/sda2 is missing


sloomy
09/06/2016, 22h38
Bonsoir,

Non je n'ai pas ca, il faudrait savoir ce qu'il y avait le nom de ta partition /dev/sd2 , je suppose que ca devait être votre /home

Cdlt
Bruno

laurent_
09/06/2016, 19h57
L'essentiel est sauvegardé, mais je vais tenter une sauvegarde "system"complète en ligne pour une remise en route plus rapide.

Ensuite, avant reinstall je vais tenter de modifier le fstab : est-ce que t'aurais un modéle de fstab pour un disque sata et plusieurs partitions ?

Laurent

sloomy
09/06/2016, 19h29
Bonjour,

C'est surtout avoir un backup qui est important !
Après c'est bizarre que ton fstab n'est pas de partition /dev/sda1

Bruno

laurent_
09/06/2016, 18h01
oui pas mal de choses. et quelques configs spécifiques pour lesquels j'avais galéré (j'ai une copie de mon etc)
mais je crois de la distribution ispconfig n'est plus disponible, donc tout refaire à partir d'une débian
je dois tout avoir à la maison (galère en upload à remonter)
je viens de prendre un vps pour sauver en ligne au cas ou... mais je me prends la tête avec le rsync : il me dit que tout est bon, mais pas de fichier sur le vps.
Tout réinstaller est une option envisageable, mais c'est vraiment le dernier recours

sloomy
09/06/2016, 17h40
Bonjour,

Tu avais beaucoup de chose sur ton dédié ?
Tu as des sauvegardes au cas ou ?

Bruno

laurent_
09/06/2016, 17h32
Le hardware vérification depuis le site web rescue ?
Tests déjà lancés toutes les partitions du disque dur (clique sur le bouton de l'interface): No errors detected

nowwhat
09/06/2016, 17h12
Il est temps d'exécuter un hardware vérification, possible quand que t'es en mode rescue.

laurent_
09/06/2016, 12h25
Merci pour vos indications.

voici le /etc/fstab d'une de mes sauvegardes :
#
/dev/sda3 / ext4 errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jq fmt=vfsv0,relatime 0 1
/dev/sda3 /var ext4 defaults,relatime,usrjquota=aquota.user,grpjquota= aquota.group,jqfmt=vfsv0 1 2
/dev/sda4 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0

j'ai essayé fsck /dev/sda1
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768

j'ai essayé e2fsck -b 8193 /dev/sda1
-> même message d'erreur ...

nowwhat
09/06/2016, 11h35
Citation Envoyé par laurent_
......
cat /mnt/etc/fstab
#
/dev/sda3 / ext4 errors=remount-ro,usrjquota=aquota.user,grpjquot
a=aquota.group,jqfmt=vfsv0,relatime 0 1
/dev/sda3 /var ext4 defaults,relatime,usrjquota=aquota.user,grpjquot
a=aquota.group,jqfmt=vfsv0 1 2
/dev/sda4 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0
Ton OS ne va pas 'mounter' /dev/sda1 car il n'a pas l'instruction pour le faire.

Compare ton fichier 'fstab' avec une version de ton sauvegarde.

Il est probablement temps de lancer un 'fsck' sur ton /dev/sda1

sloomy
08/06/2016, 23h30
Bonsoir,

Et dans votre /etc/fstab il n'y a pas de mount pour /dev/sda1 ?

Cdlt
Bruno

laurent_
08/06/2016, 19h34
Pas de raid : un SATA 3
En mode recue je peux monter sda2 et sda3, je peux chrooter (les données sont bien la) , mais je ne peux pas monter sda1

sloomy
08/06/2016, 19h24
Bonjour,

Ton KS n'a pas de Raid, je dis pas de connerie ?

En rescue tu montes la partition ou pas ?

Cdlt
Bruno

laurent_
08/06/2016, 18h41
fin de cat /mnt/var/log/dmesg

EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
devtmpfs: mounted

laurent_
08/06/2016, 18h41
mount /dev/sda1 /mnt/
mount: /dev/sda1 is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

/dev/sda2 /mnt/
/dev/sda3 /mnt/var/
cat /mnt/etc/fstab
#
/dev/sda3 / ext4 errors=remount-ro,usrjquota=aquota.user,grpjquot
a=aquota.group,jqfmt=vfsv0,relatime 0 1
/dev/sda3 /var ext4 defaults,relatime,usrjquota=aquota.user,grpjquot
a=aquota.group,jqfmt=vfsv0 1 2
/dev/sda4 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0

laurent_
08/06/2016, 18h39
fdisk -l

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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
Disklabel type: gpt
Disk identifier: 5BBFF3BA-0588-4E09-A8DB-096778511F23

Device Start End Sectors Size Type
/dev/sda1 40 2048 2009 1004.5K BIOS boot
/dev/sda2 4096 40962047 40957952 19.5G Linux filesystem
/dev/sda3 40962048 3905974271 3865012224 1.8T Linux filesystem
/dev/sda4 3905974272 3907020799 1046528 511M Linux swap

laurent_
08/06/2016, 18h38
Je viens encore d'essayer de vous envoyer le compte rendu des manipulations, mais j'ai eu le même résultat que ce matin :

laurent_
Thank you for posting! Your post will not be visible until a moderator has approved it for posting.

alors réponse minimale :
OS : ISPconfig 3.0.5.4 (Debian 7) (64bits)
ping : ok
ssh, ftp, pop, http : rien

laurent_
08/06/2016, 18h35
sloom, nowwhat :
sans formatage, voici une partie des infos demandées :

OS : ISPconfig 3.0.5.4 (Debian 7) (64bits)
ping : ok
ssh, ftp, pop, http : rien


root@rescue:~/.deb# fdisk -l

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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
Disklabel type: gpt
Disk identifier: 5BBFF3BA-0588-4E09-A8DB-096778511F23

Device Start End Sectors Size Type
/dev/sda1 40 2048 2009 1004.5K BIOS boot
/dev/sda2 4096 40962047 40957952 19.5G Linux filesystem
/dev/sda3 40962048 3905974271 3865012224 1.8T Linux filesystem
/dev/sda4 3905974272 3907020799 1046528 511M Linux swap

root@rescue:~/.deb# mount /dev/sda1 /mnt/
mount: /dev/sda1 is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
root@rescue:~/.deb# mount /dev/sda2 /mnt/
root@rescue:~/.deb# mount /dev/sda3 /mnt/var/
root@rescue:~/.deb# cat /mnt/etc/fstab
#
/dev/sda3 / ext4 errors=remount-ro,usrjquota=aquota.user,grpjquot
a=aquota.group,jqfmt=vfsv0,relatime 0 1
/dev/sda3 /var ext4 defaults,relatime,usrjquota=aquota.user,grpjquot
a=aquota.group,jqfmt=vfsv0 1 2
/dev/sda4 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0

fin de cat /mnt/var/log/dmesg

EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
devtmpfs: mounted
Freeing unused kernel memory: 964K (ffffffff823b8000 - ffffffff824a9000)
udevd[257]: starting version 175
random: nonblocking pool is initialized
Adding 523260k swap on /dev/sda4. Priority:-1 extents:1 across:523260k
EXT4-fs (sda2): re-mounted. Opts: (null)
EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jq fmt=vfsv0
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt =vfsv0
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
8021q: adding VLAN 0 to HW filter on device eth0
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

merci pour votre aide, désolé pour cette reréponse tardive

laurent_
08/06/2016, 18h10
Bonjour j'ai envoyé 2 réponses ce matin à sloomy et nowhat (avec un message m'indiquant qu'il devaient être modérés avant publication)
, est il normal qu'ils ne soient toujours pas visibles ?

peux on utiliser les balises code dans les messages ?

laurent_
08/06/2016, 11h39
Bonjour Nowwhat

Code:
root@rescue:~# fdisk -l 

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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
Disklabel type: gpt
Disk identifier: 5BBFF3BA-0588-4E09-A8DB-096778511F23

Device          Start        End    Sectors    Size Type
/dev/sda1          40       2048       2009 1004.5K BIOS boot
/dev/sda2        4096   40962047   40957952   19.5G Linux filesystem
/dev/sda3    40962048 3905974271 3865012224    1.8T Linux filesystem
/dev/sda4  3905974272 3907020799    1046528    511M Linux swap
Code:
root@rescue:~# mount /dev/sda1 /mnt/
mount: /dev/sda1 is write-protected, mounting read-only
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
root@rescue:~# mount /dev/sda2 /mnt/
root@rescue:~# mount /dev/sda3 /mnt/var
root@rescue:~# cat /mnt/etc/fstab 
#                
/dev/sda3       /       ext4    errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,relatime     0     1
/dev/sda3       /var    ext4    defaults,relatime,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0      1       2
/dev/sda4       swap    swap    defaults        0       0
proc            /proc   proc    defaults                0       0
sysfs           /sys    sysfs   defaults                0       0
tmpfs           /dev/shm        tmpfs   defaults        0       0
devpts          /dev/pts        devpts  defaults        0       0
/var/log/ispconfig/httpd/courriels.innode.fr /var/www/clients/client0/web5/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/verinov.fr /var/www/clients/client0/web6/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/test.innode.fr /var/www/clients/client0/web8/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/test2.innode.fr /var/www/clients/client0/web9/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/j.innode.fr /var/www/clients/client0/web12/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/jet.innode.fr /var/www/clients/client0/web13/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/cdl.verinov.fr /var/www/clients/client1/web14/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/comptoirdesliquoristes.com /var/www/clients/client1/web15/log    none    bind,nobootwait    0 0
/var/log/ispconfig/httpd/media.sgdc-marketing.com /var/www/clients/client1/web16/log    none    bind,nobootwait    0 0
/var/log/ispconfig/httpd/vieuxbenoit.com /var/www/clients/client0/web17/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/media.verinov.fr /var/www/clients/client0/web18/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/courriel2.innode.fr /var/www/clients/client0/web19/log    none    bind,nobootwait,_netdev    0 0
/var/log/ispconfig/httpd/mntdb.innode.fr /var/www/clients/client0/web20/log    none    bind,nobootwait,_netdev    0 0
Code:
cat /mnt/var/log/dmesg

EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
devtmpfs: mounted
Freeing unused kernel memory: 964K (ffffffff823b8000 - ffffffff824a9000)
udevd[257]: starting version 175
random: nonblocking pool is initialized
Adding 523260k swap on /dev/sda4.  Priority:-1 extents:1 across:523260k 
EXT4-fs (sda2): re-mounted. Opts: (null)
EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0
EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
8021q: adding VLAN 0 to HW filter on device eth0
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
e1000e 0000:01:00.0 eth0: 10/100 speed: disabling TSO
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Je suis indisponible jusqu'à 11h45, je répond à vos questions dès que possible
Merci beaucoup pour votre aide

Laurent

nowwhat
08/06/2016, 11h15
Citation Envoyé par laurent_
....
Après redémarrage normal sur le disque -> problème au démarrage -> diagnostique kimsufi ->" Serveur bloque sur ce message : /dev/sda2 is missing" Alors que /dev/sda2 est bien présent en mode rescue ...???
Montre-nous le résultat de
fdisk -l
après la connection SSH quand le serveur est en mode rescue.

Si l'OS n'arrive pas à "mount" le sda2, va voir (montre nous) le fichier :
/mnt/etc/fstab
Pour ça, il faut d'abord 'mount' tes disques (sda1 et sda2) dans /mnt/, puis:
cat /mnt/etc/fstab
Citation Envoyé par laurent_
....
Je ne comprend pas le rapport en mes opérations sur postresql et le rplantage du serveur. ni tout simplement ce qui s'est passé.
C'est un simple coïncidence.

Citation Envoyé par laurent_
....
Est-ce quelqu'un a une idée de ce qui s'est passé ? avez vous besoin d'élément de diagnostiques, avec vous une piste pour sortir de cette situation ?
Piste :
va en mode rescue.
mount tes partitions.
Va voir la fin de ce fichier log :
/mnt/var/log/dmsg


Chez moi, j'ai (j'ai des disques raid, donc pas de sda etc, mais des mdx):
[ 13.647948] md3: detected capacity change from 0 to 1947428913152
[ 13.759099] EXT4-fs (md2): mounted filesystem with ordered data mode. Opts: (null)
[ 15.858816] EXT4-fs (md2): re-mounted. Opts: (null)
[ 16.021254] EXT4-fs (md2): re-mounted. Opts: errors=remount-ro
[ 18.607741] EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: (null)
ce qui me montre qu'au dernière démarrage de l'OS (MOn OS, pas lui du mode rescue !! ) les disques sont correctement mount par l'OS (suivant les instructions dans /mnt/etc/fstab)

laurent_
08/06/2016, 11h15
Bonjour Bruno,
Merci pour ta réponse

ISPconfig 3.0.5.4 (Debian 7) (64bits)
ping : ok
ssh, http, ftp, pop, smtp : non

fin du sys.log :
Code:
Jun  7 23:35:04 rescue systemd[1]: Started Login Service.
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Start/stop sysstat's sadc...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: disk temperature monitoring daemon...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Machine Check Exceptions (MCE) collector & decoder...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Load kernel modules needed to enable cpufreq scaling...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Start and stop ipmidetectd...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Check mpt-status values in the background....
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Start and stop bmc-watchdog...
Jun  7 23:35:04 rescue systemd[1]: Starting System Logging Service...
Jun  7 23:35:04 rescue systemd[1]: Starting Permit User Sessions...
Jun  7 23:35:04 rescue systemd[1]: Started Network Name Resolution.
Jun  7 23:35:04 rescue systemd[1]: Started Provide limited super user privileges to specific users.
Jun  7 23:35:04 rescue systemd[1]: ipmievd.service: control process exited, code=exited status=1
Jun  7 23:35:04 rescue systemd[1]: Failed to start IPMI event daemon.
Jun  7 23:35:04 rescue systemd[1]: Unit ipmievd.service entered failed state.
Jun  7 23:35:04 rescue systemd[1]: Started vsftpd FTP server.
Jun  7 23:35:04 rescue cron[722]: (CRON) INFO (Running @reboot jobs)
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Start/stop sysstat's sadc.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: disk temperature monitoring daemon.
Jun  7 23:35:04 rescue systemd[1]: Started Permit User Sessions.
Jun  7 23:35:04 rescue loadcpufreq[735]: Loading cpufreq kernel modules...done (none).
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Load kernel modules needed to enable cpufreq scaling.
Jun  7 23:35:04 rescue sensors[771]: coretemp-isa-0000
Jun  7 23:35:04 rescue sensors[771]: Adapter: ISA adapter
Jun  7 23:35:04 rescue sensors[771]: Core 0:       +39.0°C  (crit = +100.0°C)
Jun  7 23:35:04 rescue sensors[771]: Core 1:       +34.0°C  (crit = +100.0°C)
Jun  7 23:35:04 rescue sensors[771]: w83627dhg-isa-0290
Jun  7 23:35:04 rescue sensors[771]: Adapter: ISA adapter
Jun  7 23:35:04 rescue sensors[771]: Vcore:        +1.11 V  (min =  +0.00 V, max =  +1.74 V)
Jun  7 23:35:04 rescue sensors[771]: in1:          +1.01 V  (min =  +1.15 V, max =  +1.92 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: AVCC:         +3.36 V  (min =  +2.98 V, max =  +3.63 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: +3.3V:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
Jun  7 23:35:04 rescue sensors[771]: in4:          +1.02 V  (min =  +0.91 V, max =  +0.69 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: in5:          +1.50 V  (min =  +1.63 V, max =  +1.20 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: in6:          +1.08 V  (min =  +0.06 V, max =  +0.97 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: 3VSB:         +3.38 V  (min =  +2.98 V, max =  +3.63 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: Vbat:         +3.25 V  (min =  +2.70 V, max =  +3.63 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan1:           0 RPM  (min =  167 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan2:           0 RPM  (min = 7031 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan3:           0 RPM  (min =  310 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan4:           0 RPM  (min = 1240 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan5:           0 RPM  (min =  413 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: temp1:        +31.0°C  (high = +96.0°C, hyst = +34.0°C)  sensor = CPU diode
Jun  7 23:35:04 rescue sensors[771]: temp2:       +110.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor = CPU diode
Jun  7 23:35:04 rescue sensors[771]: temp3:        +32.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
Jun  7 23:35:04 rescue sensors[771]: cpu0_vid:    +0.000 V
Jun  7 23:35:04 rescue sensors[771]: intrusion0:  ALARM
Jun  7 23:35:04 rescue systemd[1]: Started Initialize hardware monitoring sensors.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Start and stop ipmidetectd.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Start and stop bmc-watchdog.
Jun  7 23:35:04 rescue smartd[720]: smartd 6.4 2014-10-07 r4002 [x86_64-linux-3.14.32-xxxx-std-ipv6-64-rescue] (local build)
Jun  7 23:35:04 rescue smartd[720]: Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
Jun  7 23:35:04 rescue smartd[720]: Opened configuration file /etc/smartd.conf
Jun  7 23:35:04 rescue mcelog[734]: mcelog: Family 6 Model 36 CPU: only decoding architectural errors
Jun  7 23:35:04 rescue ipmidetectd[742]: ipmidetectd disabled, please adjust the configuration to your needs and then set RUN to 'yes' in /etc/default/ipmidetectd to enable it. ... failed!
Jun  7 23:35:04 rescue bmc-watchdog[747]: bmc-watchdog disabled, please adjust the configuration to your needs and then set RUN to 'yes' in /etc/default/bmc-watchdog to enable it. ... failed!
Jun  7 23:35:04 rescue smartd[720]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Jun  7 23:35:04 rescue smartd[720]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jun  7 23:35:04 rescue mcelog: Family 6 Model 36 CPU: only decoding architectural errors
Jun  7 23:35:04 rescue systemd[1]: Started /etc/rc.local Compatibility.
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda [SAT], opened
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda [SAT], HGST HUS724020ALA640, S/N:PN1134P6K4V87W, WWN:5-000cca-22dec7a98, FW:MF6OAA70, 2.00 TB
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: set CPUFreq kernel parameters...
Jun  7 23:35:04 rescue mcelog[734]: Starting Machine Check Exceptions decoder: mcelog.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting do_it_for_me caller...
Jun  7 23:35:04 rescue systemd[1]: Started do_it_for_me caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda [SAT], not found in smartd database.
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Machine Check Exceptions (MCE) collector & decoder.
Jun  7 23:35:04 rescue systemd[1]: Started getty on tty2-tty6 if dbus and logind are not available.
Jun  7 23:35:04 rescue systemd[1]: Starting Login Prompts.
Jun  7 23:35:04 rescue systemd[1]: Reached target Login Prompts.
Jun  7 23:35:04 rescue systemd[1]: Started System Logging Service.
Jun  7 23:35:04 rescue mpt-statusd[746]: Starting mpt-status monitor: mpt-statusd.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Check mpt-status values in the background..
Jun  7 23:35:04 rescue rsyslogd-2007: action 'action 17' suspended, next retry is Tue Jun  7 23:35:34 2016 [try http://www.rsyslog.com/e/2007 ]
Jun  7 23:35:04 rescue cpufrequtils[788]: CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...CPU2...CPU3...done.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: set CPUFreq kernel parameters.
Jun  7 23:35:04 rescue mpt-statusd: detected non-optimal RAID status
Jun  7 23:35:05 rescue smartd[720]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Jun  7 23:35:05 rescue smartd[720]: Monitoring 1 ATA and 0 SCSI devices
Jun  7 23:35:06 rescue smartd[720]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.HGST_HUS724020ALA640-PN1134P6K4V87W.ata.state
Jun  7 23:35:09 rescue ntpdate[642]: adjust time server 213.251.128.249 offset -0.092484 sec
Jun  7 23:35:10 rescue systemd[1]: Started OpenBSD Secure Shell server.
Jun  7 23:35:10 rescue systemd[1]: Starting Multi-User System.
Jun  7 23:35:10 rescue systemd[1]: Reached target Multi-User System.
Jun  7 23:35:10 rescue systemd[1]: Starting Graphical Interface.
Jun  7 23:35:10 rescue systemd[1]: Reached target Graphical Interface.
Jun  7 23:35:10 rescue systemd[1]: Starting Stop Read-Ahead Data Collection 10s After Completed Startup.
Jun  7 23:35:10 rescue systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup.
Jun  7 23:35:10 rescue systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jun  7 23:35:10 rescue systemd[1]: Started Update UTMP about System Runlevel Changes.
Jun  7 23:35:10 rescue systemd[1]: Startup finished in 8.582s (kernel) + 16.183s (userspace) = 24.766s.
Jun  7 23:35:10 rescue systemd[1]: Reloading OpenBSD Secure Shell server.
Jun  7 23:35:10 rescue systemd[1]: Reloaded OpenBSD Secure Shell server.
Jun  7 23:35:18 rescue systemd[1]: Starting LSB: Apache2 web server...
Jun  7 23:35:19 rescue apache2[1006]: Starting web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using rescue.ovh.net. Set the 'ServerName' directive globally to suppress this message
Jun  7 23:35:20 rescue apache2[1006]: .
Jun  7 23:35:20 rescue systemd[1]: Started LSB: Apache2 web server.
Jun  7 23:35:32 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 64s/+0.010s/0.006s/0.004s/+80ppm
Jun  7 23:35:40 rescue systemd[1]: Starting Stop Read-Ahead Data Collection...
Jun  7 23:35:40 rescue systemd[1]: Started Stop Read-Ahead Data Collection.
Jun  7 23:36:36 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 128s/+0.027s/0.006s/0.011s/+183ppm
Jun  7 23:38:45 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 256s/-0.014s/0.006s/0.014s/+155ppm
Jun  7 23:43:01 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 512s/-0.043s/0.006s/0.024s/+113ppm
Jun  7 23:45:01 rescue CRON[1684]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  7 23:45:04 rescue mpt-statusd: detected non-optimal RAID status
Jun  7 23:49:49 rescue systemd[1]: Starting Cleanup of Temporary Directories...
Jun  7 23:49:49 rescue systemd[1]: Started Cleanup of Temporary Directories.
Jun  7 23:51:33 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 512s/-0.064s/0.006s/0.064s/+51ppm
Jun  7 23:53:33 rescue kernel: EXT4-fs (sda2): recovery complete
Jun  7 23:53:33 rescue kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Jun  7 23:53:59 rescue kernel: EXT4-fs (sda3): recovery complete
Jun  7 23:53:59 rescue kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Jun  7 23:55:01 rescue CRON[1952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  7 23:55:04 rescue mpt-statusd: detected non-optimal RAID status
Jun  7 23:59:01 rescue CRON[1988]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 60 2)
Jun  8 00:00:05 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 1024s/-0.031s/0.009s/0.061s/+35ppm
Jun  8 00:05:02 rescue CRON[2022]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:05:05 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:05:06 rescue smartd[720]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 200 to 206
Jun  8 00:15:01 rescue CRON[2077]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:15:05 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:17:01 rescue CRON[2098]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 00:17:10 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.049s/0.006s/0.056s/+24ppm
Jun  8 00:25:01 rescue CRON[2135]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:25:05 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:35:02 rescue CRON[2188]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:35:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:35:06 rescue smartd[720]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 206 to 200
Jun  8 00:45:01 rescue CRON[2241]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:45:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:51:18 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.070s/0.006s/0.051s/+7ppm
Jun  8 00:55:01 rescue CRON[2294]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:55:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:05:01 rescue CRON[2347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:05:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:05:06 rescue smartd[720]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 200 to 206
Jun  8 01:10:51 rescue kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Jun  8 01:15:02 rescue CRON[2404]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:15:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:17:01 rescue CRON[2430]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 01:25:01 rescue CRON[2474]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:25:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:25:26 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.034s/0.006s/0.031s/-1ppm
Jun  8 01:35:01 rescue CRON[2540]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:35:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:45:01 rescue CRON[2598]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:45:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:55:01 rescue CRON[2651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:55:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:59:34 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.016s/0.006s/0.021s/-5ppm
Jun  8 02:05:01 rescue CRON[2704]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:05:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:15:01 rescue CRON[2759]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:15:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:17:01 rescue CRON[2780]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 02:25:01 rescue CRON[2816]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:25:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:33:43 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.008s/0.006s/0.022s/-8ppm
Jun  8 02:35:01 rescue CRON[2870]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:35:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:45:01 rescue CRON[2923]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:45:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:55:01 rescue CRON[2982]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:55:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:05:01 rescue CRON[3039]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:05:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:07:51 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.002s/0.006s/0.025s/-8ppm
Jun  8 03:15:01 rescue CRON[3094]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:15:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:17:01 rescue CRON[3115]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 03:25:01 rescue CRON[3151]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:25:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:35:01 rescue CRON[3204]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:35:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:41:59 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.006s/0.026s/-8ppm
Jun  8 03:45:01 rescue CRON[3264]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:45:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:55:01 rescue CRON[3317]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:55:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:05:01 rescue CRON[3370]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:05:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:15:01 rescue CRON[3423]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:15:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:16:07 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.006s/0.029s/-9ppm
Jun  8 04:17:01 rescue CRON[3444]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 04:25:01 rescue CRON[3479]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:25:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:35:01 rescue CRON[3534]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:35:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:45:01 rescue CRON[3587]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:45:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:50:16 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.006s/0.031s/-9ppm
Jun  8 04:55:01 rescue CRON[3642]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:55:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:05:01 rescue CRON[3695]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:05:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:15:02 rescue CRON[3748]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:15:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:17:01 rescue CRON[3769]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 05:24:24 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.031s/-9ppm
Jun  8 05:25:01 rescue CRON[3804]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:25:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:35:01 rescue CRON[3857]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:35:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:45:01 rescue CRON[3915]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:45:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:55:01 rescue CRON[3970]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:55:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:58:32 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.006s/-9ppm
Jun  8 06:05:01 rescue CRON[4025]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:05:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:15:01 rescue CRON[4080]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:15:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:17:01 rescue CRON[4102]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 06:25:01 rescue CRON[4138]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jun  8 06:25:01 rescue CRON[4139]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:25:13 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:32:40 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.003s/-9ppm
Jun  8 06:35:01 rescue CRON[4320]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:35:13 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:45:01 rescue CRON[4373]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:45:13 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:55:01 rescue CRON[4426]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:55:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:05:01 rescue CRON[4479]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:05:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:06:49 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.001s/-9ppm
Jun  8 07:15:01 rescue CRON[4534]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:15:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:17:01 rescue CRON[4555]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 07:25:02 rescue CRON[4590]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:25:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:35:01 rescue CRON[4643]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:35:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:36:26 rescue kernel: ip_set: protocol 6
Jun  8 07:41:29 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.001s/0.006s/0.001s/-9ppm
Jun  8 07:45:01 rescue CRON[4705]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:45:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:55:01 rescue CRON[4758]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:55:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:05:01 rescue CRON[4813]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:05:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:15:02 rescue CRON[4867]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:15:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:15:37 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.001s/-9ppm
Jun  8 08:17:01 rescue CRON[4888]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 08:25:01 rescue CRON[4923]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:25:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:35:01 rescue CRON[4979]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:35:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:45:01 rescue CRON[5034]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:45:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:49:46 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.001s/-9ppm
Jun  8 08:55:01 rescue CRON[5087]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:55:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:05:01 rescue CRON[5142]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:05:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:15:01 rescue CRON[5195]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:15:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:17:01 rescue CRON[5216]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 09:23:54 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.000s/-9ppm
Jun  8 09:25:01 rescue CRON[5251]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:25:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:35:01 rescue CRON[5305]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:35:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:45:02 rescue CRON[5365]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:45:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:55:01 rescue CRON[5419]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:55:17 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:58:34 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.000s/-9ppm

Je fais le test sans postgre
Quels autres log veux-tu ?

laurent_
08/06/2016, 11h13
Bonjour Bruno,
Merci pour ta réponse

ISPconfig 3.0.5.4 (Debian 7) (64bits)
ping : ok
ssh, http, ftp, pop, smtp : non

la fin du sys.log :
Code:
Jun  7 23:35:04 rescue systemd[1]: Started Login Service.
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Start/stop sysstat's sadc...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: disk temperature monitoring daemon...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Machine Check Exceptions (MCE) collector & decoder...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Load kernel modules needed to enable cpufreq scaling...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Start and stop ipmidetectd...
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Check mpt-status values in the background....
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: Start and stop bmc-watchdog...
Jun  7 23:35:04 rescue systemd[1]: Starting System Logging Service...
Jun  7 23:35:04 rescue systemd[1]: Starting Permit User Sessions...
Jun  7 23:35:04 rescue systemd[1]: Started Network Name Resolution.
Jun  7 23:35:04 rescue systemd[1]: Started Provide limited super user privileges to specific users.
Jun  7 23:35:04 rescue systemd[1]: ipmievd.service: control process exited, code=exited status=1
Jun  7 23:35:04 rescue systemd[1]: Failed to start IPMI event daemon.
Jun  7 23:35:04 rescue systemd[1]: Unit ipmievd.service entered failed state.
Jun  7 23:35:04 rescue systemd[1]: Started vsftpd FTP server.
Jun  7 23:35:04 rescue cron[722]: (CRON) INFO (Running @reboot jobs)
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Start/stop sysstat's sadc.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: disk temperature monitoring daemon.
Jun  7 23:35:04 rescue systemd[1]: Started Permit User Sessions.
Jun  7 23:35:04 rescue loadcpufreq[735]: Loading cpufreq kernel modules...done (none).
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Load kernel modules needed to enable cpufreq scaling.
Jun  7 23:35:04 rescue sensors[771]: coretemp-isa-0000
Jun  7 23:35:04 rescue sensors[771]: Adapter: ISA adapter
Jun  7 23:35:04 rescue sensors[771]: Core 0:       +39.0°C  (crit = +100.0°C)
Jun  7 23:35:04 rescue sensors[771]: Core 1:       +34.0°C  (crit = +100.0°C)
Jun  7 23:35:04 rescue sensors[771]: w83627dhg-isa-0290
Jun  7 23:35:04 rescue sensors[771]: Adapter: ISA adapter
Jun  7 23:35:04 rescue sensors[771]: Vcore:        +1.11 V  (min =  +0.00 V, max =  +1.74 V)
Jun  7 23:35:04 rescue sensors[771]: in1:          +1.01 V  (min =  +1.15 V, max =  +1.92 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: AVCC:         +3.36 V  (min =  +2.98 V, max =  +3.63 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: +3.3V:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
Jun  7 23:35:04 rescue sensors[771]: in4:          +1.02 V  (min =  +0.91 V, max =  +0.69 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: in5:          +1.50 V  (min =  +1.63 V, max =  +1.20 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: in6:          +1.08 V  (min =  +0.06 V, max =  +0.97 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: 3VSB:         +3.38 V  (min =  +2.98 V, max =  +3.63 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: Vbat:         +3.25 V  (min =  +2.70 V, max =  +3.63 V)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan1:           0 RPM  (min =  167 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan2:           0 RPM  (min = 7031 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan3:           0 RPM  (min =  310 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan4:           0 RPM  (min = 1240 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: fan5:           0 RPM  (min =  413 RPM, div = 64)  ALARM
Jun  7 23:35:04 rescue sensors[771]: temp1:        +31.0°C  (high = +96.0°C, hyst = +34.0°C)  sensor = CPU diode
Jun  7 23:35:04 rescue sensors[771]: temp2:       +110.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor = CPU diode
Jun  7 23:35:04 rescue sensors[771]: temp3:        +32.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
Jun  7 23:35:04 rescue sensors[771]: cpu0_vid:    +0.000 V
Jun  7 23:35:04 rescue sensors[771]: intrusion0:  ALARM
Jun  7 23:35:04 rescue systemd[1]: Started Initialize hardware monitoring sensors.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Start and stop ipmidetectd.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Start and stop bmc-watchdog.
Jun  7 23:35:04 rescue smartd[720]: smartd 6.4 2014-10-07 r4002 [x86_64-linux-3.14.32-xxxx-std-ipv6-64-rescue] (local build)
Jun  7 23:35:04 rescue smartd[720]: Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
Jun  7 23:35:04 rescue smartd[720]: Opened configuration file /etc/smartd.conf
Jun  7 23:35:04 rescue mcelog[734]: mcelog: Family 6 Model 36 CPU: only decoding architectural errors
Jun  7 23:35:04 rescue ipmidetectd[742]: ipmidetectd disabled, please adjust the configuration to your needs and then set RUN to 'yes' in /etc/default/ipmidetectd to enable it. ... failed!
Jun  7 23:35:04 rescue bmc-watchdog[747]: bmc-watchdog disabled, please adjust the configuration to your needs and then set RUN to 'yes' in /etc/default/bmc-watchdog to enable it. ... failed!
Jun  7 23:35:04 rescue smartd[720]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Jun  7 23:35:04 rescue smartd[720]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jun  7 23:35:04 rescue mcelog: Family 6 Model 36 CPU: only decoding architectural errors
Jun  7 23:35:04 rescue systemd[1]: Started /etc/rc.local Compatibility.
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda [SAT], opened
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda [SAT], HGST HUS724020ALA640, S/N:PN1134P6K4V87W, WWN:5-000cca-22dec7a98, FW:MF6OAA70, 2.00 TB
Jun  7 23:35:04 rescue systemd[1]: Starting LSB: set CPUFreq kernel parameters...
Jun  7 23:35:04 rescue mcelog[734]: Starting Machine Check Exceptions decoder: mcelog.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting do_it_for_me caller...
Jun  7 23:35:04 rescue systemd[1]: Started do_it_for_me caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Starting showdoc.sh caller...
Jun  7 23:35:04 rescue smartd[720]: Device: /dev/sda [SAT], not found in smartd database.
Jun  7 23:35:04 rescue systemd[1]: Started showdoc.sh caller.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Machine Check Exceptions (MCE) collector & decoder.
Jun  7 23:35:04 rescue systemd[1]: Started getty on tty2-tty6 if dbus and logind are not available.
Jun  7 23:35:04 rescue systemd[1]: Starting Login Prompts.
Jun  7 23:35:04 rescue systemd[1]: Reached target Login Prompts.
Jun  7 23:35:04 rescue systemd[1]: Started System Logging Service.
Jun  7 23:35:04 rescue mpt-statusd[746]: Starting mpt-status monitor: mpt-statusd.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: Check mpt-status values in the background..
Jun  7 23:35:04 rescue rsyslogd-2007: action 'action 17' suspended, next retry is Tue Jun  7 23:35:34 2016 [try http://www.rsyslog.com/e/2007 ]
Jun  7 23:35:04 rescue cpufrequtils[788]: CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...CPU2...CPU3...done.
Jun  7 23:35:04 rescue systemd[1]: Started LSB: set CPUFreq kernel parameters.
Jun  7 23:35:04 rescue mpt-statusd: detected non-optimal RAID status
Jun  7 23:35:05 rescue smartd[720]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Jun  7 23:35:05 rescue smartd[720]: Monitoring 1 ATA and 0 SCSI devices
Jun  7 23:35:06 rescue smartd[720]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.HGST_HUS724020ALA640-PN1134P6K4V87W.ata.state
Jun  7 23:35:09 rescue ntpdate[642]: adjust time server 213.251.128.249 offset -0.092484 sec
Jun  7 23:35:10 rescue systemd[1]: Started OpenBSD Secure Shell server.
Jun  7 23:35:10 rescue systemd[1]: Starting Multi-User System.
Jun  7 23:35:10 rescue systemd[1]: Reached target Multi-User System.
Jun  7 23:35:10 rescue systemd[1]: Starting Graphical Interface.
Jun  7 23:35:10 rescue systemd[1]: Reached target Graphical Interface.
Jun  7 23:35:10 rescue systemd[1]: Starting Stop Read-Ahead Data Collection 10s After Completed Startup.
Jun  7 23:35:10 rescue systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup.
Jun  7 23:35:10 rescue systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jun  7 23:35:10 rescue systemd[1]: Started Update UTMP about System Runlevel Changes.
Jun  7 23:35:10 rescue systemd[1]: Startup finished in 8.582s (kernel) + 16.183s (userspace) = 24.766s.
Jun  7 23:35:10 rescue systemd[1]: Reloading OpenBSD Secure Shell server.
Jun  7 23:35:10 rescue systemd[1]: Reloaded OpenBSD Secure Shell server.
Jun  7 23:35:18 rescue systemd[1]: Starting LSB: Apache2 web server...
Jun  7 23:35:19 rescue apache2[1006]: Starting web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using rescue.ovh.net. Set the 'ServerName' directive globally to suppress this message
Jun  7 23:35:20 rescue apache2[1006]: .
Jun  7 23:35:20 rescue systemd[1]: Started LSB: Apache2 web server.
Jun  7 23:35:32 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 64s/+0.010s/0.006s/0.004s/+80ppm
Jun  7 23:35:40 rescue systemd[1]: Starting Stop Read-Ahead Data Collection...
Jun  7 23:35:40 rescue systemd[1]: Started Stop Read-Ahead Data Collection.
Jun  7 23:36:36 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 128s/+0.027s/0.006s/0.011s/+183ppm
Jun  7 23:38:45 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 256s/-0.014s/0.006s/0.014s/+155ppm
Jun  7 23:43:01 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 512s/-0.043s/0.006s/0.024s/+113ppm
Jun  7 23:45:01 rescue CRON[1684]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  7 23:45:04 rescue mpt-statusd: detected non-optimal RAID status
Jun  7 23:49:49 rescue systemd[1]: Starting Cleanup of Temporary Directories...
Jun  7 23:49:49 rescue systemd[1]: Started Cleanup of Temporary Directories.
Jun  7 23:51:33 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 512s/-0.064s/0.006s/0.064s/+51ppm
Jun  7 23:53:33 rescue kernel: EXT4-fs (sda2): recovery complete
Jun  7 23:53:33 rescue kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Jun  7 23:53:59 rescue kernel: EXT4-fs (sda3): recovery complete
Jun  7 23:53:59 rescue kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Jun  7 23:55:01 rescue CRON[1952]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  7 23:55:04 rescue mpt-statusd: detected non-optimal RAID status
Jun  7 23:59:01 rescue CRON[1988]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 60 2)
Jun  8 00:00:05 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 1024s/-0.031s/0.009s/0.061s/+35ppm
Jun  8 00:05:02 rescue CRON[2022]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:05:05 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:05:06 rescue smartd[720]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 200 to 206
Jun  8 00:15:01 rescue CRON[2077]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:15:05 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:17:01 rescue CRON[2098]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 00:17:10 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.049s/0.006s/0.056s/+24ppm
Jun  8 00:25:01 rescue CRON[2135]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:25:05 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:35:02 rescue CRON[2188]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:35:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:35:06 rescue smartd[720]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 206 to 200
Jun  8 00:45:01 rescue CRON[2241]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:45:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 00:51:18 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.070s/0.006s/0.051s/+7ppm
Jun  8 00:55:01 rescue CRON[2294]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 00:55:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:05:01 rescue CRON[2347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:05:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:05:06 rescue smartd[720]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 200 to 206
Jun  8 01:10:51 rescue kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Jun  8 01:15:02 rescue CRON[2404]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:15:06 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:17:01 rescue CRON[2430]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 01:25:01 rescue CRON[2474]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:25:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:25:26 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.034s/0.006s/0.031s/-1ppm
Jun  8 01:35:01 rescue CRON[2540]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:35:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:45:01 rescue CRON[2598]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:45:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:55:01 rescue CRON[2651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 01:55:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 01:59:34 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.016s/0.006s/0.021s/-5ppm
Jun  8 02:05:01 rescue CRON[2704]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:05:07 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:15:01 rescue CRON[2759]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:15:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:17:01 rescue CRON[2780]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 02:25:01 rescue CRON[2816]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:25:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:33:43 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.008s/0.006s/0.022s/-8ppm
Jun  8 02:35:01 rescue CRON[2870]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:35:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:45:01 rescue CRON[2923]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:45:08 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 02:55:01 rescue CRON[2982]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 02:55:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:05:01 rescue CRON[3039]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:05:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:07:51 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.002s/0.006s/0.025s/-8ppm
Jun  8 03:15:01 rescue CRON[3094]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:15:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:17:01 rescue CRON[3115]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 03:25:01 rescue CRON[3151]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:25:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:35:01 rescue CRON[3204]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:35:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:41:59 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.006s/0.026s/-8ppm
Jun  8 03:45:01 rescue CRON[3264]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:45:09 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 03:55:01 rescue CRON[3317]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 03:55:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:05:01 rescue CRON[3370]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:05:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:15:01 rescue CRON[3423]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:15:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:16:07 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.006s/0.029s/-9ppm
Jun  8 04:17:01 rescue CRON[3444]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 04:25:01 rescue CRON[3479]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:25:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:35:01 rescue CRON[3534]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:35:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:45:01 rescue CRON[3587]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:45:10 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 04:50:16 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.006s/0.031s/-9ppm
Jun  8 04:55:01 rescue CRON[3642]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 04:55:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:05:01 rescue CRON[3695]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:05:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:15:02 rescue CRON[3748]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:15:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:17:01 rescue CRON[3769]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 05:24:24 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.031s/-9ppm
Jun  8 05:25:01 rescue CRON[3804]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:25:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:35:01 rescue CRON[3857]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:35:11 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:45:01 rescue CRON[3915]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:45:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:55:01 rescue CRON[3970]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 05:55:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 05:58:32 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.006s/-9ppm
Jun  8 06:05:01 rescue CRON[4025]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:05:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:15:01 rescue CRON[4080]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:15:12 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:17:01 rescue CRON[4102]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 06:25:01 rescue CRON[4138]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jun  8 06:25:01 rescue CRON[4139]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:25:13 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:32:40 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.003s/-9ppm
Jun  8 06:35:01 rescue CRON[4320]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:35:13 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:45:01 rescue CRON[4373]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:45:13 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 06:55:01 rescue CRON[4426]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 06:55:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:05:01 rescue CRON[4479]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:05:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:06:49 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.001s/-9ppm
Jun  8 07:15:01 rescue CRON[4534]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:15:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:17:01 rescue CRON[4555]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 07:25:02 rescue CRON[4590]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:25:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:35:01 rescue CRON[4643]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:35:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:36:26 rescue kernel: ip_set: protocol 6
Jun  8 07:41:29 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.001s/0.006s/0.001s/-9ppm
Jun  8 07:45:01 rescue CRON[4705]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:45:14 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 07:55:01 rescue CRON[4758]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 07:55:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:05:01 rescue CRON[4813]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:05:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:15:02 rescue CRON[4867]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:15:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:15:37 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.001s/-9ppm
Jun  8 08:17:01 rescue CRON[4888]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 08:25:01 rescue CRON[4923]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:25:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:35:01 rescue CRON[4979]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:35:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:45:01 rescue CRON[5034]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:45:15 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 08:49:46 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.001s/-9ppm
Jun  8 08:55:01 rescue CRON[5087]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 08:55:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:05:01 rescue CRON[5142]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:05:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:15:01 rescue CRON[5195]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:15:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:17:01 rescue CRON[5216]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun  8 09:23:54 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.006s/0.000s/-9ppm
Jun  8 09:25:01 rescue CRON[5251]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:25:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:35:01 rescue CRON[5305]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:35:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:45:02 rescue CRON[5365]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:45:16 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:55:01 rescue CRON[5419]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  8 09:55:17 rescue mpt-statusd: detected non-optimal RAID status
Jun  8 09:58:34 rescue systemd-timesyncd[545]: interval/delta/delay/jitter/drift 2048s/-0.000s/0.006s/0.000s/-9ppm

Je fais le test sans postgre
Quels autres log veux-tu ?

sloomy
08/06/2016, 09h58
Bonjour,

Ta version d'OS ?

Tu n'as plus la main sur ton serveur en ssh ? http ? ping ok ?

Essaie de désactiver le chargement du service postgre au démarrage voir si c'est réellement cela qui pose soucis.

Que dises les logs ?

Cordialement,
Bruno

laurent_
07/06/2016, 21h48
Bonsoir,

Après avoir créé / supprimé l'utilisateur "adm" dans postresql mon serveur est devenu inaccessible

Une connexion en mode rescue permet monter sda2 + sda3 et de chrooter -> je ne detecte rien d'anormal

Après redémarrage normal sur le disque -> problème au démarrage -> diagnostique kimsufi ->" Serveur bloque sur ce message : /dev/sda2 is missing" Alors que /dev/sda2 est bien présent en mode rescue ...???

Je ne comprend pas le rapport en mes opérations sur postresql et le rplantage du serveur. ni tout simplement ce qui s'est passé.

Est-ce quelqu'un a une idée de ce qui s'est passé ? avez vous besoin d'élément de diagnostiques, avec vous une piste pour sortir de cette situation ?

Par avance merci,

Laurent