NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Replaced failing disk in NV+ v2 - both volume expansion and volume scan fail
Hi folks,
I'm getting some slightly peculiar behaviour from my NV+ v2, and would really appreciate some help in troubleshooting.
A week or so ago, I started getting errors on disk 1 of my NAS, which was configured as follows:
1: 3Tb
2: 4Tb
3: 3Tb
4: 4Tb
For reference, the original configuration when I first set up the NAS, was 2x3Tb.
I bought a new 4Tb disk (same type as in bays 2 and 4), pulled out disk 1, and replaced it with the new 4Tb disk.
The following is (unfortunately reverse time order) the current log info from the admin view, beginning from the second (and last) failed attempt to expand the volume:
| Mon Sep 14 15:11:51 EST 2015 | Volume expansion failed | |
| Mon Sep 14 14:58:17 EST 2015 | Incompleted file system expansion detected. Resuming... | |
| Mon Sep 14 14:57:04 EST 2015 | Volume expansion failed | |
| Mon Sep 14 14:39:56 EST 2015 | Newly added drive has more space to expand the volume, will start volume expansion. | |
| Mon Sep 14 14:39:35 EST 2015 | RAID sync finished on volume C. | |
| Sat Sep 12 11:17:21 EST 2015 | RAID sync started on volume C. | |
| Sat Sep 12 11:16:46 EST 2015 | Data volume will be rebuilt with disk 1. | |
| Sat Sep 12 11:16:27 EST 2015 | New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 1] | |
| Sat Sep 12 11:11:20 EST 2015 | A disk was removed from the ReadyNAS. One or more RAID volumes are currently unprotected, and an additional disk failure or removal may result in data loss. Please add a replacement disk as soon as possible. |
As you can see, everything seemed fine until 14:57 on 14 September when the first attempt at volume expansion fails. And then a second time at 15:11 on 14 September. After that, it appeared to give up on the idea of volume expansion, so I tried a reboot (with a volume scan). Here's where it gets a bit more unsettling: volume scan also failed, quite quickly, when it attempted to run. On wading through the logs, I see the system killed fsck (or fsck killed itself) because it is out of memory. This seems a bizarre condition to encounter on startup... and yet, it now appears to do it every time.
Although - for now - it is claiming to be redundant (albeit still the old size), there doesn't appear any reason why the expansion should have failed (I don't believe I'm at the 8TiB expansion limit yet - that should happen the next time I replace a 3Tb with a 4Tb, not this time)... and no way to clear its head so it can do something as straightforward as a volume scan.
Is there a known bug in the system? Any idea what options I have? I'm not averse to doing things via SSH if there are further options to pursue there, but I want to be sure to do the right things.
31 Replies
Replies have been turned off for this discussion
I couldn't include log output in the original message due to character limits.
I have downloaded the logs, and happy to look things up in specific places. In the mean time, the following seem to be the relevant part of expand_md.log:
[2015/09/14 14:39:47 23206] Added drive to md, grown=1/0xbebb6a6c [2015/09/14 14:39:47 23206] Repair caused array grow, will do expansion... [2015/09/14 14:39:56 23206] LINE 4440: exec command: vgdisplay -c c > /var/log/frontview/.V_E.vgdisplayout ; lvdisplay -c c > /var/log/frontview/.V_E.lvdisplayout File descriptor 3 (/etc/resolv.conf (deleted)) leaked on vgdisplay invocation. Parent PID 29226: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvdisplay invocation. Parent PID 29226: sh [2015/09/14 14:39:56 23206] 0 vg= c lv= /dev/c/c [2015/09/14 14:39:56 23206] 1 vg=r/w lv=c [2015/09/14 14:39:56 23206] 2 vg=772 lv=3 [2015/09/14 14:39:56 23206] 3 vg=-1 lv=1 [2015/09/14 14:39:56 23206] 4 vg=0 lv=-1 [2015/09/14 14:39:56 23206] 5 vg=1 lv=1 [2015/09/14 14:39:56 23206] 6 vg=1 lv=19485687808 [2015/09/14 14:39:56 23206] 7 vg=-1 lv=148664 [2015/09/14 14:39:56 23206] 8 vg=0 lv=-1 [2015/09/14 14:39:56 23206] 9 vg=2 lv=0 [2015/09/14 14:39:56 23206] 10 vg=2 lv=-1 [2015/09/14 14:39:56 23206] 11 vg=9753329664 lv=253 [2015/09/14 14:39:56 23206] 12 vg=65536 lv=0 [2015/09/14 14:39:56 23206] 13 vg=148824 lv=13 [2015/09/14 14:39:56 23206] 14 vg=148664 lv=14 [2015/09/14 14:39:56 23206] 15 vg=160 lv=15 [2015/09/14 14:39:56 23206] 16 vg=rGs2iy-Av5h-nfXC-oAH1-bzUt-W3OP-Vfcp37 lv=16 [2015/09/14 14:39:56 23206] 17 vg=17 lv=17 [2015/09/14 14:39:56 23206] 18 vg=18 lv=18 [2015/09/14 14:39:56 23206] 19 vg=19 lv=19 [2015/09/14 14:39:56 23206] LINE 4879: exec command: pvresize /dev/md2 File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvresize invocation. Parent PID 23206: /usr/sbin/expand_md Physical volume "/dev/md2" changed 1 physical volume(s) resized / 0 physical volume(s) not resized [2015/09/14 14:39:57 23206] LINE 4879: exec command: pvresize /dev/md3 File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvresize invocation. Parent PID 23206: /usr/sbin/expand_md Physical volume "/dev/md3" changed 1 physical volume(s) resized / 0 physical volume(s) not resized [2015/09/14 14:39:59 23206] LINE 4440: exec command: vgdisplay -c c > /var/log/frontview/.V_E.vgdisplayout ; lvdisplay -c c > /var/log/frontview/.V_E.lvdisplayout File descriptor 3 (/etc/resolv.conf (deleted)) leaked on vgdisplay invocation. Parent PID 29236: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvdisplay invocation. Parent PID 29236: sh [2015/09/14 14:40:00 23206] 0 vg= c lv= /dev/c/c [2015/09/14 14:40:00 23206] 1 vg=r/w lv=c [2015/09/14 14:40:00 23206] 2 vg=772 lv=3 [2015/09/14 14:40:00 23206] 3 vg=-1 lv=1 [2015/09/14 14:40:00 23206] 4 vg=0 lv=-1 [2015/09/14 14:40:00 23206] 5 vg=1 lv=1 [2015/09/14 14:40:00 23206] 6 vg=1 lv=19485687808 [2015/09/14 14:40:00 23206] 7 vg=-1 lv=148664 [2015/09/14 14:40:00 23206] 8 vg=0 lv=-1 [2015/09/14 14:40:00 23206] 9 vg=2 lv=0 [2015/09/14 14:40:00 23206] 10 vg=2 lv=-1 [2015/09/14 14:40:00 23206] 11 vg=10730078208 lv=253 [2015/09/14 14:40:00 23206] 12 vg=65536 lv=0 [2015/09/14 14:40:00 23206] 13 vg=163728 lv=13 [2015/09/14 14:40:00 23206] 14 vg=148664 lv=14 [2015/09/14 14:40:00 23206] 15 vg=15064 lv=15 [2015/09/14 14:40:00 23206] 16 vg=rGs2iy-Av5h-nfXC-oAH1-bzUt-W3OP-Vfcp37 lv=16 [2015/09/14 14:40:00 23206] 17 vg=17 lv=17 [2015/09/14 14:40:00 23206] 18 vg=18 lv=18 [2015/09/14 14:40:00 23206] 19 vg=19 lv=19 [2015/09/14 14:40:00 23206] Facts:vg_total=163728,vg_alloc=148664,vg_free=15064,lv_new=14904,lv_total=% [2015/09/14 14:40:00 23206] LINE 4694: exec command: lvextend /dev/c/c -l +14904 File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvextend invocation. Parent PID 23206: /usr/sbin/expand_md Extending logical volume c to 9.98 TiB Logical volume c successfully resized [2015/09/14 14:40:02 23206] LINE 4892: exec command: /frontview/bin/volumescan & [2015/09/14 14:40:03 23206] LINE 540: exec command: echo "DOING_F_RESIZE" > /.os_V_E_continue [2015/09/14 14:40:03 23206] LINE 4569: exec command: resize2fs -pf /dev/c/c resize2fs 1.41.14 (22-Dec-2010) File descriptor 3 (/etc/resolv.conf (deleted)) leaked on vgscan invocation. Parent PID 29287: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvdisplay invocation. Parent PID 29244: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvdisplay invocation. Parent PID 29244: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvdisplay invocation. Parent PID 29244: sh resize2fs: Memory allocation failed while trying to resize /dev/c/c Please run 'e2fsck -fy /dev/c/c' to fix the filesystem after the aborted resize operation. Filesystem at /dev/c/c is mounted on /c; on-line resizing required old desc_blocks = 581, new_desc_blocks = 639 [2015/09/14 14:56:54 23206] Expand second phase error 10: resize2fs, err=0x100 [2015/09/14 14:57:04 23206] Volume expand failed, no drive added [2015/09/14 14:57:04 23206] launch expand_md again for vol expansion [2015/09/14 14:57:04 23206] LINE 6815: exec command: /usr/sbin/expand_md >> /var/log/frontview/expand_md.log 2>&1 & [2015/09/14 14:57:05 23206] xraid mode 1 disk count 4 flex level -1 [2015/09/14 14:57:05 23206] raid mode 1 data_degraded 1 disk count 4 [2015/09/14 14:57:05 23206] LINE 5210: exec command: /usr/sbin/expand_md -a super >> /var/log/frontview/expand_md.log 2>&1 & [2015/09/14 14:57:05 23206] LINE 5213: exec command: /frontview/bin/volumescan & [2015/09/14 14:57:06 23206] STAGE_WIPE: Clean my_pid 23206 [2015/09/14 14:57:06 29496] STAGE_CHECK: saved my_pid 29496 in check mode. [2015/09/14 14:57:06 29496] RAID MODE: 1, sn= File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvs invocation. Parent PID 29508: sh [2015/09/14 14:57:06 29496] LINE 4928: exec command: lvs > /var/log/frontview/.V_E.snapshotstat [2015/09/14 14:57:07 29496] Current file system status: ext4 [2015/09/14 14:57:07 29496] LINE 6523: exec command: rm -fr /var/log/frontview/.V_E.* [2015/09/14 14:57:07 29496] X_level: 5 [2015/09/14 14:57:07 29496] /usr/sbin/expand_md -a super [2015/09/14 14:57:07 29496] MD degraded 0, bg_job 0, boot 0 [2015/09/14 14:57:07 29496] ++++Write 2049488 byte to configuration++++ [2015/09/14 14:57:07 29496] /var/log/frontview/.known_cfgdir/W1F2NA5K [2015/09/14 14:57:07 29496] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 14:57:07 29496] get disk /dev/sdc format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 14:57:07 29496] LINE 9650: exec command: sgdisk -p /dev/sdc | grep '[0-9] ' > /var/log/frontview/.known_cfgdir/W1F2NA5K [2015/09/14 14:57:10 29496] /var/log/frontview/.known_cfgdir/S301BHFT - [2015/09/14 14:57:16 29496] used_disk_pt_count:4,start:4 xraid level is 5 [2015/09/14 14:57:16 29496] Not enough disk for a new array, drives with free space: 0, X_level:5 [2015/09/14 14:57:16 29496] STAGE_WIPE: Clean my_pid 29496 [2015/09/14 14:57:45 29078] STAGE_CHECK: saved my_pid 29078 in check mode. [2015/09/14 14:57:45 29078] RAID MODE: 1, sn= [2015/09/14 14:57:45 29078] LINE 4928: exec command: lvs > /var/log/frontview/.V_E.snapshotstat [2015/09/14 14:57:45 29078] Current file system status: ext4 [2015/09/14 14:57:45 29078] LINE 6523: exec command: rm -fr /var/log/frontview/.V_E.* [2015/09/14 14:57:46 29078] X_level: 5 [2015/09/14 14:57:46 29078] /usr/sbin/expand_md -a super [2015/09/14 14:57:46 29078] MD degraded 0, bg_job 0, boot 0 [2015/09/14 14:57:46 29078] ++++Write 2049488 byte to configuration++++ [2015/09/14 14:57:46 29078] /var/log/frontview/.known_cfgdir/W1F2NA5K [2015/09/14 14:57:46 29078] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 14:57:46 29078] get disk /dev/sdc format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 14:57:46 29078] LINE 9650: exec command: sgdisk -p /dev/sdc | grep '[0-9] ' > /var/log/frontview/.known_cfgdir/W1F2NA5K [2015/09/14 14:57:47 29078] Sgdisk /dev/sdc partition to file Error. rc = -1 [2015/09/14 14:57:47 29078] /var/log/frontview/.known_cfgdir/S301BHFT - repetitions snipped for character limits -
[2015/09/14 14:57:51 29078] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 14:57:51 29078] get disk /dev/sda format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 14:57:51 29078] /dev/sda used/total/partitioned = 3907016483/3907018584/3907016483, 60000000 [2015/09/14 14:57:51 29078] used_disk_pt_count:4,start:4 xraid level is 5 [2015/09/14 14:57:51 29078] Not enough disk for a new array, drives with free space: 0, X_level:5 [2015/09/14 14:57:51 29078] STAGE_WIPE: Clean my_pid 29078 [2015/09/14 14:58:07 29493] STAGE_CHECK: saved my_pid 29493 in check mode. [2015/09/14 14:58:07 29493] RAID MODE: 1, sn= File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvs invocation. Parent PID 29652: sh [2015/09/14 14:58:07 29493] LINE 4928: exec command: lvs > /var/log/frontview/.V_E.snapshotstat [2015/09/14 14:58:08 29493] Current file system status: ext4 [2015/09/14 14:58:08 29493] LINE 6523: exec command: rm -fr /var/log/frontview/.V_E.* [2015/09/14 14:58:08 29493] X_level: 5 [2015/09/14 14:58:08 29493] /usr/sbin/expand_md [2015/09/14 14:58:08 29493] MD degraded 0, bg_job 0, boot 0 [2015/09/14 14:58:08 29493] Read 2049488 byte from configuration [2015/09/14 14:58:08 29493] Disk configuration matching with online configuration. [2015/09/14 14:58:08 29493] Should do expand now... [2015/09/14 14:58:08 29493] ===== Partition Entry (MD not used) ===== [2015/09/14 14:58:08 29493] ===== Partition Entry (Used by MD) ===== [2015/09/14 14:58:08 29493] 000 /dev/sdc,W1F2NA5K,8, 32, 2930266584 2930264504 2930264504 MD_FULL 0 [2015/09/14 14:58:08 29493] partitions: 3 property: 4K [2015/09/14 14:58:08 29493] 000 /dev/sdc1, 8, 33, 4194304 MD_FULL md=/dev/md0 [2015/09/14 14:58:08 29493] 001 /dev/sdc2, 8, 34, 524288 MD_FULL md=/dev/md1 [2015/09/14 14:58:08 29493] 002 /dev/sdc3, 8, 35, 2925545912 MD_FULL md=/dev/md2 [2015/09/14 14:58:08 29493] 001 /dev/sdb,S301BHFT,8, 16, 3907018584 3907016483 3907016483 MD_FULL 0 [2015/09/14 14:58:08 29493] partitions: 4 property: 4K [2015/09/14 14:58:08 29493] 000 /dev/sdb1, 8, 17, 4194304 MD_FULL md=/dev/md0 [2015/09/14 14:58:08 29493] 001 /dev/sdb2, 8, 18, 524288 MD_FULL md=/dev/md1 [2015/09/14 14:58:08 29493] 002 /dev/sdb3, 8, 19, 2925545912 MD_FULL md=/dev/md2 [2015/09/14 14:58:08 29493] 003 /dev/sdb4, 8, 20, 976751979 MD_FULL md=/dev/md3 [2015/09/14 14:58:08 29493] 002 /dev/sdd,S301BHV7,8, 48, 3907018584 3907016483 3907016483 MD_FULL 0 [2015/09/14 14:58:08 29493] partitions: 4 property: 4K [2015/09/14 14:58:08 29493] 000 /dev/sdd1, 8, 49, 4194304 MD_FULL md=/dev/md0 [2015/09/14 14:58:08 29493] 001 /dev/sdd2, 8, 50, 524288 MD_FULL md=/dev/md1 [2015/09/14 14:58:08 29493] 002 /dev/sdd3, 8, 51, 2925545912 MD_FULL md=/dev/md2 [2015/09/14 14:58:08 29493] 003 /dev/sdd4, 8, 52, 976751979 MD_FULL md=/dev/md3 [2015/09/14 14:58:08 29493] 003 /dev/sda,Z3039RT9,8, 0, 3907018584 3907016483 3907016483 MD_FULL 0 [2015/09/14 14:58:08 29493] partitions: 4 property: 4K [2015/09/14 14:58:08 29493] 000 /dev/sda1, 8, 1, 4194304 MD_FULL md=/dev/md0 [2015/09/14 14:58:08 29493] 001 /dev/sda2, 8, 2, 524288 MD_FULL md=/dev/md1 [2015/09/14 14:58:08 29493] 002 /dev/sda3, 8, 3, 2925545912 MD_FULL md=/dev/md2 [2015/09/14 14:58:08 29493] 003 /dev/sda4, 8, 4, 976751979 MD_FULL md=/dev/md3 [2015/09/14 14:58:08 29493] Found leftover expansion actions DOING_F_RESIZE , continue... [2015/09/14 14:58:17 29493] LINE 540: exec command: echo "DOING_F_RESIZE" > /.os_V_E_continue [2015/09/14 14:58:18 29493] LINE 4569: exec command: resize2fs -pf /dev/c/c resize2fs 1.41.14 (22-Dec-2010) resize2fs: Memory allocation failed while trying to resize /dev/c/c Please run 'e2fsck -fy /dev/c/c' to fix the filesystem after the aborted resize operation. Filesystem at /dev/c/c is mounted on /c; on-line resizing required old desc_blocks = 581, new_desc_blocks = 639 [2015/09/14 15:11:40 29493] Expand second phase error 10: resize2fs, err=0x100 [2015/09/14 15:11:51 29493] File system expand failed [2015/09/14 15:11:51 29493] LINE 5210: exec command: /usr/sbin/expand_md -a super >> /var/log/frontview/expand_md.log 2>&1 & [2015/09/14 15:11:51 29493] LINE 5213: exec command: /frontview/bin/volumescan & [2015/09/14 15:11:52 29493] STAGE_WIPE: Clean my_pid 29493 [2015/09/14 15:11:52 29810] STAGE_CHECK: saved my_pid 29810 in check mode. [2015/09/14 15:11:52 29810] RAID MODE: 1, sn= File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvs invocation. Parent PID 29822: sh [2015/09/14 15:11:53 29810] LINE 4928: exec command: lvs > /var/log/frontview/.V_E.snapshotstat [2015/09/14 15:11:53 29810] Current file system status: ext4 [2015/09/14 15:11:53 29810] LINE 6523: exec command: rm -fr /var/log/frontview/.V_E.* [2015/09/14 15:11:53 29810] X_level: 5 [2015/09/14 15:11:53 29810] /usr/sbin/expand_md -a super [2015/09/14 15:11:53 29810] MD degraded 0, bg_job 0, boot 0 [2015/09/14 15:11:53 29810] ++++Write 2049488 byte to configuration++++ [2015/09/14 15:11:53 29810] /var/log/frontview/.known_cfgdir/W1F2NA5K [2015/09/14 15:11:53 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:11:53 29810] get disk /dev/sdc format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:11:53 29810] LINE 9650: exec command: sgdisk -p /dev/sdc | grep '[0-9] ' > /var/log/frontview/.known_cfgdir/W1F2NA5K [2015/09/14 15:11:56 29810] /var/log/frontview/.known_cfgdir/S301BHFT [2015/09/14 15:11:56 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:11:56 29810] get disk /dev/sdb format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:11:56 29810] LINE 9650: exec command: sgdisk -p /dev/sdb | grep '[0-9] ' > /var/log/frontview/.known_cfgdir/S301BHFT [2015/09/14 15:11:59 29810] /var/log/frontview/.known_cfgdir/S301BHV7 [2015/09/14 15:11:59 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:11:59 29810] get disk /dev/sdd format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:11:59 29810] LINE 9650: exec command: sgdisk -p /dev/sdd | grep '[0-9] ' > /var/log/frontview/.known_cfgdir/S301BHV7 File descriptor 3 (/etc/resolv.conf (deleted)) leaked on vgscan invocation. Parent PID 29860: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvdisplay invocation. Parent PID 29812: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvdisplay invocation. Parent PID 29812: sh File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvdisplay invocation. Parent PID 29812: sh [2015/09/14 15:12:00 29810] /var/log/frontview/.known_cfgdir/Z3039RT9 [2015/09/14 15:12:00 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:12:00 29810] get disk /dev/sda format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:12:00 29810] LINE 9650: exec command: sgdisk -p /dev/sda | grep '[0-9] ' > /var/log/frontview/.known_cfgdir/Z3039RT9 [2015/09/14 15:12:02 29810] LINE 5297: exec command: ps -ef | grep -v expand_md > /var/log/frontview/.V_E.snapshotstat [2015/09/14 15:12:02 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:12:02 29810] get disk /dev/sdc format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:12:02 29810] /dev/sdc used/total/partitioned = 2930264504/2930266584/2930264504, 60000000 [2015/09/14 15:12:02 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:12:02 29810] get disk /dev/sdb format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:12:02 29810] /dev/sdb used/total/partitioned = 3907016483/3907018584/3907016483, 60000000 [2015/09/14 15:12:02 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:12:02 29810] get disk /dev/sdd format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:12:02 29810] /dev/sdd used/total/partitioned = 3907016483/3907018584/3907016483, 60000000 [2015/09/14 15:12:02 29810] gpt sig:0,mbr sig:0,fake type:0 [2015/09/14 15:12:02 29810] get disk /dev/sda format is (GPT=2,MBR=1,MX=3,MISC=-1): 2 [2015/09/14 15:12:02 29810] /dev/sda used/total/partitioned = 3907016483/3907018584/3907016483, 60000000 [2015/09/14 15:12:02 29810] used_disk_pt_count:4,start:4 xraid level is 5 [2015/09/14 15:12:02 29810] Not enough disk for a new array, drives with free space: 0, X_level:5 [2015/09/14 15:12:03 29810] STAGE_WIPE: Clean my_pid 29810Expansion is also failing due to memory allocation
resize2fs: Memory allocation failed while trying to resize /dev/c/c
I don't own a v2 - but if you know of a place where the amount of memory is displayed, you should check to make sure that it is seeing 256MB.
I also suggest a memory test from the boot menu (http://www.readynas.com/download/documentation/HM/ReadyNAS_Duov2_NV+v2_HW_en_19-Sept-11.pdf ). Unfortunately Netgear doesn't disclose how to tell if the test passed/failed. But you could take a short video, and post the link here, they should be able to interpret the results here.
Are you the original purchaser? If so, when did you purchase? The warrany is 3 years. If you are still covered I think you have have enough evidence of a hardware fault that they should diagnose it w/o charge
This is the entirety of mem_info.log:
MemTotal: 246820 kB MemFree: 24704 kB Buffers: 5540 kB Cached: 60848 kB SwapCached: 18348 kB Active: 66812 kB Inactive: 96552 kB Active(anon): 41012 kB Inactive(anon): 56412 kB Active(file): 25800 kB Inactive(file): 40140 kB Unevictable: 376 kB Mlocked: 0 kB SwapTotal: 524268 kB SwapFree: 495600 kB Dirty: 296 kB Writeback: 0 kB AnonPages: 80176 kB Mapped: 13952 kB Slab: 20804 kB SReclaimable: 4624 kB SUnreclaim: 16180 kB PageTables: 2172 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 647676 kB Committed_AS: 726704 kB VmallocTotal: 385024 kB VmallocUsed: 940 kB VmallocChunk: 382812 kB
And this is memory.log:
SZ: 256 AT: SDRAM
Looks to me like it can definitely see 256MB. But now I'm going to have a go at that memory test, so at least I have the results when talking to support.
And the relevant part of system.log:
Sep 14 14:39:13 The_Library kernel: md: md2: recovery done. Sep 14 14:39:13 The_Library kernel: md: recovery of RAID array md1 Sep 14 14:39:13 The_Library kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk. Sep 14 14:39:13 The_Library kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. Sep 14 14:39:13 The_Library kernel: md: using 128k window, over a total of 524276 blocks. Sep 14 14:39:13 The_Library kernel: RAID5 conf printout: Sep 14 14:39:13 The_Library kernel: --- rd:4 wd:4 Sep 14 14:39:13 The_Library kernel: disk 0, o:1, dev:sda3 Sep 14 14:39:13 The_Library kernel: disk 1, o:1, dev:sdb3 Sep 14 14:39:13 The_Library kernel: disk 2, o:1, dev:sdc3 Sep 14 14:39:13 The_Library kernel: disk 3, o:1, dev:sdd3 Sep 14 14:39:35 The_Library RAIDiator: RAID sync finished on volume C. Sep 14 14:39:44 The_Library RAIDiator: RAID sync finished on volume C.\n\n[Mon Sep 14 14:39:24 EST 2015] Sep 14 14:39:47 The_Library kernel: md: md1: recovery done. Sep 14 14:39:47 The_Library kernel: RAID1 conf printout: Sep 14 14:39:47 The_Library kernel: --- wd:4 rd:4 Sep 14 14:39:47 The_Library kernel: disk 0, wo:0, o:1, dev:sda2 Sep 14 14:39:47 The_Library kernel: disk 1, wo:0, o:1, dev:sdb2 Sep 14 14:39:47 The_Library kernel: disk 2, wo:0, o:1, dev:sdc2 Sep 14 14:39:47 The_Library kernel: disk 3, wo:0, o:1, dev:sdd2 Sep 14 23:36:20 The_Library shutdown[2608]: shutting down for system reboot Sep 14 23:36:21 The_Library init: Switching to runlevel: 6 Sep 14 23:36:42 The_Library exiting on signal 15 Sep 14 23:39:24 The_Library syslogd 1.5.0#6: restart. - apparently normal messages trimmed for character limit - Sep 14 23:39:24 The_Library kernel: tun: Universal TUN/TAP device driver, 1.6 Sep 14 23:39:24 The_Library kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Sep 14 23:39:24 The_Library kernel: Using Hamming 1-bit ECC for NAND device Sep 14 23:39:24 The_Library kernel: NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit) Sep 14 23:39:24 The_Library kernel: Scanning device for bad blocks Sep 14 23:39:24 The_Library kernel: Bad eraseblock 637 at 0x000004fa0000 Sep 14 23:39:24 The_Library kernel: mtd: no mtd-id - more apparently normal messages snipped -
Sep 14 23:39:25 The_Library kernel: scsi: waiting for bus probes to complete ... Sep 14 23:39:25 The_Library kernel: scsi 0:0:0:0: Direct-Access Seagate ST4000VN000-1H41 SC46 PQ: 0 ANSI: 5 Sep 14 23:39:25 The_Library kernel: scsi 0:0:1:0: Direct-Access Seagate ST4000VN000-1H41 SC46 PQ: 0 ANSI: 5 Sep 14 23:39:25 The_Library kernel: scsi 0:0:2:0: Direct-Access Seagate ST3000DM001-1CH1 CC26 PQ: 0 ANSI: 5 Sep 14 23:39:25 The_Library kernel: scsi 0:0:3:0: Direct-Access Seagate ST4000VN000-1H41 SC46 PQ: 0 ANSI: 5 Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] 0-byte physical blocks Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] Write Protect is off Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00 Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] 0-byte physical blocks Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: Attached scsi generic sg1 type 0 Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] Write Protect is off Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] Mode Sense: 23 00 10 00 Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] 0-byte physical blocks Sep 14 23:39:25 The_Library kernel: sda: Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: Attached scsi generic sg2 type 0 Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB) Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] 0-byte physical blocks Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: Attached scsi generic sg3 type 0 Sep 14 23:39:25 The_Library kernel: rtc mv_rtc: setting system clock to 2015-09-14 23:37:31 UTC (1442273851) Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] Write Protect is off Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] Mode Sense: 23 00 10 00 Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] Write Protect is off Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] Mode Sense: 23 00 10 00 Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 14 23:39:25 The_Library kernel: sdb: Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sdc: Sep 14 23:39:25 The_Library kernel: sdd: sda1 sda2 sda3 sda4 Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:0:0: [sda] Attached SCSI disk Sep 14 23:39:25 The_Library kernel: sdb1 sdb2 sdb3 sdb4 Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:1:0: [sdb] Attached SCSI disk Sep 14 23:39:25 The_Library kernel: sdd1 sdd2 sdd3 sdd4 Sep 14 23:39:25 The_Library kernel: sdc1 sdc2 sdc3 Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] Sector size 0 reported, assuming 512. Sep 14 23:39:25 The_Library kernel: sd 0:0:2:0: [sdc] Attached SCSI disk Sep 14 23:39:25 The_Library kernel: sd 0:0:3:0: [sdd] Attached SCSI disk Sep 14 23:39:25 The_Library kernel: Freeing init memory: 128K Sep 14 23:39:25 The_Library kernel: armvpd: module license 'Proprietary' taints kernel. Sep 14 23:39:25 The_Library kernel: Disabling lock debugging due to kernel taint Sep 14 23:39:25 The_Library kernel: ReadyNAS Pro VPD device driver init... Sep 14 23:39:25 The_Library kernel: Tuxera NTFS driver 3011.10.19 [Flags: R/W MODULE]. Sep 14 23:39:25 The_Library kernel: eth0: link down Sep 14 23:39:25 The_Library kernel: eth0: started Sep 14 23:39:25 The_Library kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Sep 14 23:39:25 The_Library kernel: md: bind<sdb1> Sep 14 23:39:25 The_Library kernel: md: bind<sdc1> Sep 14 23:39:25 The_Library kernel: md: bind<sdd1> Sep 14 23:39:25 The_Library kernel: md: bind<sda1> Sep 14 23:39:25 The_Library kernel: raid1: raid set md0 active with 4 out of 4 mirrors Sep 14 23:39:25 The_Library kernel: md0: detected capacity change from 0 to 4293906432 Sep 14 23:39:25 The_Library kernel: md0: unknown partition table Sep 14 23:39:25 The_Library kernel: md: bind<sdb2> Sep 14 23:39:25 The_Library kernel: md: bind<sdc2> Sep 14 23:39:25 The_Library kernel: md: bind<sdd2> Sep 14 23:39:25 The_Library kernel: md: bind<sda2> Sep 14 23:39:25 The_Library kernel: raid1: raid set md1 active with 4 out of 4 mirrors Sep 14 23:39:25 The_Library kernel: md1: detected capacity change from 0 to 536858624 Sep 14 23:39:25 The_Library kernel: md1: unknown partition table Sep 14 23:39:25 The_Library kernel: md: bind<sdb3> Sep 14 23:39:25 The_Library kernel: md: bind<sdc3> Sep 14 23:39:25 The_Library kernel: md: bind<sdd3> Sep 14 23:39:25 The_Library kernel: md: bind<sda3> Sep 14 23:39:25 The_Library kernel: raid5: device sda3 operational as raid disk 0 Sep 14 23:39:25 The_Library kernel: raid5: device sdd3 operational as raid disk 3 Sep 14 23:39:25 The_Library kernel: raid5: device sdc3 operational as raid disk 2 Sep 14 23:39:25 The_Library kernel: raid5: device sdb3 operational as raid disk 1 Sep 14 23:39:25 The_Library kernel: raid5: allocated 4216kB for md2 Sep 14 23:39:25 The_Library kernel: raid5: raid level 5 set md2 active with 4 out of 4 devices, algorithm 2 Sep 14 23:39:25 The_Library kernel: RAID5 conf printout: Sep 14 23:39:25 The_Library kernel: --- rd:4 wd:4 Sep 14 23:39:25 The_Library kernel: disk 0, o:1, dev:sda3 Sep 14 23:39:25 The_Library kernel: disk 1, o:1, dev:sdb3 Sep 14 23:39:25 The_Library kernel: disk 2, o:1, dev:sdc3 Sep 14 23:39:25 The_Library kernel: disk 3, o:1, dev:sdd3 Sep 14 23:39:25 The_Library kernel: md2: detected capacity change from 0 to 8987273330688 Sep 14 23:39:25 The_Library kernel: md2: unknown partition table Sep 14 23:39:25 The_Library kernel: md: bind<sdd4> Sep 14 23:39:25 The_Library kernel: md: bind<sda4> Sep 14 23:39:25 The_Library kernel: md: bind<sdb4> Sep 14 23:39:25 The_Library kernel: raid5: device sdb4 operational as raid disk 0 Sep 14 23:39:25 The_Library kernel: raid5: device sda4 operational as raid disk 2 Sep 14 23:39:25 The_Library kernel: raid5: device sdd4 operational as raid disk 1 Sep 14 23:39:25 The_Library kernel: raid5: allocated 3174kB for md3 Sep 14 23:39:25 The_Library kernel: raid5: raid level 5 set md3 active with 3 out of 3 devices, algorithm 2 Sep 14 23:39:25 The_Library kernel: RAID5 conf printout: Sep 14 23:39:25 The_Library kernel: --- rd:3 wd:3 Sep 14 23:39:25 The_Library kernel: disk 0, o:1, dev:sdb4 Sep 14 23:39:25 The_Library kernel: disk 1, o:1, dev:sdd4 Sep 14 23:39:25 The_Library kernel: disk 2, o:1, dev:sda4 Sep 14 23:39:25 The_Library kernel: md3: detected capacity change from 0 to 2000385605632 Sep 14 23:39:25 The_Library kernel: md3: unknown partition table Sep 14 23:39:25 The_Library kernel: kjournald starting. Commit interval 5 seconds Sep 14 23:39:25 The_Library kernel: EXT3-fs: mounted filesystem with ordered data mode. Sep 14 23:39:25 The_Library kernel: eth0: link up, full duplex, speed 1 Gbps Sep 14 23:39:25 The_Library kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Sep 14 23:39:25 The_Library kernel: kjournald starting. Commit interval 5 seconds Sep 14 23:39:25 The_Library kernel: EXT3 FS on md0, internal journal Sep 14 23:39:25 The_Library kernel: EXT3-fs: mounted filesystem with ordered data mode. Sep 14 23:39:25 The_Library kernel: kjournald starting. Commit interval 5 seconds Sep 14 23:39:25 The_Library kernel: EXT3 FS on md0, internal journal Sep 14 23:39:25 The_Library kernel: EXT3-fs: mounted filesystem with ordered data mode. Sep 14 23:39:25 The_Library kernel: udevd version 125 started Sep 14 23:39:25 The_Library kernel: Adding 524268k swap on /dev/md1. Priority:-1 extents:1 across:524268k Sep 14 23:39:25 The_Library kernel: fsck.ext4 invoked oom-killer: gfp_mask=0x200da, order=0, oomkilladj=0 Sep 14 23:39:25 The_Library kernel: [<c002ecf0>] (unwind_backtrace+0x0/0xdc) from [<c009d930>] (oom_kill_process+0x58/0x1b4) Sep 14 23:39:25 The_Library kernel: [<c009d930>] (oom_kill_process+0x58/0x1b4) from [<c009de84>] (__out_of_memory+0x160/0x180) Sep 14 23:39:25 The_Library kernel: [<c009de84>] (__out_of_memory+0x160/0x180) from [<c009df08>] (out_of_memory+0x64/0x98) Sep 14 23:39:25 The_Library kernel: [<c009df08>] (out_of_memory+0x64/0x98) from [<c00a06a4>] (__alloc_pages_nodemask+0x3f0/0x4dc) Sep 14 23:39:25 The_Library kernel: [<c00a06a4>] (__alloc_pages_nodemask+0x3f0/0x4dc) from [<c00ad338>] (handle_mm_fault+0x130/0x588) Sep 14 23:39:25 The_Library kernel: [<c00ad338>] (handle_mm_fault+0x130/0x588) from [<c002fcf0>] (do_page_fault+0xe0/0x22c) Sep 14 23:39:25 The_Library kernel: [<c002fcf0>] (do_page_fault+0xe0/0x22c) from [<c0028230>] (do_DataAbort+0x30/0x90) Sep 14 23:39:25 The_Library kernel: [<c0028230>] (do_DataAbort+0x30/0x90) from [<c0028f1c>] (ret_from_exception+0x0/0x10) Sep 14 23:39:25 The_Library kernel: Exception stack(0xcd54ffb0 to 0xcd54fff8) Sep 14 23:39:25 The_Library kernel: ffa0: 5881a008 00000000 01be3004 68e93000 Sep 14 23:39:25 The_Library kernel: ffc0: ffffffff ffffffff ffffffff 10000000 00000000 00004000 00000000 bee538bc Sep 14 23:39:25 The_Library kernel: ffe0: 00000000 bee53898 40040d90 40147be8 20000010 ffffffff Sep 14 23:39:25 The_Library kernel: Mem-info: Sep 14 23:39:25 The_Library kernel: Normal per-cpu: Sep 14 23:39:25 The_Library kernel: CPU 0: hi: 90, btch: 15 usd: 14 Sep 14 23:39:25 The_Library kernel: Active_anon:25727 active_file:12 inactive_anon:22013 Sep 14 23:39:25 The_Library kernel: inactive_file:0 unevictable:2 dirty:0 writeback:8710 unstable:0 Sep 14 23:39:25 The_Library kernel: free:504 slab:4767 mapped:1 pagetables:360 bounce:0 Sep 14 23:39:25 The_Library kernel: Normal free:2016kB min:2036kB low:2544kB high:3052kB active_anon:102908kB inactive_anon:88052kB active_file:48kB inactive_file:0kB unevictable:8kB present:260096kB pages_scanned:1623 all_unreclaimable? no Sep 14 23:39:25 The_Library kernel: lowmem_reserve[]: 0 0 Sep 14 23:39:25 The_Library kernel: Normal: 2*4kB 1*8kB 3*16kB 1*32kB 2*64kB 4*128kB 3*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB 0*32768kB 0*65536kB 0*131072kB 0*262144kB 0*524288kB 0*1048576kB = 2016kB Sep 14 23:39:25 The_Library kernel: 11179 total pagecache pages Sep 14 23:39:25 The_Library kernel: 11165 pages in swap cache Sep 14 23:39:25 The_Library kernel: Swap cache stats: add 526194, delete 515029, find 127066/149636 Sep 14 23:39:25 The_Library kernel: Free swap = 0kB Sep 14 23:39:25 The_Library kernel: Total swap = 524268kB Sep 14 23:39:25 The_Library kernel: 65536 pages of RAM Sep 14 23:39:25 The_Library kernel: 589 free pages Sep 14 23:39:25 The_Library kernel: 3841 reserved pages Sep 14 23:39:25 The_Library kernel: 3230 slab pages Sep 14 23:39:25 The_Library kernel: 19 pages shared Sep 14 23:39:25 The_Library kernel: 11165 pages swap cached Sep 14 23:39:25 The_Library kernel: Out of memory: kill process 1656 (fsck.ext4) score 10926 or a child Sep 14 23:39:25 The_Library kernel: Killed process 1656 (fsck.ext4) Sep 14 23:39:25 The_Library kernel: EXT4-fs (dm-0): barriers enabled Sep 14 23:39:25 The_Library kernel: kjournald2 starting: pid 1693, dev dm-0:8, commit interval 5 seconds Sep 14 23:39:25 The_Library kernel: EXT4-fs (dm-0): internal journal on dm-0:8 Sep 14 23:39:25 The_Library kernel: EXT4-fs: file extents enabled Sep 14 23:39:25 The_Library kernel: EXT4-fs: mballoc enabled Sep 14 23:39:25 The_Library kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode Sep 14 23:39:51 The_Library syslogd 1.5.0#6: restart. Sep 14 23:39:53 The_Library ifplugd(eth0)[3782]: ifplugd 0.28 initializing.Halp!
I have same config
4TB
3TB
4TB
3TB
WD RED
Mon Sep 21 06:39:53 Volume expansion failed
Mon Sep 21 06:25:42 System is up.
Mon Sep 21 06:23:50 Incompleted file system expansion detected. Resuming...
Mon Sep 21 04:51:07 Volume expansion failed
Mon Sep 21 04:34:09 System is up.
Mon Sep 21 04:32:24 Incompleted file system expansion detected. Resuming...
Sun Sep 20 23:43:19 RAID sync finished on volume C.
Sun Sep 20 18:32:37 Volume expansion failed
Sun Sep 20 18:15:36 System is up.
Sun Sep 20 18:13:44 Incompleted file system expansion detected. Resuming...
Sun Sep 20 13:17:58 RAID sync finished on volume C.
Sun Sep 20 08:09:05 Volume expansion failed
Sun Sep 20 07:50:59 System is up.
Sun Sep 20 07:49:11 Incompleted file system expansion detected. Resuming...
Sat Sep 19 21:14:18 System is up.
Sat Sep 19 21:13:13 Continuing with volume expansion. Do not interrupt the system during this time. When complete, email notification will be sent to the alert contact list.
Sat Sep 19 19:34:45 Found space that can be used to expand capacity, expansion process will start during next boot.
Sat Sep 19 19:34:36 Data volume has been successfully expanded to 8326 GB.
Sat Sep 19 18:25:33 System is up.
Sat Sep 19 18:23:47 Incompleted file system expansion detected. Resuming...
Sat Sep 19 18:19:45 RAID sync finished on volume C.
Sat Sep 19 18:19:07 Newly added drive has more space to expand the volume, will start volume expansion.
Fri Sep 18 12:46:02 System is up.
Fri Sep 18 12:45:09 Data volume will be rebuilt with disk 1.And exactly the same problem.
Did you find any solution? This is due perhaps to the limit of 8GB.
Now showing me 5.6GB free from 8.1GBWould do well to find a solution to the ReadyNAS started normally....
I found some solution
but
root@nas-JohnyB:~# apt-get install lsof
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libupsclient1 libpcap0.8 cracklib-runtime libnss-mdns libcrack2 libcap-ng0
libavahi-client3 libnet1
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
lsof
0 upgraded, 1 newly installed, 0 to remove and 107 not upgraded.
Need to get 282 kB of archives.
After this operation, 455 kB of additional disk space will be used.
Err http://ftp.us.debian.org/debian/ squeeze/main lsof armel 4.81.dfsg.1-1
404 Not Found [IP: 128.61.240.89 80]
Failed to fetch http://ftp.us.debian.org/debian/pool/main/l/lsof/lsof_4.81.dfsg.1-1_armel.deb 404 Not Found [IP: 128.61.240.89 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?I don't now how umount /c :/ for offline resizing
Do you have an ultra or a pro? Or an NV+ v2?
- I start with
1GB
2GB
1GB
2GB
Please help me with setup volume.
BaGRoS wrote:
I start with
1GB
2GB
1GB
2GBI think you mean TB. With 2x2TB+2x1TB, the system first creates a 3 TB volume, and then immediately expands it to 4 TB. It's not completely clear if the 8 TiB growth limit starts from 3 TB or 4 TB in your case. But either way, you haven't reached the 8 TiB threshold yet (assuming you are correct on the starting point). With 2x3TB+2x4TB you should be at 10 TB, which is only 6 (or 7) TB of growth.
So either something else is wrong, or you didn't have all four disks in place when you did the factory install.
FWIW, what you are attempting has some risk, and you could lose your data.
root@nas-JohnyB:~# resize2fs -p /dev/c/c & [1] 24767 root@nas-JohnyB:~# resize2fs 1.41.14 (22-Dec-2010) Filesystem at /dev/c/c is mounted on /c; on-line resizing required old desc_blocks = 523, new_desc_blocks = 581 Performing an on-line resize of /dev/c/c to 2435710976 (4k) blocks. The filesystem on /dev/c/c is now 2435710976 blocks long.
and still waiting...
I do not know if I can reboot, there is no prompt :/
- Swap volume, sorry for t9.
I used this page as a reference for how to use the USB key as extra swap: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/System_Administration_Guide/s1-swap-adding.html
In my case, the USB key appeared as /dev/sde, so I did:
mkswap /dev/sde
swapon /dev/sdeI never managed to get it working on startup using fstab, so never got it to solve my volume scan problem... but it was volume expansion I really cared about, and it did that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
