Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Mounting Linux raid partition to save 14tb data

  1. #1
    Join Date
    May 2020
    Beans
    14

    Mounting Linux raid partition to save 14tb data

    Hello to the kind people those are reading this post.

    I'm not really a Linux guy who knows how to do everything, i have followed some post on this and many other sites to solve my problem but not one post could help me but maybe you can.

    storytime:
    I have a Dell R720 server installed with ESXi 6.7 within ESXi I have made a virtual machine with Xpenology (DSM from synology) I gave this Virtual Machine a Virtual disk of 14 TB, but for some reason I can't acces my data by GUI or terminal. DSM says the storage pool has been crashed. but the Virtual Disk is there.

    I know this is a problem i should post on xpenology but i think i have more options with you people and ubuntu. if someone could help me I would be glad.

    I have installed a ubuntu virtual machine and connected the 14tb Virtual disk to it.


    Output of fdisk -l
    Code:
    root@vincent-virtual-machine:~# fdisk -l
    Disk /dev/loop0: 27,9 MiB, 28405760 bytes, 55480 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop1: 54,97 MiB, 57614336 bytes, 112528 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop2: 240,82 MiB, 252493824 bytes, 493152 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop3: 62,9 MiB, 65105920 bytes, 127160 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop4: 49,8 MiB, 52203520 bytes, 101960 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop5: 54,97 MiB, 57618432 bytes, 112536 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/loop6: 255,58 MiB, 267980800 bytes, 523400 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    
    
    Disk /dev/sda: 50 GiB, 53687091200 bytes, 104857600 sectors
    Disk model: Virtual disk    
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x5dba0cc6
    
    Device     Boot   Start       End   Sectors  Size Id Type
    /dev/sda1  *       2048   1050623   1048576  512M  b W95 FAT32
    /dev/sda2       1052670 104855551 103802882 49,5G  5 Extended
    /dev/sda5       1052672 104855551 103802880 49,5G 83 Linux
    
    
    Disk /dev/sdb: 14 TiB, 15393162788864 bytes, 30064771072 sectors
    Disk model: Virtual disk    
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: F1A69B9D-FE35-440B-8201-A9A1C670D8FB
    
    Device       Start         End     Sectors  Size Type
    /dev/sdb1     2048     4982527     4980480  2,4G Linux RAID
    /dev/sdb2  4982528     9176831     4194304    2G Linux RAID
    /dev/sdb3  9437184 30064566271 30055129088   14T Linux RAID
    
    
    Disk /dev/mapper/osprober-linux-sdb3: 13,102 TiB, 15388226093056 bytes, 30055129088 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/md2: 13,102 TiB, 15388225044480 bytes, 30055127040 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Output of mdadm --examine /dev/sd*
    Code:
    root@vincent-virtual-machine:~# mdadm --examine /dev/sd*
    /dev/sda:
       MBR Magic : aa55
    Partition[0] :      1048576 sectors at         2048 (type 0b)
    Partition[1] :    103802882 sectors at      1052670 (type 05)
    /dev/sda1:
       MBR Magic : aa55
    /dev/sda2:
       MBR Magic : aa55
    Partition[0] :    103802880 sectors at            2 (type 83)
    mdadm: No md superblock detected on /dev/sda5.
    /dev/sdb:
       MBR Magic : aa55
    Partition[0] :   4294967295 sectors at            1 (type ee)
    mdadm: No md superblock detected on /dev/sdb1.
    mdadm: No md superblock detected on /dev/sdb2.
    /dev/sdb3:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : e83b0c59:a57672c5:81bc8de6:2ee43ed4
               Name : VinflixDSM:2
      Creation Time : Fri Jan 17 23:37:33 2020
         Raid Level : raid1
       Raid Devices : 1
    
     Avail Dev Size : 30055127040 (14331.40 GiB 15388.23 GB)
         Array Size : 15027563520 (14331.40 GiB 15388.23 GB)
        Data Offset : 2048 sectors
       Super Offset : 8 sectors
       Unused Space : before=1968 sectors, after=0 sectors
              State : clean
        Device UUID : ea70f066:9d36166a:ff7b1eef:15a0369c
    
        Update Time : Fri May  8 16:00:55 2020
           Checksum : 7763dc4e - correct
             Events : 192
    
    
       Device Role : Active device 0
       Array State : A ('A' == active, '.' == missing, 'R' == replacing)
    Last edited by rihc0; May 9th, 2020 at 01:23 AM.

  2. #2
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Mounting Linux raid partition to save 14tb data

    Moved to the server sub-forum where users may be able to help.
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  3. #3
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,377
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Mounting Linux raid partition to save 14tb data

    This might be complicated because you have multiple layers... First VMware, then Synology.

    I see in fdisk output there is some md2 device mentioned. Lets see what it has. Post the output of:
    Code:
    cat /proc/mdstat
    sudo mdadm -D /dev/md2
    Don't do anything else at the moment because wrong step during such rescue can make it much more difficult to save the data.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  4. #4
    Join Date
    May 2020
    Beans
    14

    Re: Mounting Linux raid partition to save 14tb data

    I thought so too, but it should not make a difference I think because it is a virtual disk and it only sees the content of the virtual disk and not evetyhing under the virtual disk if you know what I'm saying. (sometimes I'm terrible at explaining things)

    i have made a snapshot of the machine, I have tried some things before but nothing import.




    Code:
    root@VinflixDSM:~# cat /proc/mdstat
    Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] 
    md2 : active raid1 sdb3[0]
          15027563520 blocks super 1.2 [1/1] [U]
          
    md1 : active raid1 sdb2[0]
          2097088 blocks [12/1] [U___________]
          
    md0 : active raid1 sdb1[0]
          2490176 blocks [12/1] [U___________]
          
    unused devices: <none>
    root@VinflixDSM:~# sudo mdadm -D /dev/md2
    /dev/md2:
            Version : 1.2
      Creation Time : Fri Jan 17 23:37:33 2020
         Raid Level : raid1
         Array Size : 15027563520 (14331.40 GiB 15388.23 GB)
      Used Dev Size : 15027563520 (14331.40 GiB 15388.23 GB)
       Raid Devices : 1
      Total Devices : 1
        Persistence : Superblock is persistent
    
        Update Time : Sat May  9 05:30:13 2020
              State : clean 
     Active Devices : 1
    Working Devices : 1
     Failed Devices : 0
      Spare Devices : 0
    
               Name : VinflixDSM:2  (local to host VinflixDSM)
               UUID : e83b0c59:a57672c5:81bc8de6:2ee43ed4
             Events : 192
    
        Number   Major   Minor   RaidDevice State
           0       8       19        0      active sync   /dev/sdb3
    root@VinflixDSM:~#
    Last edited by rihc0; May 9th, 2020 at 12:19 PM.

  5. #5
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,377
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Mounting Linux raid partition to save 14tb data

    Well, that superblock looks OK. I don't know which filesystem is used. Not sure if blkid would show. Try:
    Code:
    sudo blkid
    If the filesystem on md2 is ext4 or similar, you can try mounting it temporarily as read-only. Don't mount it for writes, to make sure nothing is written on md2 yet.
    Code:
    sudo mount -o ro /dev/md2 /mnt
    ls /mnt
    Does that show any folder structure?

    The mount command might fail depending on how all of this is integrated one into the other. If this was a simple ubuntu server setup reading the array would be easy. But with VMware and Synology in the way, I don't know.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  6. #6
    Join Date
    May 2020
    Beans
    14

    Re: Mounting Linux raid partition to save 14tb data

    Something happend with the ubuntu virtual machine, I gotta re install it real quick

  7. #7
    Join Date
    May 2020
    Beans
    14

    Re: Mounting Linux raid partition to save 14tb data

    Code:
    rihc0@rihc0-virtual-machine:~$ sudo -i
    [sudo] password for rihc0: 
    root@rihc0-virtual-machine:~# blkid
    /dev/sda5: UUID="47bb378a-0048-4020-9309-aed57c800ec7" TYPE="ext4" PARTUUID="90e57f28-05"
    /dev/loop0: TYPE="squashfs"
    /dev/loop1: TYPE="squashfs"
    /dev/loop2: TYPE="squashfs"
    /dev/loop3: TYPE="squashfs"
    /dev/loop4: TYPE="squashfs"
    /dev/sda1: UUID="5E00-3EED" TYPE="vfat" PARTUUID="90e57f28-01"
    /dev/sdb1: UUID="703fe7fc-5125-5f38-3017-a5a8c86610be" TYPE="linux_raid_member" PARTUUID="cbe8ba00-3f3d-4d36-813c-f3c2c3a7cb09"
    /dev/sdb2: UUID="60b54d3a-8cf2-9066-3017-a5a8c86610be" TYPE="linux_raid_member" PARTUUID="57e012c2-78a6-4857-a17e-b4d54ec8267b"
    /dev/sdb3: UUID="e83b0c59-a576-72c5-81bc-8de62ee43ed4" UUID_SUB="ea70f066-9d36-166a-ff7b-1eef15a0369c" LABEL="VinflixDSM:2" TYPE="linux_raid_member" PARTUUID="d0f620c8-3760-4644-b578-55c26c8bee4e"
    root@rihc0-virtual-machine:~# mount -o ro /dev/md2 /mnt
    mount: /mnt: special device /dev/md2 does not exist.
    root@rihc0-virtual-machine:~# ls /mnt
    root@rihc0-virtual-machine:~# ls -al /mnt
    total 8
    drwxr-xr-x  2 root root 4096 apr 23 09:32 .
    drwxr-xr-x 20 root root 4096 mei  9 13:40 ..
    root@rihc0-virtual-machine:~#

    as you said the mount failed, i used btrfs i think, but not sure

  8. #8
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,377
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Mounting Linux raid partition to save 14tb data

    Yeah but right now it failed because md2 doesn't even exist. It doesn't show in blkid.

    I actually missed the part that you are you doing this in a virtual machine. I thought you took one disk and connected it to your desktop or something.

    The virtual disk is reported as failed I believe. In such case I doubt a new VM would see it correctly.

    But why do partitions report as "linux_raid_member" in blkid output? The VM should not see that part. VMware and then Synology will take care of the virtualization and the VMs see the vHDDs as standard disks. I don't get this...

    In any case, if you want to try you need to assemble md2 first, and then try to mount read-only and check content. In case that works it would be something like:
    Code:
    sudo mdadm --assemble --verbose /dev/md2 /dev/sdb3
    sudo mount -o ro /dev/md2 /mnt
    ls /mnt
    But honestly, I think you need to look at this from the start. For example, if VMware was the first thing you installed, and if it uses the big data disks as datastores, what is the status in VMware? What does it say for its datastore status?
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  9. #9
    Join Date
    May 2020
    Beans
    14

    Re: Mounting Linux raid partition to save 14tb data

    Code:
    root@rihc0-virtual-machine:~# sudo mdadm --assemble --verbose /dev/md2 /dev/sdb3
    mdadm: looking for devices for /dev/md2
    mdadm: /dev/sdb3 is busy - skipping
    root@rihc0-virtual-machine:~# sudo mount -o ro /dev/md2 /mnt
    mount: /mnt: wrong fs type, bad option, bad superblock on /dev/md2, missing codepage or helper program, or other error.
    root@rihc0-virtual-machine:~# ls /mnt
    root@rihc0-virtual-machine:~#
    the datastore in ESXi seems to be okay, i can still use it and DSM also boots.

  10. #10
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,377
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Mounting Linux raid partition to save 14tb data

    sdb3 might be part of differently named array now. Check again with:
    Code:
    cat /proc/mdstat
    If both ESXi and DSM show fine, what actually crashed? Where was the raid array? Please explain little the setup.

    Did you assign multiple virtual HDDs to the VM and created mdadm array from them?

    I don't know DSM but since that is the next layer, check in DSM the storage status and what it says about the virtual HDD file of interest.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •