Been having a nightmare getting my old NSA325v1 to be viewable by my Win10 PC's and then expanded to 4TB usable RAID1.
The Samba side may be resolved (yet to check) thanks to Mijzelf's help, but expanding from 2x2TB to 2x4TB seems to be a real issue.
I followed the Disk replacement procedure and then the 'Expanding a RAID1 Volume' instructions in the manual, to the letter.
All was going OK prior the the Expansion. At this point I had both 4TB drives installed and the had been synced with one of the the 2TB drives - so the new 2x4TB drives RAID1 appeared to be 2TB usable (~90% full).
The first attempt of expansion appeared to go OK, but got stuck at 99%. I had to reboot. The second attempt does not even attempt an expand. It fsck checks the drives and goes no further.
Code: Select all
e2fsck 1.41.14 (22-Dec-2010) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/md0: 617895/122068992 files (0.8% non-contiguous) 455603841/488249472 blocks e2fsck -f -y return value:0
Its also worth pointing out that prior to any attempt at expand, if I view the folders via the file explorer on the NAS I only get a short list of mainly empty folders, whereas when I check the i-data folder via ssh putty session I see the data is on the drives. So is the partition map scr*wed?
What is the correct procedure to expand from 2x2TB to 2x4TB???