5.1 -5022 update 2 expansion problem

[frostiex 0]

hi guys. I can't seem to expand the size of my Nas

 

Currently it has the following installed running SHR with 1 disk fault tolerance

2 x 4TB (3.64 actual)

2 x 3TB (2.73 actual)

4 x 2TB (1.82 actual)

=16.28 TB

 

One of the old 2TB drive is reporting bad sector and were remapped (it is an OLD drive...)

So when a sale came abou for another 4TB WD Red, I picked one up to replace it.

 

So I proceeded to remove the 2TB with bad sector and did a repair. Everything was good to this point and repair went successfully.

After the repair, I went into storage manager and it mentioned that I can expand size to about 18598GB as expected.

I proceeded to click on manage and selected Expand volume with allocated space; click apply and proceeded.

 

The storage manager displays that it is expanding at 0.00% and looks like the task is spinning; after about one min. it goes back to the screen telling me that I can expand size to about 18598GB.

I tired repeating the proceedure a few times, but no avail...any ideas? Am I doing something wrong?

[toobueller 0]

hi guys. I can't seem to expand the size of my Nas

 

Currently it has the following installed running SHR with 1 disk fault tolerance

2 x 4TB (3.64 actual)

2 x 3TB (2.73 actual)

4 x 2TB (1.82 actual)

=16.28 TB

 

One of the old 2TB drive is reporting bad sector and were remapped (it is an OLD drive...)

So when a sale came abou for another 4TB WD Red, I picked one up to replace it.

 

So I proceeded to remove the 2TB with bad sector and did a repair. Everything was good to this point and repair went successfully.

After the repair, I went into storage manager and it mentioned that I can expand size to about 18598GB as expected.

I proceeded to click on manage and selected Expand volume with allocated space; click apply and proceeded.

 

The storage manager displays that it is expanding at 0.00% and looks like the task is spinning; after about one min. it goes back to the screen telling me that I can expand size to about 18598GB.

I tired repeating the proceedure a few times, but no avail...any ideas? Am I doing something wrong?

Try repeating again, after a reboot. examine the contents of /var/log/messages for clues. I think there is another log file that may have some more messages, but I don't remember where it is and don't have access at to find it the moment.

I hope this isn't a bug in the patch.

[goRt 0]

I had the same problem on 5022 update 1 adding a forth 3tb array already containing 3*3tb drives.

Eventually I deleted the entire configuration and restored from backup as I thought this was an issue I'd created, I was unable to identify anything locking the expansion.

[frostiex 0]

I will try again after reboot. I'm going to have to let the scrub finish first. Will report back.

I did look in the log in the control panel. It did say it is successfully expanded.....so annoying

 

 

Sent from my iPhone using Tapatalk

[Diverge 1]

My one experience with expanding an array didn't go well either.. but this was way before DSM 5. I'm curious what the success rate if someone did some tests with a few disks and dummy data.

[fjf 4]

It seems there is a serious issue with xpenology not expanding. I tried with 5.0 (viewtopic.php?f=2&t=4903) with no success. Be prepared to use the command line and a few tutorials. I did not try because I could get around it and did not want to risk my data. The fact that there is a tuto here (viewtopic.php?f=15&t=3339) indicates this is a known issue nobody talks about. But it is a serious one. What good is a NAS if you cannot expand the volume?.

[manfriday 5]

I had a similar experience with a stand alone test system. The results are making me hold off upgrading the "real" DSMs.

Built from scratch with 2x1TB drives in to SHR setup, as with most reports, rebooted after the updates to discover unmouted drives. Rebooted, all was ok.

added third 1TB drive and system started the Consistency check process (This went for an inordinately long time for a 1TB drive, over 30hours) At the end of check the capacity did not expand. I went back to the post in "How To" and followed instructions to expand volume only to have no success with FSCK step as the volume VG1000 was not unmouted. I unmounted the volume and continued with steps, everything seemed to work....after boot to DSM no capacity. I rebooted DSM. The Consistency Check process started again (took a couple of hours) I had full capacity.

I have found that on the 3 systems I have, I have to follow the "How to" every time I add a new disk across different versions of DSM. I put this down the the HW but may be wrong. 2 of the 3 systems are identical MOBO and test is very similar. Zotac ITX ATOM based systems. I will bite the bullet and try for an upgrade soon but will continue to browse this forum for others experiences. the 5022-2 systems works fine now but it was not a straight forward upgrade for me

[rosiste 0]

I have expansion issue with 5.1 - 5022 update too. My hardware : Motherboard ASRock E350M1, 2GB RAM, 1x WD RED 2TB, 1x WD RED 3TB, 2x WD RE4 500GB. Volume starts expanding in web interface and crashs after few seconds.

 

I tried to scrub volume - wihout problems:

 

[  343.244147] md: requested-resync of RAID array md2
[  343.244153] md: minimum _guaranteed_  speed: 10000 KB/sec/disk.
[  343.244157] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for requested-resync.
[  343.244165] md: using 128k window, over a total of 483555264k.
[ 5726.692886] md: md2: requested-resync done.

 

And expand volme after that:

 

[ 7245.250107] Adding 511996k swap on /swap.  Priority:-2 extents:5 across:602108k
[ 7245.344014] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
[ 7245.344027] IP: [] add_new_gdb+0x25/0x470
[ 7245.344040] PGD 6047e067 PUD 604f3067 PMD 0
[ 7245.344046] Oops: 0000 [#2] SMP
[ 7245.344051] CPU 0
[ 7245.344053] Modules linked in: cifs udf isofs loop usbhid hid usblp usb_storage bromolow_synobios(P) adt7475 i2c_i801 btrfs synoacl_vfs(P) zlib_deflate hfsplus md4 hmac tn40xx(O) i2c_algo_bit fuse vfat fat chainiv cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor cpufreq_stats freq_table dm_snapshot crc_itu_t quota_v2 quota_tree psnap p8022 llc sit tunnel4 zram(C) etxhci_hcd xhci_hcd ehci_hcd uhci_hcd ohci_hcd usbcore usb_common mvsas arcmsr megaraid_sas megaraid_mbox megaraid_mm mpt2sas mptsas mptspi mptscsih mptbase scsi_transport_spi scsi_wait_scan sg ata_piix sata_uli sata_svw sata_qstor sata_sis pata_sis stex sata_sx4 sata_promise sata_nv sata_via sata_sil pdc_adma iscsi_tcp libiscsi_tcp libiscsi enic qlge qlcnic qla3xxx netxen_nic cnic ipv6 bnx2x be2net sis900 sis190 atl1e(O) atl1c atl2(O) atl1(O) alx(O) sky2 skge via_velocity crc_ccitt via_rhine r8101 r8168 r8169 8139too 8139cp tg3 broadcom libphy bnx2 ssb(O) uio forcedeth ixgbe ixgb igb ioatdma e1000e e1000 e100 dca pcnet32 amd8111e mdio mii container thermal_sys compat(O) cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic libcrc32c crc32c eseqiv krng ansi_cprng cts rng aes_generic md5 cbc cryptomgr pcompress aead crypto_hash crypto_blkcipher crypto_wq crypto_algapi [last unloaded: i2c_i801]
[ 7245.344197]
[ 7245.344202] Pid: 30747, comm: resize2fs Tainted: P      D  C O 3.2.40 #7 To Be Filled By O.E.M. Synoden/E350M1
[ 7245.344209] RIP: 0010:[]  [] add_new_gdb+0x25/0x470
[ 7245.344217] RSP: 0018:ffff880060647b58  EFLAGS: 00010282
[ 7245.344221] RAX: 0000000000000074 RBX: 0000000000001d10 RCX: ffff88006b91f000
[ 7245.344225] RDX: 0000000000001d00 RSI: 0000000000000000 RDI: ffff88005ceae360
[ 7245.344229] RBP: ffff880060647be8 R08: 7010000000000000 R09: 0000000000000000
[ 7245.344233] R10: ffde9f3da028ce02 R11: ffff880061131130 R12: ffff88006b91f000
[ 7245.344236] R13: 0000000000001d00 R14: 0000000000000000 R15: 0000000000000000
[ 7245.344241] FS:  00000000006fc880(0063) GS:ffff88006fa00000(0000) knlGS:00000000f6f446d0
[ 7245.344246] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 7245.344249] CR2: 0000000000000028 CR3: 000000004146e000 CR4: 00000000000006f0
[ 7245.344253] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 7245.344257] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 7245.344261] Process resize2fs (pid: 30747, threadinfo ffff880060646000, task ffff88006e54e6a0)
[ 7245.344265] Stack:
[ 7245.344267]  ffff88006a2c0800 ffff8800610ceeb8 ffff88005ceae360 ffffffff8161b590
[ 7245.344274]  ffff8800610ceeb8 0000000000000000 ffff880060647ba8 ffffffff8119ff86
[ 7245.344280]  ffff88005ceae360 ffff88000360c338 ffff880060647be8 ffffffff81185b98
[ 7245.344287] Call Trace:
[ 7245.344296]  [] ? jbd2_journal_get_write_access+0x36/0x50
[ 7245.344302]  [] ? __ext4_journal_get_write_access+0x38/0x80
[ 7245.344308]  [] ext4_flex_group_add+0x57e/0xd00
[ 7245.344314]  [] ext4_resize_fs+0x662/0x8f0
[ 7245.344321]  [] ? do_last+0x538/0xaa0
[ 7245.344327]  [] ? __mnt_want_write+0x30/0x50
[ 7245.344334]  [] ext4_ioctl+0x290/0xaa0
[ 7245.344340]  [] do_vfs_ioctl+0xb4/0x8b0
[ 7245.344346]  [] ? putname+0x2e/0x40
[ 7245.344351]  [] ? do_sys_open+0x164/0x1d0
[ 7245.344357]  [] sys_ioctl+0x99/0xa0
[ 7245.344364]  [] system_call_fastpath+0x16/0x1b
[ 7245.344367] Code: 84 00 00 00 00 00 55 48 89 e5 48 81 ec 90 00 00 00 4c 89 6d e8 4c 89 75 f0 41 89 d5 48 89 5d d8 4c 89 65 e0 49 89 f6 4c 89 7d f8 <4c> 8b 7e 28 48 89 7d 88 49 8b 8f 40 03 00 00 48 8b 41 68 48 89
[ 7245.344418] RIP  [] add_new_gdb+0x25/0x470
[ 7245.344423]  RSP 
[ 7245.344426] CR2: 0000000000000028
[ 7245.344432] ---[ end trace 8022fe148d921fe4 ]---

[forcefullpower 0]

I am getting the exactly the same issue. Cannot expand any volumes using synology SHR, is this a bug in xpenology or in DSM software itself. I have trashed my openelec system I was running using mhddfs to be using this with parity and come this close and to then find a glaring problem with removing and installing new drives and expanding them. I was hoping to create a spare volume to transfer data to and then copy the data across to the main disk group volume and add the last drive in. But if I can't do this its put a real show stopper on this as I was having a great time with the ease of use this software has.

[rosiste 0]

I found another bug during each boot procedure. Don't know if it's related.

 

[   34.790179] BUG: unable to handle kernel paging request at 0000000000002bf9
[   34.790191] IP: [] sata_syno_ahci_diskled_set+0x36/0x110
[   34.790204] PGD 60b5e067 PUD 60b5f067 PMD 0
[   34.790211] Oops: 0000 [#1] SMP
[   34.790216] CPU 0
[   34.790218] Modules linked in: usbhid hid usblp usb_storage bromolow_synobios(P) adt7475 i2c_i801 btrfs synoacl_vfs(P) zlib_deflate hfsplus md4 hmac tn40xx(O) i2c_algo_bit fuse vfat fat chainiv cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor cpufreq_stats freq_table dm_snapshot crc_itu_t quota_v2 quota_tree psnap p8022 llc sit tunnel4 zram(C) etxhci_hcd xhci_hcd ehci_hcd uhci_hcd ohci_hcd usbcore usb_common mvsas arcmsr megaraid_sas megaraid_mbox megaraid_mm mpt2sas mptsas mptspi mptscsih mptbase scsi_transport_spi scsi_wait_scan sg ata_piix sata_uli sata_svw sata_qstor sata_sis pata_sis stex sata_sx4 sata_promise sata_nv sata_via sata_sil pdc_adma iscsi_tcp libiscsi_tcp libiscsi enic qlge qlcnic qla3xxx netxen_nic cnic ipv6 bnx2x be2net sis900 sis190 atl1e(O) atl1c atl2(O) atl1(O) alx(O) sky2 skge via_velocity crc_ccitt via_rhine r8101 r8168 r8169 8139too 8139cp tg3 broadcom libphy bnx2 ssb(O) uio forcedeth ixgbe ixgb igb ioatdma e1000e e1000 e100 dca pcnet32 amd8111e mdio mii container thermal_sys compat(O) cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic libcrc32c crc32c eseqiv krng ansi_cprng cts rng aes_generic md5 cbc cryptomgr pcompress aead crypto_hash crypto_blkcipher crypto_wq crypto_algapi [last unloaded: i2c_i801]
[   34.790357]
[   34.790363] Pid: 16885, comm: scemd Tainted: P         C O 3.2.40 #7 To Be Filled By O.E.M. Synoden/E350M1
[   34.790371] RIP: 0010:[]  [] sata_syno_ahci_diskled_set+0x36/0x110
[   34.790379] RSP: 0018:ffff88006047fc48  EFLAGS: 00010202
[   34.790383] RAX: ffff8800694f5800 RBX: 0000000000000000 RCX: ffff8800694f5b10
[   34.790388] RDX: 0000000000000000 RSI: ffffffff81227250 RDI: ffff8800694f5b58
[   34.790393] RBP: ffff88006047fc88 R08: ffff88006acfc6b0 R09: ffff88006c357c80
[   34.790397] R10: ffff88006047e000 R11: 0000000000000001 R12: 00000000ffffffea
[   34.790402] R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000000
[   34.790407] FS:  00007f0de9f1c700(0000) GS:ffff88006fa00000(0063) knlGS:00000000f4a8bb70
[   34.790412] CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
[   34.790416] CR2: 0000000000002bf9 CR3: 0000000060b0f000 CR4: 00000000000006f0
[   34.790420] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   34.790425] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   34.790430] Process scemd (pid: 16885, threadinfo ffff88006047e000, task ffff880068acd280)
[   34.790433] Stack:
[   34.790436]  ffff88006047fc68 ffff8800694f5800 ffff88006047fc78 ffffffffffffffff
[   34.790443]  00000000ffffffea ffff88006acfc680 00000000f4a8b048 0000000000000000
[   34.790449]  00000000f4a8b048 ffffffffa09233b4 00000000ffffffea ffffffffa092051a
[   34.790455] Call Trace:
[   34.790466]  [] SetSCSIHostLedStatusByAHCIGPIO+0x14/0x60 [bromolow_synobios]
[   34.790474]  [] ? synobios_ioctl+0xe6a/0xff0 [bromolow_synobios]
[   34.790482]  [] ? path_lookupat+0xc1/0x9c0
[   34.790488]  [] ? putname+0x2e/0x40
[   34.790493]  [] ? user_path_at_empty+0x63/0xa0
[   34.790500]  [] ? do_vfs_ioctl+0xb4/0x8b0
[   34.790506]  [] ? mntput_no_expire+0x1f/0xf0
[   34.790513]  [] ? compat_sys_ioctl+0x138/0x1640
[   34.790520]  [] ? vfs_stat+0x16/0x20
[   34.790527]  [] ? sys32_stat64+0x1b/0x40
[   34.790533]  [] ? cstar_dispatch+0x7/0x27
[   34.790536] Code: 57 41 56 41 55 41 89 f5 41 54 53 89 d3 48 83 ec 18 e8 6f 33 fb ff 48 85 c0 48 89 45 c8 74 21 4c 8b b0 c0 04 00 00 4d 85 f6 74 0c <45> 8b 8e f8 2b 00 00 45 85 c9 74 18 48 8b 7d c8 e8 25 32 fb ff
[   34.790587] RIP  [] sata_syno_ahci_diskled_set+0x36/0x110
[   34.790593]  RSP 
[   34.790595] CR2: 0000000000002bf9
[   34.790601] ---[ end trace f7f4a862c941b6a3 ]---

