[super-cool]

C'est un vieux serveur: Kimsufi Bon Plan 2013
je copie les fichiers qui n'ont pas d'erreur et je supprimer le serveur

Merci, de l'aide et d'avoir fait le support

[nowwhat]

Error 5819 occurred ....

Ah, Ok !!!
Un cas 'physique' !!
T'as un disque dur archi mort.
Ils l'ont remplacé ?

[super-cool]

Quand je dit support, je parle de donner toutes les informations !
il n'y a pas que moi, comme client qui utilise proxmox en mode rescue.

ex: proxmox ou smartctl
http://guides.ovh.com/ModeRescue

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 / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4040A26D-C35E-4AAE-A826-5F8FBE605A84

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 43057151 2095104 1023M Linux swap
/dev/sda4 43057152 3907020799 3863963648 1.8T Linux LVM

Disk /dev/mapper/pve-data: 1.8 TiB, 1978344144896 bytes, 3863953408 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

et

root@rescue:/# smartctl -a -d ata /dev/sda

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.14.32-xxxx-std-ipv6-64-rescue] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST2000DM001-9YN164
Serial Number: W1E0JPK0
LU WWN Device Id: 5 000c50 04b6f441d
Firmware Version: CC4H
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Mar 28 12:18:49 2016 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 575) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 224) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 097 082 006 Pre-fail Always - 172614438
3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 34
5 Reallocated_Sector_Ct 0x0033 080 080 036 Pre-fail Always - 26848
7 Seek_Error_Rate 0x000f 077 060 030 Pre-fail Always - 21727708077
9 Power_On_Hours 0x0032 063 063 000 Old_age Always - 32624
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 33
183 Runtime_Bad_Block 0x0032 098 098 000 Old_age Always - 2
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 5817
188 Command_Timeout 0x0032 100 097 000 Old_age Always - 12 13 13
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 046 045 Old_age Always - 39 (Min/Max 36/44)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 31
193 Load_Cycle_Count 0x0032 095 095 000 Old_age Always - 11551
194 Temperature_Celsius 0x0022 039 054 000 Old_age Always - 39 (0 25 0 0 0)
197 Current_Pending_Sector 0x0012 043 031 000 Old_age Always - 9360
198 Offline_Uncorrectable 0x0010 043 031 000 Old_age Offline - 9360
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 24599h+18m+07.609s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 15816496321205
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 104158233257324

