[SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-500P)

Printers, HDDs, USB/eSATA drives, 3rd-party programs
User avatar
father_mande
Experience counts
Posts: 4991
Joined: Mon Oct 06, 2008 6:52 pm
Location: Saint Mande, France

[SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-500P)

Postby father_mande » Fri May 23, 2014 6:56 pm

Hi,
****** Having a backup is ALWAYS the best solution

****** AS YOU KNOW ... new SMB firmware use LVM (Logical Volume Manager) under Raid to create volume for file system
****** DATA RECOVER in case of QNAP's stop, is less easy than reassemble the Raid and mount the file system
****** It's risky ... but if you are at "recover" state ... BUT I CAN'T GUARANTEE ANY THINGS ... this require LINUX knowledge and some experience , and I am not responsible for your own manipulations ...

Hereafter a short information (before I hope to have time) a better and longer explain on (or a video) ... BUT BASED on real experience :

How-to use a USB3(2) extension box connected to a PC and HOW read (write) the contents (Volume on a Raid group) after a system crash (not disk ... even), or to read some data outside the QNAP
ADD : use also an UX-500P as extension ...
... THIS can be extend to any volumes put in a REXP or in external or internal slot of a PC. IT'S ABSOLUTELY THE SAME MECHANISM

How UX500P is identified by the PC ... ex. on Windows ... (I presume that you KNOW how volume are organized inside the REXP, or internally if you extract internal disk use "localize" function to identify each)
... In fact UX500 is recognize by windows as
... ... USB3 multiple Hub based on MT 1051 (Asmedia controller)
... ... external disk ... YES you can see the disk and partition (5 on S.M.B.)
... ... as 3 others disks ?? (perhaps a card controller ??? ) Asmedia
... ... 2 Prolific asynchronous controller (suppose to exchange between QNAP and REXP .. for LCD, FAN control, etc.)

So it's seem to be possible to see the disks ... and perhaps the data ...

CREATE RECOVER LINUX SYSTEM :
Now You have to create an USB Linux stick for extending the luck to read the data ...
After analyse I have selected to create The USB Linux using UNetbootin
... I have choiced Linux Ubuntu 14.04 LTS (in fact Kubuntu ... I prefer KDE to Gnome)
... to have LVM2 ... I create the Linux system on a separate disk (USB3 Lexar stick (32GB)) ... using LVM2 (to have it for QNAP volume later)
... after running ... I add mdadm software to be able to manage software Raid ...
... also NTSF-3G can be installed if you want to copy some data to internal PC with Windows disks ... others USB external can be use also

HOW-TO ...
FIRST you must understand that DISK are NOT always ordered (also in UX-500P) when you put it in extension box[/b][/color] ... so for ex.
On my PC (4 CPU I5 + 1 one SATA disk)
/dev/sda is the internal PC disk
/dev/sdc is the first bay of my UX-500P extension box
/dev/sdf is the second bay of my UX-500P ... etc.
SO the best solution is to plug ONLY one disk when connecting the extension box, then enter one by one the other disks and use dmesg to have each device identified , so you can ordered the device respectively ...

UNDERSTAND VOLUME IN QNAP :
Volume are LVM volume on VG group UNDER software Raid ... so the procedure is easy (all is relative)

1 recreate the software Raid (after all disks impacted are plugged)
The easy way ... if you have re-plug only the disk use by the QNAP volume is
mdadm --assemble --scan
... the response is "normally" that Raid and disk in the Raid are identified ... in case of failure do as usual manual assemble using disk device ... eventually rebuild from superblock
ATTENTION with this "scan" ALL Raid (system part, swap (2), system extension) are identified DEVICE ...
DON'T TRY TO MOUNT IT ...
At this moment the Raid is identified and define

2 scan the VG of LVM ... the normal response is that VG is identified by LVM
vgscan
... get the vgname (generally vg1 for first volume, vg2 for the second, vg3 etc. ) because QNAP don't use (it's a good idea) specific name for each ...
3 verify that all is correct using vgdisplay and lvdispaly command
4 mount the volume
mkdir /mnt/myvol
mount /dev/lv2/vg2 /mnt/myvol
(adapt the device path to the name listed here before)

AT THIS POINT ... you can read and write in the QNAP volume (user space) ...

HOW-TO re-plug and reuse the volume in the QNAP
TWO ways depend of :
A ) You have ONLY read data and file ...

