NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Re-adding disk to volume
I seem to have gotten myself in some trouble... I've got a RN104 with 4x3TB disks in it. It's running RAID-5 and encryption. v6.6.0. I got emails saying disk #4 was getting errors and that I ...
Status:
After cloning disk #4 I popped the clone in, started the NAS and logged in with SSH.
root@MyNAS:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid1 sdc2[2] sdb2[1] sda2[0]
523712 blocks super 1.2 [3/3] [UUU]
md0 : active raid1 sda1[6] sdc1[5] sdb1[4]
4190208 blocks super 1.2 [4/3] [UU_U]
unused devices: <none>
root@MyNAS:/var/log/readynasd# mdadm --assemble --scan -v
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/md1
mdadm: no recogniseable superblock on /dev/md/0
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: No super block found on /dev/mtdblock4 (Expected magic a92b4efc, got 06101831)
mdadm: no RAID superblock on /dev/mtdblock4
mdadm: No super block found on /dev/mtdblock3 (Expected magic a92b4efc, got 5726f12c)
mdadm: no RAID superblock on /dev/mtdblock3
mdadm: No super block found on /dev/mtdblock2 (Expected magic a92b4efc, got e580c000)
mdadm: no RAID superblock on /dev/mtdblock2
mdadm: No super block found on /dev/mtdblock1 (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/mtdblock1
mdadm: No super block found on /dev/mtdblock0 (Expected magic a92b4efc, got 2b023063)
mdadm: no RAID superblock on /dev/mtdblock0
mdadm: /dev/sdc3 is identified as a member of /dev/md/data-0, slot 1.
mdadm: /dev/sdb3 is identified as a member of /dev/md/data-0, slot 2.
mdadm: /dev/sda3 is identified as a member of /dev/md/data-0, slot 3.
mdadm: no uptodate device for slot 0 of /dev/md/data-0
mdadm: added /dev/sdb3 to /dev/md/data-0 as 2
mdadm: added /dev/sda3 to /dev/md/data-0 as 3 (possibly out of date)
mdadm: added /dev/sdc3 to /dev/md/data-0 as 1
mdadm: /dev/md/data-0 assembled from 2 drives - not enough to start the array.
mdadm: looking for devices for further assembly
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
root@MyNAS:/var/log/readynasd# mdadm --examine /dev/sd[a-g]3
/dev/sda3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b1340f07:7ebeb430:31028483:bfd6dd5b
Name : 0e35246e:data-0 (local to host 0e35246e)
Creation Time : Sat Dec 28 10:22:45 2013
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850833742 (2789.89 GiB 2995.63 GB)
Array Size : 8776250112 (8369.68 GiB 8986.88 GB)
Used Dev Size : 5850833408 (2789.89 GiB 2995.63 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262064 sectors, after=334 sectors
State : clean
Device UUID : a063c204:8a5493bb:5193b40d:d7ac0533
Update Time : Wed Nov 30 19:47:35 2016
Checksum : 349c514c - correct
Events : 25926
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b1340f07:7ebeb430:31028483:bfd6dd5b
Name : 0e35246e:data-0 (local to host 0e35246e)
Creation Time : Sat Dec 28 10:22:45 2013
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850833742 (2789.89 GiB 2995.63 GB)
Array Size : 8776250112 (8369.68 GiB 8986.88 GB)
Used Dev Size : 5850833408 (2789.89 GiB 2995.63 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=334 sectors
State : clean
Device UUID : 75ea7b81:9c6e1b73:636dd3bc:bfddbcc4
Update Time : Thu Dec 1 08:54:34 2016
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : a9b8beea - correct
Events : 28678
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 2
Array State : .AA. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b1340f07:7ebeb430:31028483:bfd6dd5b
Name : 0e35246e:data-0 (local to host 0e35246e)
Creation Time : Sat Dec 28 10:22:45 2013
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850833742 (2789.89 GiB 2995.63 GB)
Array Size : 8776250112 (8369.68 GiB 8986.88 GB)
Used Dev Size : 5850833408 (2789.89 GiB 2995.63 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=334 sectors
State : clean
Device UUID : 3d749b6f:9e210956:aac73191:571ded87
Update Time : Thu Dec 1 08:54:34 2016
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 12549594 - correct
Events : 28678
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 1
Array State : .AA. ('A' == active, '.' == missing, 'R' == replacing)
root@MyNAS:/var/log/readynasd# mdadm --assemble --force /dev/md/data-0 /dev/sdc3 /dev/sdb3 /dev/sda3 -v
mdadm: looking for devices for /dev/md/data-0
mdadm: /dev/sdc3 is identified as a member of /dev/md/data-0, slot 1.
mdadm: /dev/sdb3 is identified as a member of /dev/md/data-0, slot 2.
mdadm: /dev/sda3 is identified as a member of /dev/md/data-0, slot 3.
mdadm: NOT forcing event count in /dev/sda3(3) from 25926 up to 28678
mdadm: You can use --really-force to do that (DANGEROUS)
mdadm: no uptodate device for slot 0 of /dev/md/data-0
mdadm: added /dev/sdb3 to /dev/md/data-0 as 2
mdadm: added /dev/sda3 to /dev/md/data-0 as 3 (possibly out of date)
mdadm: added /dev/sdc3 to /dev/md/data-0 as 1
mdadm: /dev/md/data-0 assembled from 2 drives - not enough to start the array.
root@MyNAS:/var/log/readynasd# mdadm --assemble --really-force /dev/md/data-0 /dev/sdc3 /dev/sdb3 /dev/sda3 -v
mdadm: looking for devices for /dev/md/data-0
mdadm: /dev/sdc3 is identified as a member of /dev/md/data-0, slot 1.
mdadm: /dev/sdb3 is identified as a member of /dev/md/data-0, slot 2.
mdadm: /dev/sda3 is identified as a member of /dev/md/data-0, slot 3.
mdadm: forcing event count in /dev/sda3(3) from 25926 upto 28678
mdadm: clearing FAULTY flag for device 2 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/sdb3 to /dev/md/data-0 as 2
mdadm: added /dev/sda3 to /dev/md/data-0 as 3
mdadm: added /dev/sdc3 to /dev/md/data-0 as 1
mdadm: /dev/md/data-0 assembled from 3 drives - not enough to start the array.
root@MyNAS:/var/log/readynasd# mdadm --assemble --really-force --run /dev/md/data-0 /dev/sdc3 /dev/sdb3 /dev/sda3 -v
mdadm: looking for devices for /dev/md/data-0
mdadm: /dev/sdc3 is identified as a member of /dev/md/data-0, slot 1.
mdadm: /dev/sdb3 is identified as a member of /dev/md/data-0, slot 2.
mdadm: /dev/sda3 is identified as a member of /dev/md/data-0, slot 3.
mdadm: no uptodate device for slot 0 of /dev/md/data-0
mdadm: added /dev/sdb3 to /dev/md/data-0 as 2
mdadm: added /dev/sda3 to /dev/md/data-0 as 3
mdadm: added /dev/sdc3 to /dev/md/data-0 as 1
mdadm: /dev/md/data-0 has been started with 3 drives (out of 4).
root@MyNAS:/var/log/readynasd# mdadm --examine /dev/sd[a-g]3
/dev/sda3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b1340f07:7ebeb430:31028483:bfd6dd5b
Name : 0e35246e:data-0 (local to host 0e35246e)
Creation Time : Sat Dec 28 10:22:45 2013
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850833742 (2789.89 GiB 2995.63 GB)
Array Size : 8776250112 (8369.68 GiB 8986.88 GB)
Used Dev Size : 5850833408 (2789.89 GiB 2995.63 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262064 sectors, after=334 sectors
State : clean
Device UUID : a063c204:8a5493bb:5193b40d:d7ac0533
Update Time : Wed Nov 30 19:47:35 2016
Checksum : 349c5c0c - correct
Events : 28678
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b1340f07:7ebeb430:31028483:bfd6dd5b
Name : 0e35246e:data-0 (local to host 0e35246e)
Creation Time : Sat Dec 28 10:22:45 2013
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850833742 (2789.89 GiB 2995.63 GB)
Array Size : 8776250112 (8369.68 GiB 8986.88 GB)
Used Dev Size : 5850833408 (2789.89 GiB 2995.63 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=334 sectors
State : clean
Device UUID : 75ea7b81:9c6e1b73:636dd3bc:bfddbcc4
Update Time : Thu Dec 1 08:54:34 2016
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : a9b8beea - correct
Events : 28678
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 2
Array State : .AA. ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc3:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : b1340f07:7ebeb430:31028483:bfd6dd5b
Name : 0e35246e:data-0 (local to host 0e35246e)
Creation Time : Sat Dec 28 10:22:45 2013
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 5850833742 (2789.89 GiB 2995.63 GB)
Array Size : 8776250112 (8369.68 GiB 8986.88 GB)
Used Dev Size : 5850833408 (2789.89 GiB 2995.63 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=334 sectors
State : clean
Device UUID : 3d749b6f:9e210956:aac73191:571ded87
Update Time : Thu Dec 1 08:54:34 2016
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 12599593 - correct
Events : 28678
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 1
Array State : .AAA ('A' == active, '.' == missing, 'R' == replacing)
root@MyNAS:/var/log/readynasd# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid5 sdc3[5] sda3[3] sdb3[4]
8776250112 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [_UUU]
md1 : active raid1 sdc2[2] sdb2[1] sda2[0]
523712 blocks super 1.2 [3/3] [UUU]
md0 : active raid1 sda1[6] sdc1[5] sdb1[4]
4190208 blocks super 1.2 [4/3] [UU_U]
unused devices: <none>So I think I managed to get the array up and running again... However in the ReadyNAS web interface the disks still show up as red. Should I run cryptsetup luksOpen or something like that? Or should I just try restarting the NAS?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
