LVM storage problem. DATA Lost?

nastorrent · 10. Oktober 2013

Hello,

I'm on OMV 0.4.38.
Setup: 1 small System Disk, and 3 HD (2Tb,2Tb,400Gb) for storage. These 3 disk are on a LVM Volume made with LVM2 Plugin.

The LVM volume suddenly appears unmounted.

If I try to mount it again via Webmanager, I get this error:

"The configuration object is not unique: A mount point already exists for the given filesystem"

under details:

Error #3005:
exception 'OMVException' with message 'The configuration object is not unique: A mount point already exists for the given filesystem' in /var/www/openmediavault/rpc/filesystemmgmt.inc:682
Stack trace:
#0 [internal function]: FileSystemMgmtRpc->mount(Array)
#1 /usr/share/php/openmediavault/rpc.inc(265): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(98): OMVRpc::exec('FileSystemMgmt', 'mount', Array)
#3 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
#4 {main}

So I can't access to ALL my data. Any idea to fix this without losing ALL DATA.
I think that maybe the 400Gb HD (the older one) is failing, Is it possible to recover SOME DATA that is not striped to that HD?

If you need more data about config or something please tell me.

Thanks.

davidh2k · 10. Oktober 2013

login via ssh or locall on your machine via root and type in:

Code

mount -a

Greetings
David

nastorrent · 10. Oktober 2013

Thanks,

Here is the output:

Code

mount: /dev/mapper/ALMACEN-4TB: can't read superblock
mount: special device /media/328a7599-e7bb-4299-9c43-f83d8e36fde1/PELICULAS does not exist
mount: special device /media/328a7599-e7bb-4299-9c43-f83d8e36fde1/MUSICA does not exist
mount: special device /media/328a7599-e7bb-4299-9c43-f83d8e36fde1/PELICULAS_3D does not exist
mount: special device /media/328a7599-e7bb-4299-9c43-f83d8e36fde1/SERIES does not exist
mount: special device /media/328a7599-e7bb-4299-9c43-f83d8e36fde1/DOCUMENTALES does not exist
mount: special device /media/328a7599-e7bb-4299-9c43-f83d8e36fde1/TORRENT does not exist

Any idea?
Thanks

nastorrent · 10. Oktober 2013

Output of:

Code

blkid
/dev/sda1: UUID="9a9df990-5e8e-4deb-899f-001acff9f10f" TYPE="ext4"
/dev/sda5: UUID="30da3a9b-14c1-435b-b754-77d4fe236074" TYPE="swap"
/dev/sdc: UUID="JVrGeK-O2Sv-3Fqa-nb25-BEhN-VVeW-x5Ac0C" TYPE="LVM2_member"
/dev/sdb: UUID="LYl6LT-3eMs-QhiC-160A-Wm4B-hzue-xylPj6" TYPE="LVM2_member"
/dev/sdd: UUID="DZ8ORs-YP9z-rFnK-khmN-yY3o-ei5j-V31TGf" TYPE="LVM2_member"
/dev/mapper/ALMACEN-4TB: LABEL="LV4TB" UUID="328a7599-e7bb-4299-9c43-f83d8e36fde1" TYPE="xfs"

nastorrent · 10. Oktober 2013

Output of:

Code

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=9a9df990-5e8e-4deb-899f-001acff9f10f /               ext4    errors=remount -ro 0       1
# swap was on /dev/sda5 during installation
UUID=30da3a9b-14c1-435b-b754-77d4fe236074 none            swap    sw  0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
tmpfs           /tmp            tmpfs   defaults        0       0
# >>> [openmediavault]
UUID=328a7599-e7bb-4299-9c43-f83d8e36fde1 /media/328a7599-e7bb-4299-9c43-f83d8e3                                                                                                             6fde1 xfs defaults,noexec,usrquota,grpquota 0 2
/media/328a7599-e7bb-4299-9c43-f83d8e36fde1/PELICULAS /home/ftp/PELICULAS none bind 0 0
/media/328a7599-e7bb-4299-9c43-f83d8e36fde1/MUSICA /home/ftp/MUSICA none bind 0                                                                                                              0
/media/328a7599-e7bb-4299-9c43-f83d8e36fde1/PELICULAS_3D /home/ftp/PELICULAS_3D                                                                                                              none bind 0 0
/media/328a7599-e7bb-4299-9c43-f83d8e36fde1/SERIES /home/ftp/SERIES none bind 0                                                                                                              0
/media/328a7599-e7bb-4299-9c43-f83d8e36fde1/DOCUMENTALES /home/ftp/DOCUMENTALES                                                                                                              none bind 0 0
/media/328a7599-e7bb-4299-9c43-f83d8e36fde1/TORRENT /home/ftp/TORRENT none bind                                                                                                              0 0
# <<< [openmediavault]

Alles anzeigen

nastorrent · 10. Oktober 2013

Output of

Code

fdisk -l


Disk /dev/sda: 10.2 GB, 10242892800 bytes
255 heads, 63 sectors/track, 1245 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00058a7b


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1189     9541632   83  Linux
/dev/sda2            1189        1246      458753    5  Extended
/dev/sda5            1189        1246      458752   82  Linux swap / Solaris


Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdc doesn't contain a valid partition table


Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdd doesn't contain a valid partition table


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.




Disk /dev/sdb: 400.1 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdb doesn't contain a valid partition table


Disk /dev/dm-0: 4400.9 GB, 4400881860608 bytes
255 heads, 63 sectors/track, 535043 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/dm-0 doesn't contain a valid partition table

Alles anzeigen

nastorrent · 11. Oktober 2013

Still Trying...

Output of

Code

xfs_repair /dev/mapper/ALMACEN-4TB
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
xfs_repair: read failed: Error de entrada/salida
XFS: empty log check failed
zero_log: cannot find log head/tail (xlog_find_tail=5), zeroing it anyway
        - scan filesystem freespace and inode maps...
sb_icount 9728, counted 20416
sb_ifree 321, counted 263
sb_fdblocks 770238950, counted 669020665
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 16
        - agno = 17
        - agno = 18
        - agno = 19
        - agno = 20
        - agno = 21
        - agno = 22
        - agno = 23
        - agno = 24
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
Note - quota info will be regenerated on next quota mount.
done

Alles anzeigen

nastorrent · 11. Oktober 2013

After xfs_repair I disabled all HD options (APM,AAC,Spindown,SMART), and it mounted.

CIFS doesn't work, but i'm doing a backup via FTP to change HD an reinstall OMV.

Thanks

I think it's solved, at least to backup data.

PhantomSens · 13. Oktober 2013

You may want to check the drive connections.

I had a similar issue about six months ago and it turned out I had not fully seated the power connector for the drive. The system was on for about a month when the problems started. Was concerned about a bad drive. Once I properly seated the power connector all was well and has been for since.

nastorrent · 14. Oktober 2013

Thanks,

connections are good. I backup all the data, and removed that old 400Gb HD and reinstalled OMV.

Now It works OK

Thanks

Jetzt mitmachen!