Thanks for the guide. Unfortunately, seems like volume was dynamic, and it can't be restored this way. Read from the comments, that there will be another video about this problem. Will wait for this.
Thank you so much. Process wasn't as smooth as I hoped, but in the end worked it out. One tip, make sure your settings in device manager do not allow the USB drivers to power down. Makes it hard to activate the drives in VirtualBox. Also, could not get a Western Digital external drive to connect reliably. In the end that was my biggest challenge. The software walk through, super easy.
Glad it helped getting your data back. Good tip about the drives powerdown. Sounds like you may be working on a laptop - so you need to make sure power management doesn't get in the way...
Thank You for saving my files from failed qnap nas. My drive no longer could mount for some reason. Using your tutorial I was able to recover all that I thought was lost.
I kept getting error message that a memory address could not be read part way through copying a 3TB volume. It turns out I had to make sure the computer was set so it didn't go to sleep --it was timing out and disconnecting assets. If that was mentioned in the video, I missed it. Thanks for posting this tutorial--VERY helpful.
Yes - you can put the drives in a similar QNAP chassis (same chipset ideally)... But the method shown in the video will work if one of the other partitions on the drive is corrupted. If putting old drives in a new QNAP enclosure you also need to be mindful of the firmware versions and care must be taken not to inadvertently wipe the data when the new QNAP enclosure initialises....
Very constructive and useful video. I just had my raid1 ssd drives fail and QNAP adviced to use R-Linux to recover files, however it wasn't recovering any files from the third partition which contains Public, homes, etc. folders. I tried following your video, but when I do gparted, I don't see /dev/sdb2 and /dev/sdb3, but the filesystem of these partitions is marked as unknown (with a red exclamation mark). /dev/sdb3 is the biggest partition, which I assume should contain my data (Public, homes, etc). Details on those partitions show: - The file system is damaged, The file system is unknown to GParted, There is no file system available (unformatted), The device entry /dev/sdb3 is missing. What to do in this case?
Thank you for watching. I think you may need to force the partition type and mount it manually... But before you rdo this you may find the the EaseUS "Linux Partition Master for Windows" tool may help. There is a free trial that may well give you enough information to allow you to manually mount the partition in Linux - or you could just purchase the full version....
Greath tuttorial !! I have 4 HDD (raid5) connected to my PC SATA connections, can I reach them this way in ubuntu , or would I need 2 usb caddy's ? I'm with you until approx. min 24. Thanks in advance
For 4 drive RAID 5 you need to connect at least 3 good drives to get the data off. Assuming it is a 'Traditional/Static' volume the technique in the video should work. Using USB conneted drives is easiest. SATA/SAS connected drives require them to be passed to the virtual machine. Google "Passthrough Mounting A Physical Disk Drive in VirtualBox" ...
Thank you for watching. This method should work for any 'static' volume . For RAID6 wyou will need to connect at least 4 drives to the computer before being able to recover the data. I would expect GParted to be able to detect the data partitions - even if it cannot recognise the volume type. I will be adding another video showing recovery options for Thick / Thin volumes types - the basic instructions are towards the end of this post on our website: ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
@@ripcastercouk thanks for the reply. I am trying to mount my 4 hard disks to the virtual host but it seems to be limited by the IDE controller and the VM is trying to boot from one of the disks instead of the virtual image. Edit: oh ok, mounting as SATA seems working for now...
@@ripcastercouk thanks for the reply! Oh, I am finally able to mount the drives now but it seems that 1 of the drives out of 4 is missing the data and marked as unallocated likely due to the image file being written to this drive thanks to the wrong QNAP instructions of firmware recovery. Is it ok to recover the data with just 3 "working" disks? I ran sudo cat /proc/mdstat and the RAID structure could not be detected. The printout is attached: docs.google.com/document/d/1N6JDLYmTPECQ20kQpXTIuH-dt1zedKhtUrNm31srtlM/edit?usp=sharing
@@ripcastercouk Thanks. I actually posted an edited reply some hours ago but it disappeared. The printout of the mdadm commands actually looks like this: docs.google.com/document/d/1N6JDLYmTPECQ20kQpXTIuH-dt1zedKhtUrNm31srtlM/edit?usp=drive_link But the good news is I realised one of the drives has been overwritten by the firmware image with gparted so I just put the 3 working drives in a working 4 bay QNAP and then soft reset it after a while (3 second press) and it's back online and the RAID is being rebuilt at the moment. Thank you again for the guide!
Yes - I' have a solution for this and will be making a video when I get the time. The basic steps using Proxmox etc are at the end of this blog post on our website here ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
@@ripcastercouk Thank you very much will wait for video. as I tried to follow steps but too complicated without someone showing. Appreciate your efforts.
@@abhishekmor I'm not sure the next video is going to be any easier and it also requires more hardware - but it will allow recover for any volume type.
Hi. I am begginer and landed on your video which could help me. I didn't execute or follow your process yet. I have the qnap TS-130 (1 bay). My NAS is not able to start up anymore and so on ... According to QNAP support service, the hard-disks, which were plugged with some specific NAS models from QNAP, can not be connect to a SATA/USB adapter to read the data or something like that. I don't know what it implies exactly but it is the case of my TS-130. May I know the NAS model that you removed your hard-disk from? ==> It could help me investigate further (and understand just a little more) before starting your process.
Hi, I'm experiencing a similar issue and have been following your steps carefully. However, I ran into an issue at minute mark 29:51 with the "sudo mdadm - -run /dev/md124" command (mine is md127 that has the 1.8TB partition). After inputting the command, it says "mdadm: failed to start array /dev/md/1_0: Invalid argument" Could you please advise what I might be doing wrong and how to fix it?
Difficult to say with the information provided.... but I suspect you may be trying to load a non static volume. The instructions in te video only work for QNAP static volumes. I do have a solution for this type of volume and will be publishing another video covering this in the coming weeks. Also check you sure you are using the correct device name for the raid e.g md127 etc See what cat /proc/mdstat and make sure you are using the device with the larges block count
As I learned from your video this for static volume and my hdd got crashed had thin volume which is a nightmare to recover. Do you recommend I should setup my new HDD in qnap nas as static so its easy to recover? or thick ? I cant have 2 HDD and dont want to run them as raid due to cost factor.
I'm sure for 90% of users a Static volume is more appropriate than the default setting. I highly recommend using a RAID - cost of a drive is nothing compared loss of data you may experience with a single drive (You should always keep an external backup too).
@@ripcastercouk Yes which I was not aware of as I have HDD for 7 years now and still working but this Seagate iron wolf Nas drive one did not last even 1.5 years.
Just tried the fix with a 100 ohm Resistor 1/2w (0.5Watt) ±1% Tolerance Metal Film Fixed Resistor, Multiple Values of Resistance Optional with the same issue. Soldered it to pin 1 and 8. Is that the correct resistor?
Thank you for this video, Good to follow. Ive managed to see all my files and open them only it wont let me copy to another drive or the host it past stay gray and when i drag i get error about guest additions in the settings i have enabled it thks
HI, It sounds like you are trying to. drag files from the guest Linux OS to the host OS. You can do this with Guest Editions and Shared Folders - but you may find it easier to mount the destination folder/drive within the Guest Linux OS so that copy if all performed withing the virtual machine. Hope that helps. Jon
Followed instructions but my process is stuck at confirming/dev/sdb and not showing any partitions. Been there for 2 hours now. Is it normal for 4tb HDD ? any suggestions ? iIam stuck after Gparted 26:42 in your video. The orange scanning bar is moving but not getting any results like not showing any partitions. I can see the NAS HDD is also working. Appreciate your help.
If you don't see any partitions then the drive is empty (or there is a controller fault). Check you are looking at the right drive sdc,sdd etc If you cannot see any partitions then these instructions won't et your data back...
@@ripcastercouk I can see partitions in window but its stuck at that loading screen after GParted and never shows the list in linux. Partitions are visible in windows
When I run sudo cat /proc/mdstat, my mdstate for the right drive shows active (auto-read-only) raid1 sdb3[0]. After following the rest of the steps when I get to sudo lvchange -ay /dev/vg289/lv3 , I get an error WARNING: Unrecognised segment type cache_client WARNING: PV /dev/md127 in VG vg289 is using an old PV header, modify the VG to update. Refusing activation of LV vg289/lv3 containing an unrecognised segment. And disk does not show up in the side bar. I didn't try to mount it because it seems it may also fail. Any idea why. In this case my drive didn't die but my nas did.
Hi - sounds like you are doing the right steps - so it probably means the drive has a dynamic volume type. These instructions only work for static/traditioal volumes.
I had a ssd cache drive that failed and the 2 drives I have in raid 1 are ok but Qnap will not read the array now. If I have Linux on my PC (thats what I use), can I just mount one of the drive in disks section and find my files?
IF they are a 'static' volume then the method shown in the video will allow you to read the data off the drives. I'm working on another video that will show how to get data off all types of QNAP volumes (thick, thin, static). The basic steps for this are outlined at the end of this blog post: ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
Hi, The method in the video won't. But you may be able to use other Lunix (and Windows) data recovery tools that will scan the drive sector by sector to recover know file types e.g. photos, documents etc. (assuming you haven't written anything subsequently to the drive). I hope you get your data back...
Hi there. This is very useful. Does this work with an encrypted drive too? I know the password, however I get an error message when I try to run madam. Any help will be appreciated. Thanks
Hi. AT 26:54 you see your new usb connected drive in the device list. I don't. I have it ticked in the Devices dropdown. Is my disk too far gone? I have 2 RAID disks on a Wavlink 2 bay SATA adapter. THink it's RAID0, maybe RAID1. If I put in 1 drive it does similar. If I do sudo lsblk I see after sda (laptop SSDdrive) and sdb 3.9G and sdc 3.9G (I know 3.9G is shown for the disk when the ST1500L003's (1.5Tb) are faulty. Help?!
Step 1 is to make sure the physical drive is reporting the correct size to the virtual machine. See what Windows reports in Disk Management when the VM is shutdown and the drives connected. You should see a number of partitions on the drive, and it should indicate the correct overall capacity (1.5tb).
huge thanks @@ripcastercoukfro your reply. Diskmgmt shows them and then they disappear when ticked in VM. In diskmgmt they are Disk 1 and DIsk 2 but shown as Unknown/3.86 GB/Not initialised and the partitions 3.86 GB Unallocated. I know 3.86 is a default value, the disks are 1.5 TB
@@cbw2596 Drives will be removed from Disk manager in Windows when attached to VM - so that is correct. The main issue is that the drives are not reporting the correct size. Could be a fatally damaged drive (unusuall for two to exhibit the same issue?) or it could indicate your USB caddy for the drives is not working correctly - do y have an alternative to try. If USB good then it probably means the drives are bad and data recovery is beyond the scope of this method
@@ripcastercouk think this was caused by the reset not recovering well enough for intervention. I may not have given it enough time to fully cycle before powering down. These Seagate Barracuda disks exhibit this known 3.86GB fault and they wouldn't /couldn't help yesterday so I've sent them off to R3 Data Recovery who are confident, so far... Thank you for your expert help, much appreciated.
After waiting 3 hours Gparted finally worked but now I ma getting error - Warning: device /dev/sdb3 not initialized in udev databse even after waiting 10000000 microseconds. Warning: Unrecognised segment type tier-thin-pool. I can see the partition but it has red excalmation next to it and the file system is LVM2PV ---- 3.63 TiB . Can you please help how to get around this ? looks like the file system is LVM2PV. Also got another error : Error reading device /dev/sdb3 at 3990593208320 lenght 4
You have a thin provisioned volume as indicated by 'tier-thin-pool' - these instructions will only work for Static volumes. I plan to publish a video showing recovery for all volume types when I have time. The basic 'recipe' is at the end of this blog post here ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1 see section "Storage Pools and Dynamically Allocated Volumes". The long delays you are seeing are a concern. It maybe the drive has hardware failures or the USB caddy is not working correctly.
@@ripcastercouk Thanks for your reply. I would definitely wait for your video as I cant find any other source on internet to recover data from thin volume.
I and several others get stuck at this state restoring Raid 5 sudo vgscan WARNING: Unrecognised segment type tier-thin-pool WARNING: Unrecognised segment type thick WARNING: Unrecognised segment type flashcache WARNING: PV /dev/md125 in VG vg1 is using an old PV header, modify the VG to update. LV vg1/tp1, segment 1 invalid: does not support flag ERROR_WHEN_FULL. for tier-thin-pool segment. Internal error: LV segments corrupted in tp1. Cannot process volume group vg1
The instruction presented here are for static volumes only. I think the warnings indicate your RAID is on a thin/thick dynamic provisioned volume. I doubt if a standard Linux (Ubuntu) has the support for these QNAP volume types. I've seen some people creating QNAP virtual machines in VMWare - so this maybe a way to mount these volume types as they are using QNAP's own code. Hope that helps Jon
The data is stored on the volume (HDD), the Cache is only used to speed he read/write performance only - so you should look to the volume HDD for your actual data. However - given you are using a Cache I suspect you may not be using a 'static' volume. These instructions only work on Static volumes.
There's no way this method is seriously considered for use with someone's precious data. There are WAY TOO MANY instances of WILD missteps & errors here.😲😲How in God's name is there no ONE SHOT SOFTWARE available to do this WHOLE task??? It's 2023!!!!!!!!!!!!!
There are a number of commercially available packages that will attempt data recovery 'automatically'. The method presented here uses standard, freely available, Linux operating system tools. This method is only recommened if you are comfortable using the command line. We have successfully used this method many times. Please let us know any errors you may have spotted so we can update the instructions accordingly.
Drag and drop operation from guest to host failed. DnD: Error: Dragging from guest to host not supported by guest -- make sure that the Guest Additions are properly installed and running. Result Code:VBOX_E_DND_ERROR (0X80BB0011) Component:GuestDnDSourceWrap Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28} Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
dawid@dawid-VirtualBox:~$ sudo lvdisplay WARNING: Unrecognised segment type tier-thin-pool WARNING: Unrecognised segment type thick WARNING: PV /dev/md126 in VG vg1 is using an old PV header, modify the VG to update. LV vg1/tp1, segment 1 invalid: does not support flag ERROR_WHEN_FULL. for tier-thin-pool segment. Internal error: LV segments corrupted in tp1. Cannot process volume group vg1 What to do with this ?
That indicates you have a Thick volume. This method is for 'Static' or traditional volumes only. I will make another video covering recovery from all volume types (thick, thin, static) - the outline steps of this is shown at the end of the article here ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
sounds like the device (drive) isn't connected. check the usb device is attached to the virtual machine, then try gparted within the virtual machine to confirm the physical drive is visible to the linux os.
do you mean there is no way to recovery the data as I can't remember what type of volume selected as I just follow the user manual default when I set up the machine years ago
@@dicksonyeung73 The method shown here is for recovery of standard/static volumes only. If you fit the drives in another QNAP chassis the data should be readable. You may also find some dedicated data recovery software may work.
Thanks for the guide. Unfortunately, seems like volume was dynamic, and it can't be restored this way. Read from the comments, that there will be another video about this problem. Will wait for this.
Thank you so much. Process wasn't as smooth as I hoped, but in the end worked it out. One tip, make sure your settings in device manager do not allow the USB drivers to power down. Makes it hard to activate the drives in VirtualBox. Also, could not get a Western Digital external drive to connect reliably. In the end that was my biggest challenge. The software walk through, super easy.
Glad it helped getting your data back. Good tip about the drives powerdown. Sounds like you may be working on a laptop - so you need to make sure power management doesn't get in the way...
Thank You for saving my files from failed qnap nas. My drive no longer could mount for some reason. Using your tutorial I was able to recover all that I thought was lost.
Great to hear you recovered your data. happy to help.
You really saved me , using QNAP NAS and had failure in all network adapters (4) , used your method and easy mount and processes
Excellent instruction but too many gaps in my knowledge to handle out of band variables today. But a big thank you as I move nearer to understanding.
I kept getting error message that a memory address could not be read part way through copying a 3TB volume. It turns out I had to make sure the computer was set so it didn't go to sleep --it was timing out and disconnecting assets. If that was mentioned in the video, I missed it. Thanks for posting this tutorial--VERY helpful.
Thank you this saved my data. I really appreciate the effort of making this Video
Excellent tutorial. I really appreciate how well you described step by step.
Thank you very much, very helpful!
Would the working drives from the failed QNAP not slot into another QNAP or is it like trying to use a hard drive from one PC in another?
Yes - you can put the drives in a similar QNAP chassis (same chipset ideally)... But the method shown in the video will work if one of the other partitions on the drive is corrupted. If putting old drives in a new QNAP enclosure you also need to be mindful of the firmware versions and care must be taken not to inadvertently wipe the data when the new QNAP enclosure initialises....
Very constructive and useful video. I just had my raid1 ssd drives fail and QNAP adviced to use R-Linux to recover files, however it wasn't recovering any files from the third partition which contains Public, homes, etc. folders. I tried following your video, but when I do gparted, I don't see /dev/sdb2 and /dev/sdb3, but the filesystem of these partitions is marked as unknown (with a red exclamation mark). /dev/sdb3 is the biggest partition, which I assume should contain my data (Public, homes, etc). Details on those partitions show: - The file system is damaged, The file system is unknown to GParted, There is no file system available (unformatted), The device entry /dev/sdb3 is missing. What to do in this case?
Thank you for watching. I think you may need to force the partition type and mount it manually... But before you rdo this you may find the the EaseUS "Linux Partition Master for Windows" tool may help. There is a free trial that may well give you enough information to allow you to manually mount the partition in Linux - or you could just purchase the full version....
@@ripcastercouk I ended up wiping the entire drives and created RAID1 from scratch. Fortunately I still had backups of everything.
im sorry to hear that and wish you luck. i might have to do this at some point but not for anything all that useful
Greath tuttorial !!
I have 4 HDD (raid5) connected to my PC SATA connections, can I reach them this way in ubuntu , or would I need 2 usb caddy's ? I'm with you until approx. min 24. Thanks in advance
For 4 drive RAID 5 you need to connect at least 3 good drives to get the data off. Assuming it is a 'Traditional/Static' volume the technique in the video should work. Using USB conneted drives is easiest. SATA/SAS connected drives require them to be passed to the virtual machine. Google "Passthrough Mounting A Physical Disk Drive in VirtualBox" ...
@@ripcastercouk Thanks, will try it 👍
Finally I bought a 4 bay usb3 hub and had to do some FSCK. And then it was possible to mount it and get the data. Thanks !!
@@bertdegroef4205 Great to hear you managed to recover your data
Thank you for the instructions. Does it work with RAID 6 coz I ran Gparted and it couldn't detected anything?
Thank you for watching. This method should work for any 'static' volume . For RAID6 wyou will need to connect at least 4 drives to the computer before being able to recover the data. I would expect GParted to be able to detect the data partitions - even if it cannot recognise the volume type. I will be adding another video showing recovery options for Thick / Thin volumes types - the basic instructions are towards the end of this post on our website: ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
@@ripcastercouk thanks for the reply. I am trying to mount my 4 hard disks to the virtual host but it seems to be limited by the IDE controller and the VM is trying to boot from one of the disks instead of the virtual image.
Edit: oh ok, mounting as SATA seems working for now...
@@ripcastercouk thanks for the reply! Oh, I am finally able to mount the drives now but it seems that 1 of the drives out of 4 is missing the data and marked as unallocated likely due to the image file being written to this drive thanks to the wrong QNAP instructions of firmware recovery. Is it ok to recover the data with just 3 "working" disks? I ran sudo cat /proc/mdstat and the RAID structure could not be detected. The printout is attached: docs.google.com/document/d/1N6JDLYmTPECQ20kQpXTIuH-dt1zedKhtUrNm31srtlM/edit?usp=sharing
@@AldrichLee If you original configuration was 4 drives in RAID5 or 6 then you should be able to recover the data using just 3 drives.
@@ripcastercouk Thanks. I actually posted an edited reply some hours ago but it disappeared. The printout of the mdadm commands actually looks like this:
docs.google.com/document/d/1N6JDLYmTPECQ20kQpXTIuH-dt1zedKhtUrNm31srtlM/edit?usp=drive_link
But the good news is I realised one of the drives has been overwritten by the firmware image with gparted so I just put the 3 working drives in a working 4 bay QNAP and then soft reset it after a while (3 second press) and it's back online and the RAID is being rebuilt at the moment. Thank you again for the guide!
Hi are you planning to make a video on - Storage Pools and Dynamically Allocated Volumes ?
Yes - I' have a solution for this and will be making a video when I get the time. The basic steps using Proxmox etc are at the end of this blog post on our website here ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
@@ripcastercouk Thank you very much will wait for video. as I tried to follow steps but too complicated without someone showing. Appreciate your efforts.
@@abhishekmor I'm not sure the next video is going to be any easier and it also requires more hardware - but it will allow recover for any volume type.
@@ripcastercouk Thanks i already got a bare metal pc loaded with proxmox. Getting stuck with instructions.
@@abhishekmor OK - I'll try and get the video made in the next week.
Hi. I am begginer and landed on your video which could help me.
I didn't execute or follow your process yet.
I have the qnap TS-130 (1 bay).
My NAS is not able to start up anymore and so on ...
According to QNAP support service, the hard-disks, which were plugged with some specific NAS models from QNAP, can not be connect to a SATA/USB adapter to read the data or something like that.
I don't know what it implies exactly but it is the case of my TS-130.
May I know the NAS model that you removed your hard-disk from?
==> It could help me investigate further (and understand just a little more) before starting your process.
The method shown should work with any working drive from a QNAP model that has used the Static volume type.
Hi, Sudo pvdisplay doesn't bring up the information for my drive which is dev/md/0 not sure how to resolve?
Hi, I'm experiencing a similar issue and have been following your steps carefully. However, I ran into an issue at minute mark 29:51 with the "sudo mdadm - -run /dev/md124" command (mine is md127 that has the 1.8TB partition). After inputting the command, it says "mdadm: failed to start array /dev/md/1_0: Invalid argument"
Could you please advise what I might be doing wrong and how to fix it?
Difficult to say with the information provided.... but I suspect you may be trying to load a non static volume. The instructions in te video only work for QNAP static volumes. I do have a solution for this type of volume and will be publishing another video covering this in the coming weeks. Also check you sure you are using the correct device name for the raid e.g md127 etc See what cat /proc/mdstat and make sure you are using the device with the larges block count
As I learned from your video this for static volume and my hdd got crashed had thin volume which is a nightmare to recover. Do you recommend I should setup my new HDD in qnap nas as static so its easy to recover? or thick ? I cant have 2 HDD and dont want to run them as raid due to cost factor.
I'm sure for 90% of users a Static volume is more appropriate than the default setting. I highly recommend using a RAID - cost of a drive is nothing compared loss of data you may experience with a single drive (You should always keep an external backup too).
@@ripcastercouk Yes which I was not aware of as I have HDD for 7 years now and still working but this Seagate iron wolf Nas drive one did not last even 1.5 years.
Just tried the fix with a 100 ohm Resistor 1/2w (0.5Watt) ±1% Tolerance Metal Film Fixed Resistor, Multiple Values of Resistance Optional with the same issue. Soldered it to pin 1 and 8. Is that the correct resistor?
I think you are commenting on the wrong video. This is all about data recovery and done in free software.
Thank you for this video, Good to follow. Ive managed to see all my files and open them only it wont let me copy to another drive or the host it past stay gray and when i drag i get error about guest additions in the settings i have enabled it
thks
HI, It sounds like you are trying to. drag files from the guest Linux OS to the host OS. You can do this with Guest Editions and Shared Folders - but you may find it easier to mount the destination folder/drive within the Guest Linux OS so that copy if all performed withing the virtual machine. Hope that helps. Jon
Followed instructions but my process is stuck at confirming/dev/sdb and not showing any partitions. Been there for 2 hours now. Is it normal for 4tb HDD ? any suggestions ? iIam stuck after Gparted 26:42 in your video. The orange scanning bar is moving but not getting any results like not showing any partitions. I can see the NAS HDD is also working. Appreciate your help.
If you don't see any partitions then the drive is empty (or there is a controller fault). Check you are looking at the right drive sdc,sdd etc If you cannot see any partitions then these instructions won't et your data back...
@@ripcastercouk I can see partitions in window but its stuck at that loading screen after GParted and never shows the list in linux. Partitions are visible in windows
When I run sudo cat /proc/mdstat, my mdstate for the right drive shows active (auto-read-only) raid1 sdb3[0]. After following the rest of the steps when I get to sudo lvchange -ay /dev/vg289/lv3
, I get an error WARNING: Unrecognised segment type cache_client
WARNING: PV /dev/md127 in VG vg289 is using an old PV header, modify the VG to update.
Refusing activation of LV vg289/lv3 containing an unrecognised segment.
And disk does not show up in the side bar. I didn't try to mount it because it seems it may also fail. Any idea why. In this case my drive didn't die but my nas did.
Hi - sounds like you are doing the right steps - so it probably means the drive has a dynamic volume type. These instructions only work for static/traditioal volumes.
I had a ssd cache drive that failed and the 2 drives I have in raid 1 are ok but Qnap will not read the array now. If I have Linux on my PC (thats what I use), can I just mount one of the drive in disks section and find my files?
IF they are a 'static' volume then the method shown in the video will allow you to read the data off the drives. I'm working on another video that will show how to get data off all types of QNAP volumes (thick, thin, static). The basic steps for this are outlined at the end of this blog post: ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
@@ripcastercouk TY very much
Hello, I accidentally deleted the volume. Will Linux work to get my data back?
Hi, The method in the video won't. But you may be able to use other Lunix (and Windows) data recovery tools that will scan the drive sector by sector to recover know file types e.g. photos, documents etc. (assuming you haven't written anything subsequently to the drive). I hope you get your data back...
Hi there. This is very useful. Does this work with an encrypted drive too? I know the password, however I get an error message when I try to run madam. Any help will be appreciated. Thanks
Hi, I've not done this - but maybe Google "mount encrypted drive ubuntu" may help.
Hi. AT 26:54 you see your new usb connected drive in the device list. I don't. I have it ticked in the Devices dropdown. Is my disk too far gone? I have 2 RAID disks on a Wavlink 2 bay SATA adapter. THink it's RAID0, maybe RAID1. If I put in 1 drive it does similar. If I do sudo lsblk I see after sda (laptop SSDdrive) and sdb 3.9G and sdc 3.9G (I know 3.9G is shown for the disk when the ST1500L003's (1.5Tb) are faulty. Help?!
Step 1 is to make sure the physical drive is reporting the correct size to the virtual machine. See what Windows reports in Disk Management when the VM is shutdown and the drives connected. You should see a number of partitions on the drive, and it should indicate the correct overall capacity (1.5tb).
huge thanks @@ripcastercoukfro your reply. Diskmgmt shows them and then they disappear when ticked in VM. In diskmgmt they are Disk 1 and DIsk 2 but shown as Unknown/3.86 GB/Not initialised and the partitions 3.86 GB Unallocated. I know 3.86 is a default value, the disks are 1.5 TB
@@cbw2596 Drives will be removed from Disk manager in Windows when attached to VM - so that is correct. The main issue is that the drives are not reporting the correct size. Could be a fatally damaged drive (unusuall for two to exhibit the same issue?) or it could indicate your USB caddy for the drives is not working correctly - do y have an alternative to try. If USB good then it probably means the drives are bad and data recovery is beyond the scope of this method
@@ripcastercouk think this was caused by the reset not recovering well enough for intervention. I may not have given it enough time to fully cycle before powering down. These Seagate Barracuda disks exhibit this known 3.86GB fault and they wouldn't /couldn't help yesterday so I've sent them off to R3 Data Recovery who are confident, so far... Thank you for your expert help, much appreciated.
After waiting 3 hours Gparted finally worked but now I ma getting error - Warning: device /dev/sdb3 not initialized in udev databse even after waiting 10000000 microseconds. Warning: Unrecognised segment type tier-thin-pool. I can see the partition but it has red excalmation next to it and the file system is LVM2PV ---- 3.63 TiB . Can you please help how to get around this ? looks like the file system is LVM2PV. Also got another error : Error reading device /dev/sdb3 at 3990593208320 lenght 4
You have a thin provisioned volume as indicated by 'tier-thin-pool' - these instructions will only work for Static volumes. I plan to publish a video showing recovery for all volume types when I have time. The basic 'recipe' is at the end of this blog post here ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1 see section "Storage Pools and Dynamically Allocated Volumes". The long delays you are seeing are a concern. It maybe the drive has hardware failures or the USB caddy is not working correctly.
@@ripcastercouk Thanks for your reply. I would definitely wait for your video as I cant find any other source on internet to recover data from thin volume.
I and several others get stuck at this state restoring Raid 5
sudo vgscan
WARNING: Unrecognised segment type tier-thin-pool
WARNING: Unrecognised segment type thick
WARNING: Unrecognised segment type flashcache
WARNING: PV /dev/md125 in VG vg1 is using an old PV header, modify the VG to update.
LV vg1/tp1, segment 1 invalid: does not support flag ERROR_WHEN_FULL. for tier-thin-pool segment.
Internal error: LV segments corrupted in tp1.
Cannot process volume group vg1
The instruction presented here are for static volumes only. I think the warnings indicate your RAID is on a thin/thick dynamic provisioned volume. I doubt if a standard Linux (Ubuntu) has the support for these QNAP volume types. I've seen some people creating QNAP virtual machines in VMWare - so this maybe a way to mount these volume types as they are using QNAP's own code. Hope that helps Jon
Can we retrieve the data from deleted volume and migrated from RAID 1 to RAID 5
Hi, this method will not help if you have already deleted the volumes etc. You may be better looking at a low level/forensic recovery software,
Thank you for the response, any suggestions like software name or how to proceed?
This is no longer feasible option since they modified qnap's lvm2 adding new segments like tier-thin-pool, thick, flashcache
As mentioned in the video this is for static volumes only.
How do I mount my nas instead of pendrive as my data is huge ?
See our Blog post here with examples ripcaster.co.uk/Using_NAS_Storage_from_a_Linux_Computer
Does it work if you had hdd + ssd cache?
The data is stored on the volume (HDD), the Cache is only used to speed he read/write performance only - so you should look to the volume HDD for your actual data. However - given you are using a Cache I suspect you may not be using a 'static' volume. These instructions only work on Static volumes.
Hi any updates with new video?
Still trying to find the time... hopefully later this month. Jon
@@ripcastercouk appreciate your help on this will wait for it.
@@ripcastercouk Hey wondering if you got some time to look into it ?
@@abhishekmor Not yet. We do offer data recovery as a service if needed.
There's no way this method is seriously considered for use with someone's precious data. There are WAY TOO MANY instances of WILD missteps & errors here.😲😲How in God's name is there no ONE SHOT SOFTWARE available to do this WHOLE task??? It's 2023!!!!!!!!!!!!!
There are a number of commercially available packages that will attempt data recovery 'automatically'. The method presented here uses standard, freely available, Linux operating system tools. This method is only recommened if you are comfortable using the command line. We have successfully used this method many times. Please let us know any errors you may have spotted so we can update the instructions accordingly.
Drag and drop operation from guest to host failed.
DnD: Error: Dragging from guest to host not supported by guest -- make sure that the Guest Additions are properly installed and running.
Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
dawid@dawid-VirtualBox:~$ sudo lvdisplay
WARNING: Unrecognised segment type tier-thin-pool
WARNING: Unrecognised segment type thick
WARNING: PV /dev/md126 in VG vg1 is using an old PV header, modify the VG to update.
LV vg1/tp1, segment 1 invalid: does not support flag ERROR_WHEN_FULL. for tier-thin-pool segment.
Internal error: LV segments corrupted in tp1.
Cannot process volume group vg1
What to do with this ?
That indicates you have a Thick volume. This method is for 'Static' or traditional volumes only. I will make another video covering recovery from all volume types (thick, thin, static) - the outline steps of this is shown at the end of the article here ripcaster.co.uk/Data_Recovery_from_Failed_QNAP_RAID_1
when I run sudo lsblk, there is no mdxxx linked with sdc...doesn' it means I can recover my data?
sounds like the device (drive) isn't connected. check the usb device is attached to the virtual machine, then try gparted within the virtual machine to confirm the physical drive is visible to the linux os.
I tried using another HD. Following your steps and it shows similar message in the first few commands until sudo pvdisplay and nothing return..
@@dicksonyeung73 sounds like your QNAP was not configured as a static volume so this method won't work.
do you mean there is no way to recovery the data as I can't remember what type of volume selected as I just follow the user manual default when I set up the machine years ago
@@dicksonyeung73 The method shown here is for recovery of standard/static volumes only. If you fit the drives in another QNAP chassis the data should be readable. You may also find some dedicated data recovery software may work.