Здравствуйте. Пытаюсь восстановить работоспособность виртуальной машины, после сбоя в рэйде 10. Никто не ждал беды, в один момент сервер жутко затупил, и всё погасло, развалился райд. Собрал обратно райд, винда не запустилась, нашлись битые сектора. Тем не менее удалось вытащить все виртуальные машины.
Одной из них была debian x64, которая использовалась для хранения 1с бд.
Всё хранилось на lvm томах, но проблемы возникли только с этим:
/dev/mapper/LVM_GP0-LVM_VAR 92G 14G 74G 16% /var
самое интересное, что
badblocks -v /dev/mapper/LVM_GP0-LVM_VAR
ошибок не выдал
LOG: database system was interrupted; last known up at 2016-04-21 19:24:23 OMSST
LOG: could not remove cache file "base/335834/pg_internal.init": Ошибка ввода/вывода
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 23/1759B770
PANIC: unexpected pageaddr 22/D6000000 in log file 35, segment 22, offset 0
LOG: startup process (PID 2287) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
LOG: database system was interrupted while in recovery at 2016-04-22 21:33:29 OMSST
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG: could not remove cache file "base/335834/pg_internal.init": Ошибка ввода/вывода
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 23/1759B770
PANIC: unexpected pageaddr 22/D6000000 in log file 35, segment 22, offset 0
LOG: startup process (PID 2304) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
LOG: database system was interrupted while in recovery at 2016-04-22 21:38:42 OMSST
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG: could not remove cache file "base/335834/pg_internal.init": Ошибка ввода/вывода
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 23/1759B770
PANIC: unexpected pageaddr 22/D6000000 in log file 35, segment 22, offset 0
LOG: startup process (PID 2386) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
LOG: database system was interrupted while in recovery at 2016-04-22 21:45:14 OMSST
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG: could not remove cache file "base/335834/pg_internal.init": Ошибка ввода/вывода
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 23/1759B770
PANIC: unexpected pageaddr 22/D6000000 in log file 35, segment 22, offset 0
LOG: startup process (PID 2286) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
LOG: database system was interrupted while in recovery at 2016-04-22 21:46:24 OMSST
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG: could not remove cache file "base/335834/pg_internal.init": Ошибка ввода/вывода
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 23/1759B770
PANIC: unexpected pageaddr 22/D6000000 in log file 35, segment 22, offset 0
LOG: startup process (PID 2373) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
LOG: database system was interrupted while in recovery at 2016-04-22 21:46:52 OMSST
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG: could not remove cache file "base/335834/pg_internal.init": Ошибка ввода/вывода
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 23/1759B770
PANIC: unexpected pageaddr 22/D6000000 in log file 35, segment 22, offset 0
LOG: startup process (PID 2273) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
LOG: database system was interrupted while in recovery at 2016-04-22 21:48:51 OMSST
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG: could not remove cache file "base/335834/pg_internal.init": Ошибка ввода/вывода
LOG: database system was not properly shut down; automatic recovery in progress
LOG: consistent recovery state reached at 23/1759B770
PANIC: unexpected pageaddr 22/D6000000 in log file 35, segment 22, offset 0
LOG: startup process (PID 2346) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
Сервак упал в 18:24, в логе присутствует строчка со временем, 19:24 видимо каким то макаром ему удалось ещё подняться в это время, либо произошёл резолв времени, и это последнее что сказала постгри, но уже с ошибками. Скажите пожалуйста, возможно ли какой-то фикс бд запустить, чтобы хотя бы забрать из неё данные? Последний бэкап есть только за 1 день, но беда произошла в конце следующего дня, очень много работы проделали, не хотелось бы потерять столько данных.
