Hi
> On Thu, May 28, 2020 19:38, Robert Nichols wrote:
>
>> What output do you get from:
>>
>> file -s /dev/mapper/vg_voinet01-lv_log
>> lsblk -f /dev/mapper/vg_voinet01-lv_log
>>
>
> file -s /dev/mapper/vg_voinet01-lv_log
> /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5'
>
On Thu, May 28, 2020 19:38, Robert Nichols wrote:
> What output do you get from:
>
> file -s /dev/mapper/vg_voinet01-lv_log
> lsblk -f /dev/mapper/vg_voinet01-lv_log
>
file -s /dev/mapper/vg_voinet01-lv_log
/dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5'
dm-f
lsblk -f
On 5/28/20 1:33 PM, James B. Byrne via CentOS wrote:
/dev/mapper/vg_voinet01-lv_log
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2 filesystem
(and not swap or ufs or something else), then the superblock is
>
> I ran mke2fs to locate the backup superblocks:
>
> mke2fs -n /dev/mapper/vg_voinet01-lv_log
That will only tell you what mke2fs would do on that machine. I don't
know if it will be the same on every machine. You should probably run
dumpe2fs /dev/mapper/vg_voinet01-lv_log | grep
This is CentOS-6x.
I have cloned the HDD of a CentOS-6 system. I booted a host with that drive
and received the following error:
checking filesystems
/dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000
blocks
/dev/sda1: clean, 47/120016 files, 80115/512000 blocks
5 matches
Mail list logo