Hi i have upgraded my account to new lab site and created a new machine a
month ago in Spain2 region, but yesterday i started to have problems with
this machine , i tried to reboot but the problem has grown to the point
where i can't start correctly . Below here you will see disk errors i got
in console log.

You can restore a 20 days old backup

Hola, hace poco actualice mi cuenta y me movi al sitio Spain2 creando una
maquina nueva, desde ayer que accedi vi que habia problemas en la maquina,
intenté reiniciarla pero el problema crecio hasta el punto de no poder
iniciarse. En el console log he visto estos problemas de disco.

Si la unica manera de restaurarla es tirar de backup, podeis tirar hasta
unos 20 dias atras si lo veis necesario. Todavia no le metí trabajo .
Gracias

Info de la maquina:
User-Name: djquano@gmail.com

Tenant name: jacobo-garcia cloud
Tenant id: 00000000000000000000000000003316
Region: Spain2

LOG:
[467094.314429] end_request: I/O error, dev vda, sector 298496
[467096.025450] end_request: I/O error, dev vda, sector 298496
[467098.659684] end_request: I/O error, dev vda, sector 298496
[467100.863048] end_request: I/O error, dev vda, sector 298496
[467101.890086] end_request: I/O error, dev vda, sector 298496
[467103.762768] end_request: I/O error, dev vda, sector 298496
[467105.608181] end_request: I/O error, dev vda, sector 298496
[467106.960937] end_request: I/O error, dev vda, sector 298496
[467107.724798] end_request: I/O error, dev vda, sector 298496
[467109.373422] end_request: I/O error, dev vda, sector 298496
[467112.097239] end_request: I/O error, dev vda, sector 298496
[467113.516977] end_request: I/O error, dev vda, sector 298496
[467115.013116] end_request: I/O error, dev vda, sector 298496
[601611.935228] end_request: I/O error, dev vda, sector 35400
[601611.937161] end_request: I/O error, dev vda, sector 35400
[601613.562140] end_request: I/O error, dev vda, sector 146472
[601613.563517] EXT3-fs error (device vda1): ext3_find_entry: reading
directory #58728 offset 0
[601613.564928] Aborting journal on device vda1.
[601613.569933] EXT3-fs (vda1): error: remounting filesystem read-only
[601613.575565] end_request: I/O error, dev vda, sector 146472
[601613.576599] EXT3-fs error (device vda1): ext3_find_entry: reading
directory #58728 offset 0
[601613.578463] end_request: I/O error, dev vda, sector 146472
[601613.579772] EXT3-fs error (device vda1): ext3_find_entry: reading
directory #58728 offset 0
[720197.851719] EXT3-fs (vda1): error: ext3_remount: Abort forced by user
[720200.143247] EXT3-fs (vda1): error: ext3_remount: Abort forced by user
[720208.105363] end_request: I/O error, dev vda, sector 661696
[720208.107008] end_request: I/O error, dev vda, sector 661696
[720208.108703] end_request: I/O error, dev vda, sector 661696
[720411.420723] end_request: I/O error, dev vda, sector 1188552
[720411.422538] end_request: I/O error, dev vda, sector 1188552
[720411.425231] end_request: I/O error, dev vda, sector 1188552
[720428.715370] end_request: I/O error, dev vda, sector 1112856
[720428.730170] end_request: I/O error, dev vda, sector 1112856
[720428.732188] end_request: I/O error, dev vda, sector 1112856

AFTER REBOOT LOG:
Loading, please wait...
INIT: version 2.88 booting
[[36minfo[39;49m] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[?25l[?1c7[1G[[32m ok
[39;49m8[?25h[?0c.
[....] Synthesizing the initial hotplug events...[?25l[?1c7[1G[[32m ok
[39;49m8[?25h[?0cdone.
[....] Waiting for /dev to be fully populated...[?25l[?1c7[1G[[32m ok
[39;49m8[?25h[?0cdone.
[....] Activating swap...[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0cdone.
[....] Checking root file system...fsck from util-linux 2.20.1
/dev/vda1 contains a file system with errors, check forced.
/dev/vda1: | | 0.1%
/dev/vda1: | /
0.2% /dev/vda1:
Deleted inode 16538 has zero dtime. FIXED.
/dev/vda1: Inodes that were part of a corrupted orphan linked list found.

/dev/vda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4
[?25l[?1c7[1G[[31mFAIL[39;49m8[?25h[?0c[31mfailed (code 4).[39;49m
[....] An automatic file system check (fsck) of the root filesystem failed.
A manual fsck must be performed, then the system restarted. The fsck should
be performed in maintenance mode with the root filesystem mounted in
read-only mode. ...[?25l[?1c7[1G[[31mFAIL[39;49m8[?25h[?0c
[31mfailed![39;49m
[....] The root filesystem is currently mounted in read-only mode. A
maintenance shell will now be started. After performing system maintenance,
press CONTROL-D to terminate the maintenance shell and restart the system.
...[?25l[?1c7[1G[[33mwarn[39;49m8[?25h[?0c [33m(warning).[39;49m
sulogin: root account is locked, starting shell
root@qserv1:~#

muchas gracias y un saludo.
–
– Quano –

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Quano <djquano@gmail.com>]