Stop the PC where extension box is connected (also for UX-500P)
re-plug disk AT THE SAME PLACE as before in the QNAP
OR for UX-500P replug it on USB3 connector of the QNAP
open "storage management" and do a recover ... it's all

B ) The better way (longer) BUT mandatory if you write any things inside the volume ...

On the PC before stopping and unplug ... do :
1 umount of the mounted volume (ex. umount /mnt/myvol)
2 put VG in deactivate state
vgchange -an vgname (this clean the PC structure)
3 export the vg as you want to move it ... so you are sure that all VG information are IN the disk itself ...
vgexport vgname
...
stop the PC
re-plug at same place as before (even in theory ... ) the disk at the good (previous one) place THE QNAP is UP and running (or boot without disk in case it's vg1)
verify in storage management ... that disk is recognize ...
... you can test a recover BUT
... you have 99% of risk that recovery don't work
open a ssh/telnet console and do :
pvscan ... to verify that pv is recognize
vgdisplay ... to verify the vg name ... in case you forget it
vgimport vgname (re-import structure)
vgchange -ay vgname activate the VG ...

OK all is correct BUT at this point the mount point use by QNAP is NOT created and NOT know if you don't have get it before ...
Best (MANDATORY IF VG1) ... do a reboot ... and all come back at the good place with the good mount point, share, etc.

alternative REALLY DANGEROUS AND NOT A GOOD IDEA ... if /dev/mapper is correctly created or if you can recreate it (MAJOR 253 MINOR 0 and 1 for VG1 named cachedev1 and vg1-lv1 , follow minor for others volumes) recreate the directory in /share
mkdir /share/CACHEDEVx_DATA (x = 2 or 3) then mount
mount /dev/mapper/cachedevX /share/CACHEDEVx_DATA

Now you have recover your data on your QNAP with shared resources, etc.

In fact they are LOT of others command to know ... in case of crash ...
... how-to rebuid and reassemble a partial or total Raid
... how-to recover a volume group
etc. etc. ... BUT on this base you are able :
Read your data in case the QNAP is OUT

With some extra command on QNAP ... you can move easily a volume to another Linux box
... BUT due to the hidden management (and some unknown procedure) ... I don't think it's possible with this to move a volume from a QNAP to another QNAP ... BUT QNAP's dev. can eventually manage this for the future ...

I have tested this procedure with :
Non encrypted volumes
One volume on Raid1 (2 disks)
One volume on Raid5 (3 disks)
volumes on UX-500P
volumes from Internal QNAP box
disks transferred to USB box (not QNAP)
UX-500P transferred as is to a PC
tested after a clean stop and a "power plug out" stop ...

BUT you can imagine the number of case ... so it's NOT a full test ... just a first one to make progress.
ALL COMMENT, REMARKS, PERSONAL EXPERIENCES, CORRECTIONS are WELCOME AND VERY APPRECIATE ... to create a more complete how-to

Philippe.
https://www.father-mande.ovh/
QNAP TS-109 Debian 9 stretch
QNAP TS-459, TS-219P II ... 4.2.6
QNAP TS-269, TS-431+, TAS-x68 ... 4.3.4
QNAP TS-x53, TVS-x73 + UX-500P ... 4.3.4
Qgenie

User avatar
father_mande
Experience counts
Posts: 4991
Joined: Mon Oct 06, 2008 6:52 pm
Location: Saint Mande, France

[SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby father_mande » Sat Jun 28, 2014 3:21 am

Hi,

AFTER real tests :

ADD UX-500P explain on recovering data ... from UX-500P extension ... no major change, just more information ...

Philippe.
https://www.father-mande.ovh/
QNAP TS-109 Debian 9 stretch
QNAP TS-459, TS-219P II ... 4.2.6
QNAP TS-269, TS-431+, TAS-x68 ... 4.3.4
QNAP TS-x53, TVS-x73 + UX-500P ... 4.3.4
Qgenie

bonsai
First post
Posts: 1
Joined: Thu Mar 28, 2013 9:11 pm

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby bonsai » Sat Jul 19, 2014 2:39 am

Hello, I'm trying to access a disk from a TS-469L with 1 sinlge volume (created as type thick). But it's not working. Mayby you can help me?

First i connect the disk to a pc with sata.
Then i perpare a usb stick with a ubuntu live and boot from it.
Next i install the LVM2 software package with the thin-provisioning-tools.

And then i do this steps:

Code: Select all

parted -l
    Model: ATA WDC WD800JD-55MU (scsi)
    Disk /dev/sda: 80,0GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos

    Number  Start   End     Size    Type     File system  Flags
    1      1049kB  368MB   367MB   primary  ntfs         boot
    2      368MB   52,4GB  52,1GB  primary  ntfs
    3      52,4GB  80,0GB  27,6GB  primary  ntfs


    Model: ATA SAMSUNG HD154UI (scsi)
    Disk /dev/sdb: 1500GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt

    Number  Start   End     Size    File system     Name     Flags
    1      20,5kB  543MB   543MB   ext3            primary
    2      543MB   1086MB  543MB   linux-swap(v1)  primary
    3      1086MB  1491GB  1490GB                  primary
    4      1491GB  1492GB  543MB   ext3            primary
    5      1492GB  1500GB  8554MB  linux-swap(v1)  primary


    Warning: Unable to open /dev/sr0 read-write (Das Dateisystem ist nur lesbar).
    /dev/sr0 has been opened read-only.
    Error: /dev/sr0: unrecognised disk label                                 

    Error: /dev/zram0: unrecognised disk label                               

    Warning: Unable to open /dev/cloop0 read-write (Das Dateisystem ist nur lesbar).
    /dev/cloop0 has been opened read-only.
    Error: /dev/cloop0: unrecognised disk label

Code: Select all

mdadm --assemble --scan
    mdadm: /dev/md/321 has been started with 1 drive (out of 2).
    mdadm: /dev/md/13 has been started with 1 drive (out of 24).
    mdadm: /dev/md/2 has been started with 1 drive.
    mdadm: /dev/md/256 assembled from 0 drives and 1 spare - not enough to start the array.
    mdadm: /dev/md/9 has been started with 1 drive (out of 24).
    mdadm: /dev/md/256 assembled from 0 drives and 1 spare - not enough to start the array.

Code: Select all

cat /proc/mdstat
    Personalities : [raid1]
    md9 : active raid1 sdb1[25]
          530048 blocks super 1.0 [24/1] [__U_____________________]
          bitmap: 1/1 pages [4KB], 65536KB chunk

    md2 : active raid1 sdb3[0]
          1455183616 blocks super 1.0 [1/1] [U]
         
    md13 : active raid1 sdb4[25]
          458880 blocks super 1.0 [24/1] [__U_____________________]
          bitmap: 1/1 pages [4KB], 65536KB chunk

    md321 : active raid1 sdb5[0]
          8353728 blocks super 1.0 [2/1] [U_]
          bitmap: 1/1 pages [4KB], 65536KB chunk

    unused devices: <none>

Code: Select all

lvscan
      WARNING: Unrecognised segment type thin-pool
      WARNING: Unrecognised segment type thick
      inactive          '/dev/vg2/lv545' [13,88 GiB] inherit
      inactive          '/dev/vg2/tp2' [1,33 TiB] inherit
      inactive          '/dev/vg2/lv2' [1,32 TiB] inherit

Code: Select all

vgdisplay
      WARNING: Unrecognised segment type thin-pool
      WARNING: Unrecognised segment type thick
      --- Volume group ---
      VG Name               vg2
      System ID             
      Format                lvm2
      Metadata Areas        1
      Metadata Sequence No  6
      VG Access             read/write
      VG Status             resizable
      MAX LV                0
      Cur LV                3
      Open LV               0
      Max PV                0
      Cur PV                1
      Act PV                1
      VG Size               1,36 TiB
      PE Size               4,00 MiB
      Total PE              355269
      Alloc PE / Size       355269 / 1,36 TiB
      Free  PE / Size       0 / 0   
      VG UUID               2ktkBf-OyrR-eZub-NSMN-25gh-Lqyc-Ta0Vvu

So, the shown warnings confuse me.

Code: Select all

lvdisplay
      WARNING: Unrecognised segment type thin-pool
      WARNING: Unrecognised segment type thick
      --- Logical volume ---
      LV Path                /dev/vg2/lv545
      LV Name                lv545
      VG Name                vg2
      LV UUID                OAoDN1-l61r-PxPb-jSmo-vAZr-tzWY-bWdNOS
      LV Write Access        read/write
      LV Creation host, time QNAPTS469L, 2014-07-08 23:28:04 +0200
      LV Status              NOT available
      LV Size                13,88 GiB
      Current LE             3552
      Segments               1
      Allocation             inherit
      Read ahead sectors     4096
       
      --- Logical volume ---
      LV Path                /dev/vg2/tp2
      LV Name                tp2
      VG Name                vg2
      LV UUID                7yu5BA-oiTW-LPOs-auKR-1FgA-d0FA-gjdDV0
      LV Write Access        read/write
      LV Creation host, time QNAPTS469L, 2014-07-08 23:28:14 +0200
      LV Status              NOT available
      LV Size                1,33 TiB
      Current LE             347621
      Segments               1
      Allocation             inherit
      Read ahead sectors     auto
       
      --- Logical volume ---
      LV Path                /dev/vg2/lv2
      LV Name                lv2
      VG Name                vg2
      LV UUID                lZeI1R-O5M2-Gjtx-Y1Qu-cZYQ-4xNQ-WzJ0wL
      LV Write Access        read/write
      LV Creation host, time QNAPTS469L, 2014-07-08 23:28:18 +0200
      LV Status              NOT available
      LV Size                1,32 TiB
      Current LE             347108
      Segments               1
      Allocation             inherit
      Read ahead sectors     4096

With loading the needed modules for lvm ...

Code: Select all

modprobe dm_mod
lsmod| grep dm_
    dm_thin_pool           45785  0
    dm_persistent_data     54412  1 dm_thin_pool
    dm_bufio               22204  1 dm_persistent_data
    dm_bio_prison          14968  1 dm_thin_pool
    libcrc32c              12543  2 btrfs,dm_persistent_data
    dm_crypt               22622  0
    dm_multipath           22402  0
    scsi_dh                14458  1 dm_multipath
    dm_mirror              21756  0
    dm_region_hash         20121  1 dm_mirror
    dm_log                 18072  2 dm_region_hash,dm_mirror

and last

Code: Select all

lvscan
      WARNING: Unrecognised segment type thick
      ACTIVE            '/dev/vg2/lv545' [13,88 GiB] inherit
      ACTIVE            '/dev/vg2/tp2' [1,33 TiB] inherit
      inactive          '/dev/vg2/lv2' [1,32 TiB] inherit

Why a get the message "Unrecognised segment type thick"? And what can i do to activate the /dev/vg2/lv2 and mount it?

Last information

Code: Select all

    root@ubuntu:/mnt# vgscan
      Reading all physical volumes.  This may take a while...
      WARNING: Unrecognised segment type thick
      Found volume group "vg2" using metadata type lvm2

Code: Select all

    root@ubuntu:/mnt# vgdisplay
      WARNING: Unrecognised segment type thick
      --- Volume group ---
      VG Name               vg2
      System ID             
      Format                lvm2
      Metadata Areas        1
      Metadata Sequence No  6
      VG Access             read/write
      VG Status             resizable
      MAX LV                0
      Cur LV                3
      Open LV               0
      Max PV                0
      Cur PV                1
      Act PV                1
      VG Size               1,36 TiB
      PE Size               4,00 MiB
      Total PE              355269
      Alloc PE / Size       355269 / 1,36 TiB
      Free  PE / Size       0 / 0   
      VG UUID               2ktkBf-OyrR-eZub-NSMN-25gh-Lqyc-Ta0Vvu


I hope, someone can help me?

As a next test, i install a clean and small disk (200GB) alone. Install the system on it and create a volume type thick on it. Then i do the above described steps. The same result :(

User avatar
father_mande
Experience counts
Posts: 4991
Joined: Mon Oct 06, 2008 6:52 pm
Location: Saint Mande, France

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby father_mande » Fri Jul 25, 2014 9:47 pm

Hi,

I have not tested yet with thin_pool ...

I think you need to add some parameters to inform LVM of the use ...
-n thin_pool
or -n thin_meta

I will run a test is some days ... (I am out of my office for now) ... and if i have some result, I will post here ...

sorry for the delay I have miss your message ...

Now teh forum ask me to login each time I try to enter in ... and keep only very last message from last connection ... even if before it keep more ... so now, sometimes a message is dropped out of the list before I can read it ...

Philippe.
https://www.father-mande.ovh/
QNAP TS-109 Debian 9 stretch
QNAP TS-459, TS-219P II ... 4.2.6
QNAP TS-269, TS-431+, TAS-x68 ... 4.3.4
QNAP TS-x53, TVS-x73 + UX-500P ... 4.3.4
Qgenie

markwaitangi
First post
Posts: 1
Joined: Thu Oct 02, 2014 12:37 pm

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby markwaitangi » Thu Oct 02, 2014 12:56 pm

Having a similar issue at the point of:

Code: Select all

 vgchange -ay

gets

Code: Select all

  WARNING: Unrecognised segment type thick
  Refusing activation of LV lv1 containing an unrecognised segment.
  2 logical volume(s) in volume group "vg1" now active

So does anyone have any ideas of how to over come this?

Also I have

Code: Select all

lvscan

Code: Select all

  WARNING: Unrecognised segment type thick
  ACTIVE            '/dev/vg1/lv544' [20.00 GiB] inherit
  ACTIVE            '/dev/vg1/tp1' [5.40 TiB] inherit
  inactive          '/dev/vg1/lv1' [5.39 TiB] inherit


So basically how to make either the WRNING go away or the inactive to become ACTIVE
Thanks in advance

JeffryPaul
New here
Posts: 6
Joined: Tue Dec 02, 2014 3:59 pm

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby JeffryPaul » Tue Dec 02, 2014 6:13 pm

after installing the "thin-provisioning-tools" package, I was able to step past the thin-pool problem. Now I'm stuck with the vg1 not being activated due to the invalid "thick" segment type, which appears to be unique to QNAP, since there is no LVM documentation supporting such a segment type. Reviewed the segtype.h file in the lvm2 project found here: https://git.fedorahosted.org/cgit/lvm2.git

Thankfully I am just getting started with QNAP backup, and recovering from a NAS failure is one of my test cases. I would have expected QNAP to provide some assistance by now.

User avatar
father_mande
Experience counts
Posts: 4991
Joined: Mon Oct 06, 2008 6:52 pm
Location: Saint Mande, France

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby father_mande » Tue Dec 02, 2014 10:51 pm

Hi,

Best is to ask directly QNAP through the helpdesk ... if you obtain a response ?

I have not yet started test with thin-pro ... due to the lack of disks ... I just purchased 2 news ... so now I can try ... , but like you I do tests ... sometimes with success sometimes with crash ...

If I have some success ... I will write here the result.

"Invalid thinck segment" can be caused by a different level of thin provisioning or LVM2 software ... did you use a minimum of Ubuntu 14.04 LTS or equivalent in other diftro. ??

Philippe.
https://www.father-mande.ovh/
QNAP TS-109 Debian 9 stretch
QNAP TS-459, TS-219P II ... 4.2.6
QNAP TS-269, TS-431+, TAS-x68 ... 4.3.4
QNAP TS-x53, TVS-x73 + UX-500P ... 4.3.4
Qgenie

bbbh
New here
Posts: 4
Joined: Wed Oct 24, 2012 8:43 am

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby bbbh » Mon Feb 02, 2015 7:23 pm

Did you try solving that issue with the segment type as thick? I am currently in that situation with running a live ubuntu usb of 14.04. I get to your part of activating the volume group but having the wrong segment type since it is thick. I have been searching all weekend on how to mount it.

User avatar
father_mande
Experience counts
Posts: 4991
Joined: Mon Oct 06, 2008 6:52 pm
Location: Saint Mande, France

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby father_mande » Mon Feb 02, 2015 7:30 pm

Hi,
bbbh wrote:Did you try solving that issue with the segment type as thick? I am currently in that situation with running a live ubuntu usb of 14.04. I get to your part of activating the volume group but having the wrong segment type since it is thick. I have been searching all weekend on how to mount it.


I work on it ... unfortunately ... my QNAP seems to be broken ... I don't know why (I am at 600 Kms of my S.M.B. QNAP)
... I can't continue my tests ... before I solve my own problem ... and only when I can be near my QNAP ... in a week ...

So sorry if I can't try to send you more information ... (and QNAP is not my first and major activity ... :lol: )

Philippe.
https://www.father-mande.ovh/
QNAP TS-109 Debian 9 stretch
QNAP TS-459, TS-219P II ... 4.2.6
QNAP TS-269, TS-431+, TAS-x68 ... 4.3.4
QNAP TS-x53, TVS-x73 + UX-500P ... 4.3.4
Qgenie

Corsari
New here
Posts: 4
Joined: Sun Feb 15, 2015 10:36 pm

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby Corsari » Sun Feb 15, 2015 11:47 pm

Same issue here

At first sight many LV inactive

With both thin and thick warnings

After installing "thin" modules, all of them became active except one

Either if googling so much, results that this "thick" issue is always on a webpage that talks about QNAP, it is a standard "lvscan" command that reports the warning... and since "lvscan" is run on a ubuntu OS with apt-get installed LVM2 suite + thin provisioning... the message is not QNAP specific, it is built in into the "lvscan" binary.

Maybe the LVM2 mailing list could help. I've written a ticket on QNAP support ticketing system, but I'll try also the mailing list.

louiscar
Know my way around
Posts: 204
Joined: Mon Aug 10, 2015 4:32 am

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-500P)

Postby louiscar » Tue Aug 25, 2015 9:43 pm

father_mande wrote:Hi,
****** Having a backup is ALWAYS the best solution

****** AS YOU KNOW ... new SMB firmware use LVM (Logical Volume Manager) under Raid to create volume for file system


Phillipe, do you know if LVM is used regardless?
I'm wondering if this is only used when thick or thin provisioning is chosen. Perhaps it uses the old system when choosing fixed?
Model : TS-453 Pro
Firmware : 4.3.3.0262
2x WD RED 3TB - Raid 1

User avatar
schumaku
Guru
Posts: 42777
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-500P)

Postby schumaku » Tue Aug 25, 2015 10:21 pm

louiscar wrote:Phillipe, do you know if LVM is used regardless?
I'm wondering if this is only used when thick or thin provisioning is chosen. Perhaps it uses the old system when choosing fixed?
All new volume types - static, thin, and thick allocated - are LVM based volumes.

louiscar
Know my way around
Posts: 204
Joined: Mon Aug 10, 2015 4:32 am

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-500P)

