NAS 326 change disks

gyulav
gyulav Posts: 3  Freshman Member
First Comment Friend Collector

Hello!

I have the Zyxel NAS 326 with two 2TB disks installed in basic mode. The disks are full.

I would like to change two 3TB disks.

How to quickly copy/replace this two disks?

2 TB disk "linux dd command" copy to new 3TB disk? After that how expand the disk?

Or i install the two new disks into the NAS, and and format they and copy old disks to new disks via USB?

Best Answers

  • Mijzelf
    Mijzelf Posts: 2,901  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    Answer ✓

    'Basic mode' is without raid1, I suppose? In that case you've got 2 volumes. Then 'dd' is not the way to go. I'd exchange one disk, and create a new volume on the new disk. Then use the filebrowser to copy the data over, or do it from an ssh shell (with cp -a). After you're done, put back the old disk and the empty new one, and repeat.

    Finally put both new disks in. If you had custom shares, you'll have to re-enable them, as they are on another volume now.

  • Mijzelf
    Mijzelf Posts: 2,901  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    Answer ✓

    The "config is on HDD/disk, not in NAS?

    The firmware config is on an internal flashdisk. The configuration of the packages is (mainly?) on the disk, next to the packages.

    On second thought, you will loose your packages. And ZyXEL has shut down their package server. Yet it is possible to install them using a backup I made. If you use dd to copy the disk, I think the packages will remain. But it depends on sequence.

    Background: The nas has a 'system disk', on which the packages and caches are installed. The name of the system disk (actually the first 4 bytes of the raid GUID of the volume) is stored on the flash partition as a symlink (pointing to /i-data/<4 bytes hexcode>, the mountpoint of that volume). As soon as the system disk doesn't exist, and another volume is available on boot, the symlink will be changed, and the other volume will be promoted (and prepared. Existing system volume stuff is reset). So when juggling disks you will almost certain loose your system disk, and so your packages. If you have important stuff, for instance in MySQL, backup it before juggling. Getting that instance of MySQL started again could be not trivial.

All Replies

  • Mijzelf
    Mijzelf Posts: 2,901  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    Answer ✓

    'Basic mode' is without raid1, I suppose? In that case you've got 2 volumes. Then 'dd' is not the way to go. I'd exchange one disk, and create a new volume on the new disk. Then use the filebrowser to copy the data over, or do it from an ssh shell (with cp -a). After you're done, put back the old disk and the empty new one, and repeat.

    Finally put both new disks in. If you had custom shares, you'll have to re-enable them, as they are on another volume now.

  • gyulav
    gyulav Posts: 3  Freshman Member
    First Comment Friend Collector

    Yes, 'Basic mode' is without raid1.

    I will try it.

    The "config is on HDD/disk, not in NAS?

    Thanks.

  • Mijzelf
    Mijzelf Posts: 2,901  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    Answer ✓

    The "config is on HDD/disk, not in NAS?

    The firmware config is on an internal flashdisk. The configuration of the packages is (mainly?) on the disk, next to the packages.

    On second thought, you will loose your packages. And ZyXEL has shut down their package server. Yet it is possible to install them using a backup I made. If you use dd to copy the disk, I think the packages will remain. But it depends on sequence.

    Background: The nas has a 'system disk', on which the packages and caches are installed. The name of the system disk (actually the first 4 bytes of the raid GUID of the volume) is stored on the flash partition as a symlink (pointing to /i-data/<4 bytes hexcode>, the mountpoint of that volume). As soon as the system disk doesn't exist, and another volume is available on boot, the symlink will be changed, and the other volume will be promoted (and prepared. Existing system volume stuff is reset). So when juggling disks you will almost certain loose your system disk, and so your packages. If you have important stuff, for instance in MySQL, backup it before juggling. Getting that instance of MySQL started again could be not trivial.

Consumer Product Help Center