SMART Error Log Version: 1
ATA Error Count: 5819 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 5819 occurred at disk power-on lifetime: 32623 hours (1359 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 f0 ff ff ff 4f 00 6d+16:05:23.949 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:21.718 READ FPDMA QUEUED
61 00 08 00 08 91 42 00 6d+16:05:21.718 WRITE FPDMA QUEUED
ef 10 02 00 00 00 a0 00 6d+16:05:21.718 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 6d+16:05:21.717 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 5818 occurred at disk power-on lifetime: 32623 hours (1359 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 6d+16:05:18.831 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:18.822 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:18.816 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:18.815 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:18.815 READ FPDMA QUEUED

Error 5817 occurred at disk power-on lifetime: 32623 hours (1359 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 6d+16:05:15.784 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:15.783 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 6d+16:05:15.743 FLUSH CACHE EXT
61 00 08 00 08 91 42 00 6d+16:05:15.726 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 6d+16:05:15.726 WRITE FPDMA QUEUED

Error 5816 occurred at disk power-on lifetime: 32623 hours (1359 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 88 ff ff ff 4f 00 6d+16:05:12.813 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:12.812 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:12.803 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:12.792 READ FPDMA QUEUED
61 00 08 00 08 91 42 00 6d+16:05:12.792 WRITE FPDMA QUEUED

Error 5815 occurred at disk power-on lifetime: 32623 hours (1359 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 6d+16:05:09.837 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:09.837 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 6d+16:05:09.836 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 6d+16:05:09.649 FLUSH CACHE EXT
61 00 08 00 08 91 42 00 6d+16:05:09.625 WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 6198 -
# 2 Short offline Completed without error 00% 6187 -
# 3 Short offline Completed without error 00% 6187 -
# 4 Short offline Completed without error 00% 18 -
# 5 Short offline Completed without error 00% 7 -
# 6 Short offline Completed without error 00% 7 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[nowwhat]

....
je vais supprime le serveur, comme chez kimsufi il n'y à pas de support.

Même chez OVH (et SYS) on te donne PAS des support concernant un/le LOGICIEL (n’importe quel logiciel) - uniquement le matos physique.

Peut être il existe des hébergeurs avec un "co-admin" support ... mais ça sera ailleurs.

PS : KimSuFi ou "Qui Me Suiffit" ou "Je me démerde moi même"

[super-cool]

Bonjour,

Et dans .../vz/images/ ?

Cdlt
Bruno

Le dossier est vide.

Dans proxmox je n'ai que openvz des container (template debian)

Merci
je vais supprime le serveur, comme chez kimsufi il n'y à pas de support.

[sloomy]

Bonjour,

Et dans .../vz/images/ ?

Cdlt
Bruno

[super-cool]

bonjour

root@rescue:~# mount /dev/sda2 /mnt/
root@rescue:~# ls /mnt/
bin   dev  home  lib32  media  opt   run   selinux  sys  usr  vz
boot  etc  lib   lib64  lost+found            mnt    proc  root             sbin  srv      tmp  var

root@rescue:~# cat /mnt/etc/fstab
#                
/dev/sda2       /       ext3    errors=remount-ro       0       1
/dev/sda3       swap    swap    defaults        0       0
/dev/pve/data   /var/lib/vz     ext3    defaults        1       2
proc            /proc   proc    defaults        0       0
sysfs           /sys    sysfs   defaults        0       0

le serveur a fais un reboot sans redémarrage sur Proxmox

ls /mnt/var/lib/vz/
je ne voie pas mon disque ou il y a les fichiers de Proxmox

ok il faut la commande
mount /dev/mapper/pve-data /mnt/var/lib/vz

root@rescue:/mnt/var/lib/vz/private# ls -l
drwxr-xr-x   21 root       root       4096 Jun  7  2013 100
drwxr-xr-x   22 root       root       4096 Apr 18  2015 101
drwxr-xr-x   22 root       root       4096 Apr 18  2015 102
sr-sr-sr-T 6044 1790693228 1790646172    0 Mar 17  2031 103
drwxr-xr-x   21 root       root       4096 Jun  2  2013 200

je ne voie pas les fichiers et dossiers de la VM 103, une idée ?

root@rescue:/vz# pveperf
readline() on closed filehandle TMP at /usr/bin/pveperf line 29.
CPU BOGOMIPS:      0.00
REGEX/SECOND:      966874
df: Warning: cannot read table of mounted file systems: No such file or directory
HD SIZE:           19.25 GB (-)
FSYNCS/SECOND:     58.98
DNS EXT:           2012.70 ms
DNS INT:           2006.12 ms (kimsufi.com)

Merci

[nowwhat]

Et pourquoi commencer avec "LVM2_member " ????

J'aurais tenté un

mount /dev/sda2 /mnt/

qui mount probablement le root /
Puis:
cat /mnt/etc/fstab
pour voir l'autre mount point ....
Par exemple :
mount /dev/sda1 /mnt/home
ou
mount /dev/sda1 /mnt/var
etc ...

Normalement, on 'joue' avec le mode rescue dès la réception d'un serveur ..... ou suite à des modifications des partitions - vu que t'as un truc mystique nommé "LVM2_member".

[super-cool]

Bonjour

Sur la gamme Kimsufi, nous n'effectuons pas d'assistance technique ou logicielle. sur la configuration et l'administration du serveur. Je ne pourrai pas vous apporter d'assistance vis à vis de votre requête.
TICKET#2016032119093658

/dev/sda	Numéro de série : W1E0JPK0	État SMART : OK [Logs]

root@rescue:/# df -h
Filesystem                          Size  Used Avail Use% Mounted on
aufs                                 12G   78M   12G   1% /
devtmpfs                             12G     0   12G   0% /dev
91.121.126.137:/home/pub/rescue.v8  2.0T  257G  1.6T  14% /nfs
tmpfs                                12G   78M   12G   1% /rw
91.121.126.137:/home/pub/pro-power  2.0T  257G  1.6T  14% /power
91.121.126.137:/home/pub/commonnfs  2.0T  257G  1.6T  14% /common
tmpfs                                12G     0   12G   0% /dev/shm
tmpfs                                12G  9.8M   12G   1% /run
tmpfs                               5.0M     0  5.0M   0% /run/lock
tmpfs                                12G     0   12G   0% /sys/fs/cgroup
tmpfs                                12G  152K   12G   1% /tmp
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 / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4040A26D-C35E-4AAE-A826-5F8FBE605A84

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   43057151    2095104   1023M Linux swap
/dev/sda4  43057152 3907020799 3863963648    1.8T Linux LVM

Disk /dev/mapper/pve-data: 1.8 TiB, 1978344144896 bytes, 3863953408 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

root@rescue:/# pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda4
  VG Name               pve
  PV Size               1.80 TiB / not usable 0
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              471675
  Free PE               1
  Allocated PE          471674
  PV UUID               kjnQCw-HyMt-R7x8-fXqG-DuP2-zDfo-yITV6D

root@rescue:/# blkid -o list
device                     fs_type    label       mount point                    UUID
----------------------------------------------------------------------------------------------------------------------
/dev/sda2                  ext3       /           (not mounted)                  62f7e32b-bc5e-4130-890c-00b334ab20f8
/dev/sda3                  swap                   (not mounted)                  ca495e59-094d-4389-b011-4bc0e3cd1861
/dev/sda4                  LVM2_member            (in use)                       kjnQCw-HyMt-R7x8-fXqG-DuP2-zDfo-yITV6D
/dev/mapper/pve-data       ext3       /var/lib/vz (not mounted)                  f773cccc-6000-4d5d-96d3-6cf5fc00293f
/dev/sda1                                         (not mounted)
root@rescue:/# vgdisplay -cv
    DEGRADED MODE. Incomplete RAID LVs will be processed.
    Finding all volume groups
    Finding volume group "pve"
  pve:r/w:772:-1:0:1:0:-1:0:1:1:1931980800:4096:471675:471674:1:2FeQpK-a0tv-5ULp-YOCQ-IbtY-MWXk-AnZiEg

root@rescue:/# mount /dev/sda4 /mnt/
mount: unknown filesystem type 'LVM2_member'

mon disque dur est inaccessible en mode rescue !
serveur: Kimsufi Bon Plan 2013
Intel® Core™ i7 CPU 920 @ 2.67GHz
Ram 24 Go
Disque 2 To
Système (OS) VPS Proxmox

http://guides.ovh.com/ModeRescue

Merci