RN516+ Remove inactive volumes to use the disk (1 to 6)

---

Protect2207 wrote:

This is the reply, sdb3 event count is different, it suggest to use the dangerous --really-force

if i use this really-force, will it make that it will see again 5 drives + 1 spare in the array /dev/md/data-0 and mount it?

 

---

Well, it is supposed to do that.  As I said above, the event count mismatch means that some data was written to the array after the drive was removed.  

mdadm: NOT forcing event count in /dev/sdb3(1) from 511 up to 4581

You are missing ~4000 write events, which is a really high number.  So there will likely be some file system corruption (e.g., data loss) - there's no easy way to predict how much.

So i performed the cmd with "--really-force" and now the array sees 5 drives and 1 spare but claims not being able to still start an array.

root@NaS:/# mdadm --assemble --scan --really-force -v
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/md/1
mdadm: no recogniseable superblock on /dev/md/0
mdadm: /dev/sdf2 is busy - skipping
mdadm: /dev/sdf1 is busy - skipping
mdadm: No super block found on /dev/sdf (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdf
mdadm: /dev/sde2 is busy - skipping
mdadm: /dev/sde1 is busy - skipping
mdadm: No super block found on /dev/sde (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sde
mdadm: /dev/sdd2 is busy - skipping
mdadm: /dev/sdd1 is busy - skipping
mdadm: No super block found on /dev/sdd (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdd
mdadm: /dev/sdc2 is busy - skipping
mdadm: /dev/sdc1 is busy - skipping
mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdb2 is busy - skipping
mdadm: /dev/sdb1 is busy - skipping
mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdb
mdadm: /dev/sda2 is busy - skipping
mdadm: /dev/sda1 is busy - skipping
mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sda
mdadm: /dev/sdf3 is identified as a member of /dev/md/data-0, slot 5.
mdadm: /dev/sde3 is identified as a member of /dev/md/data-0, slot 4.
mdadm: /dev/sdd3 is identified as a member of /dev/md/data-0, slot 3.
mdadm: /dev/sdc3 is identified as a member of /dev/md/data-0, slot 2.
mdadm: /dev/sdb3 is identified as a member of /dev/md/data-0, slot 1.
mdadm: /dev/sda3 is identified as a member of /dev/md/data-0, slot -1.
mdadm: forcing event count in /dev/sdb3(1) from 511 upto 4581
mdadm: clearing FAULTY flag for device 5 in /dev/md/data-0 for /dev/sda3
mdadm: Marking array /dev/md/data-0 as 'clean'
mdadm: no uptodate device for slot 0 of /dev/md/data-0
mdadm: added /dev/sdc3 to /dev/md/data-0 as 2
mdadm: added /dev/sdd3 to /dev/md/data-0 as 3
mdadm: added /dev/sde3 to /dev/md/data-0 as 4
mdadm: added /dev/sdf3 to /dev/md/data-0 as 5
mdadm: added /dev/sda3 to /dev/md/data-0 as -1
mdadm: added /dev/sdb3 to /dev/md/data-0 as 1
mdadm: /dev/md/data-0 assembled from 5 drives and 1 spare - not enough to start the array.
mdadm: looking for devices for further assembly
mdadm: /dev/sdf2 is busy - skipping
mdadm: /dev/sdf1 is busy - skipping
mdadm: /dev/sde2 is busy - skipping
mdadm: /dev/sde1 is busy - skipping
mdadm: /dev/sdd2 is busy - skipping
mdadm: /dev/sdd1 is busy - skipping
mdadm: /dev/sdc2 is busy - skipping
mdadm: /dev/sdc1 is busy - skipping
mdadm: /dev/sdb2 is busy - skipping
mdadm: /dev/sdb1 is busy - skipping
mdadm: /dev/sda2 is busy - skipping
mdadm: /dev/sda1 is busy - skipping
mdadm: No arrays found in config file or automatically

After doing an assemble scan, it was able to start the volume making the /dev/md127 available so all my data :)

root@PNaS:/# mdadm --assemble --scan
mdadm: /dev/md/data-0 has been started with 5 drives (out of 6) and 1 spare.

root@NaS:/# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 
md127 : active raid5 sdb3[1] sda3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2]
      29278353920 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/5] [_UUUUU]
      [>....................]  recovery =  0.0% (361472/5855670784) finish=3239.5min speed=30122K/sec
      
md1 : active raid10 sdb2[0] sda2[5] sdf2[4] sde2[3] sdd2[2] sdc2[1]
      1566720 blocks super 1.2 512K chunks 2 near-copies [6/6] [UUUUUU]
      
md0 : active raid1 sda1[6] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[7]
      4190208 blocks super 1.2 [6/6] [UUUUUU]
      

After login in on the GUI i still saw all disks in RED as being inactive, after a while they turned blue "active" but i see on the left a resyncing tasks and the volume being degraded. 

It has 8 hours to run, so in the afternoon i will be able to see if i suffered some dataloss... hopefully not or minimal.

Lessons learned keep it locked away, BACKED UP.

I have an extension box for the my RN516, the EDA500, can i run a second volume on this and make a full backup of my data on the nas? Or should i just invest in a secondary nas, put it on a second site and do some rsync between them..?

Thank you :) :)

---

Protect2207 wrote:

So i performed the cmd with "--really-force" and now the array sees 5 drives and 1 spare but claims not being able to still start an array.

 

After doing an assemble scan, it was able to start the volume making the /dev/md127 available so all my data :)

 

After login in on the GUI i still saw all disks in RED as being inactive, after a while they turned blue "active" but i see on the left a resyncing tasks and the volume being degraded. 

 

It has 8 hours to run, so in the afternoon i will be able to see if i suffered some dataloss... hopefully not or minimal.

 

---

Great news!  I'm glad I was able to help (and also am hoping there is no significant loss).

---

Protect2207 wrote:

 

I have an extension box for the my RN516, the EDA500, can i run a second volume on this and make a full backup of my data on the nas? Or should i just invest in a secondary nas, put it on a second site and do some rsync between them..?

 

---

I prefer having backups on a completely different device if possible. NAS failures/issues can affect all volumes. That said, there is some value in keeping a backup on the EDA500 - that would have made recovery in this situation easier. You could use JBOD (one volume per disk) on the EDA500 volume(s) - giving up RAID redundancy in the backup, but simplifying recovery.  The EDA500 is very slow at resyncing, and using jbod works around that issue.  Using USB drives for backup is another local option.

Putting a NAS on a second site also gives you disaster recovery (theft, fire, lightning strike, etc).  The downside is that the backups will usually take longer (depending on internet service speeds), and it's harder to administer the remote NAS.  If you go that route, you should either use rsync over ssh (encrypted) or deploy some form of VPN to reach the remote site.  Also, don't forward HTTP (port 80) in the remote NAS, and use a strong admin password if you forward HTTPS (443) for remote access.

You could of course do both.

Using an EDA500 as a backup has one fluke:  If the main volume is destroyed and you have to re-create it, and the EDA volume was not Exported first, the EDA500 will not properly mount to the newly created OS.

There are two work-arounds:

Put the drives from the EDA into the main chassis and boot.  It will come up not knowing where the original main volume is, but will normally work (the OS volume RAID normally extends to the EDA500 drives).  Once it has done so, then you can Export the EDA volume and it will be ready to import into the new system.  Import is automatic at power-on.

Alternately, you can manuallt mount the EDA volume via SSH.  It will never show up in the GUI (at least, I've not figured out how), but you can copy files via SSH.