I have two ReadyNAS Pro Pioneer 6-bay NAS boxes. I thought buying two would add safety so if one failed the other could be used to recover files. Wrong. Both failed at the exact same time. First it was the power supply and they wouldn't power on. I bought replacement ones and now they power on but any attempt to copy files off fails saying the source isn't accessible but I can browse the shares fine.
Now I just want to recover the files and I think I am SO close, I just don't have the Linux skills.
I have a PC that I have installed Ubuntu 22.04. I installed a Dell LSI 9211-8i card and connected all six drives. After reading some forum posts I learned to install LVM2 and MDADM.
I ran: mdadm --assemble --scan
Now I can open file manager and browse my system and I see "links" to the share names of my shares on the NAS box. But they won't open up. I must be pretty close if I can see my share names.
It says "This link cannot be used because its target "/c/Bluray" doesn't exist.
What do I do and where do I go from here to get to the data itself and copy it off?
Now I can open file manager and browse my system and I see "links" to the share names of my shares on the NAS box. But they won't open up. I must be pretty close if I can see my share names.
It says "This link cannot be used because its target "/c/Bluray" doesn't exist.
Your NAS uses lvm, but not mdadm.
Normally you'd enter something like
vgscan
vgchange -a y
mount /dev/c/c /c
or maybe use
mount -o ro /dev/c/c /c
at the end in order to mount the volume as read-only.
@StephenB OK, I'm REALLY confused now. I followed your advice and tried it without mdadm. I started from a fresh install of Ubunto 22.04 and installed only LVM2.
I ran "vgscan -v" and all that would come back is:
No volume groups found.
Same for commands "vgdisplay -v" and "lvdisplay -v"
So I tried again and installed mdadm and ran the command "mdadm --assemble --scan" and low and behold:
root@utilitybr:~# mdadm --assemble --scan mdadm: /dev/md/0 has been started with 5 drives (out of 6). mdadm: /dev/md/1 has been started with 5 drives (out of 6). mdadm: /dev/md/2 has been started with 5 drives (out of 6).
Then I went to File Manager and found again, like in my picture attachment, a new 4.3GB volume that when I browse it I see at the bottom the names of all my ReadyNAS shares. It can obviously find and read them.
This seems to tell me that it does in fact use mdadm. Am I wrong. LVM2 showed me nothing, mdadm showed me files and broken shortcuts to what I want to access.
root@UbuntuOS:~# mdadm --assemble --scan --verbose --verbose mdadm: looking for devices for /dev/md/0 mdadm: No super block found on /dev/loop13 (Expected magic a92b4efc, got 89924e23) mdadm: no RAID superblock on /dev/loop13 mdadm: No super block found on /dev/loop12 (Expected magic a92b4efc, got a6c8346c) mdadm: no RAID superblock on /dev/loop12 mdadm: No super block found on /dev/loop11 (Expected magic a92b4efc, got e525eb2a) mdadm: no RAID superblock on /dev/loop11 mdadm: No super block found on /dev/loop10 (Expected magic a92b4efc, got 1a090af0) mdadm: no RAID superblock on /dev/loop10 mdadm: No super block found on /dev/loop9 (Expected magic a92b4efc, got 3e22646e) mdadm: no RAID superblock on /dev/loop9 mdadm: No super block found on /dev/loop8 (Expected magic a92b4efc, got 6042ae44) mdadm: no RAID superblock on /dev/loop8 mdadm: No super block found on /dev/sdf3 (Expected magic a92b4efc, got 00000409) mdadm: no RAID superblock on /dev/sdf3 mdadm: No super block found on /dev/sdf2 (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdf2 mdadm: No super block found on /dev/sdf1 (Expected magic a92b4efc, got f4d143af) mdadm: no RAID superblock on /dev/sdf1 mdadm: No super block found on /dev/sdf (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdf mdadm: /dev/sdd3 has wrong uuid. mdadm: /dev/sdd2 has wrong uuid. mdadm: No super block found on /dev/sdd (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdd mdadm: /dev/sdc3 has wrong uuid. mdadm: /dev/sdc2 has wrong uuid. mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdc mdadm: /dev/sde3 has wrong uuid. mdadm: /dev/sde2 has wrong uuid. mdadm: No super block found on /dev/sde (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sde mdadm: /dev/sdb3 has wrong uuid. mdadm: /dev/sdb2 has wrong uuid. mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdb mdadm: /dev/sda3 has wrong uuid. mdadm: /dev/sda2 has wrong uuid. mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sda mdadm: No super block found on /dev/loop7 (Expected magic a92b4efc, got d5ab4258) mdadm: no RAID superblock on /dev/loop7 mdadm: No super block found on /dev/loop6 (Expected magic a92b4efc, got 1bd7e597) mdadm: no RAID superblock on /dev/loop6 mdadm: No super block found on /dev/loop5 (Expected magic a92b4efc, got 6405001a) mdadm: no RAID superblock on /dev/loop5 mdadm: No super block found on /dev/loop4 (Expected magic a92b4efc, got c4b43b1a) mdadm: no RAID superblock on /dev/loop4 mdadm: No super block found on /dev/loop3 (Expected magic a92b4efc, got c4b43b1a) mdadm: no RAID superblock on /dev/loop3 mdadm: No super block found on /dev/loop2 (Expected magic a92b4efc, got 3a23b8f9) mdadm: no RAID superblock on /dev/loop2 mdadm: No super block found on /dev/loop1 (Expected magic a92b4efc, got 3a23b8f9) mdadm: no RAID superblock on /dev/loop1 mdadm: /dev/loop0 is too small for md: size is 8 sectors. mdadm: no RAID superblock on /dev/loop0 mdadm: /dev/sdd1 is identified as a member of /dev/md/0, slot 5. mdadm: /dev/sdc1 is identified as a member of /dev/md/0, slot 0. mdadm: /dev/sde1 is identified as a member of /dev/md/0, slot 4. mdadm: /dev/sdb1 is identified as a member of /dev/md/0, slot 1. mdadm: /dev/sda1 is identified as a member of /dev/md/0, slot 3. mdadm: added /dev/sdb1 to /dev/md/0 as 1 mdadm: no uptodate device for slot 2 of /dev/md/0 mdadm: added /dev/sda1 to /dev/md/0 as 3 mdadm: added /dev/sde1 to /dev/md/0 as 4 mdadm: added /dev/sdd1 to /dev/md/0 as 5 mdadm: added /dev/sdc1 to /dev/md/0 as 0 mdadm: /dev/md/0 has been started with 5 drives (out of 6). mdadm: looking for devices for /dev/md/1 mdadm: No super block found on /dev/md/0 (Expected magic a92b4efc, got 00000101) mdadm: no RAID superblock on /dev/md/0 mdadm: No super block found on /dev/loop13 (Expected magic a92b4efc, got 89924e23) mdadm: no RAID superblock on /dev/loop13 mdadm: No super block found on /dev/loop12 (Expected magic a92b4efc, got a6c8346c) mdadm: no RAID superblock on /dev/loop12 mdadm: No super block found on /dev/loop11 (Expected magic a92b4efc, got e525eb2a) mdadm: no RAID superblock on /dev/loop11 mdadm: No super block found on /dev/loop10 (Expected magic a92b4efc, got 1a090af0) mdadm: no RAID superblock on /dev/loop10 mdadm: No super block found on /dev/loop9 (Expected magic a92b4efc, got 3e22646e) mdadm: no RAID superblock on /dev/loop9 mdadm: No super block found on /dev/loop8 (Expected magic a92b4efc, got 6042ae44) mdadm: no RAID superblock on /dev/loop8 mdadm: No super block found on /dev/sdf3 (Expected magic a92b4efc, got 00000409) mdadm: no RAID superblock on /dev/sdf3 mdadm: No super block found on /dev/sdf2 (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdf2 mdadm: No super block found on /dev/sdf1 (Expected magic a92b4efc, got f4d143af) mdadm: no RAID superblock on /dev/sdf1 mdadm: No super block found on /dev/sdf (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdf mdadm: /dev/sdd3 has wrong uuid. mdadm: /dev/sdd1 has wrong uuid. mdadm: No super block found on /dev/sdd (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdd mdadm: /dev/sdc3 has wrong uuid. mdadm: /dev/sdc1 has wrong uuid. mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdc mdadm: /dev/sde3 has wrong uuid. mdadm: /dev/sde1 has wrong uuid. mdadm: No super block found on /dev/sde (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sde mdadm: /dev/sdb3 has wrong uuid. mdadm: /dev/sdb1 has wrong uuid. mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdb mdadm: /dev/sda3 has wrong uuid. mdadm: /dev/sda1 has wrong uuid. mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sda mdadm: No super block found on /dev/loop7 (Expected magic a92b4efc, got d5ab4258) mdadm: no RAID superblock on /dev/loop7 mdadm: No super block found on /dev/loop6 (Expected magic a92b4efc, got 1bd7e597) mdadm: no RAID superblock on /dev/loop6 mdadm: No super block found on /dev/loop5 (Expected magic a92b4efc, got 6405001a) mdadm: no RAID superblock on /dev/loop5 mdadm: No super block found on /dev/loop4 (Expected magic a92b4efc, got c4b43b1a) mdadm: no RAID superblock on /dev/loop4 mdadm: No super block found on /dev/loop3 (Expected magic a92b4efc, got c4b43b1a) mdadm: no RAID superblock on /dev/loop3 mdadm: No super block found on /dev/loop2 (Expected magic a92b4efc, got 3a23b8f9) mdadm: no RAID superblock on /dev/loop2 mdadm: No super block found on /dev/loop1 (Expected magic a92b4efc, got 3a23b8f9) mdadm: no RAID superblock on /dev/loop1 mdadm: /dev/loop0 is too small for md: size is 8 sectors. mdadm: no RAID superblock on /dev/loop0 mdadm: /dev/sdd2 is identified as a member of /dev/md/1, slot 5. mdadm: /dev/sdc2 is identified as a member of /dev/md/1, slot 0. mdadm: /dev/sde2 is identified as a member of /dev/md/1, slot 4. mdadm: /dev/sdb2 is identified as a member of /dev/md/1, slot 1. mdadm: /dev/sda2 is identified as a member of /dev/md/1, slot 3. mdadm: added /dev/sdb2 to /dev/md/1 as 1 mdadm: no uptodate device for slot 2 of /dev/md/1 mdadm: added /dev/sda2 to /dev/md/1 as 3 mdadm: added /dev/sde2 to /dev/md/1 as 4 mdadm: added /dev/sdd2 to /dev/md/1 as 5 mdadm: added /dev/sdc2 to /dev/md/1 as 0 mdadm: /dev/md/1 has been started with 5 drives (out of 6). mdadm: looking for devices for /dev/md/2 mdadm: No super block found on /dev/md/1 (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/md/1 mdadm: No super block found on /dev/md/0 (Expected magic a92b4efc, got 00000101) mdadm: no RAID superblock on /dev/md/0 mdadm: No super block found on /dev/loop13 (Expected magic a92b4efc, got 89924e23) mdadm: no RAID superblock on /dev/loop13 mdadm: No super block found on /dev/loop12 (Expected magic a92b4efc, got a6c8346c) mdadm: no RAID superblock on /dev/loop12 mdadm: No super block found on /dev/loop11 (Expected magic a92b4efc, got e525eb2a) mdadm: no RAID superblock on /dev/loop11 mdadm: No super block found on /dev/loop10 (Expected magic a92b4efc, got 1a090af0) mdadm: no RAID superblock on /dev/loop10 mdadm: No super block found on /dev/loop9 (Expected magic a92b4efc, got 3e22646e) mdadm: no RAID superblock on /dev/loop9 mdadm: No super block found on /dev/loop8 (Expected magic a92b4efc, got 6042ae44) mdadm: no RAID superblock on /dev/loop8 mdadm: No super block found on /dev/sdf3 (Expected magic a92b4efc, got 00000409) mdadm: no RAID superblock on /dev/sdf3 mdadm: No super block found on /dev/sdf2 (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdf2 mdadm: No super block found on /dev/sdf1 (Expected magic a92b4efc, got f4d143af) mdadm: no RAID superblock on /dev/sdf1 mdadm: No super block found on /dev/sdf (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdf mdadm: /dev/sdd2 has wrong uuid. mdadm: /dev/sdd1 has wrong uuid. mdadm: No super block found on /dev/sdd (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdd mdadm: /dev/sdc2 has wrong uuid. mdadm: /dev/sdc1 has wrong uuid. mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdc mdadm: /dev/sde2 has wrong uuid. mdadm: /dev/sde1 has wrong uuid. mdadm: No super block found on /dev/sde (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sde mdadm: /dev/sdb2 has wrong uuid. mdadm: /dev/sdb1 has wrong uuid. mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sdb mdadm: /dev/sda2 has wrong uuid. mdadm: /dev/sda1 has wrong uuid. mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000) mdadm: no RAID superblock on /dev/sda mdadm: No super block found on /dev/loop7 (Expected magic a92b4efc, got d5ab4258) mdadm: no RAID superblock on /dev/loop7 mdadm: No super block found on /dev/loop6 (Expected magic a92b4efc, got 1bd7e597) mdadm: no RAID superblock on /dev/loop6 mdadm: No super block found on /dev/loop5 (Expected magic a92b4efc, got 6405001a) mdadm: no RAID superblock on /dev/loop5 mdadm: No super block found on /dev/loop4 (Expected magic a92b4efc, got c4b43b1a) mdadm: no RAID superblock on /dev/loop4 mdadm: No super block found on /dev/loop3 (Expected magic a92b4efc, got c4b43b1a) mdadm: no RAID superblock on /dev/loop3 mdadm: No super block found on /dev/loop2 (Expected magic a92b4efc, got 3a23b8f9) mdadm: no RAID superblock on /dev/loop2 mdadm: No super block found on /dev/loop1 (Expected magic a92b4efc, got 3a23b8f9) mdadm: no RAID superblock on /dev/loop1 mdadm: /dev/loop0 is too small for md: size is 8 sectors. mdadm: no RAID superblock on /dev/loop0 mdadm: /dev/sdd3 is identified as a member of /dev/md/2, slot 5. mdadm: /dev/sdc3 is identified as a member of /dev/md/2, slot 0. mdadm: /dev/sde3 is identified as a member of /dev/md/2, slot 4. mdadm: /dev/sdb3 is identified as a member of /dev/md/2, slot 1. mdadm: /dev/sda3 is identified as a member of /dev/md/2, slot 3. mdadm: added /dev/sdb3 to /dev/md/2 as 1 mdadm: no uptodate device for slot 2 of /dev/md/2 mdadm: added /dev/sda3 to /dev/md/2 as 3 mdadm: added /dev/sde3 to /dev/md/2 as 4 mdadm: added /dev/sdd3 to /dev/md/2 as 5 mdadm: added /dev/sdc3 to /dev/md/2 as 0 mdadm: /dev/md/2 has been started with 5 drives (out of 6).
Help from ANYONE savvy about this stuff would be greatly appreciated. I feel like it's just about a correct mount command maybe but again, I'm a windows guy - SO little linux experience.
But if I can see the broken links to the shares I created on the ReadyNAS, I have to be pretty close to being able to mount the X-RAID (RAID5) and access the data. Right?
I ran "vgscan -v" and all that would come back is:
This seems to tell me that it does in fact use mdadm. Am I wrong. LVM2 showed me nothing, mdadm showed me files and broken shortcuts to what I want to access.
@mdgm corrected my post above. Your NAS uses both mdadm and lvm2, so you need to do the vgscan after you assemble with mdadm
Actually right now I'm doing this all with test drives just to prove out the process that I "can" load it up and rescue the data this way before I try to recover from my real data disks. But I have little to no linux experience so I was really hoping someone here would have enough experience to let me know what commands to use and how to use them.
That said regarding your comment: "check disk health and the state of the RAID first" - how do I do that? Are those also LVM2/mdadm commands as well?
When I run the assemble I can see the additional disk volume and at its root are what look like shortcuts to the SHARE names I used when I created the shares on ReadyNAS. But the links are broken. It says:
"The link "Bluray" is broken"
This link cannot be used because its target "/c/Bluray/" doesn't exist.
The exact details are in the attached image.
I'm hoping someone can guide me to how to mount it correctly so "/c/Bluray/" works. Hopefully more specific than "use the mount command".
As I replied earlier (as corrected by @mdgm), you need to first assemble with mdadm.
After that you need to use lvm and mount the c volume
vgscan
vgchange -a y
mount /dev/c/c /c
You can check disk health for a disk with smartctl -x /dev/sda - using the real disk device instead of sda.
You should be able to see all the mdadm device names (raid groups) after you assemble with ls /dev/md*
The mdadm status for a NAS raid group can be checked with mdadm -D /dev/mdXXX (substituting the appropriate device number for XXX). RAID groups for NAS data volumes (c in your case) are three digits - for example, md127. If you've ever vertically expanded the array, there will be more than one RAID group for the volume.
