Forum Discussion

Aspirant

Jun 11, 2020

Solved

RN628x - XRAID not expanding volume when adding a third disk.

Hi, I have added a third disk to my ReadyNAS 628X, due to getting low on disk space. I'm using X-RAID, so my understanding is that the system should detect the new drive automatically, then convert...

deacott59
Jun 19, 2020
Hi, Yesterday I formatted the disk again and tried to create a volume on it (no RAID). It failed. The alert said it "could not find the disk, please make sure it is inserted correctly." I also noticed that although the NAS was showing the disk in the list, it could not read the temperature of it. So I removed it and tried an old WD Black 2TB disk in the slot. that worked fine and created a volume. So from this I can only think the new disk is faulty.
I have request an RMA to return it for a refund. I'll buy another disk from somewhere else.

Thank you for everyones help with finding the solution.

deacott59

Aspirant

Jun 11, 2020

Hi Stephen,

Thanks for your reply. Yes, I should have mentioned in my original post, that prior to me leaving it alone for two days, I did put the brand new disk in, but nothing happened. I noticed that I had my existing disks in Slot 7 and 8, and added the new disk to slot 6. So I removed the new disk then moved the existing disks to slot 1 and 2. It then did a resync of the two disks.

Then I added the new disk and formatted it as you mentioned, then left it for a day. Nothing happened. So I removed it, rebooted the NAS and added it again. Then I left it alone. It's now been two days and nothing except the message in the logs saying that I had added the disk.

StephenB

Guru - Experienced User

Jun 11, 2020

Try formatting it again from the web ui.

deacott59
Aspirant
Jun 11, 2020
Ok, thats been Done. Clicked on disk then selected the Format button on the right hand side. Had to type FORMAT to confirm. It took about a minute to complete. No messages in the logs. How should I wait until I should see something happen?
- Sandshark
  Sensei - Experienced User
  Jun 11, 2020
  This is an odd one. That's what could happen if the new drive was just a bit smaller than the others, but you say all are the same type.
  
  Can you do a cat /proc/mdstat from SSH or look at mdstat.log in the logs downloaded .zip and see if the OS and swap partitions (md0 and md1) are showing that they span all three drives or if the NAS is just ignoring it altogether? The an lsblk command or lsblk.log and the content of disk_info.log might also be illuminating.
  
  Toggling XRAID off and back on might trigger it, or you could go to Fl;exRAID, add the drive manually (or fail to, but get a useful error message), and then go back to XRAID.
  - deacott59
    Aspirant
    Jun 11, 2020
    Hi, I ran the mdstat and thisis what I got:
    
    Welcome to ReadyNASOS 6.10.3
    
    root@NAS:~# cat /proc/mdstat
    Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
    md127 : active raid1 sda3[2] sdb3[1]
    7809176832 blocks super 1.2 [2/2] [UU]
    md1 : active raid1 sdb2[0] sda2[1]
    523264 blocks super 1.2 [2/2] [UU]
    md0 : active raid1 sda1[2] sdb1[1]
    4190208 blocks super 1.2 [2/2] [UU]
    unused devices: <none>
    root@NAS:~#
    
    and the lsblk command gave me this:
    The new disk looks to be sdc
    root@NAS:~# lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 7.3T 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 511M 0 raid1 [SWAP]
    └─sda3 8:3 0 7.3T 0 part
    └─md127 9:127 0 7.3T 0 raid1 /data
    sdb 8:16 0 7.3T 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 511M 0 raid1 [SWAP]
    └─sdb3 8:19 0 7.3T 0 part
    └─md127 9:127 0 7.3T 0 raid1 /data
    sdc 8:32 0 7.3T 0 disk
    root@NAS:~#