Hi
I have a Centos server that crashed, it would no longer boot. I thought it was the disk with the OS that was the problem so I bought a new one and did a fresh install and now the computer is again up and running. But I'm having problems with accessing the old failed disk. I can see it with gnome-disk-utility and it says that the disk is OK but has 8 bad sectors. I can mount the boot partition from it and I can decrypt the main partition. But then I can see no way to mount the main partition. It is a LVM physical volume.
Any advice?
Am 13.12.2017 um 22:31 schrieb martin.wagner@mailbit.io:
I have a Centos server that crashed, it would no longer boot. I thought it was the disk with the OS that was the problem so I bought a new one and did a fresh install and now the computer is again up and running. But I'm having problems with accessing the old failed disk. I can see it with gnome-disk-utility and it says that the disk is OK but has 8 bad sectors. I can mount the boot partition from it and I can decrypt the main partition. But then I can see no way to mount the main partition. It is a LVM physical volume.
Any advice?
Show us the output of (after decrypt):
lsblk -f
or directly - try:
vgchange -a y
mount /dev/mapper/"main partition" /oldfaileddisk
-- LF
On 13/12/17 21:42, Leon Fauster wrote:
Am 13.12.2017 um 22:31 schrieb martin.wagner@mailbit.io:
I have a Centos server that crashed, it would no longer boot. I thought it was the disk with the OS that was the problem so I bought a new one and did a fresh install and now the computer is again up and running. But I'm having problems with accessing the old failed disk. I can see it with gnome-disk-utility and it says that the disk is OK but has 8 bad sectors. I can mount the boot partition from it and I can decrypt the main partition. But then I can see no way to mount the main partition. It is a LVM physical volume.
Any advice?
Show us the output of (after decrypt):
lsblk -f
or directly - try:
vgchange -a y
mount /dev/mapper/"main partition" /oldfaileddisk
-- LF
If you think the disk is going faulty the very first thing to do is to make a copy of it and then work on the copy. If your failed disk is on (as an example) /dev/sdc, the command is:
# dd if=/dev/sdc of=/home/dd-copy-of-sdc
It will take a long time, and ensure that /home has enough space for the complete disk. Use kpartx(8) to make the disk visible and you can then mount the partitions.
lvs(8) will tell you about any logical volumes and IIRC, lvchange allows you to activate them. You can then mount them as normal.
On Dec 13, 2017, at 5:15 PM, J Martin Rushton martinrushton56@btinternet.com wrote:
# dd if=/dev/sdc of=/home/dd-copy-of-sdc
Better, use ddrescue:
https://www.gnu.org/software/ddrescue/
dd will do unfortunate things like quit early on I/O errors, even if later blocks would read just fine. ddrescue assumes the input file is dodgy and tries to cope.
On 14/12/17 18:57, Warren Young wrote:
On Dec 13, 2017, at 5:15 PM, J Martin Rushton martinrushton56@btinternet.com wrote:
# dd if=/dev/sdc of=/home/dd-copy-of-sdc
Better, use ddrescue:
https://www.gnu.org/software/ddrescue/
dd will do unfortunate things like quit early on I/O errors, even if later blocks would read just fine. ddrescue assumes the input file is dodgy and tries to cope.
Looks interesting. I've only used dd in anger, and then only maybe 3 or 4 times over the last 20 years. It's worth pointing out that ddrescue is not in the main distro, you'll need to get it from EPEL.
Whatever method you use though: "Be diligent because every time a physically damaged drive powers up and is able to output some data, it may be the very last time that it ever will." (ddrescue manual section 9)
If the data is important to you, don't mess around and contact a reputable professional data recovery expert or company.
If losing your data is a viable option, try to do it yourself. Otherwise seek professional help, with the data recovery effort of course.
On Fri, Dec 15, 2017 at 4:31 AM, J Martin Rushton martinrushton56@btinternet.com wrote:
On 14/12/17 18:57, Warren Young wrote:
On Dec 13, 2017, at 5:15 PM, J Martin Rushton martinrushton56@btinternet.com wrote:
# dd if=/dev/sdc of=/home/dd-copy-of-sdc
Better, use ddrescue:
https://www.gnu.org/software/ddrescue/
dd will do unfortunate things like quit early on I/O errors, even if later blocks would read just fine. ddrescue assumes the input file is dodgy and tries to cope.
Looks interesting. I've only used dd in anger, and then only maybe 3 or 4 times over the last 20 years. It's worth pointing out that ddrescue is not in the main distro, you'll need to get it from EPEL.
Whatever method you use though: "Be diligent because every time a physically damaged drive powers up and is able to output some data, it may be the very last time that it ever will." (ddrescue manual section 9)
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
W dniu 14.12.2017 o 23:06, Nizar Armansyah pisze:
If the data is important to you, don't mess around and contact a reputable professional data recovery expert or company.
If the data is important to you, you will get it back from your backups, won't you?
-
J Martin Rushton -
Leon Fauster -
Marcin Trendota -
martin.wagner＠mailbit.io -
Nizar Armansyah -
Warren Young