Hardware failure followed by container disk corruption

Elodie Edoh-Alove

New Member
Aug 18, 2022
1
0
1
Hello community,
I need your help.
One of our physical disk is failing and it seems like the container .raw file has been corrupted. We tried to backup this file in another location and change the container config to connect to the disk in the new storage but the container still can't start.
Here is the start error message



Task viewer: CT 101 - Start

OutputStatus

Stop
lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
lxc-start: tools/lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
TASK ERROR: command 'lxc-start -n 101' failed: exit code 1

When we tried to check the raw disk in the original storage it came out with this error message
1660842272421.png

And when we do the same in the new storage we have this (which confirms the image is corrupted I guess).

1660842358285.png

How can we proceed to retrieve the disk in a healthy storage?
Is it possible to retrieve the data from the image directly using a tool?

Kind regards
Elodie