OpenVZ Forum: Support » container fs broke after outage

Home » General » Support » container fs broke after outage

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

container fs broke after outage [message #53553]

Fri, 21 June 2019 18:30

gral
Messages: 34
Registered: May 2006

Member

Hello due a massive outage on our dc , one of our container dont boot showing a fs corruption message..

# vzctl start 8e5c4d87-a016-4457-9fc6-82f8dfa00011
Starting Container ...
Mount image: /vz/private/8e5c4d87-a016-4457-9fc6-82f8dfa00011/root.hdd
fsck.ext4: Bad magic number in super-block while trying to open /dev/ploop41260p1
Failed to mount image /vz/private/8e5c4d87-a016-4457-9fc6-82f8dfa00011/root.hdd: Error in e2fsck (fsutils.c:470): e2fsck failed (exit code Cool

[41]

Tried to do a fsck on the device;

# ls -la /dev/ploop41260p1
brw-rw---- 1 root disk 182, 660161 Jun 21 15:26 /dev/ploop41260p1
# fsck -cy /dev/ploop41260p1
fsck from util-linux 2.23.2
e2fsck 1.42.9 (28-Dec-2013)
fsck.ext2: No such device or address while trying to open /dev/ploop41260p1
Possibly non-existent or swap device?

Any suggestion how can i fix the fs ?

# uname -a
Linux vps2.xxxxxxxx.net 3.10.0-862.20.2.vz7.73.29 #1 SMP Thu Feb 21 17:35:43 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux

Thanks!

Argentina
--Vz--

Report message to a moderator