NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
readynas ultra 4 plus expansion fails
dear everybody
it seems my trusty ultra does not want to expand when given a new disk. the original configuration was 2tb, 3tb, 3tb,3tb. giving me around 7tb of space. i've replaced the 2tb with a 4tb disk now, and while the raid has (after a few reboots) synced and everything, expansion does not happen.
i'd really like to avoid a factory reset, since i don't have enough space for a proper backup.
the expansion log says the following regarding this matter:
and then it complains about not enough disk for a new array.
does anyone have any ideas?
cheers
majello
it seems my trusty ultra does not want to expand when given a new disk. the original configuration was 2tb, 3tb, 3tb,3tb. giving me around 7tb of space. i've replaced the 2tb with a 4tb disk now, and while the raid has (after a few reboots) synced and everything, expansion does not happen.
i'd really like to avoid a factory reset, since i don't have enough space for a proper backup.
the expansion log says the following regarding this matter:
[2015/04/18 17:51:29 8026] exec command: Selected: 3 total=3907018584 used/resv=2930264483/60000000 free=976754101, cl_at=0, property4k=1
[2015/04/18 17:51:29 8026] Not enough disk for a new array, drives with free space: 1, X_level:5
[2015/04/18 17:51:29 8026] STAGE_WIPE: Clean my_pid 8026
[2015/04/19 20:36:39 1973] Boot, handle mutiple expand_md
[2015/04/19 20:36:40 1974] STAGE_CHECK: saved my_pid 1974 in check mode.
[2015/04/19 20:36:40 1974] RAID MODE: 1, sn=
[2015/04/19 20:36:41 1974] LINE 4591: exec command: lvs > /var/log/frontview/.V_E.snapshotstat
[2015/04/19 20:36:41 1974] Current file system status: ext4
[2015/04/19 20:36:41 1974] LINE 5229: exec command: rm -fr /var/log/frontview/.V_E.*
[2015/04/19 20:36:42 1974] X_level: 5
[2015/04/19 20:36:42 1974] /usr/sbin/expand_md
[2015/04/19 20:36:42 1974] MD degraded 0, bg_job 0, boot 1
[2015/04/19 20:36:42 1974] Read 1957072 byte from configuration
[2015/04/19 20:36:42 1974] Disk configuration matching with online configuration.
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sdb format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sdb used/total/partitioned = 2930264483/2930266584/2930264483, 60000000
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sdc format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sdc used/total/partitioned = 2930264483/2930266584/2930264483, 60000000
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sdd format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sdd used/total/partitioned = 2930264483/2930266584/2930264483, 60000000
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sda format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sda used/total/partitioned = 2930264483/3907018584/2930264483, 60000000
[2015/04/19 20:36:42 1974] Checking: want expand from /dev/sda 2930264483, already in use /dev/sdb 2930264483
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sdb format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sda:2(2-gpt 1-mbr) correct used blocks 2930264483
[2015/04/19 20:36:42 1974] Checking: want expand from /dev/sda 2930264483, already in use /dev/sdc 2930264483
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sdc format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sda:2(2-gpt 1-mbr) correct used blocks 2930264483
[2015/04/19 20:36:42 1974] Checking: want expand from /dev/sda 2930264483, already in use /dev/sdd 2930264483
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sdd format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sda:2(2-gpt 1-mbr) correct used blocks 2930264483
[2015/04/19 20:36:42 1974] Checking: want expand from /dev/sda 2930264483, already in use /dev/sda 2930264483
[2015/04/19 20:36:42 1974] gpt sig:0,mbr sig:0,fake type:0
[2015/04/19 20:36:42 1974] get disk /dev/sda format is (GPT=2,MBR=1,MX=3,MISC=-1): 2
[2015/04/19 20:36:42 1974] /dev/sda:2(2-gpt 1-mbr) correct used blocks 2930264483
[2015/04/19 20:36:42 1974] exec command: Selected: 3 total=3907018584 used/resv=2930264483/60000000 free=976754101, cl_at=0, property4k=1
and then it complains about not enough disk for a new array.
does anyone have any ideas?
cheers
majello
9 Replies
Replies have been turned off for this discussion
- Can you send me your logs (see the Sending Logs link in my sig)?
- Thanks for the quick reply, mdgm.
i've sent the logs as per the instructions in your link.
if there is anything i can do in the meantime, let me know. - Do you have a backup?
- For some of it, but not everything. The box is pretty full and I don't have enough storage space around unfortunately.
Sorry for coming with this again, I've reported this problem previously, but was to busy to act on the offer by mdmg to look into it further.
I've upgraded one of my disks from previously 2TB to 4 TB (the other 3 are all 3TB). Unfortunately no expansion happened after detecting the new disk, which is kind of annoying.
i've now looked into things, and one thing i've noticed is that fdisk reports the first disk as 3TB (Disk /dev/sda: 4294967295 sectors, 2047G), the exact same size as the others. to be precise, /dev/sda to /dev/sdd all look like this:
Disk /dev/sdd: 4294967295 sectors, 2047G
Logical sector size: 512
Disk identifier (GUID): xxxxxxx
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134Number Start (sector) End (sector) Size Code Name
1 64 8388671 4096M 0700
2 8388672 9437247 512M 0700
3 9437248 3907025072 1858G 0700
4 3907025080 5860529038 931G 0700in addition, sda shows the last usable sector as 7814037134, which would fit the disk size...
is that normal, or the root of the problem? what could i do?
thanks in advance for any pointers
4294967295 is 2**32-1 -> the largest size possible with MBR. Note that with a sector size of 512 bytes, that is a 2 TiB partition.
So that value comes from protective MBR, the real GPT partitions are shown later on:
Number Start (sector) End (sector) Size Code Name
1 64 8388671 4096M 0700
2 8388672 9437247 512M 0700
3 9437248 3907025072 1858G 0700
4 3907025080 5860529038 931G 0700This does add up to 3 TB.
What should you do? Re-engage with mdgm :smileywink:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