Postby louiscar » Tue Aug 25, 2015 11:17 pm

schumaku wrote: All new volume types - static, thin, and thick allocated - are LVM based volumes.

Thanks for the clarification
Model : TS-453 Pro
Firmware : 4.3.3.0262
2x WD RED 3TB - Raid 1

alyf80
New here
Posts: 2
Joined: Fri Jan 23, 2015 1:50 am

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby alyf80 » Sun Sep 06, 2015 5:43 am

JeffryPaul wrote:after installing the "thin-provisioning-tools" package, I was able to step past the thin-pool problem. Now I'm stuck with the vg1 not being activated due to the invalid "thick" segment type, which appears to be unique to QNAP, since there is no LVM documentation supporting such a segment type. Reviewed the segtype.h file in the lvm2 project found here: https://git.fedorahosted.org/cgit/lvm2.git


Apparently QNAP extended the standard thin provisioning model of LVM2 in order to support new features (my guess is that this has to do with the ability to have thick-provisioned volumes within a thin-provisioning pool, which is a very desirable thing from a flexibility standpoint).
There are changes both in the userspace tools and in the kernel; this pretty much rules out the possibility of an easy recovery using a vanilla linux system.

Having said that, the QNAP GPL tarball at http://sourceforge.net/projects/qosgpl/ contains all the relevant sources, so I was able to build a working recovery environment by compiling and installing QNAP's kernel and LVM tools on a standard system.