[frostiex 0]

nope it is not working after the data scrub. it is quite annoying. I imagine it is not DSM itself. Its prolly more of xpenology. has anyone ever have this problem from the 4.x versions? or jsut starting to appear in the 5.x?

[scoobydoofus 0]

My Microserver Gen8 is arriving on Friday, really looking forward to tinkering with it.

 

Worrying reading that there are potential problems expanding an SHR formatted raid. Has anyone successfully expanded an SHR raid with DSM 5.1?

[Diverge 1]

My Microserver Gen8 is arriving on Friday, really looking forward to tinkering with it.

 

Worrying reading that there are potential problems expanding an SHR formatted raid. Has anyone successfully expanded an SHR raid with DSM 5.1?

 

I'll test SHR next. Right now I am testing Raid 5.

 

I'm starting with a 3 disk array, then adding a 4th disk to expand the array; that part is done. Now it's expanding the volume (had to reboot after expanding array - option was grayed out)... I'll post an update when it's done... it might be a while though.

 

edit: apparently expanding volumes is broken. Sometime when I click button nothing happens, other times it says it is expanding, but it's really not.... DSM thinks it is (while never increasing %), but

cat /proc/mdstat

says otherwise.

Edited February 11, 2015 by Guest

[cell123 0]

Yes please post your result, thanks.

