RN104 No volume exists

---

tom_nguyen_2004 wrote:

 

I use Windows and have no experience using Linix commands, however if you can guide me with the force mount command i should be able to work it out. Really appreciate you assistance.

 

---

First, you do need to be careful, as mistakes in typing can cause more damage.  Note that linux generally uses / for file paths, and not the \ that Windows uses.

 

If you never changed the admin password of the NAS (default is password), you will need to change it to something else first.

 

Then log in - you can enter "ssh root@nas-ip-address" in the windows command line if you are using windows 10 or windows 11.  Use the real IP address of course.  You will get a fingerprint query from Windows (don't recall the exact text), tell it to save the SSH fingerprint.  This will open up a black text console window on the PC for command entry. Use the NAS admin password when prompted by the NAS.

 

Then enter these commands:

 

mdadm --assemble --really-force /dev/md127 /dev/sd[abcd]3
mount /dev/md127 /data

 

 

You might get an error from the first command - I'm specifying all 4 disks, since I am not sure what three device letters are currently assigned to the other three.

 

If this doesn't work, copy/paste the console output in your reply so I can see what's going on.

 

If this does remount the data volume, then you should immediately make a backup. 

 

Please also run this command from ssh, and copy/paste the output in a reply:

 

cat /proc/mdstat

 

 You should see something like this:

 

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid5 sda3[5] sdd3[7] sdc3[6] sdb3[4]
      17567012352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

md1 : active raid10 sda2[0] sdc2[3] sdd2[2] sdb2[1]
      1044480 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]

md0 : active raid1 sda1[5] sdd1[7] sdc1[6] sdb1[4]
      4190208 blocks super 1.2 [4/4] [UUUU]

I'm interested in md0 and md1 - there was something not right with md0 in particular in your logs.  It should be mirrored on all disks, but it seemed to be only installed on one.  We should fix that also, but only after you have a backup of the data.