Expanding RAID volume on NAS326 is not working

Options
2

Comments

  • Tukemoni
    Tukemoni Posts: 5  Freshman Member
    Options
    Hi. Thanks for the advices. I manage to edit and save the file, but for some reason I'm not able to login over telnet after "power off" command. Any further help is highly welcome.
  • Tukemoni
    Tukemoni Posts: 5  Freshman Member
    Options
    User mistake as usual. Managed to telnet and got the system to work with expansion. Thank you Mijzelf!
  • Joonas
    Joonas Posts: 1
    Options
    Got it working replacing my 2x4TB drives with two new 2x10TB drives.
    Maybe some steps can be skipped, but for good measure I'm going to show everything I did.

    1. Removed one of the HHD:s from the NAS and inserted a new HDD in it's place. In the admin-panel (//NAS326) I could see the progress. It took roughly 8 hours.
    2. Repeated with second disk. Kept the old disks safe in case of failure.
    3. Enabled SSH (and Telnet just in case) on the NAS using the admin-panel.
    4. Installed Putty.
    5. Inserted NAS IP (without any prefix), Port 22 and Connection type: SSH in Putty. IP can be found in admin-panel --> Control Panel.
    6. Loged in with the admin account in the command window that poped up.
    7. Typed "su" and had to provide admin password again.
    8. Pasted and ran "vi /etc/init.d/rc.shutdown".
    9. Pressed "i" on keyboard.
    10. Looked for "#swapoff" and pasted theses lines after that line:
      /sbin/telnetd
      /bin/sh
    11. Pressed ESC-key and then typed and ran ":wq".
    12. Closed Putty.
    13. Opened Putty once again, using the same IP and Port, but select "Telnet" instead of "SSH" as Connection type. A new command window opened and I had to login again. I propably ran step 7. again.
    14. Pasted and ran "umount /i-data/sysvol"
    15. Pasted and ran "e2fsck -f /dev/md2". Action took a few minutes.
    16. Pasted and ran "resize2fs /dev/md2". This action took a while longer.
    17. Pasted and ran "killall -9 /bin/sh".
    18. Restarted NAS by pressing the physical power button.
    19. Loged in to the admin panel and could confirm resize. Disabled "SSH" and "Telnet" again.
    20. Made 10 cheers for Mijzelf and Gunslinger.


  • Attila76
    Attila76 Posts: 4  Freshman Member
    Options
    Hello Guys!
    Unfortunately the steps written above are not working for my 326. I had 2 pcs 1TB discs (WD10EFRX) in Raid1 in my NAS, and want to change them to bigger ones, and have bought 2 pcs 6 TB (WD red WD60EFAX). The vi editing function can be done, but during telnet the umount is not allowed by system. Can this be because of the new firmware for example (I have the last existing installed approx 1 month ago)? Thanks for your kind help!
  • Mijzelf
    Mijzelf Posts: 2,607  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    I cannot imagine the firmware changed at this point. You were able to find that '#swapoff'?

    What processes are running at that moment? Run 'ps'.
  • Attila76
    Attila76 Posts: 4  Freshman Member
    Options
    Dear Mijzelf,
    It was done as it was in the comment of Joonas, found swapoff also, entered the mentioned things.
    ps was like this:
    PID USER       VSZ STAT COMMAND
        1 root      2648 S    {init} /bin/sh -x /init
        2 root         0 SW   [kthreadd]
        3 root         0 SW   [ksoftirqd/0]
        5 root         0 SW<  [kworker/0:0H]
        7 root         0 SW<  [khelper]
        8 root         0 SW   [kdevtmpfs]
      260 root         0 SW<  [writeback]
      262 root         0 SW<  [bioset]
      264 root         0 SW<  [kblockd]
      265 root         0 SW<  [button controll]
      266 root         0 SW<  [mcu controller]
      278 root         0 SW<  [ata_sff]
      288 root         0 SW   [khubd]
      296 root         0 SW<  [md]
      305 root         0 SW<  [cfg80211]
      391 root         0 SW<  [rpciod]
      396 root         0 SW   [kswapd0]
      397 root         0 SW   [fsnotify_mark]
      398 root         0 SW<  [nfsiod]
      399 root         0 SW<  [cifsiod]
      401 root         0 SW<  [bioset]
      403 root         0 SW<  [crypto]
      418 root         0 SW   [ocf_0]
      419 root         0 SW   [ocf_ret_0]
     1003 root         0 SW<  [harddrive_hdd]
     1015 root         0 SW   [scsi_eh_0]
     1018 root         0 SW   [scsi_eh_1]
     1063 root         0 SW   [spi0]
     1118 root         0 SW<  [kpsmoused]
     1135 root         0 SW<  [kcryptd]
     1154 root         0 SW<  [deferwq]
     1300 root      2648 S    {linuxrc} init
     1333 root         0 SW<  [kworker/0:1H]
     1379 root         0 SW   [ubi_bgt4d]
     1437 root         0 SW<  [bioset]
     1438 root         0 SW   [md0_raid1]
     1449 root         0 SW<  [bioset]
     1450 root         0 SW   [md1_raid1]
     1529 root         0 SW   [jbd2/md0-8]
     1530 root         0 SW<  [ext4-dio-unwrit]
     1553 root         0 SW<  [loop0]
     1554 root         0 SW<  [ext4-dio-unwrit]
     1573 root         0 SW   [ubi_bgt2d]
     1577 root         0 SW   [ubifs_bgt2_0]
     1622 root      3696 S    /usr/sbin/zylogd
     1632 root      6000 S    /usr/sbin/uamd
     1642 root      3808 S N  /usr/sbin/cupsd
     1669 root      133m S    python /usr/local/apache/web_framework/main_wsgi.pyc
     1838 root         0 SW<  [bioset]
     1839 root         0 SW   [md2_raid1]
     1868 root         0 SW   [jbd2/md2-8]
     1869 root         0 SW<  [ext4-dio-unwrit]
     1950 root      106m S N  /usr/sbin/dservice
     2005 root      1828 S N  /usr/local/dmsf/binary/twonkystarter -appdata /i-dat
     2008 root     20652 S N  /usr/local/dmsf/binary/twonkyserver -appdata /i-data
     2058 root      2648 S    /bin/sh -c /usr/sbin/zylogger -r
     2059 root      3368 S    /usr/sbin/syslog-ng
     2062 root      3692 S    /usr/sbin/zylogger -r
     2571 root     20700 S N  pure-ftpd (SERVER)
     2609 root      9880 S    /i-data/.system/zy-pkgs/pkg_httpd -f /etc/pkg_servic
     2803 root      136m S    {transmission-da} /i-data/c590a559/.PKG/Transmission
     2816 nobody   11452 S    /i-data/.system/zy-pkgs/pkg_httpd -f /etc/pkg_servic
     2817 nobody   11452 S    /i-data/.system/zy-pkgs/pkg_httpd -f /etc/pkg_servic
     2910 root      2648 S    {xmpp_client_mon} /bin/sh /i-data/c590a559/.PKG/myZy
     3024 root     12108 S N  {zyxel_thumb_cre} /i-data/c590a559/.PKG/myZyXELcloud
     3064 root      5264 S    {zyxel_file_moni} /i-data/c590a559/.PKG/myZyXELcloud
     3068 root     25272 S N  /usr/sbin/smbd -D
     3075 root     25280 S N  /usr/sbin/smbd -D
     3076 root     17236 S N  /usr/sbin/nmbd -D
     3080 root     20340 S <  /usr/sbin/nsuagent
     3135 root      2680 S N  avahi-daemon: running [NAS.local]
     3184 root      1684 S    /usr/sbin/myhotplug
     3189 root      1684 S N  /usr/local/btn/do_btncpy
     3219 root      1752 S    /usr/sbin/hd-idle -i 1800
     3286 root      4152 S N  /usr/sbin/netatalk -F /etc/netatalk/afp.conf
     3345 root      5908 S N  /usr/sbin/afpd -d -F /etc/netatalk/afp.conf
     3350 root      4312 S N  /usr/sbin/cnid_metad -d -F /etc/netatalk/afp.conf
     3585 root     17656 S    python /usr/local/apache/web_framework/job_queue_dae
     3588 root      2788 S N  /usr/sbin/app_wd
     3596 root      1764 S N  /bin/lld2d egiga0
     3653 root     10424 S    /sbin/DAV_httpd -f /etc/service_conf/httpd_dav.conf
     3690 root      3664 S    zysync --daemon --config /etc/zysyncd.conf --log-fil
     3716 root      3780 S    stunnel /etc/stunneld.conf
     3747 root     12044 S    /sbin/DAV_httpd -f /etc/service_conf/httpd_dav.conf
     3748 root     12044 S    /sbin/DAV_httpd -f /etc/service_conf/httpd_dav.conf
     3779 root         0 SW<  [target_completi]
     3780 root         0 SW<  [tmr-rd_mcp]
     3803 root         0 SW   [iscsi_ttx]
     3804 root         0 SW   [iscsi_trx]
     3805 root         0 SW   [iscsi_ttx]
     3806 root         0 SW   [iscsi_trx]
     3807 root         0 SW   [iscsi_ttx]
     3808 root         0 SW   [iscsi_trx]
     3809 root         0 SW   [iscsi_ttx]
     3810 root         0 SW   [iscsi_trx]
     3838 root      1680 S    /sbin/ipnotify -d -s -r /sbin/ipnotify_exec.sh
     3899 root      106m S N  python /usr/local/fileye/fileye.pyc
     3908 root      2648 S    /bin/ifplugd -a -p -q -t3 -d0 -u0 -i egiga0 -r /sbin
     3929 root      2008 S    /sbin/mdadm --monitor -p /usr/sbin/mdadmstatuslog.sh
     3996 root      9892 S N  /usr/sbin/httpd -f /etc/service_conf/httpd.conf
     4045 root      2880 S    {zyxel_enet_brid} /i-data/c590a559/.PKG/myZyXELcloud
     4053 root      2648 S    {linuxrc} init
     4654 root     15564 S    {zyxel_xmpp_clie} /i-data/c590a559/.PKG/myZyXELcloud
     7424 nobody   22092 S N  /usr/sbin/httpd -f /etc/service_conf/httpd.conf
     7497 nobody   22348 S N  /usr/sbin/httpd -f /etc/service_conf/httpd.conf
     7498 nobody   22092 S N  /usr/sbin/httpd -f /etc/service_conf/httpd.conf
     7515 nobody   22096 S N  /usr/sbin/httpd -f /etc/service_conf/httpd.conf
     7726 nobody   11540 S N  /usr/sbin/httpd -f /etc/service_conf/httpd.conf
     7769 root         0 SW   [kworker/u2:1]
     7804 root      2648 S    /sbin/telnetd
     7807 root      4592 S    /sbin/sshd -f /etc/ssh/sshd_config
     7904 root         0 SW   [kworker/u2:2]
     8831 root      4592 S    {sshd} sshd: admin@pts/0
     8854 admin     2760 S    -sh
     8866 root      2760 S    sh
     8895 root         0 Z N  [sh]
     8962 root      2516 S    sleep 10
     8979 root      2760 R    ps
     9349 root      5280 S N  /usr/bin/schedule_controller
     9350 root      1544 S N  /usr/bin/timer_source
    13275 root         0 SW   [kworker/0:2]
    20199 root         0 SW   [kworker/0:0]
    27026 root     25604 S N  /usr/sbin/smbd -D
    27435 root         0 SW   [kworker/u2:0]
    27699 root      2756 S N  /sbin/crond -L /dev/null

    During the umount I have the following message:
    ~ # umount /i-data/sysvol
    umount: /i-data/c590a559: target is busy
            (In some cases useful info about processes that
             use the device is found by lsof(8) or fuser(1).)

  • Mijzelf
    Mijzelf Posts: 2,607  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    You have lots of daemons still running. Joonas list has one fatal flaw. After point 11 'enter :wq' you should run 'poweroff' to initiate the shutdown.
  • Attila76
    Attila76 Posts: 4  Freshman Member
    Options
    Dear Mijzelf,
    Thanks!
    As I don't know too much about Linux, may I ask you, what do you mean "After point 11 'enter :wq' you should run 'poweroff' to initiate the shutdown." As I understand: after exiting the vi, should I run the "poweroff" function? Sorry to ask you stupid things.

  • Mijzelf
    Mijzelf Posts: 2,607  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    The script /etc/init.d/rc.shutdown is used by the firmware to stop all processes and unmount the data partitions before powering off or restarting the box. What we do is putting some extra code in that script to get telnet access after the script has cleaned up the air. The ':wq' command exits vi, so that is the moment the script is prepared.
    Now you have to shutdown the box to get the script running, which can be done by executing 'poweroff', or by the webinterface.

  • Attila76
    Attila76 Posts: 4  Freshman Member
    Options
    Dear Mijzelf,
    It was running, thanks!
    Attila

Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）