OpenVZ Forum


Home » General » Support » container fs broke after outage
container fs broke after outage [message #53553] Fri, 21 June 2019 18:30 Go to next message
gral is currently offline  gral
Messages: 34
Registered: May 2006
Member

From: *cab.prima.net.ar
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--
Re: container fs broke after outage [message #53556 is a reply to message #53553] Sun, 23 June 2019 16:29 Go to previous message
gral is currently offline  gral
Messages: 34
Registered: May 2006
Member

From: *fibertel.com.ar
I could find the answer in this link;

https://galaxydata.ru/community/openvz-failed-to-mount-image -error-in-e2fsck-fsutils-c315-e2fsck-failed-exit-code-4-fsut ils-c293-884


Argentina
--Vz--
Previous Topic: OpenVZ7 - Failed to yum update
Next Topic: Bug reports should go to bugs.openvz.org
Goto Forum:
  


Current Time: Tue Jul 16 05:59:45 GMT 2019