Label missing or mounting issue from my HDD (can't found the data anymore)

Hi,

I was doing some test on the transfer speed on my HDDs and the ones i was testing seems to have lost their mapping with their labels, that's really weird i hope i didnt erase them by accident...

By running:

blkid -o full

I have the results:

/dev/sdg1: LABEL="Autre" UUID="380b65e9-771c-4996-abbe-3efbe4c64981" TYPE="ext4" PARTUUID="44672ec2-e421-4871-911d-a4489debb0f5"
/dev/sdb1: PARTUUID="fc2dc338-bce2-4760-9b90-816cd3980796"
/dev/sdc1: PARTUUID="b6a51930-60e2-493a-a901-f9f8f0fc199a"

and by running:

 ls -la /srv

I have:

drwxrwxrwx  3 root root    4096 févr. 14 14:58 dev-disk-by-label-Films
drwxrwxrwx  3 root root    4096 févr. 14 14:58 dev-disk-by-label-Telechargement
drwxr-xr-x  4 root root    4096 oct.  23 18:51 dev-disk-by-label-Autre

As you can see sdb1 and sdbc1 are not mapped to their system file "Films" and "Telechargement"

lsblk


NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sdb      8:16   0  10,9T  0 disk
└─sdb1   8:17   0  10,9T  0 part
sdc      8:32   0   1,8T  0 disk
└─sdc1   8:33   0   1,8T  0 part
sdg      8:96   0   3,7T  0 disk
└─sdg1   8:97   0   3,7T  0 part /srv/dev-disk-by-label-Autre

How to remapp them without loosing my data (if they are still there)?

Thank you

Anybody would have any idea?

Thank you

Hey guys

please i really some help on this one

Zitat von macom

What do you see in "filesystems" in the GUI of OMV?

Maybe you just need to mount the two filesystems on sdb1 and sdc1

How are the drives connected? USB?

It’s missing and they are connected via sata no raid.

Zitat von geaves

I don't think it's the label it appears to be the file system look at the output on blkid you could run fsck /dev/sdb

fsck from util-linux 2.33.1
e2fsck 1.45.5 (07-Jan-2020)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

I already tried to fixed it without success

Zitat von geaves

Look at the output, the superblock is corrupt, doing a search I've found this which might be helpful

The process stopped quickly:

dumpe2fs /dev/sdc | grep superblock
dumpe2fs 1.45.5 (07-Jan-2020)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdc
Found a gpt partition table in /dev/sdc
Couldn't find valid filesystem superblock

Is my data lost?

Zitat von geaves

run it again but as dumpe2fs /dev/sdc1 | grep superblock

dumpe2fs 1.45.5 (07-Jan-2020)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdc1
Couldn't find valid filesystem superblock.

Same without the gpt info

Thanks for you help!

I ended up formatting my drive...there was no important data but still.