louiscar
Know my way around
Posts: 204
Joined: Mon Aug 10, 2015 4:32 am

Re: [SMB] HOW-TO RECOVER data from LVM volume on a PC (UX-50

Postby louiscar » Sun Sep 06, 2015 9:37 am

alyf80 wrote:
JeffryPaul wrote:after installing the "thin-provisioning-tools" package, I was able to step past the thin-pool problem. Now I'm stuck with the vg1 not being activated due to the invalid "thick" segment type, which appears to be unique to QNAP, since there is no LVM documentation supporting such a segment type. Reviewed the segtype.h file in the lvm2 project found here: https://git.fedorahosted.org/cgit/lvm2.git


Apparently QNAP extended the standard thin provisioning model of LVM2 in order to support new features (my guess is that this has to do with the ability to have thick-provisioned volumes within a thin-provisioning pool, which is a very desirable thing from a flexibility standpoint).
There are changes both in the userspace tools and in the kernel; this pretty much rules out the possibility of an easy recovery using a vanilla linux system.

Having said that, the QNAP GPL tarball at http://sourceforge.net/projects/qosgpl/ contains all the relevant sources, so I was able to build a working recovery environment by compiling and installing QNAP's kernel and LVM tools on a standard system.


would love to have a bootable image of that recovery if possible for the more unix challenged amongst us or perhaps you could do a step by step tut for creating same?
Model : TS-453 Pro
Firmware : 4.3.3.0262
2x WD RED 3TB - Raid 1


Return to “Hardware & Software Compatibility”

Who is online

Users browsing this forum: No registered users and 3 guests