[networker 0]

I've been running a SHR with 4 x 4TB disks with DSM 5.1 and tried to expand it with a fifths 4 TB disk. The DSM told me that the SHR ist expandable and when I started the expansion it started working for about 30 hours. At the end the DSM told me, that the expansion has been finished well and the SHR had all 5 disks included. Unfortunately the total diskspace shown by the DSM was the same as with the 4 disk SHR before!

 

So I tried to reboot the system and when restarting, the DSM crashed (DSM didn't boot up and in the Synology Assistant it was shown as "Installable"). I switched off the system completely and restarted it again. Now the DSM booted up completely and the SHR was shown with the status "normal" including only 4 disks and telling me that is would be expandable with the fifths disk. Ok I thought and I tried it again to expand the SHR. But this time the expansion was just running for a few seconds and then stopping without a message.

The next step I did was to downsize the DSM to Version 5.0 by resetting all configuration data but keeping the SHR and the data. Once finished with the downgrade, the DSM stepped into the alarm-mode with the first boot up, showing me that I have a broken 5-disk SHR!!!

So I started the repair and after running many hours again, the DSM finished with a working 5-disk SHR, showing up all the diskspace you would expect by a 5x4TB SHR!

 

The result for me is, that the DSM 5.1 had expanded the 4-disk SHR to a 5-disk SHR on data-basis but something went wrong on the configuration basis (the data is distributed to 5-disks as it should be on a 5 disk SHR, but the config data of the DSM says, it is a well working 4 disk SHR) - very dangerous for your data! The interesting thing is, that DSM 5.0 does recognize this error and is able to correct it.

 

I think if you have a "live-system" running with importnat data on it, you shouldn't use DSM 5.1 at the moment!

[iormangund 0]

Tested and also had the same issue with 5.1-5022 SHR. Interestingly the disk group would expand, just the volume group that wouldn't.

[forcefullpower 0]

I get the following when trying to expanded with the failure.

 

Feb 11 10:09:49 XPEnology kernel: [46898.661388] CE: hpet increased min_delta_ns to 229090 nsec

Feb 11 10:09:49 XPEnology kernel: [46898.701357] CE: hpet increased min_delta_ns to 343635 nsec

Feb 11 10:09:55 XPEnology kernel: [46905.213336] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028

Feb 11 10:09:55 XPEnology kernel: [46905.213342] IP: [] add_new_gdb+0x25/0x470

Feb 11 10:09:55 XPEnology kernel: [46905.213349] PGD 2142a5067 PUD 1fe9d3067 PMD 0

Feb 11 10:09:55 XPEnology kernel: [46905.213353] Oops: 0000 [#2] SMP

Feb 11 10:09:55 XPEnology kernel: [46905.213356] CPU 0

Feb 11 10:09:55 XPEnology kernel: [46905.213357] Modules linked in: cifs udf isofs loop nfsd exportfs rpcsec_gss_krb5 usbhid hid usblp usb_storage bromolow_synobios(P) adt7475 i2c_i801 btrfs synoacl_vfs(P) zlib_deflate hfsplus md4 hmac tn40xx(O) i2c_algo_bit fuse vfat fat chainiv cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor cpufreq_stats freq_table dm_snapshot crc_itu_t quota_v2 quota_tree psnap p8022 llc sit tunnel4 etxhci_hcd xhci_hcd ehci_hcd uhci_hcd ohci_hcd usbcore usb_common mvsas arcmsr megaraid_sas megaraid_mbox megaraid_mm mpt2sas mptsas mptspi mptscsih mptbase scsi_transport_spi scsi_wait_scan sg ata_piix sata_uli sata_svw sata_qstor sata_sis pata_sis stex sata_sx4 sata_promise sata_nv sata_via sata_sil pdc_adma iscsi_tcp libiscsi_tcp libiscsi enic qlge qlcnic qla3xxx netxen_nic cnic ipv6 bnx2x be2net sis900 sis190 atl1e(O) atl1c atl2(O) atl1(O) alx(O) sky2 skge via_velocity crc_ccitt via_rhine r8101 r8168 r8169 8139too 8139cp tg3 broadcom libphy bnx2 ssb(O) uio forcedeth ixgbe ixgb igb ioatdma e1000e e1000 e100 dca pcnet32 amd8111e mdio mii container thermal_sys compat(O) cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic libcrc32c crc32c eseqiv krng ansi_cprng cts rng aes_generic md5 cbc cryptomgr pcompress aead crypto_hash crypto_blkcipher crypto_wq crypto_algapi [last unloaded: i2c_i801]

Feb 11 10:09:55 XPEnology kernel: [46905.213438]

Feb 11 10:09:55 XPEnology kernel: [46905.213440] Pid: 9885, comm: resize2fs Tainted: P D O 3.2.40 #1 HP Synoden

Feb 11 10:09:55 XPEnology kernel: [46905.213444] RIP: 0010:[] [] add_new_gdb+0x25/0x470

Feb 11 10:09:55 XPEnology kernel: [46905.213448] RSP: 0018:ffff88021eb8db58 EFLAGS: 00010282

Feb 11 10:09:55 XPEnology kernel: [46905.213450] RAX: 0000000000000196 RBX: 0000000000006590 RCX: ffff880213e6dc00

Feb 11 10:09:55 XPEnology kernel: [46905.213452] RDX: 0000000000006580 RSI: 0000000000000000 RDI: ffff8801eab38870

Feb 11 10:09:55 XPEnology kernel: [46905.213454] RBP: ffff88021eb8dbe8 R08: 6010000000000000 R09: 0000000000000000

Feb 11 10:09:55 XPEnology kernel: [46905.213456] R10: fdce9803aa184c02 R11: ffff8800daec4540 R12: ffff880213e6dc00

Feb 11 10:09:55 XPEnology kernel: [46905.213458] R13: 0000000000006580 R14: 0000000000000000 R15: 0000000000000000

Feb 11 10:09:55 XPEnology kernel: [46905.213461] FS: 00000000006fc880(0063) GS:ffff88021fc00000(0000) knlGS:00000000f75c0b40

Feb 11 10:09:55 XPEnology kernel: [46905.213463] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b

Feb 11 10:09:55 XPEnology kernel: [46905.213465] CR2: 0000000000000028 CR3: 00000002144f5000 CR4: 00000000000006f0

Feb 11 10:09:55 XPEnology kernel: [46905.213467] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

Feb 11 10:09:55 XPEnology kernel: [46905.213469] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

Feb 11 10:09:55 XPEnology kernel: [46905.213471] Process resize2fs (pid: 9885, threadinfo ffff88021eb8c000, task ffff8801fe8b8cf0)

Feb 11 10:09:55 XPEnology kernel: [46905.213473] Stack:

Feb 11 10:09:55 XPEnology kernel: [46905.213474] ffff880214d69800 ffff8801ea80b588 ffff8801eab38870 ffffffff8161b590

Feb 11 10:09:55 XPEnology kernel: [46905.213478] ffff8801ea80b588 0000000000000000 ffff88021eb8dba8 ffffffff8119ff86

Feb 11 10:09:55 XPEnology kernel: [46905.213481] ffff8801eab38870 ffff880213688130 ffff88021eb8dbe8 ffffffff81185b98

Feb 11 10:09:55 XPEnology kernel: [46905.213485] Call Trace:

Feb 11 10:09:55 XPEnology kernel: [46905.213490] [] ? jbd2_journal_get_write_access+0x36/0x50

Feb 11 10:09:55 XPEnology kernel: [46905.213494] [] ? __ext4_journal_get_write_access+0x38/0x80

Feb 11 10:09:55 XPEnology kernel: [46905.213497] [] ext4_flex_group_add+0x57e/0xd00

Feb 11 10:09:55 XPEnology kernel: [46905.213500] [] ext4_resize_fs+0x662/0x8f0

Feb 11 10:09:55 XPEnology kernel: [46905.213504] [] ? do_last+0x538/0xaa0

Feb 11 10:09:55 XPEnology kernel: [46905.213508] [] ? __mnt_want_write+0x30/0x50

Feb 11 10:09:55 XPEnology kernel: [46905.213511] [] ext4_ioctl+0x290/0xaa0

Feb 11 10:09:55 XPEnology kernel: [46905.213515] [] do_vfs_ioctl+0xb4/0x8b0

Feb 11 10:09:55 XPEnology kernel: [46905.213518] [] ? putname+0x2e/0x40

Feb 11 10:09:55 XPEnology kernel: [46905.213521] [] ? do_sys_open+0x164/0x1d0

Feb 11 10:09:55 XPEnology kernel: [46905.213524] [] sys_ioctl+0x99/0xa0

Feb 11 10:09:55 XPEnology kernel: [46905.213528] [] system_call_fastpath+0x16/0x1b

Feb 11 10:09:55 XPEnology kernel: [46905.213530] Code: 84 00 00 00 00 00 55 48 89 e5 48 81 ec 90 00 00 00 4c 89 6d e8 4c 89 75 f0 41 89 d5 48 89 5d d8 4c 89 65 e0 49 89 f6 4c 89 7d f8 <4c> 8b 7e 28 48 89 7d 88 49 8b 8f 40 03 00 00 48 8b 41 68 48 89

Feb 11 10:09:55 XPEnology kernel: [46905.213553] RIP [] add_new_gdb+0x25/0x470

Feb 11 10:09:55 XPEnology kernel: [46905.213556] RSP

Feb 11 10:09:55 XPEnology kernel: [46905.213557] CR2: 0000000000000028

Feb 11 10:09:55 XPEnology kernel: [46905.213560] ---[ end trace 29970c5af123040e ]---

Feb 11 10:09:55 XPEnology volumehandler.cgi: (fs_vol_expand.c)ExtFSExpand(88):Failed to '/sbin/resize2fs -fpF /dev/vg1/volume_1 > /dev/null 2>&1', WEXITSTATUS® = 137

Feb 11 10:09:56 XPEnology volumehandler.cgi: volume_manage_with_temp_dev.c:279 Failed to expand file system on /dev/vg1/volume_1

Feb 11 10:09:56 XPEnology volumehandler.cgi: volume_lib.cpp:1035 Failed to expand file system on /dev/vg1/volume_1

Feb 11 10:09:56 XPEnology volumehandler.cgi: volumehandler.cpp:1574 failed to expand unallocated file system: /volume1

Feb 11 10:10:04 XPEnology synostoraged: hotspare_log_repair_err.c:29 [iNFO] space [/dev/vg1/volume_1] is not degrade, skip repairing with spare disks

 

When I try again the system gives the following message with the interface saying its hanging.

 

Feb 11 10:10:24 XPEnology kernel: [46933.596039] CE: hpet increased min_delta_ns to 515452 nsec

Feb 11 10:10:24 XPEnology kernel: [46933.596039] CE: hpet increased min_delta_ns to 773178 nsec

Feb 11 10:10:26 XPEnology kernel: [46933.940955] CE: hpet increased min_delta_ns to 1000000 nsec

Feb 11 10:10:26 XPEnology kernel: [46934.157536] CE: Reprogramming failure. Giving up

 

Here is the output from mdstat which shows its not even started the expansion

 

md3 : active raid5 sdf6[5] sda6[0] sdd6[3] sdc6[2] sdb6[1]

1953467136 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [uUUUU]

bitmap: 0/4 pages [0KB], 65536KB chunk

 

md2 : active raid5 sde5[7] sdf5[6] sda5[0] sdd5[3] sdc5[2] sdb5[1]

2417776320 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [uUUUUU]

 

md1 : active raid1 sde2[4] sdf2[5] sda2[0] sdb2[1] sdc2[2] sdd2[3]

2097088 blocks [12/6] [uUUUUU______]

bitmap: 0/1 pages [0KB], 65536KB chunk

 

md0 : active raid1 sde1[5] sdf1[1] sda1[0] sdb1[2] sdc1[3] sdd1[4]

2490176 blocks [12/6] [uUUUUU______]

bitmap: 1/1 pages [4KB], 65536KB chunk

 

unused devices:

[sancome 0]

try to modify /etc/synoinfo.conf file, and change "supportraidgroup=no" to "yes", then report.

If anyone want to test, please contact me, i will email the test img to you.

sancome(AT)nanoboot.eu.org

Edited February 14, 2015 by Guest

[Diverge 1]

try to modify /etc/synoinfo.conf file, and change "supportraidgroup=no" to "yes", then report.

If anyone want to test, please contact me, sancome(AT)nanoboot.eu.org

 

I'll try after my current test of expanding SHR array. It added disk to array, but didn't expand and option was grayed out. Just have to reboot and then check option and it will likely be clickable.. but my guess is will fail at expanding.

 

Edit: will be a day or 2 until I get back to this. Currently doing tests to get Asrock to fix bios issue w/ PCIe SSD for E3C224D4I-14S motherboard (ESXI won't detect drive, but will boot preintalled OS... but once booted, no access to drive - works fine on Intel system).

Edited February 12, 2015 by Guest

[rosiste 0]

Sorry I can't test it now, because I recreated volumes from scratch and copy backuped data back to return borrowed disks to friend...

[cell123 0]

So, it sounds like SHR could cause the problem, if only do JOBD, expand disk could be ok?

[stuhad 0]

I attempted to edit the synoinfo.conf with vi, I restarted the NAS, however when I restarted it reverted back to:

supportraidgroup="no"

 

I attempted to expand the volume without restarting but so far am experiencing the same behavior, expansion get's stuck, system becomes unresponsive.

[nickwzy 0]

So, it sounds like SHR could cause the problem, if only do JOBD, expand disk could be ok?

my disks format is JBOD,same issues.

[Diverge 1]

try to modify /etc/synoinfo.conf file, and change "supportraidgroup=no" to "yes", then report.

If anyone want to test, please contact me, i will email the test img to you.

sancome(AT)nanoboot.eu.org

 

 

Changes don't stick... something is writing them back to stock.

 

DS_Test> cat /etc/synoinfo.conf |grep 'supportraidgroup'
supportraidgroup="no"
DS_Test> cat /etc/synoinfo.conf>/etc/synoinfo.conf.bak | sed -i -e 's/supportraidgroup="no"/supportraidgroup="yes"/' /etc/synoinfo.conf
DS_Test> cat /etc/synoinfo.conf |grep 'supportraidgroup'
supportraidgroup="yes"

 

upon reboot:

BusyBox v1.16.1 (2015-01-07 14:56:36 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

DS_Test> cat /etc/synoinfo.conf |grep 'supportraidgroup'
supportraidgroup="no"
DS_Test>

 

backup file there though:

DS_Test> cat /etc/synoinfo.conf.bak |grep 'supportraidgroup'
supportraidgroup="no"
DS_Test>

 

edit: array expansion failed for both raid 5 and SHR.. it adds disk to the array, but doesn't expand the volume.

[sancome 0]

try this test img

https://www.dropbox.com/sh/kpf48fhuy7l1 ... agRd5QrBma