NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 104 X-Raid Not Expanding
Bought the 104 2 years ago with a 4TB hdd with the intention of adding new disks soon after. Fast forward 2 years and I finally got around to putting 3 more 4TB drives in.
I assumed that hot inserting them 1 at a time would get X-Raid to create a mirror (Raid 1) on the 2nd disk. It looked like this was happening and it gave me a 17h time for resyncing. About 10 minutes later it said it was complete but the volume was degraded. I thought that was pretty fast for almost 4TB of data and was concerned about the degraded status after it had been fine up until that point.
I thought I may as well add the 3rd and 4th disks and see if it jumps straight to Raid 5 and save me a lot of time but that appears to not be the case.
Any thoughts? I'm at the stage now where I'm thinking that leaving it for 24h and hoping it sorts itself out but it's worth asking here in case I'm just wasting my time.
So, I ended up backing everything up again just to be sure, factory resetting and then it picked up all the disks and then copied it all back.
Took a long time, but it's back working again now!
Thanks for your help!
5 Replies
Replies have been turned off for this discussion
Do you have SSH access enabled, and can you post the results of an lsblk command? It sounds like it my have sync'ed your OS and swap volumes, but not the data one. You can wait, but I doubt anything will happen.
The only reason your one drive arrar wasn't "degraded" is because a single-drive volume never has any redundancy to degrade. I don't think your data is any more susceptible to loss now than it was with just one drive.
Output of the command: lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 3.7T 0 disk
├─sda1 8:1 0 4G 0 part
│ └─md0 9:0 0 4G 0 raid1 /
├─sda2 8:2 0 512M 0 part
│ └─md1 9:1 0 1022M 0 raid10 [SWAP]
└─sda3 8:3 0 3.6T 0 part
└─md127 9:127 0 3.6T 0 raid1 /data
sdb 8:16 0 3.7T 0 disk
├─sdb1 8:17 0 4G 0 part
│ └─md0 9:0 0 4G 0 raid1 /
├─sdb2 8:18 0 512M 0 part
│ └─md1 9:1 0 1022M 0 raid10 [SWAP]
└─sdb3 8:19 0 3.6T 0 part
└─md127 9:127 0 3.6T 0 raid1 /data
sdc 8:32 0 3.7T 0 disk
├─sdc1 8:33 0 4G 0 part
│ └─md0 9:0 0 4G 0 raid1 /
├─sdc2 8:34 0 512M 0 part
│ └─md1 9:1 0 1022M 0 raid10 [SWAP]
└─sdc3 8:35 0 3.6T 0 part
└─md127 9:127 0 3.6T 0 raid1 /data
sdd 8:48 0 3.7T 0 disk
├─sdd1 8:49 0 4G 0 part
│ └─md0 9:0 0 4G 0 raid1 /
├─sdd2 8:50 0 512M 0 part
│ └─md1 9:1 0 1022M 0 raid10 [SWAP]
└─sdd3 8:51 0 3.6T 0 part
└─md127 9:127 0 3.6T 0 raid1 /data
mtdblock0 31:0 0 1.5M 1 disk
mtdblock1 31:1 0 512K 1 disk
mtdblock2 31:2 0 6M 1 disk
mtdblock3 31:3 0 4M 1 disk
mtdblock4 31:4 0 116M 1 diskDid a bit more digging and it looks like the 3 new drives are set as warm spares. It might have synced the partition layout explaining how it was so fast.
mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Fri Sep 4 15:22:06 2015
Raid Level : raid1
Array Size : 3902166784 (3721.40 GiB 3995.82 GB)
Used Dev Size : 3902166784 (3721.40 GiB 3995.82 GB)
Raid Devices : 2
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Mon Nov 6 09:13:05 2017
State : clean, degraded
Active Devices : 1
Working Devices : 4
Failed Devices : 0
Spare Devices : 3
Name : 43020200:data-0 (local to host 43020200)
UUID : b6e671e5:ce113ecb:42d212e3:d636db0b
Events : 645
Number Major Minor RaidDevice State
0 8 51 0 active sync /dev/sdd3
- 0 0 1 removed
1 8 35 - spare /dev/sdc3
2 8 19 - spare /dev/sdb3
3 8 3 - spare /dev/sda3
So, I ended up backing everything up again just to be sure, factory resetting and then it picked up all the disks and then copied it all back.
Took a long time, but it's back working again now!
Thanks for your help!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
