frameworker  Freshman Member

... successfully done. Now I could increase the capacity up to 4TB using the unused space from the manage tool within the GUI, estimated repair time >80 hours (!!) .......

That have worked! </code><code>mdadm --zero-superblock /dev/sda3 Reboot...~ # cat /proc/mdstat<br>Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] <br>md2 : active raid1 sdb3[6] sdd3[3] sde3[4]<br> 972631040 blocks super 1.2 [3/3] [UUU]<br> <br>md1 : active raid1 sda2[4] sde2[6] sdd2[5] sdb2[7]<br>…

Seems ok: ~ # mdadm --examine /dev/sda3<br>/dev/sda3:<br> Magic : a92b4efc<br> Version : 1.2<br> Feature Map : 0x0<br> Array UUID : 90901ca4:d807cf67:b7f8bd07:32031856<br> Name : nas542:2 (local to host nas542)<br> Creation Time : Thu Jun 29 16:20:50 2017<br> Raid Level : raid1<br> Raid Devices : 4<br><br> Avail Dev Size :…

Not successful at all. I could remove the first disk via mdadm, the GUI recognize the free disk, the RAID was shown normally with three disks. But the NAS beeps like if it as degraded. So I reboot them. After that, the entire volume configuration is gone. Bump! I have the backup... the external disk is displayed…

Will try the command line today. After making a complete backup via "Archive" method from the GUI. (taking hours...)It seems there's no way to achieve this task as from the command line. So, non experts in UNIX the Zyxel GUI - regarding at least the 542 model - is not user friendly I mean.

Now the RAID1 with four disks are repaired with 1TB entore capacity. I don't understand the internals: ~ # cat /proc/mdstat <br>Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] <br>md2 : active raid1 sdb3[6] sda3[5] sde3[4] sdd3[3]<br> 972631040 blocks super 1.2 [4/4] [UUUU]<br> <br>md1 : active…

No, its just an expanded RAID1 with 1TB capacity:<div></div><pre class="CodeBlock"><code><div>Bay 1 2 3 4<br>hdd TB 1 1 4 4</div>now expand and repair so we have just a RAID 1 with 1TB capacity No I want to remove the two 1TB disks like this:<br> hdd TB x x 4 4<div><br><code><code>Bay 1 2 3 4…

Same phenomen seen on my box. Opened a call, send logfiles and configuration but they cannot recreate this problem. The call was opened several times but they cannot/want help. They want to open a TeamViewer session, but I reject it due to security reasons. I think it's a bug regarding invalid certificates, but I'm not…

@ljnrsi: tnx for the comment, regarding point 1:Can I expand an existing RAID 1 leaving the existing 1TB disks untouched like this way: Current 1TB RAID 1: Slot 1 2 3 4Disk 1 1 x x Planned:Slot 1 2 3 4Disk 1 1 2 2 ... expand the volume to 4x1TB (smallest capacity of disk), that expands the entire volume to 2TB. Or is that…

I seems samba is only be used when making connections to volumes. I've checked this now.Then I looked into httdp.conf and found a module called

Are you sure that samba comes into play when trying to logon?I've added log level = 3 passdb:5 auth:5 to the global section of /etc/samba/smb.conf. After restarting smbd I see nothing. Expecting a lot of data between httpd and possible the samba daemon, but it seems the login process will not use samba?

Looks like this: <div>BusyBox v1.19.4 (2018-05-22 01:24:01 CST) built-in shell (ash)<br>Enter 'help' for a list of built-in commands.<br><br>~ # cd /etc/samba/<br>/etc/samba # ls -l<br>-rw------- 1 root root 430080 Nov 22 14:59 secrets.tdb<br>-rwxr-xr-x 1 root root 3389 Nov 22 14:59 smb.conf<br>-rwxr-xr-x 1 root root 3167…

It's definitively the NAS itself which forget the user&password combination. After login via ssh and tell "reboot", the login works normally. The NAS works with firmware version V5.21(ABAG.0), so there's no update available. Is there no one out there who has the same problem sometimes?