Are QNAP drives readable in Ubuntu/Linux?

Questions about SNMP, Power, System, Logs, disk, & RAID.
Post Reply
Shr00m
Starting out
Posts: 18
Joined: Sat Nov 28, 2015 6:19 am

Are QNAP drives readable in Ubuntu/Linux?

Post by Shr00m » Sun Mar 17, 2019 11:27 pm

My motherboard in my QNAP TS-453 Pro died this week. I had 4 drives which are perfectly fine running in it before the board died. 2 drives were setup with RAID1 and the other 2 drives where setup in a JBOD (i think, can't remember). I think my problem is that I can't activate the LV2 pools. The reason I think this is because an lvscan gives warnings about the segments then when I run a vgchange it says it can't activate vg1/lv1 because of unrecognized segments. Here are some things I've tried, anyone have any suggestions?

Code: Select all

jason@plex:/dev$ sudo lvscan
  WARNING: Unrecognised segment type tier-thin-pool
  WARNING: Unrecognised segment type thick
  WARNING: Unrecognised segment type flashcache
  LV tp2, segment 1 invalid: does not support flag ERROR_WHEN_FULL. for tier-thin-pool segment.
  Internal error: LV segments corrupted in tp2.
  ACTIVE            '/dev/vg1/lv544' [20.00 GiB] inherit
  inactive          '/dev/vg1/tp1' [2.68 TiB] inherit
  inactive          '/dev/vg1/lv1' [1.34 TiB] inherit
  inactive          '/dev/vg1/lv2' [1.34 TiB] inherit

Code: Select all

jason@plex:~$ sudo vgchange -a y
  WARNING: Unrecognised segment type tier-thin-pool
  WARNING: Unrecognised segment type thick
  WARNING: Unrecognised segment type flashcache
  LV tp2, segment 1 invalid: does not support flag ERROR_WHEN_FULL. for tier-thin-pool segment.
  Internal error: LV segments corrupted in tp2.
  Check of pool vg1/tp1 failed (status:1). Manual repair required!
  Refusing activation of LV vg1/lv1 containing an unrecognised segment.
  Refusing activation of LV vg1/lv2 containing an unrecognised segment.
  1 logical volume(s) in volume group "vg1" now active

Code: Select all

jason@plex:/dev$ sudo lvmdiskscan
  /dev/loop0     [     <91.00 MiB]
  /dev/vg1/lv544 [      20.00 GiB]
  /dev/loop1     [     <90.99 MiB]
  /dev/loop2     [     <91.10 MiB]
  /dev/sda2      [    <127.00 GiB]
  /dev/md122     [      <2.72 TiB] LVM physical volume
  /dev/md123     [     517.62 MiB]
  /dev/md124     [    <517.69 MiB]
  /dev/md125     [      <2.72 TiB] LVM physical volume
  /dev/md126     [     448.12 MiB]
  /dev/md127     [      <6.90 GiB]
  0 disks
  9 partitions
  0 LVM physical volume whole disks
  2 LVM physical volumes

Code: Select all

jason@plex:/dev$ sudo lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
fd0               2:0    1     4K  0 disk
loop0             7:0    0    91M  1 loop  /snap/core/6405
loop1             7:1    0    91M  1 loop  /snap/core/6350
loop2             7:2    0  91.1M  1 loop  /snap/core/6531
sda               8:0    0   127G  0 disk
├─sda1            8:1    0     1M  0 part
└─sda2            8:2    0   127G  0 part  /
sdb               8:16   0   2.7T  0 disk
├─sdb1            8:17   0 517.7M  0 part
│ └─md123         9:123  0 517.6M  0 raid1
├─sdb2            8:18   0 517.7M  0 part
│ └─md124         9:124  0 517.7M  0 raid1
├─sdb3            8:19   0   2.7T  0 part
│ └─md125         9:125  0   2.7T  0 raid1
├─sdb4            8:20   0 517.7M  0 part
│ └─md126         9:126  0 448.1M  0 raid1
└─sdb5            8:21   0     8G  0 part
  └─md127         9:127  0   6.9G  0 raid1
sdc               8:32   0   2.7T  0 disk
├─sdc1            8:33   0 517.7M  0 part
│ └─md123         9:123  0 517.6M  0 raid1
├─sdc2            8:34   0 517.7M  0 part
│ └─md124         9:124  0 517.7M  0 raid1
├─sdc3            8:35   0   2.7T  0 part
│ └─md125         9:125  0   2.7T  0 raid1
├─sdc4            8:36   0 517.7M  0 part
│ └─md126         9:126  0 448.1M  0 raid1
└─sdc5            8:37   0     8G  0 part
  └─md127         9:127  0   6.9G  0 raid1
sdd               8:48   0   2.7T  0 disk
├─sdd1            8:49   0 517.7M  0 part
│ └─md123         9:123  0 517.6M  0 raid1
├─sdd2            8:50   0 517.7M  0 part
│ └─md124         9:124  0 517.7M  0 raid1
├─sdd3            8:51   0   2.7T  0 part
│ └─md122         9:122  0   2.7T  0 raid1
│   └─vg1-lv544 253:0    0    20G  0 lvm
├─sdd4            8:52   0 517.7M  0 part
│ └─md126         9:126  0 448.1M  0 raid1
└─sdd5            8:53   0     8G  0 part
  └─md127         9:127  0   6.9G  0 raid1
sde               8:64   0   2.7T  0 disk
├─sde1            8:65   0 517.7M  0 part
│ └─md123         9:123  0 517.6M  0 raid1
├─sde2            8:66   0 517.7M  0 part
│ └─md124         9:124  0 517.7M  0 raid1
├─sde3            8:67   0   2.7T  0 part
│ └─md122         9:122  0   2.7T  0 raid1
│   └─vg1-lv544 253:0    0    20G  0 lvm
├─sde4            8:68   0 517.7M  0 part
│ └─md126         9:126  0 448.1M  0 raid1
└─sde5            8:69   0     8G  0 part
  └─md127         9:127  0   6.9G  0 raid1
sr0              11:0    1  1024M  0 rom

Code: Select all

jason@plex:/dev$ sudo vgdisplay
  WARNING: Unrecognised segment type tier-thin-pool
  WARNING: Unrecognised segment type thick
  WARNING: Unrecognised segment type flashcache
  LV tp2, segment 1 invalid: does not support flag ERROR_WHEN_FULL. for tier-thin-pool segment.
  Internal error: LV segments corrupted in tp2.
  --- Volume group ---
  VG Name               vg1
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  25
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                4
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               <2.72 TiB
  PE Size               4.00 MiB
  Total PE              712966
  Alloc PE / Size       712966 / <2.72 TiB
  Free  PE / Size       0 / 0
  VG UUID               k7Pu3Q-VOUN-0p2Y-1lRS-F6XM-jRpT-PXMjqf

Code: Select all

  jason@plex:/dev$ sudo fdisk -l
Disk /dev/loop0: 91 MiB, 95416320 bytes, 186360 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: 91 MiB, 95408128 bytes, 186344 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: 91.1 MiB, 95522816 bytes, 186568 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: 127 GiB, 136365211648 bytes, 266338304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D466162D-FCA6-47C0-B814-24B22B78AF90

Device     Start       End   Sectors  Size Type
/dev/sda1   2048      4095      2048    1M BIOS boot
/dev/sda2   4096 266336255 266332160  127G Linux filesystem


Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2FD44E1C-A5B9-4043-A159-481F5F61436F

Device          Start        End    Sectors   Size Type
/dev/sdb1          40    1060289    1060250 517.7M Microsoft basic data
/dev/sdb2     1060296    2120579    1060284 517.7M Microsoft basic data
/dev/sdb3     2120584 5842744109 5840623526   2.7T Microsoft basic data
/dev/sdb4  5842744112 5843804399    1060288 517.7M Microsoft basic data
/dev/sdb5  5843804408 5860511999   16707592     8G Microsoft basic data


Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FC87A2D5-F399-4557-A0C6-2D1A83C2D2A0

Device          Start        End    Sectors   Size Type
/dev/sdc1          40    1060289    1060250 517.7M Microsoft basic data
/dev/sdc2     1060296    2120579    1060284 517.7M Microsoft basic data
/dev/sdc3     2120584 5842744109 5840623526   2.7T Microsoft basic data
/dev/sdc4  5842744112 5843804399    1060288 517.7M Microsoft basic data
/dev/sdc5  5843804408 5860511999   16707592     8G Microsoft basic data


Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5B3A0CB4-74F3-4676-9FD7-C354B156DC45

Device          Start        End    Sectors   Size Type
/dev/sdd1          40    1060289    1060250 517.7M Microsoft basic data
/dev/sdd2     1060296    2120579    1060284 517.7M Microsoft basic data
/dev/sdd3     2120584 5842744109 5840623526   2.7T Microsoft basic data
/dev/sdd4  5842744112 5843804399    1060288 517.7M Microsoft basic data
/dev/sdd5  5843804408 5860511999   16707592     8G Microsoft basic data


Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4A3B90D5-A0E4-4B51-8995-EB6D872F5F64

Device          Start        End    Sectors   Size Type
/dev/sde1          40    1060289    1060250 517.7M Microsoft basic data
/dev/sde2     1060296    2120579    1060284 517.7M Microsoft basic data
/dev/sde3     2120584 5842744109 5840623526   2.7T Microsoft basic data
/dev/sde4  5842744112 5843804399    1060288 517.7M Microsoft basic data
/dev/sde5  5843804408 5860511999   16707592     8G Microsoft basic data


Disk /dev/md127: 6.9 GiB, 7408779264 bytes, 14470272 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md126: 448.1 MiB, 469893120 bytes, 917760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md125: 2.7 TiB, 2990399094784 bytes, 5840623232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md124: 517.7 MiB, 542834688 bytes, 1060224 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md123: 517.6 MiB, 542769152 bytes, 1060096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md122: 2.7 TiB, 2990399094784 bytes, 5840623232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/vg1-lv544: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

User avatar
MrVideo
Experience counts
Posts: 4743
Joined: Fri May 03, 2013 2:26 pm

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by MrVideo » Tue Mar 19, 2019 9:18 am

If you dig thru the many postings, you will find those who have tried to read QNAP drives that were set up using LVM and have failed. I hope you have backups.
QTS MANUALS
Submit QNAP Support Ticket - QNAP Tutorials, FAQs, Downloads, Wiki - Product Support Status - Moogle's QNAP FAQ help V2
Asking a question, include the following
(Thanks to Toxic17)
QNAP md_checker nasreport (release 20210309)
===============================
Model: TS-869L -- RAM: 3G -- FW: QTS 4.1.4 Build 20150522 (used for data storage)
WD60EFRX-68L0BN1(x1)/68MYMN1(x7) Red HDDs -- RAID6: 8x6TB -- Cold spare: 1x6TB
Entware
===============================
Model: TS-451A -- RAM: 2G -- FW: QTS 4.5.2 Build 20210202 (used as a video server)
WL3000GSA6472(x3) White label NAS HDDs -- RAID5: 3x3TB
Entware -- MyKodi 17.3 (default is Kodi 16)
===============================
My 2017 Total Solar Eclipse Photos | My 2019 N. Ireland Game of Thrones tour

Shr00m
Starting out
Posts: 18
Joined: Sat Nov 28, 2015 6:19 am

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by Shr00m » Wed Mar 20, 2019 6:42 am

I do have backups. But I didn't want to have to download all the data across the Internet.

I didn't realize this but once your warranty expires you no longer have tech support either. Furthermore, they won't even help me get my data off the drives. So, I'm basically forced to pay for an expensive repair or buy another QNAP NAS. From the research I found online, QNAP does this on purpose and locks things in the software. If i would have known this going into the initial purchase I wouldn't have bought it.

Cya QNAP, you've just lost a customer. I will never recommend another one to anyone I know.

User avatar
dolbyman
Guru
Posts: 22306
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by dolbyman » Wed Mar 20, 2019 7:01 am

Heard tons of stories where QNAP support assisted in getting in old EOL devices (CAT1) back into working order, all within reason of course.

If you have working QNAP hardware that is of course ... don't expect QNAP customer support to assist recovery on a foreign system. If you haven't messed up the disks, plugging them in a migration compatible new QNAP unit, will get them back up and running as before

User avatar
MrVideo
Experience counts
Posts: 4743
Joined: Fri May 03, 2013 2:26 pm

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by MrVideo » Wed Mar 20, 2019 11:06 am

dolbyman wrote:
Wed Mar 20, 2019 7:01 am
If you have working QNAP hardware that is of course ... don't expect QNAP customer support to assist recovery on a foreign system.
Ya, no manufacturer of a NAS is going to help anyone attempt to get the NAS data extracted in another device.
QTS MANUALS
Submit QNAP Support Ticket - QNAP Tutorials, FAQs, Downloads, Wiki - Product Support Status - Moogle's QNAP FAQ help V2
Asking a question, include the following
(Thanks to Toxic17)
QNAP md_checker nasreport (release 20210309)
===============================
Model: TS-869L -- RAM: 3G -- FW: QTS 4.1.4 Build 20150522 (used for data storage)
WD60EFRX-68L0BN1(x1)/68MYMN1(x7) Red HDDs -- RAID6: 8x6TB -- Cold spare: 1x6TB
Entware
===============================
Model: TS-451A -- RAM: 2G -- FW: QTS 4.5.2 Build 20210202 (used as a video server)
WL3000GSA6472(x3) White label NAS HDDs -- RAID5: 3x3TB
Entware -- MyKodi 17.3 (default is Kodi 16)
===============================
My 2017 Total Solar Eclipse Photos | My 2019 N. Ireland Game of Thrones tour

Shr00m
Starting out
Posts: 18
Joined: Sat Nov 28, 2015 6:19 am

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by Shr00m » Thu Mar 21, 2019 9:20 pm

From what I've read online they've taken an open source file system (BTRFS) and modified it for their NAS's. This is the reason (I think) why I can't use standard BTRFS filesystem tools to mount the drive. If this is the case, QNAP is forcing you to either repair your hardware with them or purchase a new QNAP device. The tech support guy I worked with told me that QNAP locks the hardware so I can't just go out and buy the motherboard (which is what failed in my device) and put it in myself. Additionally, I can't just go purchase any QNAP model, they have a compatibility guide that I have to choose from.

If their filesystem is proprietary you'd think they would offer downloadable tools on their website to recover your data outside of recovering in their hardware. I made an assumption when I purchase this device that since it was using open source software I wouldn't be locked in. I hate being locked into a specific vendor.

User avatar
dolbyman
Guru
Posts: 22306
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by dolbyman » Thu Mar 21, 2019 9:45 pm

if everything fails you can always
buy a qnap unit
recover the data
return the unit

use that migration list to determine the cheapest unit that would be compatible (min x86 I bet..as intel-> arm migration doesnt work)

Shr00m
Starting out
Posts: 18
Joined: Sat Nov 28, 2015 6:19 am

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by Shr00m » Sat Mar 23, 2019 9:59 pm

I've thought about that. I'm sure QNAP has too, which is why I can't believe they don't offer utilities in Windows or Linux to recover your data if the hardware fails.

I have another week until all my data is downloaded again so I'm all good. Just ranting about their business practices as I've been extremely happy with them until now.....

User avatar
MrVideo
Experience counts
Posts: 4743
Joined: Fri May 03, 2013 2:26 pm

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by MrVideo » Sun Mar 24, 2019 1:34 am

I do not know of anyone that provides software that runs on other platforms in which to recover data.
QTS MANUALS
Submit QNAP Support Ticket - QNAP Tutorials, FAQs, Downloads, Wiki - Product Support Status - Moogle's QNAP FAQ help V2
Asking a question, include the following
(Thanks to Toxic17)
QNAP md_checker nasreport (release 20210309)
===============================
Model: TS-869L -- RAM: 3G -- FW: QTS 4.1.4 Build 20150522 (used for data storage)
WD60EFRX-68L0BN1(x1)/68MYMN1(x7) Red HDDs -- RAID6: 8x6TB -- Cold spare: 1x6TB
Entware
===============================
Model: TS-451A -- RAM: 2G -- FW: QTS 4.5.2 Build 20210202 (used as a video server)
WL3000GSA6472(x3) White label NAS HDDs -- RAID5: 3x3TB
Entware -- MyKodi 17.3 (default is Kodi 16)
===============================
My 2017 Total Solar Eclipse Photos | My 2019 N. Ireland Game of Thrones tour

P3R
Guru
Posts: 12557
Joined: Sat Dec 29, 2007 1:39 am
Location: Stockholm, Sweden (UTC+01:00)

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by P3R » Sun Mar 24, 2019 7:03 pm

Shr00m wrote:
Thu Mar 21, 2019 9:20 pm
From what I've read online they've taken an open source file system (BTRFS) and modified it for their NAS's.
You shouldn't believe everything you read online.

Qnap use Ext4 with MD/LVM, not BTRFS.
RAID have never ever been a replacement for backups. Without backups on a different system (preferably placed at another site), you will eventually lose data!

A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.

All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!

rramalho
New here
Posts: 7
Joined: Mon Oct 15, 2012 3:10 am

Re: Are QNAP drives readable in Ubuntu/Linux?

Post by rramalho » Thu Jun 20, 2019 12:30 am

Hi all,

QNAP MD for RAID, and then uses a segment type, on LVM2, named tier_thin_pool. On top of all that, you'll find an ext4 filesystem. This segment type was created by QNAP and never released to the public as the license GPLv2 demands.

If QNAP were a decent player, they would have sent patches for the upstream developers of LVM2. I will *not* recommend QNAP to anyone, ever again after losing 3TBytes of data, on a failure of a QNAP NAS. I have the harddrives, I've imaged them just in case, and will try to find another QNAP device, just to get my data back.

If QNAP uses Free Software, it should contribute back to the projects they benefit from.

If anyone has managed to get these drives mounted on bare Linux please contact me.

Thank you!

Post Reply

Return to “System & Disk Volume Management”